Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Need some help with systemd
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
trollo
n00b
n00b


Joined: 10 Sep 2004
Posts: 44
Location: Berlin

PostPosted: Tue Feb 11, 2014 10:22 pm    Post subject: Need some help with systemd Reply with quote

I just did a fresh Gentoo install on my laptop. Not my first, but for the first time I'm trying to migrate to systemd now. After solving an issue with LVM it boots fine now and seems to work without problems (though I haven't done exensive testing and have yet to install X and Gnome). However, looking at the logs I see a bunch of ugly and partly worrying messages which I'd like to get out of the way before I proceed setting up my system.

I could use some help with this.

boot:

Quote:
/etc/init.d/net.enp5s0[148]: net.enp5s0: not allowed to be hotplugged

Normally it would'nt worry me that my ethernet adapter can't be hotplugged, but why is this printed in RED (ERROR level)?


Quote:
systemd[1]: var.mount: Directory /var to mount over is not empty, mounting anyway.

I'm not sure if this has something to do with my seperate /var and/or LVM. Is this something to worry about? How would I check what's in there before it gets mounted?


shutdown:

Quote:
systemd-logind[215]: Failed to stop unit session-1.scope: 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.

I'm completely lost with this one, but I sure don't like it's color.


Quote:
lvm[321]: WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!

Google found this related bug: https://bugzilla.redhat.com/show_bug.cgi?id=837603, but the thing is, I have use_lvmetad=1 in my lvm.conf at all times, how can it get disabled?


Quote:
systemd[1]: Failed unmounting /var.

/var again. I thought it was all about separate /usr, but I'm beginning to think my separate /var is causing most of the trouble here. Any ideas?


The complete logs are here for boot: http://bpaste.net/show/178120/
and here for shutdown (starting at line 976): http://bpaste.net/show/178121/
I'd be happy to post anything else of need. Thanks in advance!
Back to top
View user's profile Send private message
trollo
n00b
n00b


Joined: 10 Sep 2004
Posts: 44
Location: Berlin

PostPosted: Wed Feb 12, 2014 9:56 am    Post subject: Reply with quote

Ok, I solved the issues with /var; the problem was that journald logged to it before it was mounted and kept it busy when it was supposed to be unmounted. Pretty obvious, yeah.

Unfortunately there's apparently no option to change the storage location of journald's logs (is there a rationale for that?), so I moved my separate /var into / and my (former) var Logical Volume is now mounted at /var/tmp (since I guess I will need the space for later compilations). This should be fine, right? Or am I missing any potential complications?

The other messages remain to be solved, however. Especially the two red ones give me headaches.
Back to top
View user's profile Send private message
ulenrich
Veteran
Veteran


Joined: 10 Oct 2010
Posts: 1374

PostPosted: Wed Feb 12, 2014 12:12 pm    Post subject: Reply with quote

Logind: Before shutdown?
Code:
# systemctl status systemd-logind
systemd-logind.service - Login Service
   Loaded: loaded (/usr/lib64/systemd/system/systemd-logind.service; static)
   Active: active (running) since Mi 2014-02-12 12:05:45 CET; 1h 4min ago
     Docs: man:systemd-logind.service(8)
           man:logind.conf(5)
           http://www.freedesktop.org/wiki/Software/systemd/logind
           http://www.freedesktop.org/wiki/Software/systemd/multiseat
 Main PID: 471 (systemd-logind)
   CGroup: /system.slice/systemd-logind.service
           └─471 /usr/lib/systemd/systemd-logind

Feb 12 12:05:45 maci systemd-logind[471]: Watching system buttons on /dev/input/event2 (Power Button)
Feb 12 12:05:45 maci systemd-logind[471]: Watching system buttons on /dev/input/event0 (Power Button)
Feb 12 12:05:45 maci systemd-logind[471]: Watching system buttons on /dev/input/event1 (Sleep Button)
Feb 12 12:05:45 maci systemd-logind[471]: New seat seat0.
Feb 12 12:06:32 maci systemd-logind[471]: New session 1 of user root.
Feb 12 12:06:52 maci systemd-logind[471]: New session 2 of user ral.
Feb 12 12:06:52 maci systemd-logind[471]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display.

_________________
fun2gen2
Back to top
View user's profile Send private message
trollo
n00b
n00b


Joined: 10 Sep 2004
Posts: 44
Location: Berlin

PostPosted: Wed Feb 12, 2014 12:27 pm    Post subject: Reply with quote

ulenrich wrote:
Logind: Before shutdown?

Yes.

Code:
# systemctl status systemd-logind
systemd-logind.service - Login Service
   Loaded: loaded (/usr/lib64/systemd/system/systemd-logind.service; static)
   Active: active (running) since Mi 2014-02-12 13:18:04 CET; 4min 2s ago
     Docs: man:systemd-logind.service(8)
           man:logind.conf(5)
           http://www.freedesktop.org/wiki/Software/systemd/logind
           http://www.freedesktop.org/wiki/Software/systemd/multiseat
 Main PID: 217 (systemd-logind)
   CGroup: /system.slice/systemd-logind.service
           └─217 /usr/lib/systemd/systemd-logind

Feb 12 13:18:04 leni systemd[1]: Job systemd-logind.service/start finished, result=done
Feb 12 13:18:04 leni systemd-logind[217]: New seat seat0.
Feb 12 13:18:04 leni systemd[1]: Started Login Service.
Feb 12 13:18:04 leni systemd-logind[217]: Watching system buttons on /dev/input/event3 (Power Button)
Feb 12 13:18:04 leni systemd-logind[217]: Watching system buttons on /dev/input/event5 (Video Bus)
Feb 12 13:18:04 leni systemd-logind[217]: Watching system buttons on /dev/input/event4 (Video Bus)
Feb 12 13:18:04 leni systemd-logind[217]: Watching system buttons on /dev/input/event1 (Power Button)
Feb 12 13:18:04 leni systemd-logind[217]: Watching system buttons on /dev/input/event0 (Lid Switch)
Feb 12 13:18:04 leni systemd-logind[217]: Watching system buttons on /dev/input/event2 (Sleep Button)
Feb 12 13:18:09 leni systemd-logind[217]: New session 1 of user root.


Code:
# journalctl -b -1 | grep logind
Feb 12 10:39:14 leni systemd[1]: Installed new job systemd-logind.service/start as 73
Feb 12 10:39:20 leni systemd[1]: About to execute: /usr/lib/systemd/systemd-logind
Feb 12 10:39:20 leni systemd[1]: Forked /usr/lib/systemd/systemd-logind as 219
Feb 12 10:39:20 leni systemd[1]: systemd-logind.service changed dead -> start
Feb 12 10:39:20 leni systemd[219]: Executing: /usr/lib/systemd/systemd-logind
Feb 12 10:39:20 leni systemd[1]: systemd-logind.service's D-Bus name org.freedesktop.login1 now registered by :1.1
Feb 12 10:39:20 leni systemd[1]: systemd-logind.service changed start -> running
Feb 12 10:39:20 leni systemd[1]: Job systemd-logind.service/start finished, result=done
Feb 12 10:39:20 leni systemd-logind[219]: New seat seat0.
Feb 12 10:39:20 leni systemd-logind[219]: Watching system buttons on /dev/input/event3 (Power Button)
Feb 12 10:39:20 leni systemd-logind[219]: Watching system buttons on /dev/input/event5 (Video Bus)
Feb 12 10:39:20 leni systemd-logind[219]: Watching system buttons on /dev/input/event4 (Video Bus)
Feb 12 10:39:20 leni systemd-logind[219]: Watching system buttons on /dev/input/event1 (Power Button)
Feb 12 10:39:20 leni systemd-logind[219]: Watching system buttons on /dev/input/event0 (Lid Switch)
Feb 12 10:39:20 leni systemd-logind[219]: Watching system buttons on /dev/input/event2 (Sleep Button)
Feb 12 10:39:36 leni systemd-logind[219]: New session 1 of user root.
Feb 12 13:16:05 leni systemd[1]: Got D-Bus request: org.freedesktop.DBus.Properties.GetAll() on /org/freedesktop/systemd1/unit/systemd_2dlogind_2eservice
Feb 12 13:17:35 leni systemd[1]: Installed new job systemd-logind.service/stop as 334
Feb 12 13:17:35 leni systemd-logind[219]: Failed to stop unit session-1.scope: Connection was disconnected before a reply was received
Feb 12 13:17:35 leni systemd-logind[219]: Failed to stop session scope: Connection was disconnected before a reply was received
Feb 12 13:17:35 leni systemd[1]: systemd-logind.service changed running -> stop-sigterm
Feb 12 13:17:35 leni systemd[1]: Received SIGCHLD from PID 219 (systemd-logind).
Feb 12 13:17:35 leni systemd[1]: Got SIGCHLD for process 219 (systemd-logind)
Feb 12 13:17:35 leni systemd[1]: Child 219 belongs to systemd-logind.service
Feb 12 13:17:35 leni systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Feb 12 13:17:35 leni systemd[1]: systemd-logind.service changed stop-sigterm -> failed
Feb 12 13:17:35 leni systemd[1]: Job systemd-logind.service/stop finished, result=done
Feb 12 13:17:35 leni systemd[1]: Unit systemd-logind.service entered failed state.
Back to top
View user's profile Send private message
ulenrich
Veteran
Veteran


Joined: 10 Oct 2010
Posts: 1374

PostPosted: Wed Feb 12, 2014 12:53 pm    Post subject: Reply with quote

Code:
Feb 12 13:16:05 leni systemd[1]: Got D-Bus request: org.freedesktop.DBus.Properties.GetAll() on /org/freedesktop/systemd1/unit/systemd_2dlogind_2eservice
Feb 12 13:17:35 leni systemd[1]: Installed new job systemd-logind.service/stop as 334

Do you have active a debug level for journal? (I don't see "Got D-Bus...")
Do you need more than one and a half minute to shutdown ?
Code:
Feb 12 03:14:18 maci polkitd[471]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.18, ob
Feb 12 03:14:19 maci kdm[614]: :0[614]: pam_unix(kde-np:session): session closed for user ral
Feb 12 03:14:20 maci kdm[614]: :0[614]: Abnormal termination of greeter for display :0, code 1, signal 0
Feb 12 03:14:20 maci kdm[614]: :0[614]: Abnormal greeter termination, code 1, sig 0
Feb 12 03:14:22 maci shutdown[1312]: shutting down for system halt
Feb 12 03:14:22 maci systemd-initctl[1314]: Received environment initctl request. This is not implemented in syste
Feb 12 03:14:22 maci systemd-logind[437]: Removed session 2.
Feb 12 03:14:19 maci kdm[614]: :0[614]: pam_unix(kde-np:session): session closed for user ral
Feb 12 03:14:20 maci kdm[614]: :0[614]: Abnormal termination of greeter for display :0, code 1, signal 0
Feb 12 03:14:20 maci kdm[614]: :0[614]: Abnormal greeter termination, code 1, sig 0
Feb 12 03:14:22 maci shutdown[1312]: shutting down for system halt
Feb 12 03:14:22 maci systemd-initctl[1314]: Received environment initctl request. This is not implemented in syste
Feb 12 03:14:22 maci systemd-logind[437]: Removed session 2.
Feb 12 03:14:22 maci systemd[625]: Stopping Default.
Feb 12 03:14:22 maci systemd[625]: Stopped target Default.
Feb 12 03:14:22 maci systemd[625]: Starting Shutdown.
Feb 12 03:14:22 maci systemd[625]: Reached target Shutdown.
Feb 12 03:14:22 maci systemd[625]: Starting Exit the Session...
Feb 12 03:14:22 maci systemd[596]: Stopping Default.
Feb 12 03:14:22 maci systemd[596]: Stopped target Default.
Feb 12 03:14:22 maci systemd[596]: Starting Shutdown.
Feb 12 03:14:22 maci systemd[596]: Reached target Shutdown.
Feb 12 03:14:22 maci systemd[596]: Starting Exit the Session...
... goes on a second unmounting all ....

_________________
fun2gen2
Back to top
View user's profile Send private message
trollo
n00b
n00b


Joined: 10 Sep 2004
Posts: 44
Location: Berlin

PostPosted: Wed Feb 12, 2014 1:14 pm    Post subject: Reply with quote

Yes, I had set LogLevel=debug, just in case. And no, shutdown merely takes a second or two. Sorry if this was confusing.

Code:
Feb 12 13:17:35 leni shutdown[561]: shutting down for system reboot
Feb 12 13:17:35 leni systemd[1]: Installed new job systemd-logind.service/stop as 334
Feb 12 13:17:35 leni systemd-logind[219]: Failed to stop unit session-1.scope: Connection was disconnected before a reply was received
Feb 12 13:17:35 leni systemd-logind[219]: Failed to stop session scope: Connection was disconnected before a reply was received
Feb 12 13:17:35 leni systemd[1]: systemd-logind.service changed running -> stop-sigterm
Feb 12 13:17:35 leni systemd[1]: Received SIGCHLD from PID 219 (systemd-logind).
Feb 12 13:17:35 leni systemd[1]: Got SIGCHLD for process 219 (systemd-logind)
Feb 12 13:17:35 leni systemd[1]: Child 219 belongs to systemd-logind.service
Feb 12 13:17:35 leni systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Feb 12 13:17:35 leni systemd[1]: systemd-logind.service changed stop-sigterm -> failed
Feb 12 13:17:35 leni systemd[1]: Job systemd-logind.service/stop finished, result=done
Feb 12 13:17:35 leni systemd[1]: Unit systemd-logind.service entered failed state.
Back to top
View user's profile Send private message
ulenrich
Veteran
Veteran


Joined: 10 Oct 2010
Posts: 1374

PostPosted: Wed Feb 12, 2014 1:32 pm    Post subject: Reply with quote

Beside we having different loglevels (I don't see new job dbus/stop - I will change to debug just to learn more about it)
What shutdown method do you use ?
/me : was shutdown from my user kde session - not kdm
I will try with logout kdm, login as root in a console and shutdown -h now

SeeYouLater
_________________
fun2gen2
Back to top
View user's profile Send private message
trollo
n00b
n00b


Joined: 10 Sep 2004
Posts: 44
Location: Berlin

PostPosted: Wed Feb 12, 2014 1:48 pm    Post subject: Reply with quote

ulenrich wrote:
shutdown -h now

is what I use, haven't installed X yet.
Back to top
View user's profile Send private message
ulenrich
Veteran
Veteran


Joined: 10 Oct 2010
Posts: 1374

PostPosted: Wed Feb 12, 2014 3:14 pm    Post subject: Reply with quote

Having changed to debug /etc/systemd/journald.conf
Code:
# ...
[Journal]
Storage=persistent
Compress=no
Seal=no
#SplitMode=login
SyncIntervalSec=12
RateLimitInterval=1m
RateLimitBurst=500
SystemMaxUse=444M
SystemKeepFree=111M
SystemMaxFileSize=6M
RuntimeMaxUse=256M
RuntimeKeepFree=64M
RuntimeMaxFileSize=128M
MaxRetentionSec=6days
MaxFileSec=4days
ForwardToSyslog=no
ForwardToKMsg=no
ForwardToConsole=yes
TTYPath=/dev/console
MaxLevelStore=debug
#MaxLevelSyslog=debug
MaxLevelKMsg=notice
MaxLevelConsole=info

I get after booted and rebooted from journalctl before --reboot, me login in as root to shutdown -r now:
Code:
Feb 12 15:52:04 maci login[605]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
Feb 12 15:52:04 maci login[608]: ROOT LOGIN  on '/dev/tty2'
Feb 12 15:52:04 maci systemd-logind[440]: New session 1 of user root.
Feb 12 15:52:04 maci systemd[606]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 12 15:52:04 maci systemd[606]: Failed to open private bus connection: Failed to connect to socket /run/user/0/
Feb 12 15:52:04 maci systemd[606]: Stopped target Sound Card.
Feb 12 15:52:04 maci systemd[606]: Stopped target Bluetooth.
Feb 12 15:52:04 maci systemd[606]: Starting Default.
Feb 12 15:52:04 maci systemd[606]: Reached target Default.
Feb 12 15:52:04 maci systemd[606]: Startup finished in 44ms.
Feb 12 15:52:51 maci shutdown[617]: shutting down for system reboot
Feb 12 15:52:52 maci systemd-initctl[619]: Received environment initctl request. This is not implemented in systemd.
Feb 12 15:52:52 maci systemd[606]: Stopping Default.
Feb 12 15:52:52 maci systemd[606]: Stopped target Default.
Feb 12 15:52:52 maci systemd[606]: Starting Shutdown.
Feb 12 15:52:52 maci systemd[606]: Reached target Shutdown.
Feb 12 15:52:52 maci systemd[606]: Starting Exit the Session...
Feb 12 15:52:52 maci systemd[1]: dhcpcd.service: main process exited, code=exited, status=1/FAILURE
Feb 12 15:52:52 maci dhcpcd[628]: sending signal 15 to pid 443
Feb 12 15:52:52 maci dhcpcd[628]: waiting for pid 443 to exit
Feb 12 15:52:52 maci dhcpcd[443]: received SIGTERM from PID 628, stopping
Feb 12 15:52:52 maci dhcpcd[443]: eth0: removing interface
Feb 12 15:52:52 maci dhcpcd[443]: wlan0: removing interface
Feb 12 15:52:52 maci dhcpcd[443]: wlan0: deleting route to 192.168.1.0/24
Feb 12 15:52:52 maci dhcpcd[443]: wlan0: deleting default route via 192.168.1.1
Feb 12 15:52:52 maci dhcpcd[443]: exited
Feb 12 15:52:52 maci kernel: wlan0: deauthenticating from 00:16:b6:c0:de:8a by local choice (reason=3)
Feb 12 15:52:52 maci kernel: cfg80211: Calling CRDA to update world regulatory domain
Feb 12 15:52:52 maci dhcpcd[628]: dhcpcd[628]: sending signal 15 to pid 443
Feb 12 15:52:52 maci dhcpcd[628]: dhcpcd[628]: waiting for pid 443 to exit
Feb 12 15:52:52 maci kernel: cfg80211: World regulatory domain updated:
Feb 12 15:52:52 maci kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Feb 12 15:52:52 maci systemd[1]: Unit dhcpcd.service entered failed state.
Feb 12 15:52:52 maci kernel: cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Feb 12 15:52:52 maci kernel: cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Feb 12 15:52:52 maci kernel: cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
Feb 12 15:52:52 maci kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
Feb 12 15:52:52 maci kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
Feb 12 15:52:52 maci kernel: cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
Feb 12 15:52:52 maci acpid[444]: exiting
Feb 12 15:52:52 maci systemd[1]: Shutting down.
Feb 12 15:52:52 maci systemd-journal[230]: Journal stopped
-- Reboot --

Remarks:
- I don't know what from this message when shutdown: systemd-initctl[619]: Received environment initctl request.
- my wifi network is setup by dhcpcd: putting /etc/wpa_supplicant.conf directly under /etc
then dhcpcd.service is able to super servcie wpa_supplicant on its own.
_________________
fun2gen2
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