[Bug 1503034] Re: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup
The wily-proposed version (5.1.1-1ubuntu2.1) fixed it for me too. Thanks Brian, it's much appreciated. Adam -- 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/1503034 Title: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1503034/+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 1503034] Re: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup
I edited the description in line to make it mostly in line with the SRU wiki. It's hard to provide a test case without having a full ldap client and server configuration, plus an NFS system. I don't have access to the server side configs so I can't provide those. What extra information is necessary to get this into the Wily repository? ** Description changed: I'm running Wily Beta 2, updated to the latest packages in the wily repository, with autofs-ldap using mounts stored in LDAP. On startup systemd immediately puts autofs into a failed state as it segfaults when reading the auto.master. Autofs & autofs-ldap version is 5.1.1-1ubuntu2. The log in journalctl looks like this: Oct 05 15:47:45 autofs[2232]: * Starting automount... Oct 05 15:47:45 automount[2240]: Starting automounter version 5.1.1, master map /etc/auto.master Oct 05 15:47:45 automount[2240]: using kernel protocol version 5.02 Oct 05 15:47:45 automount[2240]: lookup_nss_read_master: reading master file /etc/auto.master Oct 05 15:47:45 automount[2240]: parse_init: parse(sun): init gathered global options: (null) Oct 05 15:47:45 automount[2240]: spawn_mount: mtab link detected, passing -n to mount Oct 05 15:47:45 automount[2240]: spawn_umount: mtab link detected, passing -n to mount Oct 05 15:47:45 automount[2240]: lookup_read_master: lookup(file): read entry /net Oct 05 15:47:45 automount[2240]: lookup_read_master: lookup(file): read entry +dir:/etc/auto.master.d Oct 05 15:47:45 automount[2240]: lookup_nss_read_master: reading master dir /etc/auto.master.d Oct 05 15:47:45 automount[2240]: lookup(dir): dir map /etc/auto.master.d missing or not readable Oct 05 15:47:45 automount[2240]: lookup(file): failed to read included master map dir:/etc/auto.master.d Oct 05 15:47:45 automount[2240]: lookup_read_master: lookup(file): read entry +auto.master Oct 05 15:47:45 automount[2240]: lookup_nss_read_master: reading master files auto.master Oct 05 15:47:45 automount[2240]: parse_init: parse(sun): init gathered global options: (null) Oct 05 15:47:45 automount[2240]: lookup_nss_read_master: reading master ldap auto.master Oct 05 15:47:45 kernel: automount[2240]: segfault at 0 ip 7fb87ade5bcb sp 7ffc30b34550 error 4 in lookup_ldap.so[7fb87adca000+38000] Oct 05 15:47:47 autofs[2232]: ...fail! Oct 05 15:47:47 systemd[1]: autofs.service: Control process exited, code=exited status=1 This occurs whenever the service is started with the line in auto.master which loads the ldap mounts. The line which causes the issue is "+ldap:automountMapName=auto.master.linux,ou=automount,ou=,ou=,o=,dc=,dc=com", and this configuration worked on 14.04, 14.10 and 15.04. + + [Impact] This bug prevents the autofs-ldap module from loading, and + causes it to segfault on startup. The proposed fix allows the module to + load normally. The fix initialises configuration cache before it is + first used (it is the access to the uninitialised cache which causes the + segfault). + + [Test Case] Install the autofs-ldap package and have it read an + automount map from LDAP. The necessary auto.master & ldap.conf + configuration is dependent on the LDAP server that provides the + automount maps. + + [Regression Potential] Given the shipped package does not load at all, + it can't be a regression on the shipped binary. -- 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/1503034 Title: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1503034/+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 1503034] Re: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup
I've been running the autofs-ldap & autofs binaries from 14.04 in 15.10, they work fine. I had different issues with the 14.10 and 15.04 binaries (on their respective releases), which never worked with LDAP, but appeared to hard lock rather than segfault so it was harder to track down. -- 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/1503034 Title: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1503034/+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 1503034] Re: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup
This is the backtrace I got out of apport-cli, but I couldn't figure out where the debug symbols for autofs are. I followed the instructions to add extra debug symbols (https://wiki.ubuntu.com/DebuggingProgramCrash). ** Attachment added: "_usr_sbin_automount.0.crash" https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1503034/+attachment/4486003/+files/_usr_sbin_automount.0.crash -- 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/1503034 Title: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1503034/+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 1503034] [NEW] Autofs 5.1.1-1ubuntu2 crashes with segfault on startup
Public bug reported: I'm running Wily Beta 2, updated to the latest packages in the wily repository, with autofs-ldap using mounts stored in LDAP. On startup systemd immediately puts autofs into a failed state as it segfaults when reading the auto.master. Autofs & autofs-ldap version is 5.1.1-1ubuntu2. The log in journalctl looks like this: Oct 05 15:47:45 autofs[2232]: * Starting automount... Oct 05 15:47:45 automount[2240]: Starting automounter version 5.1.1, master map /etc/auto.master Oct 05 15:47:45 automount[2240]: using kernel protocol version 5.02 Oct 05 15:47:45 automount[2240]: lookup_nss_read_master: reading master file /etc/auto.master Oct 05 15:47:45 automount[2240]: parse_init: parse(sun): init gathered global options: (null) Oct 05 15:47:45 automount[2240]: spawn_mount: mtab link detected, passing -n to mount Oct 05 15:47:45 automount[2240]: spawn_umount: mtab link detected, passing -n to mount Oct 05 15:47:45 automount[2240]: lookup_read_master: lookup(file): read entry /net Oct 05 15:47:45 automount[2240]: lookup_read_master: lookup(file): read entry +dir:/etc/auto.master.d Oct 05 15:47:45 automount[2240]: lookup_nss_read_master: reading master dir /etc/auto.master.d Oct 05 15:47:45 automount[2240]: lookup(dir): dir map /etc/auto.master.d missing or not readable Oct 05 15:47:45 automount[2240]: lookup(file): failed to read included master map dir:/etc/auto.master.d Oct 05 15:47:45 automount[2240]: lookup_read_master: lookup(file): read entry +auto.master Oct 05 15:47:45 automount[2240]: lookup_nss_read_master: reading master files auto.master Oct 05 15:47:45 automount[2240]: parse_init: parse(sun): init gathered global options: (null) Oct 05 15:47:45 automount[2240]: lookup_nss_read_master: reading master ldap auto.master Oct 05 15:47:45 kernel: automount[2240]: segfault at 0 ip 7fb87ade5bcb sp 7ffc30b34550 error 4 in lookup_ldap.so[7fb87adca000+38000] Oct 05 15:47:47 autofs[2232]: ...fail! Oct 05 15:47:47 systemd[1]: autofs.service: Control process exited, code=exited status=1 This occurs whenever the service is started with the line in auto.master which loads the ldap mounts. The line which causes the issue is "+ldap:automountMapName=auto.master.linux,ou=automount,ou=,ou=,o=,dc=,dc=com", and this configuration worked on 14.04, 14.10 and 15.04. ** Affects: autofs (Ubuntu) Importance: Undecided Status: New ** Description changed: I'm running Wily Beta 2, updated to the latest packages in the wily repository, with autofs-ldap using mounts stored in LDAP. On startup systemd immediately puts autofs into a failed state as it segfaults when reading the auto.master. Autofs & autofs-ldap version is 5.1.1-1ubuntu2. The log in journalctl looks like this: Oct 05 15:47:45 autofs[2232]: * Starting automount... Oct 05 15:47:45 automount[2240]: Starting automounter version 5.1.1, master map /etc/auto.master Oct 05 15:47:45 automount[2240]: using kernel protocol version 5.02 Oct 05 15:47:45 automount[2240]: lookup_nss_read_master: reading master file /etc/auto.master Oct 05 15:47:45 automount[2240]: parse_init: parse(sun): init gathered global options: (null) Oct 05 15:47:45 automount[2240]: spawn_mount: mtab link detected, passing -n to mount Oct 05 15:47:45 automount[2240]: spawn_umount: mtab link detected, passing -n to mount Oct 05 15:47:45 automount[2240]: lookup_read_master: lookup(file): read entry /net Oct 05 15:47:45 automount[2240]: lookup_read_master: lookup(file): read entry +dir:/etc/auto.master.d Oct 05 15:47:45 automount[2240]: lookup_nss_read_master: reading master dir /etc/auto.master.d Oct 05 15:47:45 automount[2240]: lookup(dir): dir map /etc/auto.master.d missing or not readable Oct 05 15:47:45 automount[2240]: lookup(file): failed to read included master map dir:/etc/auto.master.d Oct 05 15:47:45 automount[2240]: lookup_read_master: lookup(file): read entry +auto.master Oct 05 15:47:45 automount[2240]: lookup_nss_read_master: reading master files auto.master Oct 05 15:47:45 automount[2240]: parse_init: parse(sun): init gathered global options: (null) Oct 05 15:47:45 automount[2240]: lookup_nss_read_master: reading master ldap auto.master Oct 05 15:47:45 kernel: automount[2240]: segfault at 0 ip 7fb87ade5bcb sp 7ffc30b34550 error 4 in lookup_ldap.so[7fb87adca000+38000] Oct 05 15:47:47 autofs[2232]: ...fail! Oct 05 15:47:47 systemd[1]: autofs.service: Control process exited, code=exited status=1 - Then it never comes up again. + This occurs whenever the service is started with the line in auto.master + which loads the ldap mounts. The line which causes the issue is + "+ldap:automountMapName=auto.master.linux,ou=automount,ou=,ou=,o=,dc=,dc=com", + and this configuration worked on 14.04, 14.10 and 15.04. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to
[Bug 512646] Re: Could not install postfix - postinst failed to properly create postfix user
It seems the NIS was also adding a postfix user, and these conflicted. It seems to have been a problem between me and my network. Sorry about that. -- Could not install postfix - postinst failed to properly create postfix user https://bugs.launchpad.net/bugs/512646 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in ubuntu. -- 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 512646] Re: Could not install postfix - postinst failed to properly create postfix user
I have the same error caused by installing mutt, though I have a slightly different terminal output. sudo apt-get install postfix Reading package lists... Done Building dependency tree Reading state information... Done postfix is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0B of additional disk space will be used. Setting up postfix (2.6.5-3) ... id: cannot find name for group ID 32321 usermod: user 'postfix' does not exist in /etc/passwd dpkg: error processing postfix (--configure): subprocess installed post-installation script returned error exit status 6 Processing triggers for libc-bin ... ldconfig deferred processing now taking place Errors were encountered while processing: postfix E: Sub-process /usr/bin/dpkg returned an error code (1) -- Could not install postfix - postinst failed to properly create postfix user https://bugs.launchpad.net/bugs/512646 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in ubuntu. -- 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 512646] Re: Could not install postfix - postinst failed to properly create postfix user
Additionally when I try and execute the commands given in post 2 I get contradictory error messages. adduser --system --no-create-home --disabled-password --ingroup postfix postfix The user `postfix' already exists. Exiting. usermod -g postfix postfix usermod: user 'postfix' does not exist in /etc/passwd So thats confusing me a little. -- Could not install postfix - postinst failed to properly create postfix user https://bugs.launchpad.net/bugs/512646 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in ubuntu. -- 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 512646] Re: Could not install postfix - postinst failed to properly create postfix user
I manually added the line to /etc/passwd and it worked. No idea why adduser wasn't doing that though. -- Could not install postfix - postinst failed to properly create postfix user https://bugs.launchpad.net/bugs/512646 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in ubuntu. -- 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
