[Solved]No active session with systemd-logind

I've read all the posts on the forum about sytemd and active sessions but I can't seem to get it working.
I'm on a up to date Arch, complete systemd. I'm using GDM as DM and latest version of Gnome.
Output of loginctl show-session $XDG_SESSION_ID
1 Id=2
2 Timestamp=Sun 2013-02-03 21:53:16 CET
3 TimestampMonotonic=14881075
4 DefaultControlGroup=name=systemd:/user/peter/2
5 VTNr=0
6 Display=:0
7 Remote=no
8 Service=gdm-password
9 Leader=2712
10 Audit=2
11 Type=x11
12 Class=user
13 Active=no
14 State=online
15 KillProcesses=no
16 IdleHint=no
17 IdleSinceHint=0
18 IdleSinceHintMonotonic=0
19 Name=peter
Output of systemctl list-unit-files |grep enabled
cups.path enabled
acpid.service enabled
chrony.service enabled
cronie.service enabled
cups.service enabled
dbus-org.freedesktop.NetworkManager.service enabled
display-manager.service enabled
dkms.service enabled
gdm.service enabled
[email protected] enabled
httpd.service enabled
lm_sensors.service enabled
mysqld.service enabled
NetworkManager.service enabled
postfix.service enabled
preload.service enabled
rsyslog.service enabled
syslog.service enabled
systemd-readahead-collect.service enabled
systemd-readahead-drop.service enabled
systemd-readahead-replay.service enabled
thinkfan.service enabled
tlp-init.service enabled
tomcat6.service enabled
[email protected] enabled
unload.service enabled
upower.service enabled
acpid.socket enabled
cups.socket enabled
remote-fs.target enabled
Output of ls -lR /etc/systemd/system
/etc/systemd/system:
total 52K
drwxr-xr-x 2 root root 4.0K Nov 1 22:52 cryptsetup.target.wants/
lrwxrwxrwx 1 root root 46 Sep 24 22:02 dbus-org.freedesktop.NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
drwxr-xr-x 2 root root 4.0K Feb 3 21:42 default.target.wants/
lrwxrwxrwx 1 root root 35 Jan 28 23:33 display-manager.service -> /usr/lib/systemd/system/gdm.service
drwxr-xr-x 2 root root 4.0K Nov 8 09:10 getty.target.wants/
drwxr-xr-x 2 root root 4.0K Nov 3 20:36 graphical.target.wants/
drwxr-xr-x 2 root root 4.0K Jan 13 16:58 local-fs.target.wants/
drwxr-xr-x 2 root root 4.0K Feb 3 21:42 multi-user.target.wants/
drwxr-xr-x 2 root root 4.0K Oct 9 09:49 printer.target.wants/
-rw-r--r-- 1 root root 216 Feb 3 21:09 rc-local.service
drwxr-xr-x 2 root root 4.0K Nov 7 23:28 shutdown.target.wants/
drwxr-xr-x 2 root root 4.0K Nov 3 20:43 sockets.target.wants/
drwxr-xr-x 2 root root 4.0K Jan 13 16:58 sysinit.target.wants/
lrwxrwxrwx 1 root root 39 Nov 3 20:39 syslog.service -> /usr/lib/systemd/system/rsyslog.service
drwxr-xr-x 2 root root 4.0K Feb 3 21:42 system-update.target.wants/
-rw-r--r-- 1 root root 166 Nov 7 23:28 unload.service
/etc/systemd/system/cryptsetup.target.wants:
total 0
lrwxrwxrwx 1 root root 42 Nov 1 22:52 [email protected] -> /usr/lib/systemd/system/[email protected]
/etc/systemd/system/default.target.wants:
total 0
lrwxrwxrwx 1 root root 57 Feb 3 21:42 systemd-readahead-collect.service -> /usr/lib/systemd/system/systemd-readahead-collect.service
lrwxrwxrwx 1 root root 56 Feb 3 21:42 systemd-readahead-replay.service -> /usr/lib/systemd/system/systemd-readahead-replay.service
/etc/systemd/system/getty.target.wants:
total 0
lrwxrwxrwx 1 root root 38 Nov 8 09:10 [email protected] -> /usr/lib/systemd/system/[email protected]
/etc/systemd/system/graphical.target.wants:
total 0
lrwxrwxrwx 1 root root 40 Sep 26 22:31 tlp-init.service -> /usr/lib/systemd/system/tlp-init.service
lrwxrwxrwx 1 root root 38 Nov 3 20:36 upower.service -> /usr/lib/systemd/system/upower.service
/etc/systemd/system/local-fs.target.wants:
total 0
/etc/systemd/system/multi-user.target.wants:
total 0
lrwxrwxrwx 1 root root 37 Nov 3 20:43 acpid.service -> /usr/lib/systemd/system/acpid.service
lrwxrwxrwx 1 root root 38 Nov 7 23:10 chrony.service -> /usr/lib/systemd/system/chrony.service
lrwxrwxrwx 1 root root 38 Sep 24 22:04 cronie.service -> /usr/lib/systemd/system/cronie.service
lrwxrwxrwx 1 root root 33 Oct 9 09:49 cups.path -> /usr/lib/systemd/system/cups.path
lrwxrwxrwx 1 root root 36 Oct 11 18:03 dkms.service -> /usr/lib/systemd/system/dkms.service
lrwxrwxrwx 1 root root 37 Sep 26 18:54 httpd.service -> /usr/lib/systemd/system/httpd.service
lrwxrwxrwx 1 root root 42 Jan 14 22:47 lm_sensors.service -> /usr/lib/systemd/system/lm_sensors.service
lrwxrwxrwx 1 root root 38 Nov 8 10:53 mysqld.service -> /usr/lib/systemd/system/mysqld.service
lrwxrwxrwx 1 root root 46 Sep 24 22:02 NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
lrwxrwxrwx 1 root root 39 Oct 3 12:00 postfix.service -> /usr/lib/systemd/system/postfix.service
lrwxrwxrwx 1 root root 39 Oct 1 23:21 preload.service -> /usr/lib/systemd/system/preload.service
lrwxrwxrwx 1 root root 40 Jan 13 16:58 remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
lrwxrwxrwx 1 root root 39 Nov 3 20:39 rsyslog.service -> /usr/lib/systemd/system/rsyslog.service
lrwxrwxrwx 1 root root 40 Sep 24 22:21 thinkfan.service -> /usr/lib/systemd/system/thinkfan.service
lrwxrwxrwx 1 root root 39 Oct 5 16:27 tomcat6.service -> /usr/lib/systemd/system/tomcat6.service
/etc/systemd/system/printer.target.wants:
total 0
lrwxrwxrwx 1 root root 36 Oct 9 09:49 cups.service -> /usr/lib/systemd/system/cups.service
/etc/systemd/system/shutdown.target.wants:
total 0
lrwxrwxrwx 1 root root 34 Nov 7 23:28 unload.service -> /etc/systemd/system/unload.service
/etc/systemd/system/sockets.target.wants:
total 0
lrwxrwxrwx 1 root root 36 Nov 3 20:43 acpid.socket -> /usr/lib/systemd/system/acpid.socket
lrwxrwxrwx 1 root root 35 Oct 9 09:49 cups.socket -> /usr/lib/systemd/system/cups.socket
/etc/systemd/system/sysinit.target.wants:
total 0
/etc/systemd/system/system-update.target.wants:
total 0
lrwxrwxrwx 1 root root 54 Feb 3 21:42 systemd-readahead-drop.service -> /usr/lib/systemd/system/systemd-readahead-drop.service
The solution posted here https://bbs.archlinux.org/viewtopic.php … 0#p1186900 with the rc.local compatubility service does work in a way. I created an empty rc.local file and made it executable. Now GDM is not starting until I hit CTRL-C, and after that my session is active!
I use the latest version of Polkit and initscripts is not installed.
Any tip is welcome!
Last edited by pgrond (2013-02-24 17:55:31)

I've read that post but I can't get it fixed. I don't need any rc-local compatibility. I'm on a complete systemd system, so I don't get why I would need this.
If I create a dummy rc-local service GDM won't start. But after a CTRL-C it will start and the session is active. Can it be some sort of race condition?
Or can it be a problem that my home partition is encrypted and mounted on login?

Similar Messages

[Solved] Numlock on boot (with systemd)

I recently upgraded to systemd. Everything is working extremely well. Except that I am given to understand that systemd no doesn't use /etc/inittab, where I had added the command from the wiki that turns on numlock on each of the virtual terminals. Unfortunately the wiki doesn't have any method to do it with systemd, only the /etc/inittab method.
This means that for a brief while, I had to live with the onerous task of hitting numlock manually. It was one of the worst weeks of my life. My index finger is still raw.
I have come up with a somewhat-solution. I just edited /etc/bash.bashrc and added
if [[ $( tty ) == /dev/tty? ]]; then
setleds +num
fi
to it, which works quite well. It turns on num lock once you're logged in as long as you are on a virtual terminal and not on one of the /dev/pts/* ones.
My question is, is there a better place to do this? Maybe some way to get it to turn on before you're even logged in? It doesn't really matter all that much, I'm just trying to make things "correct."
Last edited by scott_fakename (2012-09-06 20:29:46)

DSpider wrote:
https://wiki.archlinux.org/index.php/Ac … _on_Bootup
Set it in Xorg for whatever DE/WM you use and it will be active when you switch to a tty.
Don't forget to mark it as solved.
Yes, I tried that. I use lxdm and xfce, and setting the numlock=1 option in /etc/lxdm/lxdm.conf turns on numlock in xfce and the light in the consoles, but not the actual numlock itself in consoles.
And Kejpi thanks, I was doing that but when I upgraded to systemd it said those would be taken out "at some point" so I was trying to find out if a permanent solution existed yet. Apparently it does not exist yet, which is fine, I was just curious. So I guess I'll stick with the bashrc method for now.
Thanks for the replies.
--Scott

[Solved] Automating btrfs scrub with systemd

I have a single disk laptop (no RAID) and would like to have btrfs scrub run automatically on some interval and to be automatically emailed if any errors are found. (My data is backed up online and I can attempt a manual fix.) I'm trying to set this up with systemd and the btrfs tools. Here's what I figure I need:
A systemd service to run btrfs scrub on my entire filesystem.
A systemd timer to schedule this job weekly.
systemd services to pause and resume a running btrfs scrub when the machine suspends and wakes up.
A script to run btrfs status when the previous service has finished, parse the output for the number of errors, and email me if the number is greater than 0.
A systemd service to run that script when the scrub service has completed.
What I have so far is below. I'm sure there are problems with it all, and I'm especially uncertain about #5, since I don't know if the After attribute of one service waits until another has completed or just started. If anyone could take a look and give me some pointers I'd appreciate it very much. (The python script is a hack but I'm more concerned with the systemd at the moment, unless you see obvious problems or improvements you'd like to suggest.)
Attempt at 1 and 2:
/etc/systemd/system/btrfs_scrub.service
[Unit]
Description=Run btrfs scrub on filesystem
[Service]
Type=forking
ExecStart=btrfs scrub start /home
/etc/systemd/system/btrfs_scrub.timer
[Unit]
Description=Weekly btrfs scrub
[Timer]
OnCalendar=weekly
Persistent=true
[Install]
WantedBy=timers.target
Attempt at 3:
/etc/systemd/system/btrfs_cancel.service
[Unit]
Description=Pause a running btrfs scrub on suspend
Before=suspend.target
[Service]
Type=oneshot
ExecStart=btrfs scrub cancel /home
[Install]
WantedBy=suspend.target
/etc/systemd/system/btrfs_resume.service
[Unit]
Description=Resume a paused btrfs scrub after suspend
After=suspend.target
[Service]
Type=oneshot
ExecStart=btrfs scrub resume /home
[Install]
WantedBy=suspend.target
Attempt at 4:
/home/username/Code/Scripts/btrfs_results.py
#Runs btrfs scrub and looks for an indication of errors found, upon
#which an email is sent.
import subprocess
import smtplib
from email.mime.text import MIMEText
def email_alert():
text = "btrfs scrub found errors"
addr = 'myemail@address'
username = 'myusername'
password = 'mypassword'
msg = MIMEText(text)
msg['Subject'] = 'btrfs errors'
msg['From'] = addr
msg['To'] = addr
server = smtplib.SMTP('smtp.gmail.com', '587')
server.starttls()
server.login(username,password)
server.sendmail(addr, addr, msg.as_string())
server.quit()
print('email sent')
def main():
cmd = ['btrfs', 'scrub', 'status', '/home']
output = subprocess.check_output(cmd)
output_str = output.decode("utf-8")
output_words = output_str.split(' ')
for w in range(0, len(output_words)):
if output_words[w].find('error') > -1:
if int(output_words[w - 1]) > 0:
email_alert()
main()
Attempt at 5:
/etc/systemd/system/btrfs_results.service
[Unit]
Description=Parse output from btrfs scrub
Requires=btrfs_scrub.service
After=btrfs_scrub.service
[Service]
Type=oneshot
ExecStart=/usr/bin/python /home/username/Code/Scripts/btrfs_results.py
[Install]
WantedBy=multi-user.target
Last edited by 0112358 (2014-09-16 01:26:21)

0112358 wrote:I have a single disk laptop (no RAID) and would like to have btrfs scrub run automatically on some interval and to be automatically emailed if any errors are found. (My data is backed up online and I can attempt a manual fix.) I'm trying to set this up with systemd and the btrfs tools. Here's what I figure I need:
0112358 wrote:
A systemd service to run btrfs scrub on my entire filesystem.
A systemd timer to schedule this job weekly.
Should not be hard.
0112358 wrote:systemd services to pause and resume a running btrfs scrub when the machine suspends and wakes up.
This happens automatically with s2disk. Am I missing something?
0112358 wrote:A script to run btrfs status when the previous service has finished, parse the output for the number of errors, and email me if the number is greater than 0.
You might want to integrate that in the main btrfs scrub script, just after scrub is completed you will run this. Right?
0112358 wrote:A systemd service to run that script when the scrub service has completed.
0112358 wrote: What I have so far is below. I'm sure there are problems with it all, and I'm especially uncertain about #5, since I don't know if the After attribute of one service waits until another has completed or just started. If anyone could take a look and give me some pointers I'd appreciate it very much. (The python script is a hack but I'm more concerned with the systemd at the moment, unless you see obvious problems or improvements you'd like to suggest.)
0112358 wrote:
Attempt at 1 and 2:
/etc/systemd/system/btrfs_scrub.service
[Unit]
Description=Run btrfs scrub on filesystem
[Service]
Type=forking
ExecStart=btrfs scrub start /home
/etc/systemd/system/btrfs_scrub.timer
[Unit]
Description=Weekly btrfs scrub
[Timer]
OnCalendar=weekly
Persistent=true
[Install]
WantedBy=timers.target
Yes, why not wrap this in some sort of main bash (or python) script.
0112358 wrote:
Attempt at 3:
/etc/systemd/system/btrfs_cancel.service
[Unit]
Description=Pause a running btrfs scrub on suspend
Before=suspend.target
[Service]
Type=oneshot
ExecStart=btrfs scrub cancel /home
[Install]
WantedBy=suspend.target
/etc/systemd/system/btrfs_resume.service
[Unit]
Description=Resume a paused btrfs scrub after suspend
After=suspend.target
[Service]
Type=oneshot
ExecStart=btrfs scrub resume /home
[Install]
WantedBy=suspend.target
Why not do nothing at all? Just let the fs continue after resume. Or is s2disk cancelling this process?
0112358 wrote:
Attempt at 4:
/home/username/Code/Scripts/btrfs_results.py
#Runs btrfs scrub and looks for an indication of errors found, upon
#which an email is sent.
import subprocess
import smtplib
from email.mime.text import MIMEText
def email_alert():
text = "btrfs scrub found errors"
addr = 'myemail@address'
username = 'myusername'
password = 'mypassword'
msg = MIMEText(text)
msg['Subject'] = 'btrfs errors'
msg['From'] = addr
msg['To'] = addr
server = smtplib.SMTP('smtp.gmail.com', '587')
server.starttls()
server.login(username,password)
server.sendmail(addr, addr, msg.as_string())
server.quit()
print('email sent')
def main():
cmd = ['btrfs', 'scrub', 'status', '/home']
output = subprocess.check_output(cmd)
output_str = output.decode("utf-8")
output_words = output_str.split(' ')
for w in range(0, len(output_words)):
if output_words[w].find('error') > -1:
if int(output_words[w - 1]) > 0:
email_alert()
main()
Ok
0112358 wrote:
Attempt at 5:
/etc/systemd/system/btrfs_results.service
[Unit]
Description=Parse output from btrfs scrub
Requires=btrfs_scrub.service
After=btrfs_scrub.service
[Service]
Type=oneshot
ExecStart=/usr/bin/python /home/username/Code/Scripts/btrfs_results.py
[Install]
WantedBy=multi-user.target
Yeah, why not wrap 1,2,4 and 5 into one script/service. Why the fine granularity?

[SOLVED] Problem with acpid and systemd-logind

Hi, I have the following problem: I want set an action, when power button is pushed, different from shutdown and I want do this with a rule in acpid. Before set a rule in acpid, I modified the /etc/systemd/logind.conf in the following way:
HandlePowerKey=ignore
HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=ignore
Of course I restart systemd-logind service.
After this, I run #acpi_listen and when I press the power button, the output is the following:
button/power PBTN 00000080 00000000
button/power LNXPWRBN:00 00000080 00000008
So at this point, with reference to arch wiki, I tried to set the acpid rule with a modify the /etc/acpi/handler.sh in this way:
#!/bin/bash
# Default acpi script that takes an entry for all actions
case "$1" in
button/power)
case "$2" in
PBTN)
notify-send "this is a test message"
logger 'Power button pressed'
esac
esac
Because with this setting doesn't happens nothing, I tried the alternative configuration suggested in the arch wiki, So I create a file in /etc/acpi/events/power with this content:
event=button/power
action=/etc/acpi/actions/power.sh "%e"
where power.sh has this content:
#!/bin/bash
notify-send "this is a test message"
but also in the way when I push the power button doesn't happens nothing. Can you help me?
P.S. I try to restart both service systemd-logind and acpid but the result is the same
Last edited by pepib (2015-03-09 12:07:27)

In the handler.sh script I put the getuser function and I modified the handler.sh as following:
case "$1" in
button/power)
case "$2" in
PBTN)
getuser notify-send "this is a test message"
but it continued to doesn't working. So at this point at place of getuser function I tried to put the
export XAUTHORITY="/home/user/.Xauthority"
export DISPLAY=":0.0"
but it doesn't working. Fortunately, at the end I find this possible solution http://goo.gl/Lq4TsY that use uacpid. What was the problem? Where I wrong?

[SOLVED] Can not shutdown/restart from KDE with systemd

Hello,
Recently, following I switched to a pure systemd setup. The process was simple and most things worked "right out of the bpx". However, I can not shutdown or restart from KDE!
Let's say that I do the 3 finger salute (ALT-CTRL-DEL) and select "Turn off computer" what I get is KDE shutting down, but then I will only get a console (TTY) login prompt. Pressing ALT-CTRL-DEL then will trigger a reboot. I can also login and use "systemctl poweroff". However, I don't understand why it doesn't work straight from KDE.
Are there some packages I must install? Are there some systemd services that I must enable? What other relevant info should I include in this post?
Active units :
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
proc-sys...misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount Point
sys-devi...d-card0.device loaded active plugged MCP79 High Definition Audio
sys-devi...da-sda1.device loaded active plugged ST9500420ASG
sys-devi...da-sda2.device loaded active plugged ST9500420ASG
sys-devi...da-sda3.device loaded active plugged ST9500420ASG
sys-devi...da-sda4.device loaded active plugged ST9500420ASG
sys-devi...da-sda5.device loaded active plugged ST9500420ASG
sys-devi...da-sda6.device loaded active plugged ST9500420ASG
sys-devi...ock-sda.device loaded active plugged ST9500420ASG
sys-devi...et-eth0.device loaded active plugged RTL8111/8168B PCI Express Gigabit Ethernet controller
sys-devi...t-wlan0.device loaded active plugged AR928X Wireless Network Adapter (PCI-Express)
sys-devi...y-ttyS0.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS0
sys-devi...y-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1
sys-devi...y-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2
sys-devi...y-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3
sys-module-fuse.device loaded active plugged /sys/module/fuse
-.mount loaded active mounted /
dev-hugepages.mount loaded active mounted Huge Pages File System
dev-mqueue.mount loaded active mounted POSIX Message Queue File System
home.mount loaded active mounted /home
run-user-1000-gvfs.mount loaded active mounted /run/user/1000/gvfs
sys-fs-f...nections.mount loaded active mounted FUSE Control File System
sys-kernel-debug.mount loaded active mounted Debug File System
tmp.mount loaded active mounted /tmp
cups.path loaded active waiting CUPS Printer Service Spool
systemd-...d-console.path loaded active waiting Dispatch Password Requests to Console Directory Watch
systemd-...word-wall.path loaded active waiting Forward Password Requests to Wall Directory Watch
bluetooth.service loaded active running Bluetooth service
colord-sane.service loaded active running Daemon for monitoring attached scanners and registering them with colord
colord.service loaded active running Manage, Install and Generate Color Profiles
console-...daemon.service loaded active running Console Manager
console-...-start.service loaded active exited Console System Startup Logging
cups.service loaded active running CUPS Printing Service
dbus.service loaded active running D-Bus System Message Bus
[email protected] loaded active running Getty on tty1
kdm.service loaded active running K Display Manager
NetworkManager.service loaded active running Network Manager
sshd.service loaded active running OpenSSH Daemon
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-...s-load.service loaded active exited Load Kernel Modules
systemd-...unt-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-...-setup.service loaded active exited Recreate Volatile Files and Directories
systemd-...rigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-...ssions.service loaded active exited Permit User Sessions
systemd-...-setup.service loaded active exited Setup Virtual Console
udisks2.service loaded active running Storage Daemon
upower.service loaded active running Daemon for power management
wpa_supplicant.service loaded active running WPA supplicant
cups.socket loaded active running CUPS Printing Service Sockets
dbus.socket loaded active running D-Bus System Message Bus Socket
systemd-initctl.socket loaded active listening /dev/initctl Compatibility Named Pipe
systemd-journald.socket loaded active running Journal Socket
systemd-shutdownd.socket loaded active listening Delayed Shutdown Socket
systemd-...control.socket loaded active listening udev Control Socket
systemd-...-kernel.socket loaded active running udev Kernel Socket
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
network.target loaded active active Network
remote-fs.target loaded active active Remote File Systems
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
systemd-...es-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
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.
JOB = Pending job for the unit.
72 units listed. Pass --all to see inactive units, too.
Last edited by Prozzaks (2012-08-20 17:35:48)

Demon wrote:For me the system only halts, it does not poweroff. How I can solve this?
As bgc1954 said, there is also a symlink "/sbin/poweroff". Just edit the file "/usr/share/config/kdm/kdmrc", go to [shutdown] an replace the line "HaltCmd=/sbin/halt" with "HaltCmd=/sbin/poweroff".

Systemd-logind - no session created

I had no problems switching to systemd on my machine, but on another with a similar setup there is the following problem.
After logining in, there is no systemd-logind session, meaning no permissions for automounting etc. Env. variables XDG_SESSION_ID and XDG_VTNR are empty, loginctl does not show session 1.
$ journalctl -b | grep -i login
systemd[1]: Starting Login Service...
systemd-logind[855]: New seat seat0.
systemd[1]: Started Login Service.
systemd[1]: Starting Login Prompts.
systemd[1]: Reached target Login Prompts.
login[975]: pam_unix(login:session): session opened for user joe by LOGIN(uid=0)
login[975]: LOGIN ON tty1 BY joe
systemd-logind[855]: New session 2 of user sawyer.
In the above, the last line is from my ssh session, but I am missing a similar one for session 1 after the login from tty.
$ loginctl
SESSION UID USER SEAT
2 1000 sawyer
1 sessions listed.
Note that the user was still logged in when the above was ran.
Any ideas on how to tackle the problem? I followed the wiki to transition to systemd, and as mentioned did the same on my computer before and everything works for me.

Same kind of problem here ...
Setup:
/etc/systemd/system/
├── dbus-org.freedesktop.Avahi.service -> /usr/lib/systemd/system/avahi-daemon.service
├── default.target -> /usr/lib/systemd/system/multi-user.target
├── getty.target.wants
│   └── [email protected] -> /usr/lib/systemd/system/[email protected]
├── graphical.target.wants
├── multi-user.target.wants
│   ├── avahi-daemon.service -> /usr/lib/systemd/system/avahi-daemon.service
│   ├── netcfg.service -> /usr/lib/systemd/system/netcfg.service
│   ├── remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
│   ├── sshd.service -> /usr/lib/systemd/system/sshd.service
│   └── sshdgenkeys.service -> /usr/lib/systemd/system/sshdgenkeys.service
└── sockets.target.wants
└── avahi-daemon.socket -> /usr/lib/systemd/system/avahi-daemon.socket
When I log from tty1, logintcl shows noting, but when I log from ssh I do get a
session in loginctl.
I've re-installed arch on a vm just to check what's going on
On the vm, I do get a login session, and the logs say:
$ journalct -b | grep login
Mar 16 13:40:32 arch systemd-logind[164]: Watching system buttons on /dev/input/event3 (Power Button)
Mar 16 13:40:32 arch systemd-logind[164]: Watching system buttons on /dev/input/event4 (Sleep Button)
Mar 16 13:40:32 arch systemd-logind[164]: New seat seat0.
Mar 16 13:40:32 arch systemd-logind[164]: Watching system buttons on /dev/input/event3 (Power Button)
Mar 16 13:40:32 arch systemd-logind[164]: Watching system buttons on /dev/input/event4 (Sleep Button)
Mar 16 13:40:43 arch login[166]: pam_unix(login:session): session opened for user yannick by LOGIN(uid=0)
Mar 16 13:40:43 arch systemd-logind[164]: New session 1 of user yannick.
On my box the logs say:
Mar 16 15:26:49 bermudes systemd-logind[975]: Watching system buttons on /dev/input/event3 (Power Button)
Mar 16 15:26:49 bermudes systemd-logind[975]: Watching system buttons on /dev/input/event5 (Video Bus)
Mar 16 15:26:49 bermudes systemd-logind[975]: Watching system buttons on /dev/input/event0 (Power Button)
Mar 16 15:26:49 bermudes systemd-logind[975]: Watching system buttons on /dev/input/event1 (Lid Switch)
Mar 16 15:26:49 bermudes systemd-logind[975]: Watching system buttons on /dev/input/event2 (Sleep Button)
So for some reason on my box the seat does not even get created ...
edit: solved for me Turned out I changed /etc/pam.d/login back in 2011 and never merged in with /etc/pam.d/login.pacnew.
For reference, here's the /etc/pam.d/login that did the trick
auth required pam_securetty.so
auth requisite pam_nologin.so
auth include system-local-login
account include system-local-login
session include system-local-login
@sawyer: maybe you should look at your .pacnew files too, or ask for help on #systemd irc channel
Last edited by Yannick_LM (2013-03-16 14:26:04)

[Solved] postgresql with systemd

Hello Guys,
I'm having problems starting the postgres with systemd.
Following errors:
Running systemctl start postgresql
k@archK ~ % sudo systemctl start postgresql
Job for postgresql.service failed. See 'systemctl status postgresql.service' and 'journalctl -xn' for details.
1 k@archK ~ %
Running systemctl status postgresql.service got the message below:
k@archK ~ % systemctl status postgresql.service
postgresql.service - PostgreSQL database server
Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled)
Active: failed (Result: exit-code) since Sáb, 2012-12-29 19:09:19 BRT; 1min 19s ago
Process: 1746 ExecStart=/usr/bin/pg_ctl -s -D ${PGROOT}/data start -w -t 120 (code=exited, status=1/FAILURE)
Process: 1741 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGROOT}/data (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/postgresql.service
3 k@archK ~ %
and journalctl -xn this:
k@archK ~ % sudo journalctl -xn
[sudo] password for k:
-- Logs begin at Sáb, 2012-12-29 03:47:42 BRT, end at Sáb, 2012-12-29 19:11:49 BRT. --
Dez 29 19:09:19 archK systemd[1]: postgresql.service: control process exited, code=exited status=1
Dez 29 19:09:19 archK systemd[1]: Failed to start PostgreSQL database server.
-- Subject: Unit postgresql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
-- Unit postgresql.service has failed.
-- The result is failed.
Dez 29 19:09:19 archK systemd[1]: Unit postgresql.service entered failed state
Dez 29 19:09:19 archK sudo[1738]: pam_unix(sudo:session): session closed for user root
Dez 29 19:11:27 archK udisks-daemon[430]: **** Refreshing ATA SMART data for /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
Dez 29 19:11:27 archK udisks-daemon[430]: helper(pid 1781): launched job udisks-helper-ata-smart-collect on /dev/sda
Dez 29 19:11:28 archK udisks-daemon[430]: helper(pid 1781): completed with exit code 0
Dez 29 19:11:28 archK udisks-daemon[430]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
Dez 29 19:11:49 archK sudo[1786]: k : TTY=pts/0 ; PWD=/home/k ; USER=root ; COMMAND=/usr/bin/journalctl -xn
Dez 29 19:11:49 archK sudo[1786]: pam_unix(sudo:session): session opened for user root by k(uid=0)
Here is the postgresql.service
[Unit]
Description=PostgreSQL database server
After=network.target
[Service]
Type=forking
TimeoutSec=120
User=postgres
Group=postgres
Environment=PGROOT=/var/lib/postgres
SyslogIdentifier=postgres
PIDFile=/var/lib/postgres/data/postmaster.pid
ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGROOT}/data
ExecStart= /usr/bin/pg_ctl -s -D ${PGROOT}/data start -w -t 120
ExecReload=/usr/bin/pg_ctl -s -D ${PGROOT}/data reload
ExecStop= /usr/bin/pg_ctl -s -D ${PGROOT}/data stop -m fast
# Due to PostgreSQL's use of shared memory, OOM killer is often overzealous in
# killing Postgres, so adjust it downward
OOMScoreAdjust=-200
[Install]
WantedBy=multi-user.target
and /etc/conf.d/postgresql
## Parameters to be passed to postgresql
## Default data directory location
PGROOT="/var/lib/postgres"
## Passed to initdb if necessary
INITOPTS="--locale en_US.UTF-8"
## Default log file location
#PGLOG="/var/log/postgresql.log"
## Additional options to pass via pg_ctl's '-o' option
#PGOPTS=""
Does anyone have any idea how to fix this?
Thanks.
Last edited by kleitonkk (2013-01-03 23:51:41)

Sorry for the delay, was traveling and just returned yesterday.
lothar_m was followed as described in the post, since removed the packages twice and did the install again but the same error.
[root@archK conf.d]# systemctl start postgresql
Job for postgresql.service failed. See 'systemctl status postgresql.service' and 'journalctl -xn' for details.
[root@archK conf.d]#
systemctl status postgresql.service
➜ ~ systemctl status postgresql.service
postgresql.service - PostgreSQL database server
Loaded: loaded (/usr/lib/systemd/system/postgresql.service; disabled)
Active: failed (Result: exit-code) since Thu, 2013-01-03 18:14:43 BRT; 9min ago
Process: 10897 ExecStart=/usr/bin/pg_ctl -s -D ${PGROOT}/data start -w -t 120 (code=exited, status=1/FAILURE)
Process: 10892 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGROOT}/data (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/postgresql.service
➜ ~
[root@archK conf.d]# journalctl -xn
-- Logs begin at Wed, 2013-01-02 16:50:57 BRT, end at Thu, 2013-01-03 18:34:41 BRT. --
Jan 03 18:25:28 archK su[11082]: pam_unix(su:session): session opened for user root by k(uid=1000)
Jan 03 18:34:36 archK systemd[1]: Starting PostgreSQL database server...
-- Subject: Unit postgresql.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/7d4958e842da4a758f6c1cdc7b36dcc5
-- Unit postgresql.service has begun starting up.
Jan 03 18:34:36 archK postgres[11127]: LOG: could not translate host name "localhost", service "5432" to address: Name or service not known
Jan 03 18:34:36 archK postgres[11127]: WARNING: could not create listen socket for "localhost"
Jan 03 18:34:36 archK postgres[11127]: FATAL: could not create any TCP/IP sockets
Jan 03 18:34:41 archK postgres[11127]: pg_ctl: could not start server
Jan 03 18:34:41 archK postgres[11127]: Examine the log output.
Jan 03 18:34:41 archK systemd[1]: postgresql.service: control process exited, code=exited status=1
Jan 03 18:34:41 archK systemd[1]: Failed to start PostgreSQL database server.
-- Subject: Unit postgresql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
-- Unit postgresql.service has failed.
-- The result is failed.
Jan 03 18:34:41 archK systemd[1]: Unit postgresql.service entered failed state
/usr/lib/systemd/system/postgresql.service
[Unit]
Description=PostgreSQL database server
After=network.target
[Service]
Type=forking
TimeoutSec=120
User=postgres
Group=postgres
Environment=PGROOT=/var/lib/postgres
SyslogIdentifier=postgres
PIDFile=/var/lib/postgres/data/postmaster.pid
ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGROOT}/data
ExecStart= /usr/bin/pg_ctl -s -D ${PGROOT}/data start -w -t 120
ExecReload=/usr/bin/pg_ctl -s -D ${PGROOT}/data reload
ExecStop= /usr/bin/pg_ctl -s -D ${PGROOT}/data stop -m fast
# Due to PostgreSQL's use of shared memory, OOM killer is often overzealous in
# killing Postgres, so adjust it downward
OOMScoreAdjust=-200
[Install]
WantedBy=multi-user.target
➜ ~ pacman -Q |grep postgres
postgresql 9.2.2-2
postgresql-libs 9.2.2-2
➜ ~
/etc/conf.d
## Parameters to be passed to postgresql
## Default data directory location
PGROOT="/var/lib/postgres"
## Passed to initdb if necessary
INITOPTS="--locale en_US.UTF-8"
## Default log file location
#PGLOG="/var/log/postgresql.log"
## Additional options to pass via pg_ctl's '-o' option
#PGOPTS=""
/usr/lib/systemd/system/postgresql.service
[Unit]
Description=PostgreSQL database server
After=network.target
[Service]
Type=forking
TimeoutSec=120
User=postgres
Group=postgres
Environment=PGROOT=/var/lib/postgres
SyslogIdentifier=postgres
PIDFile=/var/lib/postgres/data/postmaster.pid
ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGROOT}/data
ExecStart= /usr/bin/pg_ctl -s -D ${PGROOT}/data start -w -t 120
ExecReload=/usr/bin/pg_ctl -s -D ${PGROOT}/data reload
ExecStop= /usr/bin/pg_ctl -s -D ${PGROOT}/data stop -m fast
# Due to PostgreSQL's use of shared memory, OOM killer is often overzealous in
# killing Postgres, so adjust it downward
OOMScoreAdjust=-200
[Install]
WantedBy=multi-user.target
I'm still looking for how to solve.
Thank you.

Got systemd-logind: failed to get session: when optirun glxgrears

I installed nvidia and bumblebee, primus.
When I tried to test optirun, I ran
optirun glxgrears -info
Then I got this,
[ 2376.692764] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) systemd-logind: failed to get session: PID 1540 does not belong to any known session
[ 2376.692829] [ERROR]Aborting because fallback start is disabled.
Here is my /var/log/Xorg.8.log ,
[ 2376.692764] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) systemd-logind: failed to get session: PID 1540 does not belong to any known session
[ 2376.692829] [ERROR]Aborting because fallback start is disabled.
[hk@hkpc ~]$ cat /var/log/Xorg.8.log
[ 2376.682]
X.Org X Server 1.16.0
Release Date: 2014-07-16
[ 2376.682] X Protocol Version 11, Revision 0
[ 2376.682] Build Operating System: Linux 3.15.5-2-ARCH x86_64
[ 2376.682] Current Operating System: Linux hkpc 3.15.8-1-ARCH #1 SMP PREEMPT Fri Aug 1 08:51:42 CEST 2014 x86_64
[ 2376.682] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=669c53af-9ee3-4bbf-b62f-14c76e81da89 rw quiet
[ 2376.682] Build Date: 31 July 2014 11:53:19AM
[ 2376.682]
[ 2376.682] Current version of pixman: 0.32.6
[ 2376.682] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2376.682] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2376.683] (==) Log file: "/var/log/Xorg.8.log", Time: Mon Aug 4 22:39:09 2014
[ 2376.683] (++) Using config file: "/etc/bumblebee/xorg.conf.nouveau"
[ 2376.683] (++) Using config directory: "/etc/bumblebee/xorg.conf.d"
[ 2376.683] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 2376.683] (==) ServerLayout "Layout0"
[ 2376.683] (==) No screen section available. Using defaults.
[ 2376.683] (**) |-->Screen "Default Screen Section" (0)
[ 2376.683] (**) | |-->Monitor "<default monitor>"
[ 2376.683] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 2376.683] (**) | |-->Device "DiscreteNvidia"
[ 2376.683] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 2376.683] (**) Option "AutoAddDevices" "false"
[ 2376.683] (**) Option "AutoAddGPU" "false"
[ 2376.683] (**) Not automatically adding devices
[ 2376.683] (==) Automatically enabling devices
[ 2376.683] (**) Not automatically adding GPU devices
[ 2376.683] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 2376.683] Entry deleted from font path.
[ 2376.683] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 2376.683] Entry deleted from font path.
[ 2376.683] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 2376.683] Entry deleted from font path.
[ 2376.683] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 2376.683] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 2376.683] Entry deleted from font path.
[ 2376.683] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 2376.683] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/
[ 2376.683] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2376.683] (==) |-->Input Device "<default pointer>"
[ 2376.684] (==) |-->Input Device "<default keyboard>"
[ 2376.684] (==) The core pointer device wasn't specified explicitly in the layout.
Using the default mouse configuration.
[ 2376.684] (==) The core keyboard device wasn't specified explicitly in the layout.
Using the default keyboard configuration.
[ 2376.684] (II) Loader magic: 0x818d80
[ 2376.684] (II) Module ABI versions:
[ 2376.684] X.Org ANSI C Emulation: 0.4
[ 2376.684] X.Org Video Driver: 18.0
[ 2376.684] X.Org XInput driver : 21.0
[ 2376.684] X.Org Server Extension : 8.0
[ 2376.685] (EE) systemd-logind: failed to get session: PID 2304 does not belong to any known session
[ 2376.686] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 2376.686] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 2376.686] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
[ 2376.688] (--) PCI:*(0:1:0:0) 10de:0fd4:1558:3700 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 2376.688] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 2376.688] (II) LoadModule: "glx"
[ 2376.688] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2376.690] (II) Module glx: vendor="X.Org Foundation"
[ 2376.690] compiled for 1.16.0, module version = 1.0.0
[ 2376.690] ABI class: X.Org Server Extension, version 8.0
[ 2376.690] (==) AIGLX enabled
[ 2376.690] (II) LoadModule: "nouveau"
[ 2376.690] (WW) Warning, couldn't open module nouveau
[ 2376.690] (II) UnloadModule: "nouveau"
[ 2376.690] (II) Unloading nouveau
[ 2376.690] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 2376.690] (II) LoadModule: "mouse"
[ 2376.691] (WW) Warning, couldn't open module mouse
[ 2376.691] (II) UnloadModule: "mouse"
[ 2376.691] (II) Unloading mouse
[ 2376.691] (EE) Failed to load module "mouse" (module does not exist, 0)
[ 2376.691] (II) LoadModule: "kbd"
[ 2376.691] (WW) Warning, couldn't open module kbd
[ 2376.691] (II) UnloadModule: "kbd"
[ 2376.691] (II) Unloading kbd
[ 2376.691] (EE) Failed to load module "kbd" (module does not exist, 0)
[ 2376.691] (EE) No drivers available.
[ 2376.691] (EE)
Fatal server error:
[ 2376.691] (EE) no screens found(EE)
[ 2376.691] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 2376.691] (EE) Please also check the log file at "/var/log/Xorg.8.log" for additional information.
What should I do?

barchiesi wrote:
Oedner wrote:after updating to linux 3.16 i got this error too. using the command without the -info works however.
Are you sure that it only doesn't work with the '-info'? I see no difference.
i just tried it a couple of times and it looks like its completely random o.O
you are right, using it (with or without -info) only works like every third attempt while the others throw the error mentioned by the op. i got that idea because it worked when i tried it. starting nvidia-settings with optirun is the same, error, working, error, working. can't say whats the problem here, i just switched to arch again recently.

[SOLVED] samba does not start properly again -this time with systemd

Definitely no luck with this one...
So, today I've switched to a pure systemd init system, and noticed that I have this old issue again.
(Link to my old thread: https://bbs.archlinux.org/viewtopic.php?id=142704)
Samba doesn't start properly again, more precisely smbd is launched but not nmbd, so samba is not working as it should (for example smbtreee lists nothing).
Last time I've solved it by putting samba long before networkmanager in the daemons array, but with systemd I'm a bit confused...
Anyone has this issue?
Last edited by scar (2012-11-03 07:05:42)

I think that nmbd isn't waiting for networkmanager to start on my system, because I'm getting journal entries like
Oct 31 00:47:21 spacebar winbindd[431]: [2012/10/31 00:47:21.556005, 0] param/loadparm.c:7969(lp_do_parameter)
Oct 31 00:47:21 spacebar systemd[1]: nmbd.service: main process exited, code=exited, status=1
Oct 31 00:47:21 spacebar systemd[1]: Unit nmbd.service entered failed state.
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> (eth0): carrier now ON (device state 20)
Oct 31 00:47:22 spacebar kernel: r8169 0000:03:00.0: eth0: link up
Oct 31 00:47:22 spacebar kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Auto-activating connection 'Static'.
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) starting connection 'Static'
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started...
Oct 31 00:47:22 spacebar rpc.mountd[462]: Version 1.2.6 starting
Oct 31 00:47:22 spacebar systemd[1]: Startup finished in 3s 850ms 155us (kernel) + 21s 279ms 972us (userspace) = 25s 130ms 127us.
Oct 31 00:47:23 spacebar NetworkManager[391]: <info> (eth0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Oct 31 00:47:23 spacebar ntpd_intres[441]: DNS 0.au.pool.ntp.org -> 116.66.160.39
Oct 31 00:47:23 spacebar NetworkManager[391]: <info> Policy set 'Static' (eth0) as default for IPv4 routing and DNS.
Oct 31 00:47:23 spacebar NetworkManager[391]: <info> Activation (eth0) successful, device activated.
Oct 31 00:47:23 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete.
Oct 31 00:47:23 spacebar dbus[401]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Oct 31 00:47:20 spacebar smbd[428]: [2012/10/31 00:47:20.771872, 0] param/loadparm.c:7969(lp_do_parameter)
Oct 31 00:47:20 spacebar smbd[428]: Ignoring unknown parameter "user client driver"
Oct 31 00:47:20 spacebar smbd[428]: [2012/10/31 00:47:20.794252, 0] lib/interface.c:543(load_interfaces)
Oct 31 00:47:20 spacebar smbd[428]: WARNING: no network interfaces found
Oct 31 00:47:20 spacebar smbd[428]: [2012/10/31 00:47:20.805126, 0] smbd/server.c:1109(main)
Oct 31 00:47:20 spacebar smbd[428]: standard input is not a socket, assuming -D option
Oh, this started happening after putting a MUCH faster cpu and motherboard in the system, so maybe there's a race-condition there?
Last edited by MisterAnderson (2012-10-30 04:59:46)

[Solved]I deleted /etc/systemd/logind.conf by mistake

I deleted /etc/systemctl/logind.conf by mistake with
sudo rm /etc/systemd/logind.conf
How can I get that file back?
Last edited by aaa234 (2015-06-07 10:26:56)

it's ok now, I reinstalled it with
sudo pacman -S systemd
The problem is solved, thank u so much everyone.

[solved] What makes systemd-logind.service fail?

After last update made yesterday I was unable to reboot. With the help of an installation cd and chrooting I disabled my graphical login manager lxdm which, when started, seems to do nothing and the system is stuck.
Without lxdm service enabled, I can start xfce4 with
startxfce4
from commandline and everything seems to run fine.
But the booting process gives me several messages telling that the service systemd-logind failed. Apart from the virtual console created while booting and the one running X11 there is no other one (no login prompt when pressing strg+alt f3 e.g.)
[root@amd64-archlinux ~]# systemctl status systemd-logind
● systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
Active: failed (Result: start-limit) since Sun 2014-06-08 19:09:24 CEST; 5min 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
Process: 336 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)
Main PID: 336 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
Jun 08 19:09:24 amd64-archlinux systemd[1]: Failed to start Login Service.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Unit systemd-logind.service entered failed state.
Jun 08 19:09:24 amd64-archlinux systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Stopping Login Service...
Jun 08 19:09:24 amd64-archlinux systemd[1]: Starting Login Service...
Jun 08 19:09:24 amd64-archlinux systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Failed to start Login Service.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Unit systemd-logind.service entered failed state.
Has anyone an idea where to lead me?
Last edited by bernd_b (2014-06-09 11:20:21)

I don't know if I got you point - but here is a try:
I am running X11 started manually with "startxfce4". So firing up a konsole in X11 I do and get
root@amd64-archlinux pkg]# systemctl stop systemd-logind
[root@amd64-archlinux pkg]# systemctl start systemd-logind
Job for systemd-logind.service failed. See 'systemctl status systemd-logind.service' and 'journalctl -xn' for details.
journalctl -xn:
-- Unit systemd-logind.service has begun shutting down.
Jun 08 21:38:18 amd64-archlinux systemd[1]: Starting Login Service...
-- Subject: Unit systemd-logind.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-logind.service has begun starting up.
Jun 08 21:38:18 amd64-archlinux systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start.
Jun 08 21:38:18 amd64-archlinux systemd[1]: Failed to start Login Service.
-- Subject: Unit systemd-logind.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-logind.service has failed.
-- The result is failed.
I ran the service directly I get:
[root@amd64-archlinux pkg]# /usr/lib/systemd/systemd-logind
Failed to connect to system bus: No such file or directory
Failed to fully start up daemon: No such file or directory
What I figured out so far is this in addition:
- krusader does not start- there is no response or message in the konsole when firing up this application.
- I can only mount nfs-shares with the option "-o nolock" otherwise I get, e.g.
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified
Last edited by bernd_b (2014-06-08 19:48:43)

[solved] How to restart all services with systemd?

I had the habit of restarting all daemons after an upgrade so to make sure the newest libraries, configuration files etc were loaded. I did that with a shell script that restarted the daemons in order which they were listed in rc.conf. With systemd I could do something similar by first getting a list of running services and ordering a 'systemcrl restart <servicename>' for each. But since systemd keeps track of dependencies I wonder if that would be the way to do it. Also I would need to filter out 'one shot' type services that are only needed on bootup.
<edit>restart instead of reload</edit>
<edit>solved it with a little script</edit>
Last edited by rwd (2012-11-27 21:02:02)

I think that's what systemctl snapshot does.
snapshot [NAME]
Create a snapshot. If a snapshot name is specified, the new snapshot will be named after it. If none is specified an automatic snapshot name is generated. In either case, the snapshot name used is printed to STDOUT, unless --quiet is specified.
A snapshot refers to a saved state of the systemd manager. It is implemented itself as a unit that is generated dynamically with this command and has dependencies on all units active at the time. At a later time the user may return to this state by using the isolate command on the snapshot unit.
Snapshots are only useful for saving and restoring which units are running or are stopped, they do not save/restore any other state. Snapshots are dynamic and lost on reboot.
Then, isolate emergency.target or rescue target and switch to the snapshot.

[SOLVED] Shall i enable systemd-logind.service?

hi!
I'm using xfce 4.10 with consolekit. So the question is: do i need systemd-logind.service?
And, may be, can i get rid of consolekit and use this systemd feature, even if xfce4-session and slim need it?and finally, is there a good guide to help me doing this?
Thank you very much!
ps: the most important answer i need is the first
EDIT: i found now two lines in the wiki that explains better what i've to do to replace consolekit with logind.service . So all i need is an hint about the first question! Thanks again!
Last edited by nierro (2012-06-08 20:12:19)

It's running in any case - systemd starts it on its own whether you explicitly enable it or not. Confirm with "systemctl status systemd-logind.service".
You may want to investigate the "loginctl" tool that comes with systemd - it shows you what logind is doing for you.

[Solved] Running mpd as user mpd with systemd without using mpd.conf

Maybe this is tivial, but I searched about an hour without any results. I want to run mpd as user mpd. I cant use the mpd config file since mpd set the UID and GID explicitely resulting in mpd not having the necessary supplementary groups to access the locally shared music on my pc. Well I tried to run mpd with systemd by
# systemctl start mpd
and the systemd contains the user mpd
$ cat /etc/systemd/system/default.target.wants/mpd.service
[Unit]
Description=Music Player Daemon
After=network.target sound.target
[Service]
User=mpd
ExecStart=/usr/bin/mpd --no-daemon
# allow MPD to use real-time priority 50
LimitRTPRIO=50
LimitRTTIME=-1
# move MPD to a top-level cgroup, as real-time budget assignment fails
# in cgroup /system/mpd.service, because /system has a zero real-time
# budget; see
# http://www.freedesktop.org/wiki/Software/systemd/MyServiceCantGetRealtime/
ControlGroup=cpu:/mpd
# assign a real-time budget
ControlGroupAttribute=cpu.rt_runtime_us 500000
[Install]
WantedBy=default.target
but it did not run as mpd.
Well how can I run mpd as mpd? Is there a way to do it like with dropbox: dropbox@<user>.service
Last edited by manuelschneid3r (2015-03-25 12:52:52)

Glad you solved it. Was just typing a response and I'll still add two remarks:
The ps|grep output showed that you run grep as root, not mpd itself (which won't have a space in the command -- the second time it only worked because the mpd group is preceded by a space).
It sounds like it took you a while to find the drop-in configuration snippet in the mpd.service.d directory. These drop-in are shown in `systemctl status`, which is something you'd normally check in situations like these, and that might help to discover them more quickly.
Last edited by Raynman (2015-03-25 12:58:36)

Alternate Xorg session with desktop [SOLVED]

My goal is to run multiple X sessions with separate openbox and KDE enviroments.
I open TTY6 with alt+ctrl+F6 and run xinit /usr/bin/openbox -- :1 and my new and shiny openbox opens nicely.
The problem is, that when I return to my KDE with alt+ctrl+F7 and then try to switch to my still running openbox instance - I see only running xorg messages on my TTY6 but no desktop.
I can kill xorg on TTY6 with ctrl+C and start openbox session again, but it's still very annoying.
I can start that other xorg session with any desktop enviroment, even altrnate KDE, but the result is the same, console screen with running xorg messages.
Any ideas would be appreciated.
Last edited by uhuu (2013-03-12 23:37:57)

You're welcome.
A TTY can't be both a terminal and an X server. For example, on my computer, when my computer boots it automatically makes TTY1 my X server. Then I go to TTY2 and use the "startx -- :1" command, and the new X server starts on TTY3.
The same thing happened before systemd, except traditionally it was TTY1 - TTY6 for terminals and TTY7 - TTY10 for X servers, so it was easier to know where things were going to be (you can still setup systemd to behave that way)
Also, I don't think "TTY" is the correct word to use... But I don't know the correct term.

[Solved]No active session with systemd-logind

Similar Messages

Maybe you are looking for