Bug ID | 994773 |
---|---|
Summary | nfs-config.service failed: Process /usr/libexec/nfs-utils/nfs-utils_env.sh could not be executed |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | x86-64 |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Network |
Assignee | bnc-team-screening@forge.provo.novell.com |
Reporter | manfred.h@gmx.net |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
I just updated my TW systems to the latest snapshot 20160818 and after rebooting, I found this in the logs: Aug 21 13:00:53 saturn systemd[2429]: nfs-config.service: Failed at step EXEC spawning /usr/libexec/nfs-utils/nfs-utils_env.sh: No such file or directory -- Subject: Process /usr/libexec/nfs-utils/nfs-utils_env.sh could not be executed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The process /usr/libexec/nfs-utils/nfs-utils_env.sh could not be executed and failed. -- -- The error number returned by this process is 2. Aug 21 13:00:53 saturn systemd[1]: Failed to start Preprocess NFS configuration. -- Subject: Unit nfs-config.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nfs-config.service has failed. -- -- The result is failed. According to "zypper se -s -f nfs-utils_env.sh", this file is part of package "nfs-client", but it's at a different location than what the service file calls for: # rpm -ql nfs-client | fgrep nfs-utils_env.sh /usr/lib/systemd/scripts/nfs-utils_env.sh Oh well... Systemd ruling everywhere :(