CUPS does not start on system boot

[mico]

Hi folks,
my first post here, I hope I am putting this in the appropriate forum.

I have set up Archlinux from ArchLinuxARM-rpi-latest.tar.gz on Raspberry Pi B+

CUPS is installed and configured. Everything works fine when started manually with
$this->bbcode_second_pass_code('', 'systemctl start org.cups.cupsd.service')

I have enabled the service, symlinks were created, no errors.

$this->bbcode_second_pass_code('', '# systemctl list-unit-files | grep cups
org.cups.cupsd.path enabled
cups-browsed.service disabled
org.cups.cups-lpd@.service static
org.cups.cupsd.service enabled
org.cups.cups-lpd.socket disabled
org.cups.cupsd.socket enabled')

After each reboot, CUPS is not running:

$this->bbcode_second_pass_code('', '# systemctl status org.cups.cupsd.service
● org.cups.cupsd.service - CUPS Scheduler
Loaded: loaded (/usr/lib/systemd/system/org.cups.cupsd.service; enabled; vend
Active: inactive (dead)
Docs: man:cupsd(8)')

The journal shows only messages from stopping the service when the system was going down for reboot. No errors or anything about starting after reboot:

$this->bbcode_second_pass_code('', 'journalctl -xn --unit org.cups.cupsd.service
-- Unit org.cups.cupsd.service has begun starting up.
avg 14 20:11:23 alarmpi systemd[1]: Started CUPS Scheduler.
-- Subject: Unit org.cups.cupsd.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit org.cups.cupsd.service has finished starting up.
--
-- The start-up result is done.
avg 14 20:33:53 alarmpi systemd[1]: Stopping CUPS Scheduler...
-- Subject: Unit org.cups.cupsd.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit org.cups.cupsd.service has begun shutting down.
avg 14 20:33:53 alarmpi systemd[1]: Stopped CUPS Scheduler.
-- Subject: Unit org.cups.cupsd.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit org.cups.cupsd.service has finished shutting down.
')

The issue is with CUPS only. I installed ntp and it starts automatically after reboot.

[WarheadsSE]

`journalctl -lu` willget you more complete information. I suspect there is a reason it is shutting down.

[mico]

It is not shutting down by itself. That last message is from reboot when cups shut down due to system reboot. This is normal.

Problem is there aren't any messages afterwards about starting cups after reboot.

CUPS starts perfectly fine when started manually with systemctl start. Printing works, everything is fine except I have to manually start cups after each reboot.

Output of journalctl -lu org.cups.cupsd.service:
$this->bbcode_second_pass_code('', '
avg 15 09:26:50 pi-print systemd[1]: Starting CUPS Scheduler...
avg 15 09:26:51 pi-print systemd[1]: Started CUPS Scheduler.
avg 15 16:47:36 pi-print systemd[1]: Stopping CUPS Scheduler...
avg 15 16:47:37 pi-print systemd[1]: Stopped CUPS Scheduler.
')
At 09:26 I started cups with systemctl start then at 16:47 I did a reboot. As in my previous post, there are no messages about starting cups after rebooting.

I even disabled and enabled org.cups.cupsd.service a few times to no avail. The symlinks seem ok:
$this->bbcode_second_pass_code('', '
/etc/systemd/system/multi-user.target.wants/org.cups.cupsd.path -> /usr/lib/systemd/system/org.cups.cupsd.path
/etc/systemd/system/printer.target.wants/org.cups.cupsd.service -> /usr/lib/systemd/system/org.cups.cupsd.service
/etc/systemd/system/sockets.target.wants/org.cups.cupsd.socket -> /usr/lib/systemd/system/org.cups.cupsd.socket
')