Mageia forum

I just installed Mageia 7.1 and find that the CUPS server does not automatically start after rebooting.
I the control center it is set to start at boot. After I reboot the computer and check MCC, the cups server is listed as "stopped" and the box "start on boot" is checked.
I have to manually start it after every reboot.
That seems to be an issue.

Please show the output as root of

Code: Select all

systemctl status cups.service -al -n150

Here is the output

Code: Select all

● cups.service - CUPS Scheduler
   Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2019-09-27 16:06:53 EDT; 17h ago
     Docs: man:cupsd(8)
 Main PID: 28151 (cupsd)
   Status: "Scheduler is running..."
   Memory: 4.5M
   CGroup: /system.slice/cups.service
           └─28151 /usr/sbin/cupsd -l

Sep 27 16:06:53 localhost systemd[1]: Starting CUPS Scheduler...
Sep 27 16:06:53 localhost cupsd[28151]: Missing value on line 502 of /var/cache/cups/job.cache.
Sep 27 16:06:53 localhost cupsd[28151]: Missing value on line 1258 of /var/cache/cups/job.cache.
Sep 27 16:06:53 localhost cupsd[28151]: Missing value on line 1270 of /var/cache/cups/job.cache.
Sep 27 16:06:53 localhost cupsd[28151]: Missing value on line 4594 of /var/cache/cups/job.cache.
Sep 27 16:06:53 localhost cupsd[28151]: Missing value on line 5314 of /var/cache/cups/job.cache.
Sep 27 16:06:53 localhost cupsd[28151]: Missing value on line 5938 of /var/cache/cups/job.cache.
Sep 27 16:06:53 localhost cupsd[28151]: Missing value on line 5950 of /var/cache/cups/job.cache.
Sep 27 16:06:53 localhost cupsd[28151]: Missing value on line 5974 of /var/cache/cups/job.cache.
Sep 27 16:06:53 localhost cupsd[28151]: CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Sep 27 16:06:53 localhost cupsd[28151]: CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Sep 27 16:06:53 localhost cupsd[28151]: CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Sep 27 16:06:53 localhost cupsd[28151]: CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Sep 27 16:06:53 localhost cupsd[28151]: CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Sep 27 16:06:53 localhost cupsd[28151]: CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Sep 27 16:06:53 localhost cupsd[28151]: CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Sep 27 16:06:53 localhost cupsd[28151]: CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Sep 27 16:06:53 localhost cupsd[28151]: CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Sep 27 16:06:53 localhost systemd[1]: Started CUPS Scheduler.


Thank you

And this is after or before you manually started it ? I don't see an issue, it is started and it stays running.

yes that is after I started it manually.
I suspect everything above the "started" line relates to the attempt for it to begin at boot.

Can you please do a clean reboot, and rerun that command before starting cups manually ?

Just what i was thinking. finally had a chance to do it and here is the result after reboot and before any manual start.

Code: Select all

● cups.service - CUPS Scheduler
   Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit-hit) since Sat 2019-09-28 18:07:46 EDT; 2min 5s ago
     Docs: man:cupsd(8)
  Process: 5699 ExecStart=/usr/sbin/cupsd -l (code=killed, signal=TERM)
 Main PID: 5699 (code=killed, signal=TERM)

Sep 28 18:07:46 localhost systemd[1]: Starting CUPS Scheduler...
Sep 28 18:07:46 localhost cupsd[5699]: Missing value on line 502 of /var/cache/cups/job.cache.
Sep 28 18:07:46 localhost cupsd[5699]: Missing value on line 1258 of /var/cache/cups/job.cache.
Sep 28 18:07:46 localhost cupsd[5699]: Missing value on line 1270 of /var/cache/cups/job.cache.
Sep 28 18:07:46 localhost cupsd[5699]: Missing value on line 4594 of /var/cache/cups/job.cache.
Sep 28 18:07:46 localhost cupsd[5699]: Missing value on line 5314 of /var/cache/cups/job.cache.
Sep 28 18:07:46 localhost cupsd[5699]: Missing value on line 5938 of /var/cache/cups/job.cache.
Sep 28 18:07:46 localhost cupsd[5699]: Missing value on line 5950 of /var/cache/cups/job.cache.
Sep 28 18:07:46 localhost cupsd[5699]: Missing value on line 5974 of /var/cache/cups/job.cache.
Sep 28 18:07:46 localhost cupsd[5699]: CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Sep 28 18:07:46 localhost cupsd[5699]: CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Sep 28 18:07:46 localhost cupsd[5699]: CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Sep 28 18:07:46 localhost cupsd[5699]: CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Sep 28 18:07:46 localhost cupsd[5699]: CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Sep 28 18:07:46 localhost cupsd[5699]: CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Sep 28 18:07:46 localhost cupsd[5699]: CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Sep 28 18:07:46 localhost cupsd[5699]: CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Sep 28 18:07:46 localhost cupsd[5699]: CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Sep 28 18:07:46 localhost systemd[1]: cups.service: Main process exited, code=killed, status=15/TERM
Sep 28 18:07:46 localhost systemd[1]: cups.service: Succeeded.
Sep 28 18:07:46 localhost systemd[1]: Stopped CUPS Scheduler.
Sep 28 18:07:46 localhost systemd[1]: cups.service: Start request repeated too quickly.
Sep 28 18:07:46 localhost systemd[1]: cups.service: Failed with result 'start-limit-hit'.
Sep 28 18:07:46 localhost systemd[1]: Failed to start CUPS Scheduler.

Any further thoughts?

Not sure what the particular reason is. You could try to stop cups, and then move away / rename the cache /var/cache/cups/job.cache

I believe the
"CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files"
messages are because colord is not installed or not enabled, but they shouldn't prevent cups from starting.

After a quick search, seems this issue is already known: https://bugs.mageia.org/show_bug.cgi?id=24189
Is your printer powered on when you boot or powered off? The latter seems to be helping ...

Thank you for your help.

"CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files"
messages are because colord is not installed or not enabled, but they shouldn't prevent cups from starting.

Yes. Installed colord and message went away and no change in cups.service

You could try to stop cups, and then move away / rename the cache /var/cache/cups/job.cache

Tried this and it did not help.

Is your printer powered on when you boot or powered off? The latter seems to be helping ...

This resolved the issue. I turned off the printer and rebooted with it off and after the boot the cups.service was active.

Again thanks

You can follow https://bugs.mageia.org/show_bug.cgi?id=24189 for progress on the actual solution but as this is more or less a corner case and not easily reproducible, I don't see a fix coming soon ...

Thank you

@leon244

Please add your test comments in the bug 24189. It might help to narrow the issue.

OK