Bug 21608 - GSSAPI fails to start during boot
Summary: GSSAPI fails to start during boot
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-25 17:19 CEST by Robert Fox
Modified: 2023-03-13 10:50 CET (History)
2 users (show)

See Also:
Source RPM: gssproxy, kernel
CVE:
Status comment:


Attachments

Description Robert Fox 2017-08-25 17:19:16 CEST
Description of problem:

GSSAPI fails to start during boot:

[root@foxmain rfox]# service gssproxy status
Redirecting to /bin/systemctl status gssproxy.service
● gssproxy.service - GSSAPI Proxy Daemon
   Loaded: loaded (/usr/lib/systemd/system/gssproxy.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2017-08-25 17:07:39 CEST; 2min 41s ago
  Process: 1282 ExecStart=/usr/sbin/gssproxy -D (code=exited, status=1/FAILURE)

Aug 25 17:07:39 foxmain systemd[1]: Starting GSSAPI Proxy Daemon...
Aug 25 17:07:39 foxmain gssproxy[1282]: GSS-Proxy is not supported by this kernel since file /proc/net/rpc/use-gss-proxy could not be found: 2 (No such file or directory)
Aug 25 17:07:39 foxmain systemd[1]: gssproxy.service: Control process exited, code=exited status=1
Aug 25 17:07:39 foxmain systemd[1]: Failed to start GSSAPI Proxy Daemon.
Aug 25 17:07:39 foxmain systemd[1]: gssproxy.service: Unit entered failed state.
Aug 25 17:07:39 foxmain systemd[1]: gssproxy.service: Failed with result 'exit-code'.

Version-Release number of selected component (if applicable):
gssproxy-0.7.0-1.mga6

How reproducible:
everytime - just reboot

Steps to Reproduce:
1.
2.
3.
David Walser 2017-08-25 23:27:26 CEST

CC: (none) => guillomovitch, tmb
Assignee: bugsquad => pkg-bugs
Source RPM: (none) => gssproxy, kernel

Comment 1 sturmvogel 2023-03-13 10:50:20 CET
This bug was filed against MGA6 which is EOL since September 2019.

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.