Hi all,
I has a problem with CUPS. It sometimes "forgets" the IP address of my printer and stops printing (pausing the printer). The job is held in the queue. Here is what I see right now (as my printer is stuck yet again) in http://localhost:631/printers/Brother_MFC_J680DW:
pending since
Fri 01 Jan 2021 02:02:17 PM GMT
"No destination host name supplied by cups-browsed for printer "Brother_MFC_J680DW", is cups-browsed running?"
Whenever this happens, I check the status of cups-browsed and it is present:
/etc/cups # systemctl status cups-browsed
● cups-browsed.service - Make remote CUPS printers available locally
Loaded: loaded (/usr/lib/systemd/system/cups-browsed.service; disabled; vendor preset: enabled)
Active: active (running) (thawing) since Thu 2020-12-31 13:19:41 GMT; 24h ago
Main PID: 162645 (cups-browsed)
Tasks: 3 (limit: 38425)
Memory: 3.4M
CGroup: /system.slice/cups-browsed.service
└─162645 /usr/sbin/cups-browsed
Dec 31 13:19:41 hostname systemd[1]: Started Make remote CUPS printers available locally.
Now, if I restart this with systemctl restart cups-browsed the problem is fixed and the job that is pending immediately resumes printing.
So, any ideas what could be causing this? It's annoying having to bounce cups-browsed daily...
I noticed that in the status there is a "Active: active (running) (thawing)" and found it is part of freezing/unfreezing a process (https://www.freedesktop.org/software/systemd/man/systemctl.html#thaw%20PATTERN%E2%80%A6). So I am assuming something freezes cups-browsed and then it fails to unfreeze (i.e. "thaw").
When trying this manually I get:
/etc/cups # systemctl thaw cups-browsed.service
Failed to thaw unit cups-browsed.service: Unit 'cups-browsed.service' does not support freezing.
So how did something manage to freeze it in the first place and why is it stuck in "thawing" if it's not supposed to do that at all?
This started recently by the way; wondering if it's related to updates...
