You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.
Given CentOS 7 with Puppet 6.12 and CUPS 1.6.3, and 20+ queues present.
When I apply the manifest
class { 'cups':
service_ensure => 'running',
}
cups_queue { 'Office':
ensure => 'printer',
}
include cups::workarounds::systemd_service_restart
In order to manage a CUPS queue.
Then I get the error message:
Error: Could not prefetch cups_queue provider 'cups': IPP query 'ipptool -c ipp://localhost/ /dev/stdin' failed.
EXITCODE: 1
STDIN:
{
OPERATION CUPS-Get-Classes
GROUP operation
ATTR charset attributes-charset utf-8
ATTR language attributes-natural-language en
DISPLAY printer-name
DISPLAY member-names
}
STDOUT:
STDERR:
ipptool: Unable to connect to localhost on port 631 - Transport endpoint is not connected
Error: Failed to apply catalog: IPP query 'ipptool -c ipp://localhost/ /dev/stdin' failed.
In other words, issue #35 from last year was not really solved.
The workaround we added relies on cups.socket picking up connections until CUPS is ready, but the fix in bc45a96 just installs the systemd dropin without restarting the socket unit, so it does nothing. Also, the socket unit needs to be started before the service unit or it may fail to grab the socket.
The text was updated successfully, but these errors were encountered:
tequeter
added a commit
to tequeter/puppet-cups
that referenced
this issue
Feb 25, 2020
bc45a96 had only half the fix, as demonstrated in the updated
acceptance test.
It is necessary to restart the cups.service and cups.socket services in
that order, for the current Puppet run to work.
Fixesleoarnold#249.
Given CentOS 7 with Puppet 6.12 and CUPS 1.6.3, and 20+ queues present.
When I apply the manifest
In order to manage a CUPS queue.
Then I get the error message:
In other words, issue #35 from last year was not really solved.
The workaround we added relies on
cups.socket
picking up connections until CUPS is ready, but the fix in bc45a96 just installs the systemd dropin without restarting the socket unit, so it does nothing. Also, the socket unit needs to be started before the service unit or it may fail to grab the socket.The text was updated successfully, but these errors were encountered: