Bug 20301 - gssproxy.service: Control process exited, code=exited status=1
Summary: gssproxy.service: Control process exited, code=exited status=1
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Guillaume Rousse
QA Contact:
URL:
Whiteboard:
Keywords: 6sta2
Depends on:
Blocks:
 
Reported: 2017-02-16 13:59 CET by Bit Twister
Modified: 2017-05-26 12:52 CEST (History)
1 user (show)

See Also:
Source RPM: gssproxy-0.6.1-1.mga6.src.rpm
CVE:
Status comment:

Attachments
/etc/gssproxy/gssproxy.conf (887 bytes, text/plain)
2017-02-16 14:01 CET, Bit Twister 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2017-02-16 13:59:42 CET 
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
Comment 1 Bit Twister 2017-02-16 14:01:58 CET 
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
Assignee: bugsquad => guillomovitch

Comment 2 Guillaume Rousse 2017-05-07 18:34:28 CEST 
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

Comment 3 Bit Twister 2017-05-07 23:08:40 CEST 
(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.
Comment 4 Guillaume Rousse 2017-05-26 12:52:21 CEST 
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
Status: ASSIGNED => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.