Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
systemd logind fail sto start
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
wichtounet
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2012
Posts: 116

PostPosted: Wed Dec 18, 2013 3:01 pm    Post subject: systemd logind fail sto start Reply with quote

Hi,

I had to reinstall my work machine and I decided to go with systemd.

I installed Gentoo, systemd, LVM, X.Org, slim and awesome. I've already performed the same installation on my laptop without any problems.

All of that seemed to work well, but now I have several problems. I don't know at exact which point the problems started :(

First, I saw that vim refused to start:

Quote:
+ 3392 suspended (tty output) vim


Then, I saw that systemd commands were taking a very long time and there were some time out:

Code:
sudo systemctl status dbus.service

Quote:
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib64/systemd/system/dbus.service; static)
Active: active (running) since Wed 2013-12-18 15:34:17 CET; 12min ago
Main PID: 3127 (dbus-daemon)
CGroup: /system.slice/dbus.service
└─3127 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation

Dec 18 15:45:33 heimdall dbus-daemon[3127]: dbus[3127]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Dec 18 15:45:33 heimdall dbus[3127]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Dec 18 15:45:58 heimdall dbus-daemon[3127]: dbus[3127]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Dec 18 15:45:58 heimdall dbus[3127]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Dec 18 15:46:20 heimdall dbus-daemon[3127]: dbus[3127]: [system] Activating systemd to hand-off: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Dec 18 15:46:20 heimdall dbus[3127]: [system] Activating systemd to hand-off: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Dec 18 15:46:23 heimdall dbus-daemon[3127]: dbus[3127]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Dec 18 15:46:23 heimdall dbus[3127]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Dec 18 15:46:45 heimdall dbus-daemon[3127]: dbus[3127]: [system] Failed to activate service 'org.freedesktop.login1': timed out
Dec 18 15:46:45 heimdall dbus[3127]: [system] Failed to activate service 'org.freedesktop.login1': timed out


A very weird thing is that I can launch vim from root without and that if I do "systemctl status dbus.service" as root, it is very fast. If I login as root in Slim, I still experience a big delay before I'm logged, but then once logged, I can use vim. As the delay is also with root, I don't think that it can be a user-related problems.

Could it be something wrong with sessions ?

I would gladly accept any help, I'm running out of ideas :(

Thanks


Last edited by wichtounet on Thu Dec 19, 2013 9:07 am; edited 2 times in total
Back to top
View user's profile Send private message
wichtounet
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2012
Posts: 116

PostPosted: Wed Dec 18, 2013 3:07 pm    Post subject: Reply with quote

I also just saw that in journalctl, there is an error after each reboot:

Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory
Back to top
View user's profile Send private message
wichtounet
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2012
Posts: 116

PostPosted: Wed Dec 18, 2013 3:56 pm    Post subject: Reply with quote

I have found an interesting thing comparing the two machines running almost the same configuration.

On the machine where I have no problem, systemctl status slim.service returns that:

Quote:
slim.service - SLiM Simple Login Manager
Loaded: loaded (/usr/lib64/systemd/system/slim.service; enabled)
Active: active (running) since Wed 2013-12-18 16:41:14 CET; 7min ago
Main PID: 3293 (slim)
CGroup: /system.slice/slim.service
└─3295 /usr/bin/X -nolisten tcp -br -deferglyphs 16 vt07 -auth /var/run/slim.auth
‣ 3293 /usr/bin/slim -nodaemon -s


On the machine that has problems, I got that:

Quote:
slim.service - SLiM Simple Login Manager
Loaded: loaded (/usr/lib64/systemd/system/slim.service; enabled)
Active: active (running) since Wed 2013-12-18 16:50:18 CET; 3min 11s ago
Main PID: 3127 (slim)
CGroup: /system.slice/slim.service
├─3127 /usr/bin/slim -nodaemon -s
├─3129 /usr/bin/X -nolisten tcp -br -deferglyphs 16 vt07 -auth /var/run/slim.auth
├─3151 /usr/bin/awesome
├─3154 xcompmgr
├─3157 urxvt
├─3158 zsh
├─3179 sudo su
├─3182 su
├─3187 zsh
├─3194 /usr/lib64/chromium-browser/chrome --extra-plugin-dir=/usr/lib64/nsbrowser/plugins
├─3196 /usr/lib64/chromium-browser/chrome --extra-plugin-dir=/usr/lib64/nsbrowser/plugins --type=sandbox-ipc
├─3197 /usr/lib64/chromium-browser/chrome-sandbox /usr/lib64/chromium-browser/chrome --type=zygote
├─3200 /usr/lib64/chromium-browser/chrome --type=zygote
├─3206 /usr/lib64/chromium-browser/chrome --type=zygote
├─3238 /usr/lib64/chromium-browser/chrome --type=renderer --lang=en-US --force-fieldtrials=DeferBackgroundExtensionCreation/Deferred/ForceCompositingMode/disable/InfiniteCache/No/Prefetch/ContentPrefetchPrefetchOff/Prerender...
├─3244 /usr/lib64/chromium-browser/chrome --type=renderer --lang=en-US --force-fieldtrials=DeferBackgroundExtensionCreation/Deferred/ForceCompositingMode/disable/InfiniteCache/No/Prefetch/ContentPrefetchPrefetchOff/Prerender...
├─3256 dbus-launch --autolaunch e3aee6f87e29615231bd4eed52b066f6 --binary-syntax --close-stderr
├─3257 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
├─3261 /usr/lib64/chromium-browser/chrome --type=renderer --lang=en-US --force-fieldtrials=DeferBackgroundExtensionCreation/Deferred/ForceCompositingMode/disable/InfiniteCache/No/Prefetch/ContentPrefetchPrefetchOff/Prerender...
├─3274 /usr/lib64/chromium-browser/chrome --type=renderer --lang=en-US --force-fieldtrials=DeferBackgroundExtensionCreation/Deferred/ForceCompositingMode/disable/InfiniteCache/No/Prefetch/ContentPrefetchPrefetchOff/Prerender...
├─3281 /usr/lib64/chromium-browser/chrome --type=renderer --lang=en-US --force-fieldtrials=DeferBackgroundExtensionCreation/Deferred/ForceCompositingMode/disable/InfiniteCache/No/Prefetch/ContentPrefetchPrefetchOff/Prerender...
├─3288 /usr/lib64/chromium-browser/chrome --type=renderer --lang=en-US --force-fieldtrials=DeferBackgroundExtensionCreation/Deferred/ForceCompositingMode/disable/InfiniteCache/No/Prefetch/ContentPrefetchPrefetchOff/Prerender...
├─3310 /usr/lib64/chromium-browser/chrome --type=renderer --lang=en-US --force-fieldtrials=DeferBackgroundExtensionCreation/Deferred/ForceCompositingMode/disable/InfiniteCache/No/Prefetch/ContentPrefetchPrefetchOff/Prerender...
├─3318 /usr/lib64/chromium-browser/chrome --type=service
├─3353 /usr/lib64/chromium-browser/chrome --type=gpu-process --channel=3194.10.2031580957 --supports-dual-gpus=false --gpu-driver-bug-workarounds=0,22 --disable-accelerated-video-decode --gpu-vendor-id=0x1002 --gpu-device-id...
├─3357 /usr/lib64/chromium-browser/chrome --type=gpu-process --channel=3194.10.2031580957 --supports-dual-gpus=false --gpu-driver-bug-workarounds=0,22 --disable-accelerated-video-decode --gpu-vendor-id=0x1002 --gpu-device-id...
└─3465 systemctl status slim.service


All the processes are put in control group of slim. Perhaps it is a problem ? And why this difference ?

Hope that helps someone find a solution.
Back to top
View user's profile Send private message
wichtounet
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2012
Posts: 116

PostPosted: Thu Dec 19, 2013 7:44 am    Post subject: Reply with quote

The problem does not seem to be related to slim at all. I disable slim.service and now I boot to the console and I experience the same delay with the login.

I also noticed that in the journal:

Quote:
Dec 19 08:22:12 heimdall systemd[1]: RequestName() failed: Access denied
...
Dec 19 08:22:22 heimdall login[3128]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
Dec 19 08:22:22 heimdall dbus-daemon[3125]: dbus[3125]: [system] Activating systemd to hand-off: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Dec 19 08:22:22 heimdall dbus[3125]: [system] Activating systemd to hand-off: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Dec 19 08:22:37 heimdall systemd-logind[3127]: Failed to enable subscription: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Dec 19 08:22:37 heimdall systemd-logind[3127]: Failed to register name on bus: Access denied
Dec 19 08:22:37 heimdall systemd-logind[3127]: Failed to fully start up daemon: Input/output error


I think that is the root of the problem.

I tried reinstalling/upgrading dbus, but it didn't make any difference.

Here is the full boot journal, there are several errors but I do not have enough knowledge of systemd to understand them :(

journalctl output
Back to top
View user's profile Send private message
wichtounet
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2012
Posts: 116

PostPosted: Thu Dec 19, 2013 10:20 am    Post subject: Reply with quote

I've been able to change the state of things.

I've removed polkit from my use flags and performed a world update.

Now there are no more delays in login and systemd-logind is running

However, I still have the problem regarding vim getting suspended.

I've noticed this in the log:

Quote:
Dec 19 11:14:19 heimdall systemd[3141]: Failed to open private bus connection: Failed to connect to socket /run/user/0/dbus/user_bus_socket: No such file or directory


So there is still a problem with dbus, but I don't see what could cause that :(

I also noticed that in the logs:

Quote:
Dec 19 11:14:14 heimdall systemd[1]: var-run.mount: Directory /var/run to mount over is not empty, mounting anyway.


Could that be the cause of the problem?

I can provide the full journal again if it is of some helps.
Back to top
View user's profile Send private message
wichtounet
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2012
Posts: 116

PostPosted: Thu Dec 19, 2013 11:49 am    Post subject: Reply with quote

I resolved the tty output suspension problem it was a bug in a plugin. Still don't know why policykit doesn't work, but I'll do without it for now.

Sorry for all these question posts :(
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
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