Linux – Systemd service start error

linuxservicessystemd

I have a Beaglebone Black (BBB) running Angstrom Linux (v2012.12). Since none of my other Linux machines have systemd yet, and Angstrom does, I figured I'd get familiar with systemd before its shoved down my throat on Debian. I'm fairly clear on systemd usage/capabilities but for one error I get when trying to start lighttpd. I assume the format of the error message is typical for a systemd service error..

When I try to start the lighttpd service, I get the following:

root@beaglebone:/etc# systemctl start lighttpd.service
Job for lighttpd.service failed. See 'systemctl status lighttpd.service' and 'journalctl -xn' for details.

If I run systemctl status lighttpd.service, I get the following

root@beaglebone:/etc# systemctl status lighttpd.service
lighttpd.service - Lightning Fast Webserver With Light System Requirements
      Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled)
      Active: failed (Result: exit-code) since Mon 2015-02-16 07:23:30 PST; 3min 3s ago
     Process: 872 ExecStart=/usr/sbin/lighttpd -D -f /etc/lighttpd.conf (code=exited, status=255)
      CGroup: name=systemd:/system/lighttpd.service

Running journalctl -xn gets the following:

Feb 16 07:28:04 beaglebone systemd[1]: Starting Lightning Fast Webserver With Light System Requirements...
Feb 16 07:28:04 beaglebone systemd[1]: lighttpd.service: main process exited, code=exited, status=255/n/a
Feb 16 07:28:04 beaglebone systemd[1]: Failed to start Lightning Fast Webserver With Light System Requirements.
Feb 16 07:28:05 beaglebone systemd[1]: Unit lighttpd.service entered failed state

All of the systemd documentation I've been able to find doesn't go into details about errors like this. I never had any trouble with the old-school way of starting daemons, and I've been playing with Linux since 1995. Help!

Best Answer

I'm assuming you have checked nothing else is using port 80 (which I assume lighttpd is configured to use). Check that bonescript still doesn't have the port bound, stop it with:

systemctl stop bonescript.service
systemctl stop bonescript.socket

Related Solutions

Linux – How to figure out why systemctl service “systemd-modules-load” fails

I too had this issue. I was able to solve it by following the instructions on the Arch Linux systemd wiki page. Here is a summary of what I did :

Lets find the systemd services which fail to start

$ systemctl --failed  
------------------------------------------------------------------------
systemd-modules-load.service   loaded failed failed  Load Kernel Modules

Ok, we found a problem with systemd-modules-load service. We want to know more.

$ systemctl 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 So 2013-08-25 11:48:13 CEST; 32s ago  
     Docs: man:systemd-modules-load.service(8).  
           man:modules-load.d(5)
  Process: 15630 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)

If the Process ID is not listed, just restart the failed service with

$ systemctl restart systemd-modules-load

Now we have the process id (PID) to investigate this error in depth. Enter the following command with the current Process ID (here: 15630):

$ journalctl _PID=15630
----------------------------------------------------------------------
-- Logs begin at Sa 2013-05-25 10:31:12 CEST, end at So 2013-08-25 11:51:17 CEST. --
Aug 25 11:48:13 mypc systemd-modules-load[15630]: Failed to find module 'blacklist usblp'
Aug 25 11:48:13 mypc systemd-modules-load[15630]: Failed to find module 'install usblp /bin/false'

We see that some of the kernel module configs have wrong settings. Therefore we have a look at these settings in /etc/modules-load.d/

$ ls -Al /etc/modules-load.d/
----------------------------------------------------------------------
...  
-rw-r--r--   1 root root    79  1. Dez 2012  blacklist.conf  
-rw-r--r--   1 root root     1  2. Mär 14:30 encrypt.conf  
-rw-r--r--   1 root root     3  5. Dez 2012  printing.conf  
-rw-r--r--   1 root root     6 14. Jul 11:01 realtek.conf  
-rw-r--r--   1 root root    65  2. Jun 23:01 virtualbox.conf  
...

The Failed to find module 'blacklist usblp' error message might be related to a wrong setting inside of blacklist.conf. Lets deactivate it with inserting a trailing # before each option we found via step 3:
```
/etc/modules-load.d/blacklist.conf  
----------------------------------------------------------------------
# blacklist usblp  
# install usblp /bin/false  
```

Now, try to start systemd-modules-load:

$ systemctl restart systemd-modules-load

If it was successful, this should not prompt anything. If you see any error, go back to step 3 and use the new PID for solving the errors left.

If everything is ok, you can verify that the service was started successfully with:

$ systemctl status systemd-modules-load
----------------------------------------------------------------------
systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
   Active: active (exited) since So 2013-08-25 12:22:31 CEST; 34s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
 Process: 19005 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS)
Aug 25 12:22:31 mypc systemd[1]: Started Load Kernel Modules.

Linux – Start a systemd user service at boot

I dont know if this is your case but i could solve it with the answer of https://unix.stackexchange.com/questions/251211/why-doesnt-my-systemd-user-unit-start-at-boot The problem was i had WantedBy=multi-user.target and had to change it to WantedBy=default.target and it worked.

Another thing, i have my service file in ~/.config/systemd/user

Best Answer

Related Solutions

Linux – How to figure out why systemctl service “systemd-modules-load” fails

Linux – Start a systemd user service at boot

Related Question