You are not logged in.

#1 2012-09-23 00:58:29

Convergence
Member
Registered: 2005-07-02
Posts: 370

"Sharing" cups printer causes systemd/journald to go crazy.

Let me say that I've kind of already posted on this in someone else's thread.  After re-reading part of the Forum Etiquette thread, I decided to give this it's own thread.   Here is that other thread:  https://bbs.archlinux.org/viewtopic.php … 6#p1165116

I had some trouble running cups after upgrading to pure systemd via the wiki.  I applied this fix: https://bbs.archlinux.org/viewtopic.php?id=146154, and it didn't seem to help.  Then I noticed that journald was thrashing my cpu and SSD producing millions of these errors:

Sep 20 14:38:04 t1000 systemd[1]: cups.service start request repeated too quickly, refusing to start.
Sep 20 14:38:04 t1000 systemd[1]: cups.service start request repeated too quickly, refusing to start.
Sep 20 14:38:04 t1000 systemd[1]: cups.service start request repeated too quickly, refusing to start.
Sep 20 14:38:04 t1000 systemd[1]: cups.service start request repeated too quickly, refusing to start.
Sep 20 14:38:04 t1000 systemd[1]: cups.service start request repeated too quickly, refusing to start.

I disabled the service, rebooted, used a vanilla cupsd.conf, and that seemed to fix everything.  Until, I (via cups' network interface) asked cups to "share" the printer over the network.  When I confirmed the changes, I got the message "restarting cups server", and I was back at square one.  My CPU usage was high, and once again Journald was cranking out thousands of errors every second as cups tried to restart. 

So, to sum up, "sharing" my printer on the network causes cups to fail somehow, this in turn causes journald and systemd to eat lots of cpu time, and floods my logs with errors.  Any suggestions?

Edit:  Markup Error.

Last edited by Convergence (2012-09-23 15:03:37)


It's a very deadly weapon to know what you're doing
---  William Murderface

Offline

#2 2012-09-27 03:17:02

Convergence
Member
Registered: 2005-07-02
Posts: 370

Re: "Sharing" cups printer causes systemd/journald to go crazy.

Huh. I guess it was just me.  Oh well, I'm going to toss my printer anyway due to hardware problems.


It's a very deadly weapon to know what you're doing
---  William Murderface

Offline

#3 2012-10-01 09:19:43

Šaran
Member
From: Bosnia
Registered: 2011-09-03
Posts: 407

Re: "Sharing" cups printer causes systemd/journald to go crazy.

Same thing happen to me just now. Restoring default config with sharing disabled solved it.

nss-mdns is installed and dbus daemon is started.

Oct 01 11:39:20 asus sudo[11794]: fuchs : TTY=pts/1 ; PWD=/home/fuchs ; USER=root ; COMMAND=/usr/bin/systemctl start cups.service
Oct 01 11:39:20 asus sudo[11794]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 01 11:39:20 asus systemd[1]: Starting CUPS Printing Service...
Oct 01 11:39:20 asus systemd[1]: Started CUPS Printing Service.
Oct 01 11:39:20 asus sudo[11794]: pam_unix(sudo:session): session closed for user root
Oct 01 11:39:20 asus cupsd[11797]: Unknown directive DefaultAuthType on line 9.
Oct 01 11:39:20 asus dbus-daemon[296]: dbus[296]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Oct 01 11:39:20 asus dbus[296]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Oct 01 11:39:20 asus dbus[296]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status 
Oct 01 11:39:20 asus dbus-daemon[296]: dbus[296]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 
Oct 01 11:39:20 asus cupsd[11797]: cupsd: client.c:757: avahi_client_get_host_name: Assertion `client' failed.
Oct 01 11:39:20 asus systemd[1]: cups.service: main process exited, code=killed, status=6
Oct 01 11:39:20 asus systemd[1]: Unit cups.service entered failed state.
Oct 01 11:39:21 asus sudo[11641]: pam_unix(sudo:session): session closed for user root
Oct 01 11:39:22 asus sudo[11810]: fuchs : TTY=pts/0 ; PWD=/home/fuchs ; USER=root ; COMMAND=/usr/bin/journalctl
Oct 01 11:39:22 asus sudo[11810]: pam_unix(sudo:session): session opened for user root by (uid=0)

This is probably related to this bug.

Last edited by Šaran (2012-10-01 09:44:48)

Offline

#4 2012-10-05 20:42:09

CyrIng
Member
From: France
Registered: 2010-07-17
Posts: 76
Website

Re: "Sharing" cups printer causes systemd/journald to go crazy.

Convergence wrote:

...

I disabled the service, rebooted, used a vanilla cupsd.conf, and that seemed to fix everything.  Until, I (via cups' network interface) asked cups to "share" the printer over the network.  When I confirmed the changes, I got the message "restarting cups server", and I was back at square one.  My CPU usage was high, and once again Journald was cranking out thousands of errors every second as cups tried to restart. 

So, to sum up, "sharing" my printer on the network causes cups to fail somehow, this in turn causes journald and systemd to eat lots of cpu time, and floods my logs with errors.  Any suggestions?

Edit:  Markup Error.

I have the same issue since I move to Systemd.
What a mess , my fs /var/log filled 100%. fortunately It was mounted to a limited 64MB tmpfs
As you did, the workaround is ;

# systemctl stop cups.service
# systemctl stop cups.path
# systemctl stop cups.socket

Now, I'm left without any printer

Offline

#5 2012-10-05 21:56:52

ataraxia
Member
From: Pittsburgh
Registered: 2007-05-06
Posts: 1,545

Re: "Sharing" cups printer causes systemd/journald to go crazy.

I suspect that avahi-daemon needs to be running for cups to work with sharing enabled.

Offline

#6 2012-10-30 06:37:47

gemon
Member
Registered: 2010-11-23
Posts: 20

Re: "Sharing" cups printer causes systemd/journald to go crazy.

I have exactly the same problem with dbus.service ... it goes crazy and fills my log with thousand of lines like

dbus.service start request repeated too quickly, refusing to start

trying to figure out what's the problem, but systemd is not that usable with a chrooted environment...

Gemon

Offline

#7 2012-12-23 20:47:15

martinled
Member
Registered: 2012-12-23
Posts: 5

Re: "Sharing" cups printer causes systemd/journald to go crazy.

I wonder if anybody found a solution to this problem. I want to share my printer with another computer on the local network but my systemd goes crazy by eating all my cpu after any attempt, with the message "cups.service start request repeated too quickly, refusing to start" in my cups log file. The problem appears whether by sharing the printer using the web interface or by modifying the cupsd.conf file in which I replaced the following lines:

Listen localhost:631 -> Port 631

And changed

<Location />
  Order allow,deny
</Location>

for the following:

<Location />
  Order allow,deny
  Allow from localhost
  Allow from 192.168.1.101/255.255.255.0
</Location>
where 192.168.1.101 is the IP of the computer I want to access the printer connected to my laptop.

Any help would be very much appreciated.
Thanks !

Offline

#8 2013-01-20 17:11:41

Nudin
Member
Registered: 2012-11-22
Posts: 4

Re: "Sharing" cups printer causes systemd/journald to go crazy.

Having the same problem, I disabled networksharing of printers. (Don't need it realy)
But this Bug has filled my /var/log/journal with several GB of data. I wounder why this happens even when I have a maximum size of the logs configured as mentioned in the Wiki.

I'm not sure now, can I simply delete the content of the folder by rm, or is ther any better way to clean up the log?

Tanks,
Michi

Offline

#9 2013-03-04 18:40:04

martinled
Member
Registered: 2012-12-23
Posts: 5

Re: "Sharing" cups printer causes systemd/journald to go crazy.

Did anybody found a solution to this problem ? Plz note that it does not seem related to my hardware since in the past I sucessfully shared the same printer with the same computers, but under Debian.

Thanks again!

Offline

#10 2013-03-04 18:59:47

dave1
Member
Registered: 2010-04-07
Posts: 5

Re: "Sharing" cups printer causes systemd/journald to go crazy.

I'm no expert here, but I had a similar problem that was solved by starting avahi.service at boot. No idea why. Before this, every time I tried to restart cups it failed.

Offline

#11 2013-03-05 03:30:19

martinled
Member
Registered: 2012-12-23
Posts: 5

Re: "Sharing" cups printer causes systemd/journald to go crazy.

Thank you so much dave1, your solution completely solved my problem. I have been able to share my printer through the local network, and systemd is still acting normally. 

I used the following steps:
1) sudo pacman -S avahi
2) sudo systemctl enable avahi-daemon.service
3) reboot
4) share printer through the cups interface

While I don't know if this solution will work for other users in this thread, I can state that the symptoms they described (with systemd and journald) were practically identical to mine. I suggest to mark this thread as solved.

Thanks again for your help,
Martin

PS: If it can be usefull, my printer is an old Samsung ML-1430 and my laptop consists in a Dell inspiron 1525 running Manjaro Linux (based on Arch, indeed).

Offline

Board footer

Powered by FluxBB