** Changed in: maas (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1349857
Title:
maas-common fails to set up symbolic link to
Still broken in 16.04 as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-snmp in Ubuntu.
https://bugs.launchpad.net/bugs/1246347
Title:
Lots of "error on subcontainer ‘ia_addr’ insert (-1)" reports in
/var/log/syslog
To
Hi Cam,
On our hosts, 4 physical interfaces and then a bunch of bonds and
bridges taking total up to 12 entries in /etc/network/interfaces . So
contention certainly seems plausible?
My guests have actually gone back to working normally, so I likely have
mis-attributed an unrelated problem that
This fix is causing problems on Ubuntu 12.04 for me; for both KVM hosts
and KVM guests. I see a message like
lockfile creation failed: exceeded maximum number of lock attempts
On my hosts, it delays boot finishing for several minutes; while some of
my guests just never become network accessible.
** Package changed: systemd (Ubuntu) = autofs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1475990
Title:
autofs service fails to connect to upstart
To manage
Also on Raspberry Pi 2 with irqbalanxe 1.0.6-3ubuntu1 (vivid). It was
using 270MB, I've now disabled the service.
--
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/1247107
Title:
LP: #1408478 for more information.)
Nathan
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1410195
Title:
Ctrl+Alt+F7 bypasses
For those that are winding up at this bug report from searches looking
to resolve the problem - regardless of platform, here's a quick fix:
* Move the keys out of ~/.ssh
* gnome-keyring-daemon -r -d
It's certainly not an actual fix, but will at least resolve the
immediate annoyance.
More
If you are working on cleaning up the slapd.postinst script, you may
find some of these related discussions to be interesting and/or
helpful...:
LP: #450645 error during slapd configuration: chown: cannot access
`olcDbDirectory\nolcDbDirectory'
LP: #632051 Improve slapd postinst error message in
** Also affects: ntp via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691672
Importance: Unknown
Status: Unknown
** Also affects: ntp (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691672
Importance: Unknown
Status: Unknown
** No longer affects: ntp
Public bug reported:
the cron.daily/chkrootkit script's current logic for simplifying the
PACKET SNIFFER lines for dhclient and dhcpcd processes needs to be
updated to include the names of current versions of those binaries.
** Affects: chkrootkit (Ubuntu)
Importance: Undecided
We have found that chkrootkit now complains after each reboot, with a message
similar to:
-eth0: PACKET SNIFFER(/sbin/dhclient[895])
+eth0: PACKET SNIFFER(/sbin/dhclient[888])
---[ END: diff -u
*** This bug is a duplicate of bug 571572 ***
https://bugs.launchpad.net/bugs/571572
Sorry about the delayed response. I'll answer your questions in the
other bug.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to krb5 in Ubuntu.
[Replying from a duplicating issue:]
This affects any system using MIT's Kerberos in the 1.10 series prior to
1.10.2-final. To the best of my knowledge, no 1.11 series releases were
affected by this issue, and 1.9 remains affected. The upstream patch [1]
applies cleanly against the Ubuntu 12.04
Public bug reported:
The libkrb5-dev package provided for Precise is missing a critical
bugfix in 1.10.2+ maintenance versions of MIT's Kerberos distribution
which allows reverse DNS service principal name canonicalization to be
disabled. The upstream ticket is here:
This package (0.9.0-0ubuntu3.6) fixes the bug for me.
** 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1227313
Title:
1215391 is fixed now. This can now be pushed to raring-proposed, right?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1227313
Title:
Error parsing lxc-start apparmor profile
To
This package (0.9.0-0ubuntu3.5) fxies the bug for me.
** 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1215391
Title:
Public bug reported:
The lxc-start package reads its apparmor profile from
/proc/$PID/attr/current but does not remove the trailing newline
character. When trying to run an unconfined container, this causes
comparisons with the unconfined string in the source code to fail, and
the apparmor
Just to confirm, the bug wrt the apparmor profile is indeed fixed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1215386
Title:
lxc-start tries to change apparmor profile to
You are correct, the error I'm seeing comes from the fact that I have
this line on the container's fstab:
proc /var/lib/lxc/test/rootfs/proc proc ro,nodev,noexec,nosuid 0 0
That is, I was trying to mount /proc as read-only in the container. This
works for me in 12.04 but not in 13.04.
--
You
I tried it with /etc/apparmor.d/usr.bin.lxc-start both enabled and
disabled, and also with and without lxc.aa_profile = unconfined in the
configuration file and all tests worked fine in the four possible
combinations of those settings.
--
You received this bug notification because you are a
Hi
The issue is still not fixed with the patch. While there's no more
garbage in the buffer that stores the apparmor profile read from /proc,
that data is still terminated by a \n, (ie., the profile is returned
as, eg. unconfined\n instead of unconfined). This causes comparisons
with the
Public bug reported:
When starting a container that has 'lxc.aa_profile = unconfined' on its
configuration file, lxc-start fails with
lxc-start: Read-only file system - failed to change apparmor profile
to unconfined
This happens because the buffer used by lxc-start to read the process'
Public bug reported:
A container with an IPv6 address in its configuration (for example,
'lxc.network.ipv6 = 2001:db8:fedc:abcd::2/80') fails to start with the
error below.
lxc-start 1377083732.942 ERRORlxc_confile - No such file or
directory - invalid ipv6 address:
that the combo of backticks
and redirection to /dev/null means the expression doesn't work as intended...
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609430
Nathan
** Bug watch added: Debian Bug tracker #609430
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609430
--
You received
5.51.6-0.3 is now in quantal, and has a debian/watch file which seems
appropriate.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nmap in Ubuntu.
https://bugs.launchpad.net/bugs/988043
Title:
nmap has no debian/watch file
To
I used Finder via Go - Connect to Server. The path was
smb://server/Documents.
Here are the configuration:
[global]
workgroup = WORKGROUP
server string = %h server
dns proxy = no
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
panic action =
Public bug reported:
Connecting with an OSX client to a server running Precise 12.04 and
samba 3.6.3-2ubuntu2.3 it has the error below.
[2012/06/25 13:35:13.252295, 0] lib/fault.c:47(fault_report)
===
[2012/06/25 13:35:13.252430,
I was able to solve this crash by upgrading to 3.6.5-3ubuntu2 for
quantal.
--
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/1017702
Title:
samba gets INTERNAL ERROR: Signal 11 when a
** Also affects: mysql-5.5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
https://bugs.launchpad.net/bugs/879560
Title:
Logrotate conf file for mysql-server
Seeing this on a new installation of mysql server 5.5 in Precise as
well. I see this on all my ubuntu servers Lucid - Precise-- on some of
the lucid ones i see one mysql.log.old
The largest I see any of them are about ~35KB most in 10-20KB.
mysql-server 5.5.24-0ubuntu0.12.04.1
--
You received
reconfigure the bind9 package. There's another bug open on
that issue: LP: #996088 .
($RET is the return from the db_get function call, which reads the
current value of the bind9/run-resolvconf setting from the debconf
database.)
Nathan
--
You received this bug notification because you are a member
@bkerensa, thanks for the constructive contribution to the
conversation... i discussed this with a couple folks in #ubuntu-server
and one of the Ubuntu php maintainers, and filed this with their
feedback.
@all, i'm well aware that security by obscurity is no solution, but as
noted by Francois in
--
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/1002443
Title:
php5-fpm exposes full ubuntu package version in headers
To manage notifications about this bug go to:
-By
header
nathan@juttenheim:~$ curl -I localhost:8080
HTTP/1.1 200 OK
Server: nginx/1.1.19
Date: Mon, 21 May 2012 18:51:17 GMT
Content-Type: text/html
Connection: keep-alive
Vary: Accept-Encoding
X-Powered-By: PHP/5.3.10-1ubuntu3.1
nathan@juttenheim:~$ sudo sed -i 's/^expose_php = On/expose_php = Off/g
...?
Nathan
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/999725
Title:
broken start-up dependencies for ntp
To manage notifications about this bug go to:
https
to be up, so probably
such a dependency wouldn't be found in a default
installation. But if ntp were converted to Upstart, it
would be much easier for the system administrator to add
that dependency manually)
Nathan
** Summary changed:
- broken
I'm not sure off hand how the decision is made whether to
convert a package such as ntp to Upstart... but I see a
couple other bugs open on the topic: LP #604717 , LP #913379
Sorry, should have written those bug references as: LP: #604717 , LP:
#913379
--
You received this bug notification
*** This bug is a duplicate of bug 604717 ***
https://bugs.launchpad.net/bugs/604717
** This bug has been marked a duplicate of bug 604717
Please convert init script to upstart
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
-nameservers line in your interfaces
stanza in order for DNS resolution to work at all (given that you are
using a static configuration).
So, what toes /etc/resolv.conf contain now? Also, what does
ls -l /etc/resolv.conf show?
Nathan
--
You
itself actually succeeds, but the question is
whether it can resolve the name to an IP number.) How about host
ntp0.dundee.ac.uk?
Nathan
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp
bizarre about the network management.
You mentioned earlier that you had NIS installed on this machine, so I'm
guessing the behavior you are seeing is related to that, but I'm not
personally very familiar with using NIS for host information.
Nathan
--
You
to resolve this NIS v.s. ntpd start-up
dependency issue
Nathan
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/999725
Title:
broken start-up
** Branch unlinked: lp:~nathwill/ubuntu/precise/mysql-5.1/fix-for-879560
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
https://bugs.launchpad.net/bugs/879560
Title:
Logrotate conf file for mysql-server and
the same thing in /etc/ldap.conf for the
libpam-ldap/libpam-nss packages -- or in /etc/nslcd.conf for the nscld
package -- though it seems like you have to spell it TLS_CACERTFILE
instead of TLS_CACERT there.)
Nathan
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
* Loading open-vm-tools modules
FATAL: Module vmhgfs
not found.
FATAL: Module vmsync not found.
FATAL: Module vmblock not found.
FATAL: Module vmxnet not found.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/921389
Title:
open-vm-dkms 2011.07.19-450511-0ubuntu2: open-vm-tools kernel module
failed to build
To manage notifications
Just ran into this issue myself.
Openstack is looking for lun-0, but the device shows up on my Oneiric
install as lun-1.
Have subscribed to bug report...hopefully looking for an update here.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Tested on 10.04 64bit. Before installing the proposed package, guests'
/var/log/dmesg contained this after every time the host was shutdown (either
with shutdown command or by pressing power button):
[7.316252] EXT3-fs: INFO: recovery required on readonly filesystem.
[7.316256] EXT3-fs:
Public bug reported:
fresh install, multiple pop ups about this same error/bug.
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: ntpdate 1:4.2.6.p2+dfsg-1ubuntu5.1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Fri
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/829625
Title:
package ntpdate 1:4.2.6.p2 dfsg-1ubuntu5.1 failed to install/upgrade:
error writing to 'standard output': No such file or
Can we get this fix backported to Lucid as well?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to logwatch in ubuntu.
https://bugs.launchpad.net/bugs/606715
Title:
Logfile defintions wrong after changes to logfile rotation in Ubuntu
Public bug reported:
Binary package hint: puppet
Hello
There's a bug in Puppet 0.25.4 that breaks class-level dependency
handling when using the require function multiple times:
http://projects.puppetlabs.com/issues/3186
The fix is a one-liner:
Sorry, I forgot to report back about the panics. They were caused by a
corrupted XFS filesystem on that server. I haven't had time to do any
further testing with my packages since then - I just hacked the shutdown
command to do what I needed until I have time to thoroughly test them.
--
Should
is installed it
really is too late for the slapd.preinst script dump_databases()
function to be able to export the database)
Thanks.
Nathan
--
upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 (so
slapd aborts with Program version 4.8 doesn't match environment version 4.7
export/import cycle
Nathan
--
upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 (so
slapd aborts with Program version 4.8 doesn't match environment version 4.7
error message)
https://bugs.launchpad.net/bugs/658227
You
Nathan
--
upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 (so
slapd aborts with Program version 4.8 doesn't match environment version 4.7
error message)
https://bugs.launchpad.net/bugs/658227
You received this bug notification because you are a member
-0ubuntu1). That should guarantee that the export
is being run using a pre-2.4.23 version of slapcat, and
avoid touching the database on systems coming up from
post-2.4.23 versions (since the script can't do anything
for those systems anyway).
Nathan
--
upgrade process does not upgrade underlying BDB
with the slapd
package installed to wait until the new package is in
place (in order to avoid having to go through the manual
steps to recover from installing in intermediate package)?
Nathan
--
upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 (so
slapd aborts with Program version
This bug is related to to LP: #632051. The two are triggered by a
different specific issue within the slapd.conf file, and would need
different changes to the postinst script in order to allow it to
actually parse the config file correctly... but I think the patch I
proposed in that bug would
Given that this seems to affect any system upgrading slapd from Lucid to
Maverick, I wonder if it's worth trying to get it added to the Maverick
release notes?
** Summary changed:
- upgrade process does not upgrade underlying BDB format from 4.7 to 4.8
+ upgrade process does not upgrade
** Changed in: openldap (Ubuntu)
Status: Incomplete = Confirmed
--
Dist-Upgrade Karmic-Lucid: Upgrading slapd fails with chown: invalid
argument: `'
https://bugs.launchpad.net/bugs/574474
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Can you look through the /var/log/dist-upgrade/apt-term.log and post the
lines that come from the upgrade of the slapd package?
(I don't know off hand if any of the discussion there applies in the
Lucid-to-Mavick upgrade case, but in case it's helpful I'll point you to
LP #536958, which covers
Ubuntu devs,
I took a quick look at the slapd.posting/slapd.scripts-common files in
the lp:ubuntu/maverick/openldap branch, and also in the Bazaar change
summary for revision 26 (which is the one that includes the note Use
libdb4.8-dev (LP: #572489)), but I don't see any edits to the postinst
Andrew,
As we expected, this shows that the slapd scripts made no attempt to do an
export/import cycle on your database. (When that happened during my
Hardy-Lucid upgrade, I had a Dumping... line, like this:
Preparing to replace slapd 2.4.9-0ubuntu0.8.04.3 (using
I just remembered that the postinst failure I mentioned in my previous
post wasn't triggered by the restart of the slapd daemon, but rather by
another step that the postinst script was attempting to do at that time.
So, in your case, did the apt upgrade/configure cycle appear to complete
FWIW, you might want to mark /etc/default/libvirt-bin as a conffile in the
libvirt packaging.
I think it already is? (dpkg --status libvirt-bin says it is... but I've been
changing things all over the place so I might have confused it)
Also, it might make more sense to package
@John Morrissey - Nice work on getting this working! I hope you don't mind,
I've taken the liberty of packaging all your changes and putting them in a PPA
for easier testing.
One question on omit-kvm-vm-pids from #51, what does the '##*/' mean toward the
end of line 26?
--
Should shut down
/2010-September/031493.html
The thread also covers various situation where otther applications are
hitting the limit; if you (Alex) are lucky perhaps something there will
give you an idea why you are doing so but other sites don't seem to
be
Nathan
--
slapd Too many open files
https
On Mon, Sep 20, 2010 at 14:39:27 -, Nathan Stratton Treadway wrote:
(The very last comment on Debian bug 378261 seems to
indicate that the -DOPENLDAP_FD_SETSIZE=8192 patch
shouldn't actually make any difference in the Lucid
version.)
The bug is currently closed, but just in case new
not reference the /etc/ldapd.conf file,
so the ignoreusers line doesn't affect that test case.)
[For what it's worth, I tested cron using those same
combinations of NSS/PAM resolution libraries but didn't find any
situation where it failed...]
Nathan
On Fri, Sep 24, 2010 at 16:46:25 -, Nathan Stratton Treadway wrote:
As greenmoss found, when I was running with libpam/nss-ldap and
no nscd (and didn't have any of the users in question listed in
the ignoreusers line), my at commands worked for LDAP users
but not for ones defined in /etc
** Summary changed:
- NSS using LDAP+SSL breaks setuid applications like su and sudo
+ NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec,
and atd
--
NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec,
and atd
Alex, have you tried going back to using the stock Lucid version of the
slapd binary (but with the /etc/defaults/slapd ulimit changes)?
(The very last comment on Debian bug 378261 seems to indicate that the
-DOPENLDAP_FD_SETSIZE=8192 patch shouldn't actually make any difference
in the Lucid
I also just ran into this bug in Lucid. Please fix it.
--
Cannot change password on ldap client unless libpam-cracklib also installed
https://bugs.launchpad.net/bugs/329067
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libpam-ldap in
** Summary changed:
- Improve error message in case suffix is incorrect
+ Improve slapd postinst error message in case database directory can't be
determined for a given LDAP suffix
** Description changed:
Bug is due to buggy configuration, but we could have a better error
message. See
** Changed in: openldap (Ubuntu)
Status: Incomplete = Confirmed
--
error during slapd configuration: chown: cannot access
`olcDbDirectory\nolcDbDirectory'
https://bugs.launchpad.net/bugs/450645
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I didn't explain clearly in my earlier comments that it's only the
olcDbDirectory grep that actually causes the chown error here. I added
the .ldif extension to the grep in the get_suffix function only to
keep the two consistent (figuring that if it's true we only care about
files that end in
I wonder if the cause of this chown error is at all related to the one
discussed in bug #450645
If you can post the output of the following commands it might provide
enough information to figure out what exactly is triggering the bug:
$ sudo sh -c ls -l
Ah, okay, you are still using the slapd.conf file, rather than the
slapd.d configuration directory, so your error and the one in #450645
are more like cousins than siblings :)
# Backend specific directives apply to this backend until another
# 'backend' directive occurs
database hdb
suffix
It occured to me that when the postinst script is unable to determine
the database directory associated with a particular suffix (for whatever
reason), simply producing the error message chown: invalid argument:
`' and then aborting isn't very helpful to the system administrator.
Here's a patch
** Patch added: restrict grep searches to files with names ending in .ldif
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/450645/+attachment/1535371/+files/slapd_2.4.21-0ubuntu5.3_postinst.patch
--
error during slapd configuration: chown: cannot access
Ross,
In your case, I believe the error is triggered because you have two different
olcDatabase files that include the same oldSuffix line:
/etc/ldap/slapd.d/cn=config/olcDatabase={1}hdb.ldif:olcSuffix:
dc=cpd,dc=co,dc=uk
/etc/ldap/slapd.d/cn=config/olcDatabase={3}ldap.ldif:olcSuffix:
Is there going to be a back port to Hardy 8.04 LTS?
I have had a serious issue with a Virtual Server where the only access
is via SSHD. This resulted in an errant CPAN update downing the entire
box due to all services started via SSH being oom_adj == -17 and
therefore not being killed when out of
*** This bug is a duplicate of bug 567043 ***
https://bugs.launchpad.net/bugs/567043
hi, I have samed problem.
sudo apt-get install php5-cli php5-common php5-suhosin
Reading package lists... Done
Building dependency tree
Reading state information... Done
php5-cli is already the newest
/openldap-server.html
Nathan
--
openldap sections in ubuntu server guide not updated for packages in karmic
https://bugs.launchpad.net/bugs/463684
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
The DpkgTerminalLog.txt file shows several attempts to upgrade the slapd
package, each with the same result; here is the output from one of them:
=
Setting up slapd (2.4.21-0ubuntu5) ...
Backing up /etc/ldap/slapd.d/ in /var/backups/slapd-2.4.21-0ubuntu4... done.
Starting
Yes, I think that explains why you are getting the chown: invalid
argument `' error
Specifically, when the slapd.postinst parses through the slapd.conf
file, it attempts to process included files... but it assumes that the
database, suffix, and directory lines for a particular database
are
The slapd.postinst script attempts to ensure that various files and
directories have the proper ownerships (and permissions) set. It looks
like it may be having trouble extracting the correct list of directories
in your case.
Can you post the output of the following command (run as root)?
Mathias (or other OpenLDAP developers):
Any reason the grep commands in the get_suffix and get_directory
fuctions shouldn't use olcDatabase*.ldif for the list of files to
search (instead of olcDatabase*, as they currently do)?
--
error during slapd configuration: chown: cannot access
*** This bug is a duplicate of bug 573048 ***
https://bugs.launchpad.net/bugs/573048
(I confirmed that the VarLogDistupgradeApt* and
VarLogDistupgradeMainlog.gz files attached here are exactly the same as
those attached to bug 473048.)
** This bug has been marked a duplicate of bug 573048
Looking through VarLogDistupgradeApttermlog, I see that slapd is
restarted successfully a few times (i.e. when packages such as libc6,
libpam0g, and libssl are upgraded). Then later on these lines appear:
===
Подготовка к замене пакета ldap-utils 2.4.9-0ubuntu0.8.04.3
deutsche Makar,
I'm thinking something may have gone wrong setting the permissions on
the BDB database files.
Can you post the output of the following commands?
ls -ld /var/backups/dc*
ls -l /var/backups/dc*
uname -a
grep ^directory /etc/ldap/slapd.conf*
ls -la path listed in output
Looking more closely at the slapd.postinst script, I see that the word
failed. is actually associated with the Migrating slapd.conf file
message below it, not with the chowning database directory message
above it. So I don't think there's problem with the permissions after
all.
What happens if
Mathias, Thierry: neither of these scripts appear to clean up the
olcAuthzRegexp:
gidNumber=\[\[:digit:]]\+\\\+uidNumber=0,cn=peercred,cn=external,cn=auth
cn=localroot,cn=config'
line that got added to the ${SLAPD_CONF}/cn=config.ldif file by earlier
upgrades. I believe that as long as
?
(If you did have to fix permissions, what exactly did you have to change
to get that part working?)
Nathan
--
slapd 2.4.21-0ubuntu5 corrupts olcDatabase={-1}frontend.ldif with duplicate
olcAccess lines (again)
https://bugs.launchpad.net/bugs/571057
Public bug reported:
As a result of LP: #427842, the initial configuration created upon installation
of slapd 2.4.21-0ubuntu4 and later will include the following ACLs on the
{-1}frontend database:
olcAccess: to dn.base= by * read
olcAccess: to dn.base=cn=subschema by * read
However, when
I have opened Bug #571752 for the issue related to missing ACLs for the
frontend database after upgrading from earlier versions of slapd
(discussed in comments 3 12 here).
(Obviously, the discussion related to the issue mentioned in comment 11
here has moved to Bug #571057.)
--
olcAccess are
*** This bug is a duplicate of bug 427842 ***
https://bugs.launchpad.net/bugs/427842
Note that the fix committed as part of bug #427842 only changed the
settings for new installations, while this bug is actually about
permission problems after migrating from an earlier version of the slapd
1 - 100 of 167 matches
Mail list logo
