You are not logged in.
Pages: 1
Stirred from a discussion on IRC, I checked
~ $ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● netctl@wlp2s0\x2deduroam.service loaded failed failed A wireless connection using a custom block configuration. This works for eduroam. Mind the password w
● netctl@wlp2s0\x2dSKY64C93.service loaded failed failed A simple WPA encrypted wireless connection
● shadow.service loaded failed failed Verify integrity of password and group files
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
3 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
~ $ systemctl status shadow.service
● shadow.service - Verify integrity of password and group files
Loaded: loaded (/usr/lib/systemd/system/shadow.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2016-01-09 12:03:42 CET; 10min ago
Process: 17935 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
Main PID: 17935 (code=exited, status=2)
Jan 09 12:03:42 gls systemd[1]: Starting Verify integrity of password and group files...
Jan 09 12:03:42 gls pwck[17935]: user 'mysql': directory '/var/lib/mysql' does not exist
Jan 09 12:03:42 gls pwck[17935]: pwck: no changes
Jan 09 12:03:42 gls systemd[1]: shadow.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jan 09 12:03:42 gls systemd[1]: Failed to start Verify integrity of password and group files.
Jan 09 12:03:42 gls systemd[1]: shadow.service: Unit entered failed state.
Jan 09 12:03:42 gls systemd[1]: shadow.service: Failed with result 'exit-code'.
~ $ journalctl _PID=17935
-- Logs begin at Sat 2015-06-27 00:29:40 CEST, end at Sat 2016-01-09 12:14:01 CET. --
Jan 09 12:03:42 gls pwck[17935]: user 'mysql': directory '/var/lib/mysql' does not exist
Jan 09 12:03:42 gls pwck[17935]: pwck: no changesThe warning from shadow.service I see frequently at boot, and would like to get rid of it. I am most likely misinterpreting the msg, as I check and there are no 'user' named mysql. I never used anything related to mysql explicitely or installed something to work with it (e.g. no mariadb). So I am bit lost, should I just ignore this? Mkdir so that it is happy?
Offline
what is the output of
$getent passwd mysqlOffline
The misterious
mysql:x:89:89::/var/lib/mysql:/bin/falseOffline
So there is a mysql user as pwck reported.
pwck[17935]: user 'mysql': directory '/var/lib/mysql' does not existChanging the home directory for the mysql user to a path that exists or removing the mysql user should both resolve the warning.
See https://www.archlinux.org/todo/usergroup-management/ for an explanation of why the user was not automatically removed.
Offline
I see, sorry for being a total noob.
User only prints logged in users, to check all user in existence
awk -F: '{ print $1 }' /etc/passwdSo, now I also know what the misterious output above is, the line of /etc/passwd.
Question: is it safe to remove this mysql user? Who do I go about finding out/finding out what/why it was created?
Offline
Question: is it safe to remove this mysql user? Who do I go about finding out/finding out what/why it was created?
As per the link above as long as there are no files owned by the mysql user.
You should probably remove the mysql group as well after checking there are no files owned by the mysql group.
Check the pacman log to see if mysql / mariadb packages were ever installed?
What has this got to do with hardware or the kernel?
Offline
Since it was a systemd error that led me here, I didn't know how to categorize this properly. I cannot move the topic myself, I believe.
Offline
Pages: 1