FS#49453 - [mariadb] Uninstalling mariadb causes shadow.service to complain
Attached to Project:
Arch Linux
Opened by Hugh Manning (sunghail) - Monday, 23 May 2016, 23:06 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 24 May 2016, 14:11 GMT
Opened by Hugh Manning (sunghail) - Monday, 23 May 2016, 23:06 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 24 May 2016, 14:11 GMT
|
Details
Description:
The .INSTALL file for the mariadb package does not remove the mysql user and its group when the package is removed. However since the mysql user's home directory (/var/lib/mysql) is removed by pacman automatically, the entry in /etc/passwd now points to a nonexistent directory and shadow.service fails on startup. This does not prevent the system from booting. Additional info: * Checked in mariadb-10.1.9-2 Journal: ~ >sudo systemctl status shadow.service [sudo] password for hugh: ● 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 Tue 2016-05-24 10:12:24 NZST; 49min ago Process: 388 ExecStart=/usr/bin/pwck -r (code=exited, status=2) Main PID: 388 (code=exited, status=2) May 24 10:12:22 hugh-pc systemd[1]: Starting Verify integrity of password and group files... May 24 10:12:23 hugh-pc pwck[388]: user 'mysql': directory '/var/lib/mysql' does not exist May 24 10:12:24 hugh-pc pwck[388]: pwck: no changes May 24 10:12:24 hugh-pc systemd[1]: shadow.service: Main process exited, code=exited, status=2/INVALIDARGUMENT May 24 10:12:24 hugh-pc systemd[1]: Failed to start Verify integrity of password and group files. May 24 10:12:24 hugh-pc systemd[1]: shadow.service: Unit entered failed state. May 24 10:12:24 hugh-pc systemd[1]: shadow.service: Failed with result 'exit-code'. Steps to reproduce: * Install mariadb with pacman * Remove mariadb with pacman * Reboot |
This task depends upon
Closed by Doug Newgard (Scimmia)
Tuesday, 24 May 2016, 14:11 GMT
Reason for closing: Not a bug
Additional comments about closing: This is equivalent to a warning. Fix it locally if you want.
Tuesday, 24 May 2016, 14:11 GMT
Reason for closing: Not a bug
Additional comments about closing: This is equivalent to a warning. Fix it locally if you want.