[Solved] systemd fails to start spawning /bin/plymouth

Hello all,
I currently can't get my system to boot up, systemd hangs and after a while enters emergency mode.
journalctl -xb
show the following error:
systemd[257]: Failed at step EXEC spwaning /bin/plymouth:
-- Subject: Process /bin/plymouth could not be executed
.. The process /bin/plymouth could not be executed and failed.
-- The error number returned while executing this process is 2.
I am not sure what to make of this, as far as I know plymouth is some splash screen utility which I have never installed. I also can't find any corresponding .service files. I also tried appending plymouth.enable=0 to the kernel command line, to no effect. Does anyone know this problem (since my hardware is currently in a rather shaky state I would not rule out some related error)?
Last edited by x2b (2013-09-11 17:55:32)

x2b wrote:I am not sure what to make of this, as far as I know plymouth is some splash screen utility which I have never installed.
Yes, that's plymouth.
I also can't find any corresponding .service files. I also tried appending plymouth.enable=0 to the kernel command line, to no effect. Does anyone know this problem (since my hardware is currently in a rather shaky state I would not rule out some related error)?
Might have something to do with https://bugs.archlinux.org/task/31031 so plymouth should not be the problem.
Edit: I just checked my journal and I could not find any plymouth related messages in there, but I remember seeing those before, too (must have been before february 20th, that's as far back as my journal goes). When did you do your last update?
Last edited by cookies (2013-09-11 13:58:43)

Similar Messages

Failed at step EXEC spawning /bin/plymouth: No such file or directory

Hi guys, Yet Another Plymouth Problem:
I just did a system update. Haven't done this for several months and problems with /bin happened, as expected. Anyway, after update completed, the system won't boot normally:
If I type ^d boot continues with no problems and all services are started as expected. I have trouble finding what causes the system to go to emergency mode. The /srv/nfs/trunk/ seems to be mounted at a second attempt.
An excerpt from journalctl -xb, right after the xfs messages :
Sep 18 00:55:50 xxxlinux systemd[1]: Startup finished in 2.322s (kernel) + 1.350s (userspace) = 3.672s.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
-- Kernel start-up required 2322291 microseconds.
-- Initial RAM disk start-up required INITRD_USEC microseconds.
-- Userspace start-up required 1350682 microseconds.
Sep 18 00:55:50 xxxlinux systemd[168]: Failed at step EXEC spawning /bin/plymouth: No such file or directory
-- Subject: Process /bin/plymouth could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/641257651c1b4ec9a8624d7a40a9e1e7
-- The process /bin/plymouth could not be executed and failed.
-- The error number returned while executing this process is 2.
Sep 18 00:55:50 xxxlinux ntfs-3g[294]: Version 2013.1.13 external FUSE 29
Sep 18 00:55:50 xxxlinux ntfs-3g[294]: Mounted /dev/sdb6 (Read-Write, label "", NTFS 3.1)
Sep 18 00:55:50 xxxlinux ntfs-3g[294]: Cmdline options: rw,uid=1000,gid=100,dmask=022,fmask=133
Sep 18 00:55:50 xxxlinux ntfs-3g[294]: Mount options: rw,allow_other,nonempty,relatime,default_permissions,fsname=/dev/sdb6,blkdev,blk
Sep 18 00:55:50 xxxlinux ntfs-3g[294]: Global ownership and permissions enforced, configuration type 7
Sep 18 00:55:50 xxxlinux kernel: scsi 6:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0
Sep 18 00:55:50 xxxlinux kernel: scsi 6:0:0:1: Direct-Access Generic USB CF Reader 1.01 PQ: 0 ANSI: 0
Sep 18 00:55:50 xxxlinux kernel: sd 6:0:0:0: [sde] Attached SCSI removable disk
Sep 18 00:55:50 xxxlinux kernel: scsi 6:0:0:2: Direct-Access Generic USB SM Reader 1.02 PQ: 0 ANSI: 0
Sep 18 00:55:50 xxxlinux kernel: sd 6:0:0:1: [sdf] Attached SCSI removable disk
Sep 18 00:55:50 xxxlinux kernel: scsi 6:0:0:3: Direct-Access Generic USB MS Reader 1.03 PQ: 0 ANSI: 0
Sep 18 00:55:50 xxxlinux kernel: sd 6:0:0:2: [sdg] Attached SCSI removable disk
Sep 18 00:55:50 xxxlinux kernel: sd 6:0:0:3: [sdh] Attached SCSI removable disk
After I press ^d:
Sep 18 00:56:21 xxxlinux systemd[1]: Stopping Sound Card.
-- Subject: Unit sound.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sound.target has begun shutting down.
Sep 18 00:56:21 xxxlinux systemd[1]: Stopped target Sound Card.
-- Subject: Unit sound.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/9d1aaa27d60140bd96365438aad20286
-- Unit sound.target has finished shutting down.
Sep 18 00:56:21 xxxlinux systemd[1]: Stopping Emergency Mode.
-- Subject: Unit emergency.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit emergency.target has begun shutting down.
Sep 18 00:56:21 xxxlinux systemd[1]: Stopped target Emergency Mode.
-- Subject: Unit emergency.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/9d1aaa27d60140bd96365438aad20286
-- Unit emergency.target has finished shutting down.
Sep 18 00:56:21 xxxlinux systemd[1]: Stopping Emergency Shell...
-- Subject: Unit emergency.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit emergency.service has begun shutting down.
And the system boots.
I found a thread explaining that there is a sysV runlevel specified in kernel boot line. I am not sure if I am looking at the proper file, but my /boot/grub/grub.cfg does not contain "runlevel".
I also found it may be a problem of software RAID, but I am not using it neither LVM, plain mounts by UUID.
I ran pacman -S linux, /etc/mkinitcpio.conf does not contain a reference to plymouth: HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
Just checked with my laptop, both computers run systemd-204-3, neither have /bin/plymouth, but the laptop does not fail with this message
Just tell me if you need more information.

# Intel SSD 1
UUID=775642a3-f485-4cc6-b9d5-c336aa276c39 / xfs rw,relatime,attr2,inode64,noquota 0 1
# Intel SSD 2
UUID=75232369-0f3f-45f5-99fe-234089a1ea8e /boot xfs rw,relatime,attr2,inode64,noquota 0 2
# Intel SSD 3
UUID=595fa411-2c31-48e1-960b-fad259460248 /home xfs rw,relatime,attr2,inode64,noquota 0 2
# WD 1T 1
UUID=4fcb28a9-66fe-4463-9f31-e325d62d5017 /mnt/wd1 xfs rw,relatime,attr2,inode64,noquota 0 2
# WD 1T 2
UUID=4803c5db-72a3-4cd5-ad94-f7de2de2ea09 /mnt/wd2 xfs rw,relatime,attr2,inode64,noquota 0 2
# WD 1T 3
UUID=b937ce12-31a4-4816-9630-d53cab774a7e /mnt/wd3 xfs rw,relatime,attr2,inode64,noquota 0 2
# SG 320G 1 1
UUID=76fd28c6-1541-40bd-958b-cd05d787ff7b /mnt/sg1_1 xfs rw,relatime,attr2,inode64,noquota 0 2
# SG 320G 2 1
UUID=789845B4984571A4 /mnt/sg2_5 ntfs-3g uid=1000,gid=users,dmask=022,fmask=133 0 0
UUID=32BC47F9BC47B5DF /mnt/sg2_6 ntfs-3g uid=1000,gid=users,dmask=022,fmask=133 0 0
tmpfs /tmp tmpfs nodev,nosuid,size=20G 0 0
# NFS mounts
/mnt/multimedia /srv/nfs/multimedia none bind 0 0
/mnt/images /srv/nfs/images none bind 0 0
/mnt/trunk /srv/nfs/trunk none bind 0 0
[2] ognyan@xxxlinux : ~ >ll /mnt/
total 40K
drwxr-xr-x 8 root root 124 Jun 13 01:22 .
drwxr-xr-x 18 root root 4.0K Sep 17 23:52 ..
lrwxrwxrwx 1 root root 3 Jun 4 17:16 images -> wd1
lrwxrwxrwx 1 root root 3 Jun 4 17:16 multimedia -> wd2
drwxr-xr-x 23 ognyan users 4.0K Sep 19 14:37 sg1_1
drwxr-xr-x 1 ognyan users 8.0K Mar 30 21:28 sg2_5
drwxr-xr-x 1 ognyan users 12K Mar 30 21:28 sg2_6
lrwxrwxrwx 1 root root 3 Jun 3 21:27 srv -> wd3
lrwxrwxrwx 1 root root 5 Jun 4 17:15 trunk -> sg1_1
drwxr-sr-x 203 ognyan users 8.0K Aug 4 20:53 wd1
drwxr-xr-x 5 root root 41 Sep 19 10:32 wd2
drwxr-xr-x 8 root root 76 Aug 31 23:13 wd3
Last edited by bigblondewolf (2013-09-19 22:15:36)

[PARTIALLY SOLVED] HAL fails to start

** UPDATE: PARTIALLY SOLVED - SEE BOTTOM OF THE FIRST POST
HAL fails to start. I'm not exactly sure why this is, but I believe it has something to do with my attempts to get automounting working under gnome.
[zen@intellitech ~]$ sudo /etc/rc.d/hal start
:: Starting Hardware Abstraction Layer [FAIL]
[zen@intellitech ~]$ vim /etc/rc.conf
MODULES=(acpi-cpufreq cpufreq_ondemand e1000 iwl4965 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore thinkpad_acpi uinput vboxdrv)
DAEMONS=(syslog-ng @network !net-profiles @net-auto @netfs !samba !crond @acpid @dbus @hal @alsa !daemoot !avahi-daemon @cups @ddclient @bluetooth)
[zen@intellitech ~]$ pacman -Q | grep hal
hal 0.5.11-1
hal-info 0.20080508-1
[zen@intellitech ~]$ /usr/sbin/hald --daemon=no --verbose=yes
03:13:37.451 [i] hald.c:669: hal 0.5.11
03:13:37.451 [i] hald.c:734: Will not daemonize
03:13:37.451 [i] hald_dbus.c:5381: local server is listening at unix:abstract=/var/run/hald/dbus-pdtZvbqaVq,guid=312b47921cba4c5cdbee099a48ec87d1
03:13:37.452 [E] ck-tracker.c:367: Error doing GetSeats on ConsoleKit: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
03:13:37.452 [E] ck-tracker.c:792: Could not get seats and sessions
03:13:37.452 [W] hald_dbus.c:5806: Could not initialize seats and sessions from ConsoleKit
Runner started - allowed paths are '/usr/lib/hal:/usr/lib/hal/scripts:/usr/bin'
03:13:37.453 [i] hald_runner.c:301: Runner has pid 3675
03:13:37.453 [i] hald_runner.c:182: runner connection is 0x15bdec0
03:13:37.456 [W] osspec.c:373: Unable to open /proc/mdstat: No such file or directory
03:13:37.457 [D] util_helper.c:124: drop_privileges: could not set group id
[zen@intellitech ~]$ vim /etc/group
root::0:root
bin::1:root,bin,daemon
daemon::2:root,bin,daemon
sys::3:root,bin
adm::4:root,daemon
tty::5:root,zen
disk::6:root,zen
lp::7:daemon
mem::8:
kmem::9:
wheel::10:root,zen
ftp::11:
mail::12:
log::19:root
smmsp::25:
games::50:
network:x:90:zen
video:x:91:zen
audio::92:root,zen
optical::93:root,zen
floppy:x:94:root,zen
storage:x:95:root,zen
power:x:98:root,zen
nobody::99:
users::100:zen
locate:x:21:
uucp:x:14:
http:x:33:
scanner:x:96:
dbus:x:81:root,zen
hal:x:82:root,zen
avahi:x:84:root,zen
camera:x:97:
gdm:x:101:
vboxusers:x:108:zen
samba:x:109:zen,root
* Yes, I know it is bad practice to have a normal user listed under the disk group. It is necessary, however, in order to have raw disk access for virtual box.
[zen@intellitech ~]$ sudo /etc/rc.d/dbus stop
:: Stopping D-BUS system messagebus [DONE]
[zen@intellitech ~]$ sudo /etc/rc.d/hal start
:: Starting D-BUS system messagebus [DONE]
:: Starting Hardware Abstraction Layer [FAIL]
It's odd, because D-BUS will start but hal will not... Anybody have any suggestions?
* UPDATE (10/08/08): Did a full system upgrade and removed dbus from daemons array in rc.conf. UDEV EVENTS Processing speed seems to be back to normal.
** SOLUTION UPDATE: After removing custom ntfs-3g fdi policies from /etc/hal/fdi/policy/, hal seems to load without any problems. This seems to be a bug, since my policies were working at one point, and I believe a hal update caused the problem. I'll see if I can track down the exact hal version that it breaks on, and submit a respective bug report for it.
** OFF-TOPIC UPDATE: Using hwdetect --modules to get a modules list, and using these modules in rc.conf with MOD_AUTOLOAD turned off (and also in mkinitcpio.conf and running mkinitcpio -g <path>), seems to have dramatically increased my "Load udev events" processing time. After doing this, my udev speed went from almost 4000ms to literally < 500ms.
Last edited by intellitech (2008-10-08 14:58:53)

koch wrote:
intellitech wrote:DAEMONS=(syslog-ng @network !net-profiles @net-auto @netfs !samba !crond @acpid @dbus @hal @alsa !daemoot !avahi-daemon @cups @ddclient @bluetooth)
you have dbus starting before hal but hal starts debus by default so please try this...
DAEMONS=(...@acpid @hal @alsa...)
and delete debus from that line.
Removed dbus from the daemons array and hal still won't start. Also, I noticed that the "Loading udev events" portion of the boot process seems to take a lot longer than it used to. Last boot, it took about 19130ms, whereas it used to take < 3000ms. Could these be related?
Also, I ran a full system upgrade, both udev and hal were upgraded.
[zen@intellitech ~]$ pacman -Q | grep hal
hal 0.5.11-4
hal-info 0.20080508-1
[zen@intellitech ~]$ pacman -Q | grep udev
klibc-udev 128-1
udev 128-5

[SOLVED]apache failes to start

Hi folks,
As of a few moments ago my server failes to start apache
systemctl status httpd gives me following error
sudo systemctl status httpd
* httpd.service - Apache Web Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
Active: failed (Result: exit-code) since Mon 2014-03-31 15:08:45 CEST; 24s ago
Process: 3639 ExecStart=/usr/bin/apachectl start (code=exited, status=1/FAILURE)
Mar 31 15:08:45 odp apachectl[3639]: [Mon Mar 31 15:08:45.031005 2014] [so:warn] [pid 3641] AH01574: module suexec_module is already loaded, skipping
Mar 31 15:08:45 odp apachectl[3639]: AH00534: httpd: Configuration error: No MPM loaded.
Mar 31 15:08:45 odp systemd[1]: httpd.service: control process exited, code=exited status=1
Mar 31 15:08:45 odp systemd[1]: Failed to start Apache Web Server.
Mar 31 15:08:45 odp systemd[1]: Unit httpd.service entered failed state.
I am not really sure what to make out of this error
Last edited by odp (2014-03-31 14:55:13)

I realize it has to do with the httpd.conf structure has changed thus there is a generated httpd.conf.pacnew file using this works fine. So forget about the old question. The new question is, how can I merge the two files?

[solved] systemd services not starting at boot (or at all)

On my router, some systemd services fail to start at boot.
The services are :
adsl (pppoe connetction on the wan interface)
shorewall (funny again for a router)
logind (brings up only tty1, and not the others with a 'timeout' error)
adsl starts fine manually after booting up
the others don't work, I have to launch shorewall with the old sysvinit rc script (and it works)
I really don't know, what happened to logind...
Last edited by scar (2012-11-30 10:20:44)

cups: avahi client failed
adsl: timeout (ppp0 running on eth0, the service did not found eth0)
shorewall: did not work by the systemctl command, only with the old rc script
I'm not sure if there was an error with logind, but I've had only tty1, not all the others (I have not touched /etc/inittab)
since this was a very old install (but up to date), I've decided to reinstall the whole thing,
Everything works
(But reinstalling does not solve any problem, it erases the problems...)
Last edited by scar (2012-11-30 10:21:20)

[solved]Network fails to start sometimes

Hello!
I'm having a problem with my network. Sometimes it fails to start. Usually, a reboot solves this. Here is the error log:
[root@claudia log]# cat errors.log
Aug 6 03:16:28 claudia dhcpcd[3194]: dhcpStart: interface eth0 is not Ethernet or 802.2 Token Ring
rc.conf:
# NETWORKING
HOSTNAME="claudia"
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.1.1"
ROUTES=(!gateway)
hosts:
[root@claudia log]# cat /etc/hosts
# /etc/hosts: static lookup table for host names
#<ip> <hostname> <hostname>
127.0.0.1 localhost.localdomain localhost claudia
# End of file
What should I do to solve this?
Thanks and regards,
Gustavo

I'd say it's because since the ethernet over firewire module is loaded too, it's counted as a network device too - and which one gets to be eth0 depends if the NIC or ethernet over firewire module is loaded first. There are many solutions to this:
1) If you don't need ethernet over firewire, keep it from being loaded by putting the module name (eth1394 I think) in MOD_BLACKLIST in /etc/rc.conf, like this:
MOD_BLACKLIST=(eth1394)
2) You can make both eth0 and eth1 (and perhaps other NICs too) start up together (I do this with my 2 NICs). To do that, make the rc.conf network section something like this:
lo="lo 127.0.0.1"
eth0="dhcp"
eth1="dhcp"
INTERFACES=(lo eth0 eth1)
Then you should put a @ in front of "network" ( @network ) in the DAEMONS array unless you like waiting for a NIC that won't start

[SOLVED] SSHD fails to start

Hi to everyone.
his is my 1st post and the second day I have bee playng with arch linux. I installed everythig up to gnome and everything worked just fine. Nevertheless I'm a newbie and I didn't manage to have sshd working. I followed the wiki but it simply fails to start (either at boottime or from commandline)
The error message is:
:: Starting Secure Shell Deamon [FAIL]
What can I do ?
Thanks in advance for any help
Paolo
Italy
Last edited by kayard (2007-09-30 16:27:50)

I'm not sure why but it works ... and Yes the reason why I was getting "FAILED" when trying to start sshd is because it was already working on port 22.
I didn't realized this earlier because I couldn't connect from another computer and I thought that was the reason while, in fact, was something else ...
(for the sake of knowledge during setup my ethernet card was eth1 and after setup the kernel set it up as eth0 but boot-time scripts didn't complain therefore the sistem booted flawlessy with a eth1 apparently working. Changing in rc.conf from eth1 to eth0 solved the problem)
By the way thanks for the guide and the nmap tip which will cam handy in the future.
Paolo

[SOLVED]Apache fails to start

I`ve had Apache,PHP and mysql running but few days ago i saw that httpd fails to start.
# apachectl configtest
httpd: Syntax error on line 54 of /etc/httpd/conf/httpd.conf: Cannot load /home/svejaka/Server/modules/mod_authn_file.so into server: /home/svejaka/Server/modules/mod_authn_file.so: cannot open shared object file: No such file or directory
Last edited by svejaka (2009-10-14 17:51:45)

I get the same error but my ServerRoot is ok. (/etc/httpd/)
So I really have no clue aboout what to do.
this is my .conf
# This is the main Apache HTTP server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so 'log/access_log'
# with ServerRoot set to '/www' will be interpreted by the
# server as '/www/log/access_log', where as '/log/access_log' will be
# interpreted as '/log/access_log'.
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
# Do not add a slash at the end of the directory path. If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk. If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
ServerRoot "/etc/httpd"
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#Listen 12.34.56.78:80
Listen 80
# Dynamic Shared Object (DSO) Support
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
# Example:
# LoadModule foo_module modules/mod_foo.so
LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_anon_module modules/mod_authn_anon.so
LoadModule authn_dbd_module modules/mod_authn_dbd.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule file_cache_module modules/mod_file_cache.so
LoadModule cache_module modules/mod_cache.so
LoadModule disk_cache_module modules/mod_disk_cache.so
LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule dbd_module modules/mod_dbd.so
LoadModule dumpio_module modules/mod_dumpio.so
LoadModule reqtimeout_module modules/mod_reqtimeout.so
LoadModule ext_filter_module modules/mod_ext_filter.so
LoadModule include_module modules/mod_include.so
LoadModule filter_module modules/mod_filter.so
LoadModule substitute_module modules/mod_substitute.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule ldap_module modules/mod_ldap.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule log_forensic_module modules/mod_log_forensic.so
LoadModule logio_module modules/mod_logio.so
LoadModule env_module modules/mod_env.so
LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule expires_module modules/mod_expires.so
LoadModule headers_module modules/mod_headers.so
LoadModule ident_module modules/mod_ident.so
LoadModule usertrack_module modules/mod_usertrack.so
LoadModule unique_id_module modules/mod_unique_id.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule version_module modules/mod_version.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule ssl_module modules/mod_ssl.so
LoadModule mime_module modules/mod_mime.so
LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule asis_module modules/mod_asis.so
LoadModule info_module modules/mod_info.so
LoadModule suexec_module modules/mod_suexec.so
LoadModule cgi_module modules/mod_cgi.so
LoadModule cgid_module modules/mod_cgid.so
LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
LoadModule imagemap_module modules/mod_imagemap.so
LoadModule actions_module modules/mod_actions.so
LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule php5_module modules/libphp5.so
<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
User http
Group http
</IfModule>
</IfModule>
# 'Main' server configuration
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. [email protected]
ServerAdmin [email protected]
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
# If your host doesn't have a registered DNS name, enter its IP address here.
#ServerName www.example.com:80
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
DocumentRoot "/srv/http"
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
# First, we configure the "default" to be a very restrictive set of
# features.
<Directory />
Options FollowSymLinks Includes
AllowOverride None
Order deny,allow
Deny from all
</Directory>
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
# This should be changed to whatever you set DocumentRoot to.
<Directory "/srv/http">
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
Options Indexes FollowSymLinks
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
AllowOverride None
# Controls who can get stuff from this server.
Order allow,deny
Allow from all
</Directory>
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
<IfModule dir_module>
DirectoryIndex index.html
</IfModule>
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
<FilesMatch "^\.ht">
Order allow,deny
Deny from all
Satisfy All
</FilesMatch>
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
ErrorLog "/var/log/httpd/error_log"
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
<IfModule log_config_module>
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
<IfModule logio_module>
# You need to enable mod_logio.c to use %I and %O
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
</IfModule>
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
CustomLog "/var/log/httpd/access_log" common
# If you prefer a logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#CustomLog "/var/log/httpd/access_log" combined
</IfModule>
<IfModule alias_module>
# Redirect: Allows you to tell clients about documents that used to
# exist in your server's namespace, but do not anymore. The client
# will make a new request for the document at its new location.
# Example:
# Redirect permanent /foo http://www.example.com/bar
# Alias: Maps web paths into filesystem paths and is used to
# access content that does not live under the DocumentRoot.
# Example:
# Alias /webpath /full/filesystem/path
# If you include a trailing / on /webpath then the server will
# require it to be present in the URL. You will also likely
# need to provide a <Directory> section to allow access to
# the filesystem path.
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the target directory are treated as applications and
# run by the server when requested rather than as documents sent to the
# client. The same rules about trailing "/" apply to ScriptAlias
# directives as to Alias.
ScriptAlias /cgi-bin/ "/srv/http/cgi-bin/"
</IfModule>
<IfModule cgid_module>
# ScriptSock: On threaded servers, designate the path to the UNIX
# socket used to communicate with the CGI daemon of mod_cgid.
#Scriptsock /run/httpd/cgisock
</IfModule>
# "/srv/http/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
<Directory "/srv/http/cgi-bin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
DefaultType text/plain
<IfModule mime_module>
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
TypesConfig conf/mime.types
# AddType allows you to add to or override the MIME configuration
# file specified in TypesConfig for specific file types.
#AddType application/x-gzip .tgz
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#AddHandler cgi-script .cgi
# For type maps (negotiated resources):
#AddHandler type-map var
# Filters allow you to process content before it is sent to the client.
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#AddType text/html .shtml
#AddOutputFilter INCLUDES .shtml
</IfModule>
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
MIMEMagicFile conf/magic
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or one of the special
# values 'default', 'none' or 'unlimited'.
# Default setting is to accept 200 Ranges.
#MaxRanges unlimited
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall is used to deliver
# files. This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
#EnableMMAP off
#EnableSendfile off
# Supplemental configuration
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.
# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf
# Multi-language error messages
Include conf/extra/httpd-multilang-errordoc.conf
# Fancy directory listings
Include conf/extra/httpd-autoindex.conf
# Language settings
Include conf/extra/httpd-languages.conf
# User home directories
Include conf/extra/httpd-userdir.conf
# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf
# Virtual hosts
#Include conf/extra/httpd-vhosts.conf
# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf
# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf
# Various default settings
Include conf/extra/httpd-default.conf
# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
# Note: The following must must be present to support
# starting without SSL on platforms with no /dev/random equivalent
# but a statically compiled-in mod_ssl.
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>
#PHP
Include conf/extra/php5_module.conf
# phpMyAdmin configuration
Include conf/extra/httpd-phpmyadmin.conf
#Adminers for sql
Include conf/extra/httpd-adminer.conf

[SOLVED] systemd not alway starts dnsmasq and minidlna service

Hi!
After I've annoyed some of you (and hopefully helped others) with my threads on systemd I got systemd working. But; I still have one problem. Systemd seems to have trouble starting dnsmasq and minidlna.
dnsmasq.service loaded failed failed A lightweight DHCP and caching DNS server
[email protected] loaded active running Getty on tty1
httpd.service loaded active running Apache Web Server
logitechmediaserver.service loaded active running Logitech Media Server Daemon
lvm.service loaded active exited LVM activation
minidlna.service loaded failed failed minidlna server
Sometimes they do load, sometimes not. Is there a way to find out why a service could not be started?
btw
systemctl start minidlna dnsmasq
does start them perfectly
Last edited by theking2 (2012-12-13 18:50:35)

Yes, there is such a command systemctl status and it says
Dec 11 20:54:44 janus systemd[1]: Starting A lightweight DHCP and caching DNS server...
Dec 11 20:54:45 janus dnsmasq[308]: dnsmasq: syntax check OK.
Dec 11 20:54:45 janus dnsmasq[335]: dnsmasq: failed to create listening socket for 172.16.0.8: Cannot assign requested address
Dec 11 20:54:45 janus systemd[1]: dnsmasq.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Dec 11 20:54:45 janus systemd[1]: Failed to start A lightweight DHCP and caching DNS server.
Dec 11 20:54:45 janus systemd[1]: Unit dnsmasq.service entered failed state
and
minidlna.service - minidlna server
Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled)
Active: failed (Result: exit-code) since Tue, 2012-12-11 20:54:45 CET; 46s ago
Process: 303 ExecStart=/usr/sbin/minidlna -P /var/run/minidlna/minidlna.pid (code=exited, status=255)
CGroup: name=systemd:/system/minidlna.service

Systemd- failed to start packet filtering framework

I had installed systemd and also iptables and till recently everything seemed all right. Now I have started getting an error message on bootup that "failed to start packet filtering framework".
There is a suggestion at this site: https://mailman.archlinux.org/pipermail … 30565.html
On running the command "sudo systemctl status iptables", following is the output:
iptables.service - Packet Filtering Framework
Loaded: loaded (/usr/lib/systemd/system/iptables.service; disabled)
Active: failed (Result: exit-code) since Tue, 23 Oct 2012 17:30:07 +0000; 12min ago
Process: 200 ExecStart=/usr/sbin/iptables-restore /etc/iptables/iptables.rules (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/iptables.service
Oct 23 17:30:16 myhost iptables-restore[200]: Can't open /etc/iptables/iptables.rules: No such file or directory
How can I correct this error? Please help.
Last edited by rnarch (2012-10-23 12:17:56)

/etc/iptables/iptables.rules file does not exist, but system was not giving this error message earlier. I was loading iptables rules by following command in /etc/rc.local:
iptables-restore /home/myfw-regular.saved
Probably, I should move myfw-regular.saved file to /etc/iptables/iptables.rules and remove the rc.local line.

[SOLVED] X failed to start, then cannot login in tty

Recently I changed the X's monitor setting at /etc/X11/xorg.conf.d/10-monitor.conf. Seems that there is a wrong setting, and the X failed to start. So when booting, it says: INIT: Id 'x' respawning too fast: disabled for 5 minutes. So I changed to tty2 (alt-F2) and input my usual username and password, but checkpassword always says that my password is wrong.
So which username and password should I use? Or how to login to my computer?
The login manager is SLiM, DE is openbox + tint2, tty is fgetty (not agetty).
Last edited by chrlin (2012-02-10 02:00:06)

chrlin wrote:
But I'm still quite disappointed that the system offers no fallback from this kind of error. Any way to get around?
I guess the system should automatically goes to runlevel 3 (or other runlevel) in case runlevel 5 goes error or something. But it doesn't (Or I'm wrong?).
Well, in case you couldn't even as root, I had supposed you'd boot with your Arch live cd anyway, chroot properly into your system then, and edit /etc/inittab to runlevel 3. You'd probably be able to login afterwards and do startx from console, see what happens and check the log for errors.
When booting form cd you can cat it e.g. in /mnt/var/log/Xorg.0.log after mounting btw. -- Maybe there's an alternative way to edit the command line at boot as well, haven't looked for that yet. If there is, you might put that option into the bootloader's config of Arch's fallback kernel installation, so you could choose at startup.
At least to my knowledge once you configured your system to boot graphically (say, runlevel 5), there's no "fallback mode" into rl3. But what you can also do is to make your display manager able to alternatively get you into console (if possible; I know that's the case for cdm).
However, if you think your problem is now fixed, you should edit the header of your first post and add [SOLVED].

[SOLVED] Redis failing to start on boot

Content of redis.service:
[Unit]
Description=Advanced key-value store
After=network.target
[Service]
User=redis
Group=redis
ExecStart=/usr/bin/redis-server /etc/redis.conf
ExecStop=/usr/bin/redis-cli shutdown
CapabilityBoundingSet=
PrivateTmp=true
PrivateDevices=true
ProtectSystem=full
ProtectHome=true
NoNewPrivileges=true
RuntimeDirectory=redis
RuntimeDirectoryMode=700
[Install]
WantedBy=multi-user.target
On every boot:
Mar 09 10:03:17 carpo systemd[1]: redis.service: main process exited, code=exited, status=233/RUNTIME_DIRECTORY
Mar 09 10:03:17 carpo systemd[702]: Failed at step RUNTIME_DIRECTORY spawning /usr/bin/redis-cli: File exists
Mar 09 10:03:17 carpo systemd[1]: redis.service: control process exited, code=exited status=233
Mar 09 10:03:17 carpo systemd[1]: Unit redis.service entered failed state.
Mar 09 10:03:17 carpo systemd[1]: redis.service failed.
Restarting it manually after the boot starts it properly. RuntimeDirectory was added recently by the package. Directory /run is not persistant:
# mount | grep -e '^run'
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
I am stuck on figuring out what happens here. Did anybody else have this issue?
Last edited by kotnik (2015-03-18 09:44:48)

sharow wrote:related: https://bugs.archlinux.org/task/44067
Thank you for pointing me to that issue.
Issue is solved in version 2.8.19-4.

[SOLVED] systemd: Failed to open private dbus connection

Below is a snapshot from journalctl -b:
systemd[1]: Starting user-1000.slice.
systemd[1]: Created slice user-1000.slice.
systemd[1]: Starting User Manager for 1000...
systemd[1]: Starting Session 1 of user me.
systemd[1]: Started Session 1 of user me.
systemd-logind[195]: New session 1 of user me.
systemd[261]: pam_unix(systemd-user:session): session opened for user me by (uid=0)
systemd[261]: Failed to open private dbus connection: Failed to connect to socet /run/usr/1000/dbususer_bus_socket: No such file or directory
systemd[261]: Mounted /sys/kernel/config.
systemd[261]: Stopped target Bluetooth.
systemd[261]: Stopped target Sound Card.
systemd[261] Starting Default.
systemd[261]: Reached target Default.
systemd[261]: Startup finished in 135ms.
systemd[1]: Started User Manager for 1000.
login[199]: LOGIN ON tty1 BY me
It's a fresh Arch Linux install and I didn't even had a time yet to tinker with systemd so it's unlikely that I've messed things up. I suspect that it might be the cause of the following problem:
$ systemctl status --user
Failed to issue method call: Process /bin/false exited with status 1
For reference, systemd version:
$ systemctl --version
systemd 207
+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ
Any ideas how can I solve the private dbus connection problem?
Last edited by vox23 (2013-09-25 17:02:22)

65kid wrote:do you actually experience any problems?
I thought that it might be related to:
$ systemctl status --user
Failed to issue method call: Process /bin/false exited with status 1
however when I followed wiki and created:
$cat /etc/systemd/system/[email protected]/environment.conf
[Service]
Environment=DISPLAY=:0
Environment=XDG_RUNTIME_DIR=/run/user/%I
Environment=SHELL=%s
then /bin/false error went away. I still have some problems with systemd managing my user session but unrelated to the above. Marking as solved.

[Solved] SystemD, how to start a service after network is up.

Hello,
I'm recently involved to set up a daemon which should be ready after boot (aria2). Then it fails, as it fails minidlna as well.
The reason is that they try to come up but there's no host to talk to. See this page.
For my purposes, it should be good when the daemons find the necessary to stay alive (even they won't have a network fully ready, that may happen in less than a minute later). For minidlna is needed a valid IP which could be 127.0.0.1 or localhost, for aria2 it may be same or just looking for a RPC binding.
This what the logs are telling me.
I was trying to set more dependencies in the service, but even to set
After=wpa_supplicant.service
it doesn't have effect.
I don't find a solution, as far as my knowledge spans. Another chance would take to set a systemD timer and when that will be gone to start the daemon. Sorry but I don't know much about that.
Looking for someone here to guide to right direction.
TIA
Last edited by TheSaint (2013-07-15 03:12:37)

WonderWoofy wrote:It depends on what network management utility you use and therefore also how you connect. If you are using an ethernet connection, you could just use dhcpcd@<interface>.service. This is a very simple service, and the network.target will not be reached until the IP address and connectivity is established.
Meanwhile some good suggestion (like yours) came up, I've tried a couple of recipes. But dhcpcd.service didn't get it right. Maybe dhcpcd@<interface>.service, would work, I'll see later.
I got this working:
[Unit]
Description=aria2 Service
Requires=network.target
After=dhcpcd.service
[Service]
Type=forking
User=aria2
Group=aria2
EnvironmentFile=/etc/conf.d/aria2.conf
WorkingDirectory=/var/aria2
ExecStart=/usr/bin/aria2c $ARIACMD
ExecReload=/usr/bin/kill -HUP $MAINPID
RestartSec=1min
Restart=on-failure
[Install]
WantedBy=multi-user.target
You may note the After=dhcpcd.service, but it doesn't work. I found RestartSec=1min ,Restart=on-failure more effective and perhaps less blocking to wait for the network to be ready. As a server this should be a small issue, very seldom compared with the running time. We (family members) can accept a little wait for the service to be on.
Exactly I don't know which of the two is the right solution, maybe the delay is the right one.
I was doing a cron scheduled job, before using systemd boot, which was kicking minidlna every 5 minutes, since it was dieing often. I didn't discover what was the reason.
I think I'll have to study another recipe which sets up a timer and keep an eye on these two services, for the long term service. But even cron would suffice, I think.
WonderWoofy wrote:if you are using wireless, the only two real solutions would be to use netctl@<profile>.service, which too won't reach the network.target until a conplete connection is made
Yes I'm on wireless network and the interface plugged on USB . My intent should go beyond any particular configuration. Maybe because I'd like to show a working setup, which may fit for all configuration (90 % )
I have to admit that the actual solution do not care much whether the network is found, so I hope to get a smarter setup that counts on the necessary tools before try something. However it's proved that they fail when no connection to the router is done. But I'm preferring that they succeed.
WonderWoofy wrote: NetworkManager gets around this by implementing an additional service called (unimaginatively) NetworkManager-wait-online.service, which is pulled in automatically when you enable NetowrkManager.service.
As I stated above I'm expecting a solution that won't pull in so much dependencies. Even NM is my connection manager, on the server.
WonderWoofy wrote:
You probably also want to use Requisite=aria2c.service on the minidlna.service as well. This too means that it will be started after aria2c, but that it will not start at all if it is not running or fails.
Additionally, you could try using the Requisite configuration on the minidnla, while setting the aria2c to restart itself on failure. So that it will keep trying, and once it does, then minidlna will start.
looks like a dog biting the tail . It's much preferable a separated failure, just in case.
WonderWoofy wrote:Edit: Also, it is not SystemD. It is systemd (like other "daemon" binaries in *nix).
I'm quite sure I saw it somewhere, none of my inventions
Last edited by TheSaint (2013-07-13 07:10:33)

[SOLVED] systemd service not starting

Hi,
Been using Arch for just over a week now moving from Ubuntu and loving it. Achieved so much more on Arch in this short time until this evening.
I am trying to run a shell script at startup. I added the service file under /etc/systemd/system/myapp.service
With the following content:
[Unit]
Description=Notification
[Service]
ExecStart=/usr/bin/myscript
[Install]
WantedBy=multi-user.target
As it is I can run "systemctl restart myapp.service" and the script execute flawlessly however on reboot it does nothing and I get this error when I run systemctl status myapp.service:
systemctl status myapp.service
myapp.service - Notification
Loaded: loaded (/etc/systemd/system/myapp.service; enabled)
Active: failed (Result: exit-code) since Thu 1970-01-01 10:00:08 EST; 14s ago
Process: 116 ExecStart=/usr/bin/myscript (code=exited, status=6)
Other info:
Script starts with #!/bin/sh
Script permissions 755
Tried adding After=network.target under unit.
Tried Type=oneshot and forking
O yes /var/log/messages.log | grep myapp
Sep 6 14:25:56 alarm systemd[1]: [/etc/systemd/system/myapp.service:1] Unknown section 'unit'. Ignoring.
Sep 6 14:25:56 alarm systemd[1]: [/etc/systemd/system/myapp.service:2] Assignment outside of section. Ignoring.
Jan 1 01:00:11 alarm systemd[1]: myapp.service: main process exited, code=exited, status=6/NOTCONFIGURED
Jan 1 01:00:11 alarm systemd[1]: Unit myapp.service entered failed state.
Jan 1 01:00:11 alarm [ 3.243318] systemd[1]: [/etc/systemd/system/myapp.service:1] Unknown section 'unit'. Ignoring.
Jan 1 01:00:11 alarm [ 3.243490] systemd[1]: [/etc/systemd/system/myapp.service:2] Assignment outside of section. Ignoring.
Only thing I dont get is the date difference? I have set the timezone correctly..
Any suggestions?
thanks
Last edited by blueteq (2013-09-10 10:01:11)

Reaching the network.target does not necessarily mean that an active connection has been reached. For example, if you use wicd or netctl-auto, it will report the stating of the service as successful after the daemon itself has started, but starting the daemon simply means that it is ready to start scanning for wireless networks and then connect.
If you want to be absolutely sure that there is a network connection before the service starts, you should use NetworkManager.service. That will also pull in the NetworkManager-wait-online.service which will not complete until a full connection has been reached. At that point the startup will have reached the network-online.target. So you should order the service after that instead. In reality, you should order it after that anyway, no matter what netowrk connection service you use, as that is a built in target to systemd.
Even though you have the RestartSec=35 and Restart=on-failure (which is a sane thing to do IMO), it is probably a good idea to order it After=netowrk-online.target anyway, as that will cause the service to start a bit later and at least attempt to order itself correctly. That way it will also ensure that the service is stopped before the network is taken down as well, hopefully ensuring a clean disconnect as well.

[Solved] systemd fails to start spawning /bin/plymouth

Similar Messages

Maybe you are looking for