| View previous topic :: View next topic |
| Author |
Message |
piii_man
n00b
Joined: 18 Jul 2004
Posts: 39
|
 Posted: Mon Nov 13, 2023 7:57 pm Post subject: systemd-userdbd Start Failure |
 |
|
I'm seeing a service start failure for systemd-userdbd. I wasn't able to find much information about this, aside from very old bugs. Does anyone have any insight here?[/i]
dmesg:
| Code: |
[ 6.136691] systemd[1]: Starting systemd-userdbd.service...
[ 6.137501] systemd[1]: systemd-userdbd.service: Main process exited, code=exited, status=226/NAMESPACE
[ 6.137579] systemd[1]: systemd-userdbd.service: Failed with result 'exit-code'.
[ 6.137671] systemd[1]: Failed to start systemd-userdbd.service.
[ 6.138880] systemd[1]: Starting systemd-userdbd.service...
[ 6.139397] systemd[1]: systemd-userdbd.service: Main process exited, code=exited, status=226/NAMESPACE
[ 6.139459] systemd[1]: systemd-userdbd.service: Failed with result 'exit-code'.
[ 6.139531] systemd[1]: Failed to start systemd-userdbd.service.
[ 6.140590] systemd[1]: Starting systemd-userdbd.service...
[ 6.141096] systemd[1]: systemd-userdbd.service: Main process exited, code=exited, status=226/NAMESPACE
[ 6.141157] systemd[1]: systemd-userdbd.service: Failed with result 'exit-code'.
[ 6.141233] systemd[1]: Failed to start systemd-userdbd.service.
[ 6.142338] systemd[1]: Starting systemd-userdbd.service...
[ 6.142849] systemd[1]: systemd-userdbd.service: Main process exited, code=exited, status=226/NAMESPACE
[ 6.142909] systemd[1]: systemd-userdbd.service: Failed with result 'exit-code'.
[ 6.142979] systemd[1]: Failed to start systemd-userdbd.service.
[ 6.144063] systemd[1]: Starting systemd-userdbd.service...
[ 6.144571] systemd[1]: systemd-userdbd.service: Main process exited, code=exited, status=226/NAMESPACE
[ 6.144631] systemd[1]: systemd-userdbd.service: Failed with result 'exit-code'.
[ 6.144701] systemd[1]: Failed to start systemd-userdbd.service.
[ 6.145162] systemd[1]: systemd-userdbd.service: Start request repeated too quickly.
[ 6.145165] systemd[1]: systemd-userdbd.service: Failed with result 'exit-code'.
[ 6.145189] systemd[1]: Failed to start systemd-userdbd.service.
[ 6.145569] systemd[1]: systemd-userdbd.socket: Failed with result 'service-start-limit-hit'.
|
| Code: |
systemctl list-units --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● systemd-userdbd.service loaded failed failed User Database Manager
● systemd-userdbd.socket loaded failed failed User Database Manager Socket
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.
2 loaded units listed.
|
| Code: |
journalctl -u systemd-userdbd.service -u systemd-userdbd.socket -n 15 --no-pager
Nov 12 23:14:19 Eric systemd[1]: systemd-userdbd.service: Got notification message from PID 278417, but reception only permitted for main PID 251
Nov 12 23:14:19 Eric systemd[1]: systemd-userdbd.service: Got notification message from PID 278418, but reception only permitted for main PID 251
Nov 12 23:14:19 Eric systemd[1]: systemd-userdbd.service: Got notification message from PID 278416, but reception only permitted for main PID 251
Nov 12 23:19:42 Eric systemd[1]: systemd-userdbd.service: Got notification message from PID 278609, but reception only permitted for main PID 251
Nov 12 23:19:42 Eric systemd[1]: systemd-userdbd.service: Got notification message from PID 278608, but reception only permitted for main PID 251
Nov 12 23:19:42 Eric systemd[1]: systemd-userdbd.service: Got notification message from PID 278607, but reception only permitted for main PID 251
Nov 12 23:20:11 Eric systemd[1]: systemd-userdbd.service: Got notification message from PID 278843, but reception only permitted for main PID 251
Nov 12 23:20:11 Eric systemd[1]: systemd-userdbd.service: Got notification message from PID 278842, but reception only permitted for main PID 251
Nov 12 23:20:11 Eric systemd[1]: systemd-userdbd.service: Got notification message from PID 278841, but reception only permitted for main PID 251
Nov 12 23:20:14 Eric systemd[1]: systemd-userdbd.service: Got notification message from PID 279013, but reception only permitted for main PID 251
Nov 12 23:20:14 Eric systemd[1]: systemd-userdbd.service: Got notification message from PID 279012, but reception only permitted for main PID 251
Nov 12 23:20:14 Eric systemd[1]: systemd-userdbd.service: Got notification message from PID 279014, but reception only permitted for main PID 251
-- Boot c330bbc4c58247409b93ff71b656c721 --
Nov 12 23:30:16 Eric systemd[1]: Listening on systemd-userdbd.socket.
Nov 12 23:30:16 Eric systemd[1]: Starting systemd-userdbd.service...
Nov 12 23:30:16 Eric systemd[1]: Started systemd-userdbd.service.
|
Note On Nov 12 I manually started the service and it seemed to start fine. I subsequently ran a portage update. Post-update I still get the failed start but I'm no longer seeing the detail about getting notification from wrong PID in my logs.
When actually running userdbctl all the outputs look normal, and I'm not seeing any errors despite systemd-userdbd failing to start.
P.S. Didn't see a great place to post this, but since it's relatively low level picked kernel & hardware. Feel free to move |
|
| Back to top |
|
 |
Child_of_Sun_24
Guru
Joined: 28 Jul 2004
Posts: 589
|
| Posted: Tue Nov 14, 2023 6:28 am Post subject: |
|
|
| I have the same problem, had made a fresh install yesterday, since then this error occurs. Manual starting this service works for me, too. |
|
| Back to top |
|
|
Child_of_Sun_24
Guru
Joined: 28 Jul 2004
Posts: 589
|
| Posted: Mon Nov 27, 2023 4:54 pm Post subject: |
|
|
https://github.com/coreos/fedora-coreos-tracker/issues/1296
There is a workaround for this error.
You create a file with the name:
| Code: | | /etc/systemd/system/systemd-userdbd.service.d/override.conf |
The directory systemd-userdbd.service.d have to be created, too.
Then you put this into the override.conf:
| Code: | [Service]
PrivateTmp=no
PrivateDevices=no |
Then the service should start at boot. For me this worked. |
|
| Back to top |
|
|
ebray187
Tux's lil' helper
Joined: 02 Mar 2005
Posts: 121
Location: Al otro lado de la pantalla
|
| Posted: Mon Dec 11, 2023 9:48 pm Post subject: |
|
|
| Child_of_Sun_24 wrote: | | Code: | | /etc/systemd/system/systemd-userdbd.service.d/override.conf |
| Code: | [Service]
PrivateTmp=no
PrivateDevices=no |
|
Thanks! That did the trick
_________________
# emerge -C world >> 9/8
A flower?! |
|
| Back to top |
|
|
piii_man
n00b
Joined: 18 Jul 2004
Posts: 39
|
| Posted: Mon Dec 18, 2023 4:23 am Post subject: Thanks |
|
|
Worked for me too.
| Code: |
systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.
|
Feels good that this is empty again! Thank you. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
