| Summary: | gssproxy.service: Control process exited, code=exited status=1 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Bit Twister <bittwister2> |
| Component: | RPM Packages | Assignee: | Guillaume Rousse <guillomovitch> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11 |
| Version: | Cauldron | Keywords: | 6sta2 |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | gssproxy-0.6.1-1.mga6.src.rpm | CVE: | |
| Status comment: | |||
| Attachments: | /etc/gssproxy/gssproxy.conf | ||
Created attachment 8964 [details]
/etc/gssproxy/gssproxy.conf
Bit Twister
2017-02-16 14:02:29 CET
Keywords:
(none) =>
6sta2
Marja Van Waes
2017-02-16 15:30:15 CET
CC:
(none) =>
marja11 Either update to 0.7.0, once submitted, or remove the nfs-server part of your configuration file, which seems to be the cause of the start failure. Status:
NEW =>
ASSIGNED (In reply to Guillaume Rousse from comment #2) > Either update to 0.7.0, once submitted, I did the update and reboot. Still failed with code=exited status=1 > or remove the nfs-server part of > your configuration file, Did it, rebooted, still failed. > which seems to be the cause of the start failure. Also, removed the nfs-client stanza and no start failure. Also restored the original configuration file and have no start failure. The main reason for the bug report was to get the application to indicate what it did not like. Feel free to close this as won't fix if you like. Well, you'd better report this issue upstream if you want to change its behaviour, I don't have any added-value here. Resolution:
(none) =>
WONTFIX |
Description of problem: $ journalctl --no-hostname | grep gssproxy Feb 16 02:48:14 systemd[1]: gssproxy.service: Control process exited, code=exited status=1 gssproxy.service: Unit entered failed state. gssproxy.service: Failed with result 'exit-code'. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. create /etc/gssproxy/gssproxy.conf See attachment 2. systemctl restart gssproxy.service 3. journalctl --no-hostname | grep gssproxy