Bug 87943

Summary: system 195 aborts at src/core/service.c:1077on OpenSuse 12.3
Product: systemd Reporter: huaraz
Component: generalAssignee: systemd-bugs
Status: RESOLVED FIXED QA Contact: systemd-bugs
Severity: major    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description huaraz 2015-01-01 18:21:35 UTC
When copying an existing /etc/init.d/ script, updating with INIT header and then run /etc/init.d/<script> status system aborts.

# cp /etc/init.d/sockd /etc/init.d/sockd-1.5.0
# insserv /etc/init.d/sockd-1.5.0

Update INIT INFO from 

 ### BEGIN INIT INFO
 # Provides:       sockd

to

 ### BEGIN INIT INFO
 # Provides:       sockd-1.5.0

Then run 

# systemctl status sockd-1.5.0
Failed to issue method call: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus 
security policy blocked the reply, the reply timeout expired, or the network 
connection was broken.
# systemctl status sockd-1.5.0
Failed to get D-Bus connection: Failed to connect to socket 
/run/systemd/private: Connection refused

2015-01-01T17:52:01.625495+00:00 opensuse12 systemd[1]: Accepted connection 
on private bus.
2015-01-01T17:52:01.626333+00:00 opensuse12 systemd[1]: Running GC...
2015-01-01T17:52:01.627976+00:00 opensuse12 systemd[1]: Got D-Bus request: 
org.freedesktop.DBus.Properties.GetAll() on 
/org/freedesktop/systemd1/unit/sockd_2d1_2e5_2e0
2015-01-01T17:52:01.636546+00:00 opensuse12 systemd[1]: Assertion 
'endswith(path, ".service")' failed at src/core/service.c:1077, function 
service_load_sysv_name(). Aborting.
2015-01-01T17:52:01.686714+00:00 opensuse12 systemd[1]: Caught <ABRT>, 
dumped core as pid 2925.
2015-01-01T17:52:01.687538+00:00 opensuse12 systemd[1]: Freezing execution.


I am running Opensuse 12.3

# rpm -q -f /sbin/init
systemd-sysvinit-195-13.45.1.x86_64

# systemd --version
systemd 195
suse
+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ

This is 100% reproducible. And only a hard reboot fixes it :-(

Markus
Comment 1 Zbigniew Jedrzejewski-Szmek 2015-01-01 18:28:22 UTC
Sorry for suggesting opening of the bug. As pointed out on the mailing list, v195 is ancient history and the bug has almost certainly been fixed, since this code was completely removed from PID 1 and replaced by systemd-sysv-generator.
Comment 2 Zbigniew Jedrzejewski-Szmek 2015-01-01 18:30:54 UTC
You might want to file a bug at the suse bug tracker. But that too would probably be a waste of time, and it is better to simply avoid the bug by not triggering the issue (I'd guess that the dots in the name trip up systemd). 

Since root privileges are necessary to add a unit file anyway, this is mostly an annoyance.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.