[Bug 1325468] Re: [systemd] container startup fails with AppArmor
After that fix I can start containers with "lxc.aa_profile = unconfined". With containers using the default profile I still get an error on startup: $ sudo lxc-start -n adt-utopic [sudo] password for martin: lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1; continuing lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1; continuing lxc-start: No such file or directory - failed to change apparmor profile to lxc-container-default lxc-start: invalid sequence number 1. expected 4 lxc-start: failed to spawn 'adt-utopic' lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/hugetlb/lxc/adt-utopic lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/perf_event/lxc/adt-utopic lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/blkio/lxc/adt-utopic lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/net_cls,net_prio/lxc/adt-utopic lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/freezer/lxc/adt-utopic lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/devices/lxc/adt-utopic lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/memory/lxc/adt-utopic lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpu,cpuacct/lxc/adt-utopic lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpuset/lxc/adt-utopic There are no AppArmor denials (or other error messages) in dmesg. -- 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/1325468 Title: [systemd] container startup fails with AppArmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1325468/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1325470] Re: [systemd] error 5 creating /usr/lib/x86_64-linux-gnu/lxc/dev/lxc/console
Ah, turns out this is just fallout from bug 1325468. Apparently that failed startup left the /usr/lib/x86_64-linux-gnu/lxc/dev/ directory on my host system, which then causes this error. After a reboot the directory is gone and (unconfined) container startup works. ** Changed in: lxc (Ubuntu) Importance: Undecided => Wishlist ** Changed in: lxc (Ubuntu) Importance: Wishlist => Low ** Summary changed: - [systemd] error 5 creating /usr/lib/x86_64-linux-gnu/lxc/dev/lxc/console + [systemd] error 5 creating /usr/lib/x86_64-linux-gnu/lxc/dev/lxc/console after failed container startup ** Tags removed: systemd-boot -- 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/1325470 Title: [systemd] error 5 creating /usr/lib/x86_64-linux- gnu/lxc/dev/lxc/console after failed container startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1325470/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1325470] [NEW] [systemd] error 5 creating /usr/lib/x86_64-linux-gnu/lxc/dev/lxc/console
Public bug reported:
LXC containers fail to start up with systemd. After setting up lxcbr0
manually (bug 1312532) and adjusting the AppArmor profile (bug 1325468)
they fail with:
$ sudo strace -fvvs1024 -o /tmp/t lxc-start -n debci
lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1;
continuing
lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1;
continuing
lxc-start: Input/output error - error 5 creating
/usr/lib/x86_64-linux-gnu/lxc/dev/lxc/console
lxc-start: failed to setup the console for 'debci'
lxc-start: failed to setup the container
lxc-start: invalid sequence number 1. expected 2
lxc-start: failed to spawn 'debci'
strace shows:
10421 mkdir("/usr/lib/x86_64-linux-gnu/lxc/dev/lxc", 0755) = -1 EEXIST (File
exists)
10421 unlink("/usr/lib/x86_64-linux-gnu/lxc/dev/console") = -1 ENOENT (No such
file or directory)
10421 creat("/usr/lib/x86_64-linux-gnu/lxc/dev/lxc/console", 0660) = -1 EIO
(Input/output error)
Indeed /usr/lib/x86_64-linux-gnu/lxc/dev/ does not have a "console"
(while my /dev does).
There is no relevant error in dmesg:
[ 1238.586524] device vethLLNW81 entered promiscuous mode
[ 1238.587813] IPv6: ADDRCONF(NETDEV_UP): vethLLNW81: link is not ready
[ 1238.627543] IPv6: ADDRCONF(NETDEV_CHANGE): vethLLNW81: link becomes ready
[ 1238.627671] lxcbr0: port 1(vethLLNW81) entered forwarding state
[ 1238.627712] lxcbr0: port 1(vethLLNW81) entered forwarding state
[ 1238.671822] lxcbr0: port 1(vethLLNW81) entered disabled state
[ 1238.674607] device vethLLNW81 left promiscuous mode
[ 1238.674676] lxcbr0: port 1(vethLLNW81) entered disabled state
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Tags: systemd-boot
** Tags added: systemd-boot
--
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/1325470
Title:
[systemd] error 5 creating /usr/lib/x86_64-linux-
gnu/lxc/dev/lxc/console
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1325470/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1325468] Re: [systemd] container startup fails with AppArmor
This particular issue can be fixed in /etc/apparmor.d/abstractions/lxc /start-container by adding a line mount options in rw, slave, After "sudo /etc/init.d/apparmor reload" that "Failed to make / rslave" error is now gone. It still fails with the next error (Input/output error - error 5 creating /usr/lib/x86_64-linux-gnu/lxc/dev/lxc/console), but this seems to be an unrelated other bug. -- 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/1325468 Title: [systemd] container startup fails with AppArmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1325468/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1325468] [NEW] [systemd] container startup fails with AppArmor
Public bug reported: When booting with systemd, and manually setting up lxcbr0 (bug 1312532), container startup fails with: $ sudo lxc-start -n adt-utopic lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1; continuing lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1; continuing lxc-start: Permission denied - Failed to make / rslave lxc-start: Continuing... lxc-start: Input/output error - error 5 creating /usr/lib/x86_64-linux-gnu/lxc/dev/lxc/console lxc-start: failed to setup the console for 'adt-utopic' lxc-start: failed to setup the container lxc-start: invalid sequence number 1. expected 2 lxc-start: failed to spawn 'adt-utopic' The relevant kernel error: [ 1086.599639] audit: type=1400 audit(1401687485.695:171): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="/usr/bin/lxc-start" name="/" pid=10125 comm="lxc-start" flags="rw, rslave" ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor systemd-boot ** Tags added: apparmor systemd-boot -- 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/1325468 Title: [systemd] container startup fails with AppArmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1325468/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1312532] Re: [systemd] Factorize lxcbr0 setup and use it for all init systems
** Summary changed: - [systemd] Container startup fails on missing lxcbr0 + [systemd] Factorize lxcbr0 setup and use it for all init systems -- 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/1312532 Title: [systemd] Factorize lxcbr0 setup and use it for all init systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1312532/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1278466] Re: [FFe] ceph firefly stable release
This bug was fixed in the package ceph - 0.80.1-0ubuntu1 --- ceph (0.80.1-0ubuntu1) trusty; urgency=medium * New upstream release stable point release (LP: #1278466). ceph (0.80-0ubuntu1) trusty; urgency=medium * New upstream release stable release (LP: #1278466). -- James PageWed, 14 May 2014 11:09:37 -0400 ** Changed in: ceph (Ubuntu Trusty) Status: Fix Committed => Fix Released -- 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/1278466 Title: [FFe] ceph firefly stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1278466/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1278466] Update Released
The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- 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/1278466 Title: [FFe] ceph firefly stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1278466/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1301051] Re: vsftpd will not run on ubuntu 13.10 (Linux 3.11.0-19-generic x86_64)
[Expired for vsftpd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vsftpd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/1301051 Title: vsftpd will not run on ubuntu 13.10 (Linux 3.11.0-19-generic x86_64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1301051/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1276414] Re: Panic or segfault in Samba
[Expired for samba (Ubuntu) because there has been no activity for 60 days.] ** Changed in: samba (Ubuntu) Status: Incomplete => Expired -- 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/1276414 Title: Panic or segfault in Samba To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1276414/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1325454] [NEW] Sync convoy 0.2.1+bzr25-3 (main) from Debian unstable (main)
Public bug reported: Please sync convoy 0.2.1+bzr25-3 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: There are no Ubuntu-specific changes. It was just released and then rebuilt. No patches. Changelog entries since current utopic version 0.2.1+bzr20-0ubuntu2: convoy (0.2.1+bzr25-3) unstable; urgency=low * Add missing autopkgtest dependencies on python-mocker and python- paste. -- Jelmer Vernooij Mon, 26 May 2014 22:03:16 +0200 convoy (0.2.1+bzr25-2) unstable; urgency=medium * Re-add autopkgtest. * Force use of python_distutils now that upstream has added a Makefile. -- Jelmer Vernooij Sun, 25 May 2014 17:50:58 +0200 convoy (0.2.1+bzr25-1) unstable; urgency=medium * Remove autopkgtest. * New upstream snapshot. -- Jelmer Vernooij Sat, 24 May 2014 04:55:54 +0200 convoy (0.2.1+bzr20-2) unstable; urgency=medium * Add autopkgtest. -- Jelmer Vernooij Mon, 21 Apr 2014 16:06:09 +0200 convoy (0.2.1+bzr20-1) unstable; urgency=medium * Upload to Debian unstable. Closes: #744298 * Bump standards version to 3.9.5. -- Jelmer Vernooij Sat, 12 Apr 2014 18:14:58 +0200 ** Affects: convoy (Ubuntu) Importance: Wishlist Status: New ** Changed in: convoy (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to convoy in Ubuntu. https://bugs.launchpad.net/bugs/1325454 Title: Sync convoy 0.2.1+bzr25-3 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/convoy/+bug/1325454/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1325446] Re: Database corrupted during ldapadd
Errors in syslog now when I shut down slapd (having added some entries): Jun 2 03:05:33 fitpc slapd[17448]: daemon: shutdown requested and initiated. Jun 2 03:05:33 fitpc slapd[17448]: slapd shutdown: waiting for 0 operations/tasks to finish Jun 2 03:05:33 fitpc slapd[17448]: bdb(dc=balaam,dc=com): BDB0060 PANIC: fatal region error detected; run recovery Jun 2 03:05:33 fitpc slapd[17448]: message repeated 3 times: [ bdb(dc=balaam,dc=com): BDB0060 PANIC: fatal region error detected; run recovery] Jun 2 03:05:33 fitpc slapd[17448]: bdb_db_close: database "dc=balaam,dc=com": txn_checkpoint failed: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery (-30973). Jun 2 03:05:33 fitpc slapd[17448]: bdb(dc=balaam,dc=com): BDB1581 File handles still open at environment close Jun 2 03:05:33 fitpc slapd[17448]: bdb(dc=balaam,dc=com): BDB1582 Open file handle: /var/lib/ldap/__db.001 Jun 2 03:05:33 fitpc slapd[17448]: bdb(dc=balaam,dc=com): BDB1582 Open file handle: /var/lib/ldap/__db.002 Jun 2 03:05:33 fitpc slapd[17448]: bdb(dc=balaam,dc=com): BDB1582 Open file handle: /var/lib/ldap/__db.003 Jun 2 03:05:33 fitpc slapd[17448]: bdb(dc=balaam,dc=com): BDB1582 Open file handle: /var/lib/ldap/id2entry.bdb Jun 2 03:05:33 fitpc slapd[17448]: bdb(dc=balaam,dc=com): BDB1582 Open file handle: /var/lib/ldap/dn2id.bdb Jun 2 03:05:33 fitpc slapd[17448]: bdb(dc=balaam,dc=com): BDB0060 PANIC: fatal region error detected; run recovery Jun 2 03:05:33 fitpc slapd[17448]: bdb_db_close: database "dc=balaam,dc=com": close failed: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery (-30973) Jun 2 03:05:33 fitpc slapd[17448]: slapd stopped. -- 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/1325446 Title: Database corrupted during ldapadd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1325446/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1325446] Re: Database corrupted during ldapadd
If I use aa-complain to (hopefully) remove any problems caused by
apparmor, I still see the same problem:
$ sudo apt-get purge slapd
$ sudo rm -rf /var/lib/ldap/
$ sudo rm -rf /var/lib/slapd/
$ sudo apt-get install slapd
$ sudo aa-complain /usr/sbin/slapd
Setting /usr/sbin/slapd to complain mode.
$ tail /var/log/syslog
Jun 2 02:39:53 fitpc kernel: [10792.499186] type=1400
audit(1401673193.818:187): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="/usr/sbin/slapd" pid=16686 comm="apparmor_parser"
$ sudo service slapd restart
$ tail /var/log/syslog
Jun 2 02:40:15 fitpc slapd[16652]: daemon: shutdown requested and initiated.
Jun 2 02:40:15 fitpc slapd[16652]: slapd shutdown: waiting for 0
operations/tasks to finish
Jun 2 02:40:15 fitpc slapd[16652]: slapd stopped.
Jun 2 02:40:15 fitpc slapd[16749]: @(#) $OpenLDAP: slapd (Ubuntu) (Mar 17
2014 21:20:08)
$#012#011buildd@aatxe:/build/buildd/openldap-2.4.31/debian/build/servers/slapd
Jun 2 02:40:15 fitpc kernel: [10814.600456] type=1400
audit(1401673215.917:188): apparmor="ALLOWED" operation="open"
profile="/usr/sbin/slapd" name="/usr/share/p11-kit/modules/" pid=16749
comm="slapd" requested_mask="r" denied_mask="r" fsuid=119 ouid=0
Jun 2 02:40:15 fitpc kernel: [10814.600643] type=1400
audit(1401673215.917:189): apparmor="ALLOWED" operation="open"
profile="/usr/sbin/slapd"
name="/usr/share/p11-kit/modules/p11-kit-trust.module" pid=16749 comm="slapd"
requested_mask="r" denied_mask="r" fsuid=119 ouid=0
Jun 2 02:40:15 fitpc kernel: [10814.600916] type=1400
audit(1401673215.917:190): apparmor="ALLOWED" operation="file_mmap"
profile="/usr/sbin/slapd"
name="/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so" pid=16749 comm="slapd"
requested_mask="m" denied_mask="m" fsuid=119 ouid=0
Jun 2 02:40:15 fitpc slapd[16750]: slapd starting
$ sudo ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/ldap/db.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
adding new entry "olcDatabase={1}hdb,cn=config"
modifying entry "olcDatabase={-1}frontend,cn=config"
modifying entry "olcDatabase={0}config,cn=config"
modifying entry "olcDatabase={0}config,cn=config"
andy@fitpc:~$ tail /var/log/syslog
Jun 2 02:40:43 fitpc slapd[16750]: hdb_db_open: database "dc=balaam,dc=com":
unclean shutdown detected; attempting recovery.
--
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/1325446
Title:
Database corrupted during ldapadd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1325446/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1325446] [NEW] Database corrupted during ldapadd
Public bug reported:
When I install slapd I see a complaint about an apparmor denial. When I
try to set up my ldap setup, I see database corruption messages. After
this slapd is unusable.
The same setup (as far as I can see) worked in 12.04.
$ lsb_release -rd
Description:Ubuntu 14.04 LTS
Release:14.04
$ apt-cache policy slapd
slapd:
Installed: 2.4.31-1+nmu2ubuntu8
Candidate: 2.4.31-1+nmu2ubuntu8
Version table:
*** 2.4.31-1+nmu2ubuntu8 0
500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
$ sudo apt-get purge slapd
$ sudo rm -rf /var/lib/ldap/
$ sudo rm -rf /var/lib/slapd/
$ sudo apt-get install slapd
$ tail /var/log/syslog
Jun 2 02:31:10 fitpc slapd[15569]: @(#) $OpenLDAP: slapd (Ubuntu) (Mar 17
2014 21:20:08)
$#012#011buildd@aatxe:/build/buildd/openldap-2.4.31/debian/build/servers/slapd
Jun 2 02:31:10 fitpc kernel: [10269.219731] type=1400
audit(1401672670.552:184): apparmor="DENIED" operation="open"
profile="/usr/sbin/slapd" name="/usr/share/p11-kit/modules/" pid=15569
comm="slapd" requested_mask="r" denied_mask="r" fsuid=119 ouid=0
Jun 2 02:31:10 fitpc slapd[15570]: slapd starting
$ sudo ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/ldap/db.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
adding new entry "olcDatabase={1}hdb,cn=config"
modifying entry "olcDatabase={-1}frontend,cn=config"
modifying entry "olcDatabase={0}config,cn=config"
modifying entry "olcDatabase={0}config,cn=config"
$ tail /var/log/syslog
Jun 2 02:32:28 fitpc slapd[15570]: hdb_db_open: database "dc=balaam,dc=com":
unclean shutdown detected; attempting recovery.
$ cat /etc/ldap/db.ldif
###
# DATABASE SETUP
###
# Create directory database
dn: olcDatabase={1}hdb,cn=config
objectClass: olcDatabaseConfig
objectClass: olcHdbConfig
olcDatabase: {1}hdb
olcDbDirectory: /var/lib/ldap
olcSuffix: dc=balaam,dc=com
olcRootDN: cn=admin,dc=balaam,dc=com
olcRootPW:
olcAccess: {0}to attrs=userPassword,shadowLastChange by
dn="cn=admin,dc=balaam,dc=com" write by anonymous auth by self write by * none
olcAccess: {1}to dn.base="" by * read
olcAccess: {2}to * by dn="cn=admin,dc=balaam,dc=com" write by * read
olcLastMod: TRUE
olcDbCheckpoint: 512 30
olcDbConfig: {0}set_cachesize 0 2097152 0
olcDbConfig: {1}set_lk_max_objects 1500
olcDbConfig: {2}set_lk_max_locks 1500
olcDbConfig: {3}set_lk_max_lockers 1500
olcDbIndex: uid pres,eq
olcDbIndex: cn,sn,mail pres,eq,approx,sub
olcDbIndex: objectClass eq
###
# DEFAULTS MODIFICATION
###
# Some of the defaults need to be modified in order to allow
# remote access to the LDAP config. Otherwise only root
# will have administrative access.
dn: olcDatabase={-1}frontend,cn=config
changetype: modify
delete: olcAccess
dn: olcDatabase={0}config,cn=config
changetype: modify
add: olcRootPW
olcRootPW: {CRYPT}7hzU8RaZxaGi2
dn: olcDatabase={0}config,cn=config
changetype: modify
delete: olcAccess
** Affects: openldap (Ubuntu)
Importance: Undecided
Status: New
--
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/1325446
Title:
Database corrupted during ldapadd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1325446/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1325438] [NEW] Failed to get file from tftp-hpa with samba share
Public bug reported: I have a tftp-hpa server installed under /var/lib/tftpboot. I create a subdirectory and using it to mount a samba share sam@HostA:/var/lib/tftpboot/eco$ cat /etc/default/tftpd-hpa # /etc/default/tftpd-hpa TFTP_USERNAME="ssu" TFTP_DIRECTORY="/var/lib/tftpboot" TFTP_ADDRESS="0.0.0.0:69" TFTP_OPTIONS="--create --secure" sam@HostA:/var/lib/tftpboot$ ll total 24 drwxr-xr-x 8 ssu ssu 4096 Jun 1 11:23 ./ drwxr-xr-x 47 root root 4096 Jun 1 11:17 ../ drwxr-xr-x 2 ssu ssu 4096 Jun 1 11:23 config/ drwxr-xr-x 2 ssu ssu 4096 Jun 1 17:06 eco/ drwxr-xr-x 96 ssu ssu 0 May 23 10:17 oak/ drwxr-xr-x 2 ssu ssu 4096 Jun 1 11:23 pkg/ drwxrwxr-x+ 24 ssu ssu 0 Jun 1 02:00 swap/ drwxr-xr-x 2 ssu ssu 4096 Jun 1 11:23 tmp/ In which oak/ is mounted as "sudo mount //x.x.x.x/Images /var/lib/tftpboot/oak/ -o user=ssu -o uid=ssu -o gid=ssu" If I tftp get file from under oak/, it is always failed, but if I get file from other directory, it will succeed. This setup is working under Ubuntu 10.04 lts, but do not work under 12.04lts or 14.04lts Any idea what happened? ** Affects: tftp-hpa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tftp-hpa in Ubuntu. https://bugs.launchpad.net/bugs/1325438 Title: Failed to get file from tftp-hpa with samba share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1325438/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 908112] Re: #110992 still happens (modules are not loaded)
** Branch linked: lp:ubuntu/ipmitool -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/908112 Title: #110992 still happens (modules are not loaded) To manage notifications about this bug go to: https://bugs.launchpad.net/eilt/+bug/908112/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 908112] Re: #110992 still happens (modules are not loaded)
This bug was fixed in the package ipmitool - 1.8.14-2 --- ipmitool (1.8.14-2) unstable; urgency=medium * patch 115-lib_declarations.patch - lib/kontronoem.c correct declaration of write_fru_area ( Closes: #749913 ) * remove hardening-wrapper from build-Depends * add ipmi* kernel-modules to startup-script ( LP: #908112 ) * add debian/systemd/ipmitool.conf to load ipmi* kernel-modules under systemd * add debian/source/option compression xy / level 9 [ Gerald Turner ] * changes on systemd startup scripts ( Closes: #750003 ) -- Jörg Frings-Fürst Tue, 27 May 2014 14:53:55 +0200 ** Changed in: ipmitool (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/908112 Title: #110992 still happens (modules are not loaded) To manage notifications about this bug go to: https://bugs.launchpad.net/eilt/+bug/908112/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 908112] Re: #110992 still happens (modules are not loaded)
** Branch linked: lp:debian/ipmitool -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/908112 Title: #110992 still happens (modules are not loaded) To manage notifications about this bug go to: https://bugs.launchpad.net/eilt/+bug/908112/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1297224] Re: Improve xen packages and hvm domUs support
Seabios package from version 1.7.5-1 removes the xen support in 128k build, than the seabios build change to 256k is needed for future build on utopic: http://changelogs.ubuntu.com/changelogs/pool/main/s/seabios/seabios_1.7.5-1/changelog -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1297224 Title: Improve xen packages and hvm domUs support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1297224/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1257186] Re: memory leakage messages
"sudo pam-auth-update " did the trick for me. -- 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/1257186 Title: memory leakage messages To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1257186/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1325349] [NEW] logcheck-database: wpa_supplicant rules missing (rules included)
Public bug reported:
please add the following rules:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ wpa_supplicant\[[0-9]+\]: wlan[0-9]:
CTRL-EVENT-SCAN-STARTED$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ wpa_supplicant\[[0-9]+\]: wlan[0-9]: WPA:
Group rekeying completed with ([0-9a-f]{2}:){5}[0-9a-f]{2} \[GTK=(CCMP|TKIP)\]$
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: logcheck-database 1.3.16
ProcVersionSignature: Ubuntu 3.15.0-4.9-generic 3.15.0-rc7
Uname: Linux 3.15.0-4-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.3-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Jun 1 12:39:39 2014
Dependencies:
InstallationDate: Installed on 2014-05-30 (2 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
PackageArchitecture: all
SourcePackage: logcheck
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.logcheck.cracking.d.kernel: [deleted]
modified.conffile..etc.logcheck.cracking.d.rlogind: [deleted]
modified.conffile..etc.logcheck.cracking.d.rsh: [deleted]
modified.conffile..etc.logcheck.cracking.d.smartd: [deleted]
modified.conffile..etc.logcheck.cracking.d.tftpd: [deleted]
modified.conffile..etc.logcheck.cracking.d.uucico: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.bind: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.cron: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.incron: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.logcheck: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.postfix: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.ppp: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.pureftp: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.qpopper: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.squid: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.ssh: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.stunnel: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.sysklogd: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.telnetd: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.tripwire: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.usb: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.acpid: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.amandad: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.amavisd.new: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.anacron: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.anon.proxy: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.apache: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.apcupsd: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.arpwatch: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.asterisk: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.automount: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.bind: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.bluez.utils: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.courier: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.cpqarrayd: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.cpufreqd: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.cron: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.cron.apt: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.cups.lpd: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.cvs.pserver: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.cvsd: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.cyrus: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.dcc: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.ddclient: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.dhclient: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.dhcp: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.dictd: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.dkfilter: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.dkim.filter: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.dnsmasq: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.dovecot: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.dropbear: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.dspam: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.epmd: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.exim4: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.fcron: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.ftpd: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.git.daemon: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.gnu.imap4d: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.gps: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.grinch: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.horde3: [del
[Bug 1323758] Re: Mouse stops working when connected usb-storage-device
** Description changed: I'm running a guest that has Windows 8 Pro (x64) installed. Every time I pass through a usb storage device from the host to the guest, the mouse stops working in the vnc client. When I remove the usb-device the mouse works again. The mouse only stops working when I pass through a usb storage device and then make the vlc viewer (client) inactive by clicking on another program on the local computer (where I'm running the vnc viewer (client)). As long as I keep the vnc viewer active, the mouse works without any problems. But as soon as I make the vnc viewer inactive and then active again, the mouse will no longer work. I have to reboot the guest or remove the usb storage device. I can't find any related problems on the internet, so it may be just me? I hope someone can help me with this. + + EDIT: I posted the extra/new information in comments. But as I know see + it might be wrong and maybe I should've posted them in this bug + description container (by editing)? Please tell me if I did it wrong and + I will change it. Sorry for this misunderstanding. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1323758 Title: Mouse stops working when connected usb-storage-device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1323758/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1247107] Re: Runaway irqbalance consuming CPU and Memory
Seen on several ARM devices (ODROID-X2, Cubieboard1, OLinuXino-A20-MICRO) on Ubuntu 14.04 as well. -- 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: Runaway irqbalance consuming CPU and Memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1247107/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
