Just tried building http://cdimage.ubuntu.com/ubuntu-
server/daily/current/xenial-server-amd64.iso (dated 14th March) and it
still has this bug.
The workaround posted by "andrewsomething" at:
https://github.com/boxcutter/ubuntu/issues/22 still works.
Ian
--
You received this bug no
Thanks for the pointers (I have no idea why I failed to find the gnutls26 bug
yesterday when I looked)
bug 1533230 comment #12
(https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1534230/comments/12)
seems to be the same problem as I'm having.
Using the command:
gnutls-cli -p 636
Public bug reported:
syncrepl gives a "slap_client_connect: URI=ldap://ldaphost.domain.com Error,
ldap_start_tls failed (-11)" error
syncrepl was working perfectly until I upgraded libgnutls26 from
version 2.12.14-5ubuntu3.10
to
version 2.12.14-5ubuntu3.11
This new version of gnutls just
Stephane,
Juju doesn't decide what images to use directly. It uses ubuntu-cloudimg-query
for that.
So this utility will need to be changed. It is in the cloud-image-utils package.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
Stephane, you are right. We can change Juju to use mangle the output of
the cloud-image-query to add "root.tar.xz". Is this guaranteed to always
work for all series / arch? Are there the correct root.tar.xz files on
cloud-image.ubuntu.com ?
--
You received this bug notification because you are a
I've tested 1.0.6-2ubuntu0.14.04.4 for several hours and the problem is
fixed, I can't reproduce this at all.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1469214
Title:
HP
Tested with vivid 1.0.6-3ubuntu1.1, bug is fixed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1469214
Title:
HP ProLiant m400 Server crashes with unhandled level 3 translation
Andrew, I'm still testing it for vivid, will be done in a few hours.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1469214
Title:
HP ProLiant m400 Server crashes with unhandled
Tested with wily 1.0.6-3ubuntu3, bug fixed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1469214
Title:
Hi there,
I need access to the machine to test this, any hints on the machine
name and how to access it would be useful. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
It appears this was fixed with the patch
https://attachments.samba.org/attachment.cgi?id=9882 in Samba bug 10524
(https://bugzilla.samba.org/show_bug.cgi?id=10524) against their 4.1
code base. Is there any chance in getting this applied to the 14.04 LTS
Samba release or the Utopic release
The cause is the following:
- oslo.vmware requires urllib3 and if that requirement is uncapped, it installs
1.11
- no one tends to install over the default system python-requests which is 2.2.1
- for an unexplained reason, urllib3 1.11 and requests 2.2.1 do not mix nor
will they mix (I'm not
*** This bug is a duplicate of bug 1459912 ***
https://bugs.launchpad.net/bugs/1459912
This issue is supposed to be fixed in the latest Juju 1.24 release
https://launchpad.net/juju-core/+milestone/1.24.5
Please re-open if the issue is still observed.
** This bug has been marked a duplicate
@Seth, with the user mode containers - lxc didn't support that when the
local provider feature was first developed. And now we have lxd on the
horizon so we will be re-tooling local provider to use lxd and this will
be delivered for Juju 1.26 around end of January 2016. We don't plan on
making any
What trunk document? Is this actually meant for the Ubuntu or Debian
package(s)?
** Changed in: glance
Status: New = Incomplete
** Also affects: glance (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server
You need to roughly the Installation Guide for Ubuntu because the Debian
one is no longer developed. That will be closer to what you expect than
the RHEL version.
** Changed in: glance
Status: Incomplete = Invalid
** Changed in: glance (Ubuntu)
Status: Incomplete = Invalid
--
You
RE: some of the issues raised in comment 48
- juju-backup shell script uses incorrect quoting method needlessly
Juju no longer uses a shell script for backup. That was a short term
implementation which has now been replaced by server side functionality
written in go.
- The local environment
On 28/07/15 18:26, Christian Reis wrote:
The code which sets up the role lives here:
https://github.com/juju/juju/blame/8da94246468a4da71e62894f7a8a1bbbce112697/mongo/admin.go#L136
The roles we are setting up are:
Roles: []mgo.Role{
mgo.RoleDBAdminAny,
libpam-smbpass 2:4.1.6+dfsg-1ubuntu2.14.04.8 fixes it for me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1257186
Title:
memory leakage messages (no talloc stackframe)
To manage
** Changed in: glance
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to glance in Ubuntu.
https://bugs.launchpad.net/bugs/1447215
Title:
Schema Missing kernel_id, ramdisk_id causes #1447193
To
gollum53 wrote in comment #96:
This bug also affects vsftpd functionality. When SMB password synchronisation
is selected in pam-auth-update, vsftpd can not authenticate users and
segfaults with OOPS message.
I had a quick go at trying to reproduce that to see if I could install a
modified
** Changed in: glance
Status: New = Invalid
** Changed in: nova
Status: New = Invalid
** Changed in: neutron
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-eventlet in Ubuntu.
I'm not sure why unresolved bugs for missed milestones can't be moved to
the next milestone automatically. Less chance of them being ignored that
way!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
I think this should be easy to fix if Canonical can find anyone to
assign the bug to. I managed to fix it locally by following the guide at
https://help.ubuntu.com/community/UpdatingADeb to rebuild the samba
packages from source with the upstream patch applied. For the final
step, I used sudo debi
This is happening still in 14.04.2.
I installed libpam-smbpass:amd64 2:4.1.6+dfsg-1ubuntu2.14.04.7
Whenever I do sudo commands and login in the issue shows up with talloc.
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.2 LTS
Release:
Marked as Fixed Released, does it still occur?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1355813
Title:
Interface MTU management across MAAS/juju
To manage notifications
Public bug reported:
The metadata server listens on 169.254.269.254 but not on any ipv6
address. Thus v6-only machines must be configured with a config-drive.
(There is no v6 address assigned to metadata, but it could easily listen
on the v4-in-v6 address ::169.254.169.254 in the same way.)
**
Public bug reported:
Apt-get fails to upgrade cgmanager package and dies with the following
error:
Preparing to unpack .../cgmanager_0.34-1_amd64.deb ...
/usr/sbin/invoke-rc.d: 580: /usr/sbin/invoke-rc.d: Syntax error: fi
unexpected (expecting then)
dpkg: warning: subprocess old pre-removal
As per the cloud init output log in comment #2, on a precise system, if
you do:
apt-get install cloud-image-utils
apt-decides it needs to remove the cloud-init package (amongst others).
Suggested fix along the lines of:
smoser we can fix that with a packaging change to cloud-init in precise.
For now, I've worked around in Juju by not explicitly installing cloud-
image-utils. Where tis matter, in local providers, I've added a check to
ensure that cloud-image-utils is installed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1328958
Title:
Local provider fails when an unrelated
** Changed in: juju-core
Milestone: 1.22 = 1.21-beta4
** Changed in: juju-core
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: juju-core/1.21
Importance: Undecided = Medium
** Changed in: juju-core/1.21
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core/1.21
Milestone: None = 1.21-beta4
** Changed in: juju-core/1.21
Status: New = In Progress
--
You received
** Changed in: juju-core/1.21
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1328958
Title:
Local provider fails when an unrelated
** Changed in: juju-core
Milestone: None = 1.22
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1328958
Title:
Local provider fails when an unrelated /home/ubuntu directory
** Changed in: juju-core
Status: Triaged = Incomplete
** Changed in: juju-core (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Removing this bug from juju-core as the issue required a cloud init fix.
** No longer affects: juju-core
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1353008
Title:
MAAS
Please change 0.86.x to 0.80.x throughout to avoid confusion.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1381410
Title:
[SRU] 0.86.7 stable update
To manage notifications about
*** This bug is a duplicate of bug 1309207 ***
https://bugs.launchpad.net/bugs/1309207
** This bug has been marked a duplicate of bug 1309207
bad apt proxy config file in deployed nodes
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
*** This bug is a duplicate of bug 1309207 ***
https://bugs.launchpad.net/bugs/1309207
** This bug is no longer a duplicate of bug 1329051
local provider must transform localhost in apt proxy address
** This bug has been marked a duplicate of bug 1309207
bad apt proxy config file in
*** This bug is a duplicate of bug 1329051 ***
https://bugs.launchpad.net/bugs/1329051
** This bug has been marked a duplicate of bug 1329051
local charm deployment fails on git not found due to wrong apt proxy
--
You received this bug notification because you are a member of Ubuntu
** Changed in: juju-core
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1190986
Title:
ERROR Nonce already used
To manage notifications
** Tags added: 14.10
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1329051
Title:
local charm deployment fails on git not found due to wrong apt proxy
To manage notifications
** Changed in: juju-core
Milestone: None = 1.21-alpha1
** Changed in: juju-core
Milestone: 1.21-alpha1 = 1.20.6
** Changed in: juju-core
Importance: Undecided = High
** Changed in: juju-core
Status: New = Triaged
--
You received this bug notification because you are a member
Seems to me that the issue is not that the MTU isn't being honoured, but
that the MTU should be checked *before* TSO assembly and not *after*.
Assembly should happen outside the VM if the VM has enabled it on the
interface internally, and clearly the incoming segments (not packets, at
this point)
Still doing this with Winbind Version: 2:4.1.6+dfsg-1ubuntu2.14.04.3
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1346825
Title:
Winbind panic
To manage notifications about this
** Also affects: juju-core/1.20
Importance: Undecided
Status: New
** Changed in: juju-core/1.20
Milestone: None = 1.20.2
** Changed in: juju-core/1.20
Importance: Undecided = High
** Changed in: juju-core/1.20
Status: New = In Progress
** Changed in: juju-core
** Changed in: juju-core/1.20
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1318366
Title:
jujud on state server panic misses
** Changed in: juju-core
Assignee: (unassigned) = Nate Finch (natefinch)
** Changed in: juju-core
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
Public bug reported:
Just upgraded from 12.04 to 14.04 and now Winbind is panicking about 10
times an hour, always in the same place.
Backtrace:
0x7f0e7262a98c in __libc_waitpid (pid=29930,
stat_loc=stat_loc@entry=0x7fff82f48d10, options=options@entry=0) at
Winbind Version: 2:4.1.6+dfsg-1ubuntu2.14.04.2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1346825
Title:
Winbind panic
To manage notifications about this bug go to:
Ubuntu Server 14.04 x86-64 up to date as of 2014-07-22.
Samba is working fine - no problem contacting fileshares - just the
panic emails every few minutes.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
The ability to specify a different image stream to allow daily images to
be used query simpleastreams images was added in 1.17.2, but this was
for cloud nodes started by the provider directly in the cloud, not
images fetched by uvt-simplestreams-libvirt as is done when creating a
kvm container.
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core
Importance: Undecided = High
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Milestone: None = next-stable
--
You received this bug notification because you
I can verify that openipmi_2.0.18-0ubuntu7.1 from trusty backports seems to fix
the problem.
tag verification-done
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
It seems the problem is in debian/patches/0006-add-JARs-below-var-to-
class-loader.patch. A patch for this patch is attached.
** Attachment added: patch.txt
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1308284/+attachment/4129244/+files/patch.txt
--
You received this bug
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core
Importance: Undecided = High
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Milestone: None = next-stable
--
You received this bug notification because you
A note from the juju side of the fence - Juju currently just syncs the
latest released image when calling uvt-simplestreams-libvirt. It could
be configured to add a --source arg to get a daily image if required.
But configuration adds complexity so if the released kvm images were
updated more
Can confirm similar behaviour on my XPS M1330 with 14.04. If I suspend
by closing the lid, when I open again, I have no keyboard response.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
I've raised a new bug to track the mongo issue lp:1321025
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1314686
Title:
Please add support for utopic
To manage notifications
The original issue reported in the bug - the inability to generate
tools for utopic - has been fixed. The logs identify a new, separate
issue - the fact that mongo appears to have not started. We would need
to see the mongo logs to determine why that is. I'm closing this bug
again and a new bug
** Also affects: juju-core/1.18
Importance: Undecided
Status: New
** Changed in: juju-core/1.18
Milestone: None = 1.18.4
** Changed in: juju-core/1.18
Importance: Undecided = High
** Changed in: juju-core/1.18
Status: New = Triaged
--
You received this bug notification
** Changed in: juju-core/1.18
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core/1.18
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https
We do need the actual series name and version number in the code. The
reason is that there's validation to ensure that simplestreams metadata
for images and tools is correct, and we need to check that the series
information encoded in the metadata is correct. We read the series info
from
** Changed in: juju-core/1.18
Assignee: Nate Finch (natefinch) = Ian Booth (wallyworld)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1304407
Title:
juju bootstrap defaults
The fallback if there's no ubuntu.csv file is to look at a static map of
known series. utopic isn't there yet. AFAIK, we should only get the
error in this bug if distro-info-data pkg is not installed on the
machine wanting to use the local provider
--
You received this bug notification because
** Changed in: juju-core
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https
This is a patch to the bug. This is extracted from the current openipmi
centos package.
It handles the fact the the IPMI modules may now be built into the
kernel.
** Patch added: Patch to bug
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1304407
Title:
juju bootstrap defaults to i386
To manage
** Branch linked: lp:~wallyworld/juju-core/amd64plz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1304407
Title:
juju bootstrap defaults to i386
To manage notifications about
I am seeing this in 13.10 server.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dovecot imap broken by apparmor policy
To manage notifications about this bug go to:
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1301464
Title:
The mega-watcher for machines does not include
** Branch linked: lp:~wallyworld/juju-core/watcher-address-issues-trunk
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1301464
Title:
The mega-watcher for machines does not
** Branch linked: lp:~wallyworld/juju-core/container-provisioner-
retrywatche-1.18
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1299588
Title:
LXC permission denied issue with
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1299588
Title:
LXC permission denied issue with 1.17.7
To
** Changed in: juju-core
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https
** Branch linked: lp:~wallyworld/juju-core/watcher-address-issues
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1301464
Title:
The mega-watcher for machines does not include
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core
Milestone: None = 1.17.8
** Changed in: juju-core
Status: New = In Progress
** Changed in: juju-core
** Branch linked: lp:~wallyworld/juju-core/container-provisioner-
retrywatcher
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1299588
Title:
LXC permission denied issue with
In case it assists when this bug gets triaged, I've repeated my build
today with Samba 2:4.1.6+dfsg-1 from Jessie and this bug is also not
present in the 4.1.6 release, which includes security fixes over 4.1.5.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
As this bug stops an other application using the Kerberos details stored
in the Samba directory, it is quite a show-stopper for the Trusty
release. Is there anything I can tag this bug with or anyone I should
notify in an attempt to get 4.1.5 pulled from Jessie for the Trusty
release?
--
You
Public bug reported:
To reproduce this bug, carry out the following:
Install a fresh Trust Tahr 14.04 AMD64 development build in a (KVM)
virtual machine as a basic server.
Install the samba (2:4.1.3+dfsg-2ubuntu3) and bind9 packages.
Provision an Active Directory Domain with the following
I've just upgraded Samba to 2:4.1.5+dfsg-1 from the Debian Jessie
repository. This also forced the following updates:
2014-03-10 17:13:00 upgrade python-samba:amd64 2:4.1.3+dfsg-2ubuntu3
2:4.1.5+dfsg-1
2014-03-10 17:13:00 upgrade samba-dsdb-modules:amd64 2:4.1.3+dfsg-2ubuntu3
2:4.1.5+dfsg-1
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Changed in: juju-core
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
The fix was initially developed for 1.17 and backported to 1.16. So
trusty will indeed ship with the fix.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1246320
Title:
Azure
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1129720
Title:
juju instances not including the default
Since some deployments will want the global default group added to Juju
machines and others not, we've decided to make it configurable - the
default is false so existing behaviour is preserved. But deployments
that want to use the default group can do so but changing the config
option to true.
--
** Branch linked: lp:~wallyworld/juju-core/instance-default-secgroup
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1129720
Title:
juju instances not including the default
** Changed in: juju-core
Milestone: None = 1.17.1
** Changed in: juju-core
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core
Status: Triaged = In Progress
** Changed in: juju
Status: Triaged = Won't Fix
--
You received this bug notification
I was testing with devstack, and the latest Folsom of the moment. If
it's not turning up in either case at the moment then apparently it's
gone away - I'll reopen with more detail if I see it again.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I compiled 2.6.7 from the original source and it seems to not refresh
kerberos tickets either.
I have reported this upstream.
See https://bugzilla.samba.org/show_bug.cgi?id=9098
** Bug watch added: Samba Bugzilla #9098
https://bugzilla.samba.org/show_bug.cgi?id=9098
--
You received this
Public bug reported:
winbindd will renew kerberos tickets until they expire, but it seems unable to
refresh them before expiry.
I am using in smb.conf
winbind refresh ticket = true
and have cached_login set for pam_winbind
After 7 days ( the renewal limit on AD kerberos tickets) the ticket
** Patch added: diry hack to fix issue
https://bugs.launchpad.net/bugs/1037055/+attachment/3261981/+files/refresh_ticket.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1037055
** Description changed:
+ winbindd will renew kerberos tickets until they expire, but it seems
+ unable to refresh them before expiry.
- winbindd will renew kerberos tickets until they expire, but it seems unable
to refresh them before expiry.
-
- I am using in smb.conf
+ I have the
Public bug reported:
slapd seems to have random connection failures.
The log files show
Jul 18 14:01:57 simpson slapd[24409]: conn=1387 op=0 do_extended:
protocol version (2) too low
for every connection failure.
The same command will succeed 99% of the time but will fail
occasionally.
The
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1026570
Title:
slapd has random connection failures related to do_extended: protocol
version (2) too low
To manage notifications
Yep
ian@lawrence ~ $ sudo apt-get -f install
[sudo] password for ian:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
nspluginwrapper
Use 'apt-get autoremove' to remove
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1013719
Title:
package php5-cgi 5.3.5-1ubuntu7.8 failed to install/upgrade:
subprocess installed post-installation script returned
Public bug reported:
apt-get upgrade
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: php5-cgi 5.3.5-1ubuntu7.8
ProcVersionSignature: Ubuntu 2.6.38-13.52-generic 2.6.38.8
Uname: Linux 2.6.38-13-generic x86_64
Architecture: amd64
Date: Thu Jun 14 20:56:30 2012
ErrorMessage: subprocess
1 - 100 of 175 matches
Mail list logo
