Description of problem: I don't know. I ran a yum update, which included autofs; then I rebooted; and autofs crashed on startup. Version-Release number of selected component: autofs-5.0.7-20.fc19 Additional info: reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/sbin/automount --pid-file /run/autofs.pid crash_function: mount_mount executable: /usr/sbin/automount kernel: 3.9.4-301.fc19.x86_64 runlevel: N 5 uid: 0 Truncated backtrace: Thread no. 1 (7 frames) #0 mount_mount at mount_nfs.c:193 #1 sun_mount at parse_sun.c:695 #2 parse_mount at parse_sun.c:1612 #3 lookup_mount at lookup_file.c:1130 #4 lookup_name_file_source_instance at lookup.c:720 #5 lookup_nss_mount at lookup.c:912 #6 do_mount_indirect at indirect.c:776
Created attachment 759997 [details] File: backtrace
Created attachment 759998 [details] File: cgroup
Created attachment 759999 [details] File: core_backtrace
Created attachment 760000 [details] File: dso_list
Created attachment 760001 [details] File: environ
Created attachment 760002 [details] File: limits
Created attachment 760003 [details] File: maps
Created attachment 760004 [details] File: open_fds
Created attachment 760005 [details] File: proc_pid_status
Created attachment 760006 [details] File: var_log_messages
Created attachment 760042 [details] Patch - fix probe each nfs version in turn for singleton mounts.
I'm not sure if this simple mistake is the only problem but could you give this Rawhide build a try please. It can be found at: http://koji.fedoraproject.org/koji/buildinfo?buildID=426132
I've installed it... I'll see what happens! The crash isn't immediate, so I'll leave it for a few hours and see if it's stable.
This does seem to have fixed it, thanks! Now when it fails to find the hostname, it doesn't kill the process. [root@zoe avocs]# systemctl status autofs autofs.service - Automounts filesystems on demand Loaded: loaded (/usr/lib/systemd/system/autofs.service; enabled) Active: active (running) since Wed 2013-06-12 16:11:09 BST; 3h 54min ago Process: 1254 ExecStart=/usr/sbin/automount $OPTIONS --pid-file /run/autofs.pid (code=exited, status=0/SUCCESS) Main PID: 1276 (automount) CGroup: name=systemd:/system/autofs.service └─1276 /usr/sbin/automount --pid-file /run/autofs.pid Jun 12 16:11:09 zoe automount[1276]: lookup_read_master: lookup(nisplus): couldn't locat...ter Jun 12 16:11:09 zoe systemd[1]: Started Automounts filesystems on demand. Jun 12 16:18:25 zoe automount[1276]: add_host_addrs: hostname lookup failed: Name or ser...own Jun 12 16:19:34 zoe automount[1276]: add_host_addrs: hostname lookup failed: Name or ser...own Jun 12 19:56:32 zoe automount[1276]: add_host_addrs: hostname lookup failed: Name or ser...own [root@zoe avocs]#
(In reply to James Heather from comment #14) > This does seem to have fixed it, thanks! Now when it fails to find the > hostname, it doesn't kill the process. OK, unless there is something else I'll apply the change to f19? Ian
Yes please!
autofs-5.0.7-21.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/autofs-5.0.7-21.fc19
Package autofs-5.0.7-21.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing autofs-5.0.7-21.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-10754/autofs-5.0.7-21.fc19 then log in and leave karma (feedback).
autofs-5.0.7-22.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/autofs-5.0.7-22.fc19
autofs-5.0.7-23.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/autofs-5.0.7-23.fc19
autofs-5.0.7-23.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.