Connection problem (SOLVED)

[watchdog]

OK, in fact it was the "ServerName" line in the /etc/cups/client.conf 
(not in /etc/cups/cupsd.conf, which I scanned and doublechecked again 
and again, uselessly :-)) that was changed this summer to some 
particular thing and that I did not change back. So be careful if it 
happens to you a day or another :-)
JB


watchdog wrote:
> Anonymous wrote:
> 
>> Hello,
>> I'm puzzled.
>> CUPS used to work fine, but now I can no longer reach by any "lpstat 
>> -t", "lpq" or "lpr" command. I must say that my cupsd server is 
>> correctly running, and I can contact the webinterface on port 631 of 
>> my machine. To trouble shoot, I have put "Allow From All" lines in my 
>> cupsd.conf file, but the same behaviour remains: always get a 
>> "connection refused" or "scheduler not running" error when I try one 
>> of the above commands.
>> Even at a "debu2g" level, my /var/log/cupsd/error_log file does not 
>> contain any single line concerning the connection trials, just mute.
>> I am running a Debian testing distro, with cupsys 1.1.23-12.
>> Thanks!
>> JB
> 
> 
> OK, I still have no answer so I guess I have to be more accurate :
> 1) I have doublechecked for the rights, for instance on /dev/usb/lp0 
> (where my printer is). Put them 777, just to see.
> 2) I also checked my /etc/cups/cupsd.conf file. There I have "Allow From 
> All" lines and have commented the other (related) ones.
> 3) The web interface accessible through the http://localhost:631 is 
> operating correctly (btw, all is local, on a single machine directly 
> conected to the printer)
> 4) BUT none of the lpadmin, lpstat, lpq, etc... tools can access the 
> cups server.
> 5) I would like to have a /var/log/cups/access_log more detailed, but 
> the only verbosity option to be found in cupsd.conf is about error_log, 
> not access_log...
> 
> Any help would be great...
> Thanks