Bug 14678

Summary:	systemd-journal-gateway user not automatically created
Product:	Mageia	Reporter:	claire robinson <eeeemail>
Component:	RPM Packages	Assignee:	Colin Guthrie <mageia>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	zen25000
Version:	5
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description claire robinson 2014-11-28 14:36:29 CET

This may be for good reasons but thought it worthy of a bug report.

I tried systemd-journal-gatewayd today for the first time, it's a useful optional http journal interface. When I started the service, which is really a socket, and tried to connect to it with a browser I wasn't able to.

# systemctl start systemd-journal-gatewayd.socket

http://127.0.0.1:19531/browse

The journal shows..

systemd[1]: systemd-journal-gatewayd.service: main process exited, code=exited, status=217/USER


With a bit of googling I found this explanation
http://bneijt.nl/blog/post/trying-out-systemd-journal-gatewayd/

" By default systemd-journal-gatewayd will try to run as the systemd-journal-gateway user and group. But, as the user does not exist we get an exit code 217. The solution is to add the user:

sudo useradd --system systemd-journal-gateway "

Confirmed that after adding the user and then starting the socket again I was then able to connect with a browser.

Should the user be created during systemd installation or is it better kept as a manual process?

Reproducible: 

Steps to Reproduce:

Barry Jackson 2014-11-28 14:51:47 CET

CC: (none) => zen25000

Comment 1 Colin Guthrie 2014-11-28 15:00:09 CET

FWIW, this is fixed in newer versions of system which uses sysusers to create the user via this snippet:

/usr/lib/sysusers.d/systemd-remote.conf


So yes, it should really be created on install, so will keep this in mind for any further updates to systemd for MGA4.

Comment 2 claire robinson 2014-11-28 16:27:40 CET

Thanks Col

Comment 3 Samuel Verschelde 2015-09-21 13:21:09 CEST

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Comment 4 claire robinson 2015-09-21 14:38:13 CEST

Need to defer to Colin on this one. I can't tell whether this is fixed in mga5 as my systemd-journal-gatewayd user (UID 470) still exists on the upgraded system.

New systemd users -timesync -resolve -network etc. are in 990 UID range though.

Comment 5 Colin Guthrie 2015-09-21 14:41:38 CEST

It's fine these days.

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

Rémi Verschelde 2015-09-21 15:09:24 CEST

Version: 4 => 5