Bug 879716

Summary: systemctl error messages are cryptic
Product: [Fedora] Fedora Reporter: Dimitrios Apostolou <jimis>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: rawhideCC: johannbg, lnykryn, metherid, msekleta, notting, plautrba, systemd-maint, vpavlin
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-14 13:01:40 EST Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Dimitrios Apostolou 2012-11-23 16:37:20 EST
I'm new to systemd, so I tried overriding a unit file by copying it to /etc/systemd/system/multi-user.target.wants/ directory and editing it there.

That was a mistake, the proper path to copy unit files is /etc/systemd/system/.

However it took me a decent amount of time to find out, since everything I tried was failing with the following message. Google gave me the answer, but as an admin I like to search things on my own. Strace'ing systemctl didn't help (it sends messages via socket) and I still don't know what was the dreaded method call that failed...

# systemctl reenable MYSERVICE   # Or almost every command on MYSERVICE
Failed to issue method call: Invalid argument
Comment 1 Lennart Poettering 2013-01-14 13:01:40 EST
The failing reenable is actually discussed here.



*** This bug has been marked as a duplicate of bug 880353 ***