You are not logged in.
Followed the setup on the systemd wiki page and installed systemd and systemd-arch-units. Upon rebooting and querying the running services, I noticed several failed to start for reasons that are unknown to me.
List of just those that failed:
$ systemctl list-units
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
proc-sys-fs-binfmt_misc.automount loaded failed failed Arbitrary Executable File Formats File Sys
systemd-modules-load.service loaded failed failed Load Kernel Modules
smbd.service loaded failed failed Samba SMB/CIFS serverNot sure what would be helpful in diagnosing this; contrary to the wiki, I have no journalctl... perhaps it resides in an optional package?
$ pkgfile -s journalctlSome info:
$ systemctl status proc-sys-fs-binfmt_misc.automount
proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point
Loaded: loaded (/usr/lib/systemd/system/proc-sys-fs-binfmt_misc.automount; static)
Active: failed (Result: resources)
Where: /proc/sys/fs/binfmt_misc$ status systemd-modules-load
systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
Active: failed (Result: exit-code) since Sat, 14 Apr 2012 06:59:07 -0400; 2min 49s ago
Process: 117 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/systemd-modules-load.service$ status smbd
smbd.service - Samba SMB/CIFS server
Loaded: loaded (/usr/lib/systemd/system/smbd.service; enabled)
Active: failed (Result: exit-code) since Sat, 14 Apr 2012 06:43:06 -0400; 14s ago
Process: 2434 ExecStart=/usr/sbin/smbd -F (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/smbd.serviceLast edited by graysky (2012-04-14 17:55:45)
Offline
Offline
@falconindy - you're right about the typo. I edited the original post to fix it. Do you have any thoughts regarding the failures? Thanks!
Last edited by graysky (2012-04-14 11:04:31)
Offline
The issue with samba is probably due to FS#26239. The solution is in the first comment. (Maybe someone should move this bugreport to the samba package).
Can't help you with the other issues, though.
Offline
Nice, thanks guelfi.
Last edited by graysky (2012-04-14 17:57:59)
Offline
Most of the time it can be useful to run the command that is specified in the ExecStart line to get some useful output why starting the service failed, e.g. in your case:
# /usr/lib/systemd/systemd-modules-loadOffline
The issue with samba is probably due to FS#26239. The solution is in the first comment. (Maybe someone should move this bugreport to the samba package).
Can't help you with the other issues, though.
Hi
I was also seeing the smbd.service failure. As a result of being a complete noob I guess !! (I don't have /var mounted on a temporary drive).
Perhaps someone could explain how systemd units interact with these /var/run/.. folders? Why does the smbd.service need a /var/run/samba folder?
Still finding my feet with SystemD... ![]()
Thanks
Bob
Offline
guelfi wrote:The issue with samba is probably due to FS#26239. The solution is in the first comment. (Maybe someone should move this bugreport to the samba package).
Can't help you with the other issues, though.
Hi
I was also seeing the smbd.service failure. As a result of being a complete noob I guess !! (I don't have /var mounted on a temporary drive).
Why shoukld you? /var should not be on a tmpfs; several applications (including pacman) save their databases etc. there.
Perhaps someone could explain how systemd units interact with these /var/run/.. folders? Why does the smbd.service need a /var/run/samba folder?
Samba tries to create a PIDfile (a file that just contains the PID of some process) in /var/run/samba. As /var/run is on a tmpfs and systemd doesn't automatically create this folder (in contrast to the original initscripts), you have to instruct systemd to create /var/run/samba on every reboot.
Still finding my feet with SystemD...
Yes, it is written systemd, not system D or System D, or even SystemD. And it isn't system d either. Why? Because it's a system daemon, and under Unix/Linux those are in lower case, and get suffixed with a lower case d. And since systemd manages the system, it's called systemd. It's that simple. But then again, if all that appears too simple to you, call it (but never spell it!) System Five Hundred since D is the roman numeral for 500 (this also clarifies the relation to System V, right?). The only situation where we find it OK to use an uppercase letter in the name (but don't like it either) is if you start a sentence with systemd. On high holidays you may also spell it sÿstëmd. But then again, Système D is not an acceptable spelling and something completely different (though kinda fitting).
Offline
Samba tries to create a PIDfile (a file that just contains the PID of some process) in /var/run/samba. As /var/run is on a tmpfs and systemd doesn't automatically create this folder (in contrast to the original initscripts), you have to instruct systemd to create /var/run/samba on every reboot.
Yeh I thought it was PID storage. I see now that /run is in my mount-points as tmpfs. So Samba isn't going to autostart without some extra help I guess...
I was getting confused about the emphasis on systemd - so thanks!! So are other people I see...
$ pacman -Ss systemd
...
community/systemd-arch-units 20120410-1 [installed: 20120401-1]
Arch specific Systemd unit files
community-testing/systemd-arch-units 20120412-1 [installed: 20120401-1]
Arch specific Systemd unit filesThanks
Bob
Offline
Offline
Duh... "read" that before but I see the light now... ![]()
Thanks
Bob
Offline