Cannot connect to localhost:631
AG
via the web-page using localhost:631. The error message is "cannot
connect: connection to the server refused".
I have double-checked /etc/hosts and that seems fine, checking the Net
for help throws up suggestions on changing a setting in cupsd.conf but
the only cupsd.conf file I can find on my system is a binary file in
/var/sbin. I also tried system-config-printer but that didn't help.
I have restarted the CUPS server and can print okay ... just cannot
connect to the server.
Anything else that I can try?
Cheers
AG
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/4DF899CE...@gmail.com
Juan Sierra Pons
Is cups daemon running?
What's on cups logs?
Best regards
--
Mi nueva dirección es: - My new email address is: - Mon nouveau email est:
ju...@elsotanillo.net
----------------------------------------------------------------------------
Usuario Linux Registrado: #257202
http://www.elsotanillo.net
----------------------------------------------------------------------------
2011/6/15 AG <computin...@googlemail.com>:
Archive: http://lists.debian.org/BANLkTinQ9JiMFip+...@mail.gmail.com
Camaleón
> On Wheezy, I have lost the capability of connecting to the CUPS server
> via the web-page using localhost:631. The error message is "cannot
> connect: connection to the server refused".
(...)
"http://127.0.0.1:631" neither works?
Check if the port is listening:
netstat -ant | grep 631
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Brian
> I have restarted the CUPS server and can print okay ... just cannot
> connect to the server.
CUPS needs a cupsd.conf to run. The file is installed when CUPS is
installed (it is not a binary file). I cannot see how you can get the
server restarted. /var/sbin does not exist on this system.
desktop:/home/brian# mv /etc/cups/cupsd.conf /etc/cups/cupsd.conf-orig
desktop:/home/brian#
desktop:/home/brian# /etc/init.d/cups restart
Restarting Common Unix Printing System: cupsd
Message from syslogd@desktop at Jun 15 13:55:33 ...
cupsd: Unable to read configuration file '/etc/cups/cupsd.conf' -
exiting!
cupsd: Child exited with status 1!
failed!
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20110615125639.GL19572@desktop
Wayne Topa
> On Wheezy, I have lost the capability of connecting to the CUPS server
> via the web-page using localhost:631. The error message is "cannot
> connect: connection to the server refused".
>
> I have double-checked /etc/hosts and that seems fine, checking the Net
> for help throws up suggestions on changing a setting in cupsd.conf but
> the only cupsd.conf file I can find on my system is a binary file in
> /var/sbin. I also tried system-config-printer but that didn't help.
>
> I have restarted the CUPS server and can print okay ... just cannot
> connect to the server.
>
> Anything else that I can try?
Is localhost allowed in /etc/hosys.allow?
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Juan Sierra Pons
What "nmap localhost" says?
Best Regards
--
Mi nueva dirección es: - My new email address is: - Mon nouveau email est:
ju...@elsotanillo.net
----------------------------------------------------------------------------
Usuario Linux Registrado: #257202
http://www.elsotanillo.net
----------------------------------------------------------------------------
2011/6/15 Wayne Topa <linu...@gmail.com>:
Archive: http://lists.debian.org/BANLkTiWgNuBJHG5N...@mail.gmail.com
Wayne Topa
> On 06/15/2011 07:38 AM, AG wrote:
>> On Wheezy, I have lost the capability of connecting to the CUPS server
>> via the web-page using localhost:631. The error message is "cannot
>> connect: connection to the server refused".
>>
>> I have double-checked /etc/hosts and that seems fine, checking the Net
>> for help throws up suggestions on changing a setting in cupsd.conf but
>> the only cupsd.conf file I can find on my system is a binary file in
>> /var/sbin. I also tried system-config-printer but that didn't help.
>>
>> I have restarted the CUPS server and can print okay ... just cannot
>> connect to the server.
>>
>> Anything else that I can try?
>
> Is localhost allowed in /etc/hosys.allow?
Have to learn to proof read. :-(
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
AG
> On 06/15/2011 07:38 AM, AG wrote:
>> On Wheezy, I have lost the capability of connecting to the CUPS server
>> via the web-page using localhost:631. The error message is "cannot
>> connect: connection to the server refused".
>>
>> I have double-checked /etc/hosts and that seems fine, checking the Net
>> for help throws up suggestions on changing a setting in cupsd.conf but
>> the only cupsd.conf file I can find on my system is a binary file in
>> /var/sbin. I also tried system-config-printer but that didn't help.
>>
>> I have restarted the CUPS server and can print okay ... just cannot
>> connect to the server.
>>
>> Anything else that I can try?
>
> Is localhost allowed in /etc/hosys.allow?
>
>
/etc/hosts.allow is empty
AG
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
AG
> On Wed, 15 Jun 2011 12:38:54 +0100, AG wrote:
>
>> On Wheezy, I have lost the capability of connecting to the CUPS server
>> via the web-page using localhost:631. The error message is "cannot
>> connect: connection to the server refused".
> (...)
>
> "http://127.0.0.1:631" neither works?
>
> Check if the port is listening:
>
> netstat -ant | grep 631
>
> Greetings,
>
No feedback from the command line. How do I open the port and how would
I secure it? Does it make any difference this being a USB printer?
Cheers
AG
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
AG
> On Wed 15 Jun 2011 at 12:38:54 +0100, AG wrote:
>
>> I have restarted the CUPS server and can print okay ... just cannot
>> connect to the server.
> CUPS needs a cupsd.conf to run. The file is installed when CUPS is
> installed (it is not a binary file). I cannot see how you can get the
> server restarted. /var/sbin does not exist on this system.
>
> desktop:/home/brian# mv /etc/cups/cupsd.conf /etc/cups/cupsd.conf-orig
> desktop:/home/brian#
>
> desktop:/home/brian# /etc/init.d/cups restart
> Restarting Common Unix Printing System: cupsd
> Message from syslogd@desktop at Jun 15 13:55:33 ...
> cupsd: Unable to read configuration file '/etc/cups/cupsd.conf' -
> exiting!
> cupsd: Child exited with status 1!
> failed!
>
>
My bad. Forget that stanza about /var/sbin . I have located it in
/etc/cups/cups.conf and elsewhere. Not sure what I was going on about :(
AG
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Camaleón
> On 15/06/11 13:03, Camaleón wrote:
>> On Wed, 15 Jun 2011 12:38:54 +0100, AG wrote:
>>
>>> On Wheezy, I have lost the capability of connecting to the CUPS server
>>> via the web-page using localhost:631. The error message is "cannot
>>> connect: connection to the server refused".
>> (...)
>>
>> "http://127.0.0.1:631" neither works?
>>
>> Check if the port is listening:
>>
>> netstat -ant | grep 631
>>
>
> No feedback from the command line.
Nothing? You should see something like:
sm01@stt008:~$ netstat -ant | grep 631
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN
tcp6 0 0 ::1:631 :::* LISTEN
> How do I open the port and how would I secure it?
Cups daemon (the start up script) should care about opening the socket at
booting, unless it has been manually disabled.
> Does it make any difference this being a USB printer?
I think that's irrelevant, at least for the port binding. Even with no
printers at all Cups should open the port, but dunno why is failing to
do it so in your case, maybe a bug? :-?
http://packages.debian.org/changelogs/pool/main/c/cups/cups_1.4.6-9/changelog
Buff... I've found this stanza about "port numbers", but won't put my hand
on the fire this is what is causing you the grief :-P
* debian/patches/cups-avahi.dpatch: In contrary to the libdns_sd API the
Avahi API requires port numbers in host order and not in network order.
This made the Avahi-based DNS-SD broadcasting of CUPS advertizing wronmg
port numbers. Updated the Avahi patch to fix it. Thanks to Tim Waugh
from Red Hat on confirming this (LP: #792309).
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
lee
> On Wheezy, I have lost the capability of connecting to the CUPS server
> via the web-page using localhost:631. The error message is "cannot
> connect: connection to the server refused".
Did you check the configuration of cups to see which port it´s using? Is
cups actually running?
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Brian
> On 15/06/11 13:03, Camaleón wrote:
>>
>> Check if the port is listening:
>>
>> netstat -ant | grep 631
>
> No feedback from the command line.
You can print, so CUPS has be listening for a connection. Please do
/etc/init.d/cups restart
and post the output of
netstat -ant | grep LISTEN
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20110616145946.GQ19572@desktop
Wayne Topa
> On 15/06/11 14:35, Wayne Topa wrote:
>> On 06/15/2011 07:38 AM, AG wrote:
>>> On Wheezy, I have lost the capability of connecting to the CUPS server
>>> via the web-page using localhost:631. The error message is "cannot
>>> connect: connection to the server refused".
>>>
>>> I have double-checked /etc/hosts and that seems fine, checking the Net
>>> for help throws up suggestions on changing a setting in cupsd.conf but
>>> the only cupsd.conf file I can find on my system is a binary file in
>>> /var/sbin. I also tried system-config-printer but that didn't help.
>>>
>>> I have restarted the CUPS server and can print okay ... just cannot
>>> connect to the server.
>>>
>>> Anything else that I can try?
>>
>> Is localhost allowed in /etc/hosys.allow?
>>
>>
> Wayne
>
> /etc/hosts.allow is empty
>
forgotten to allow localhost in /etc/hosts.allow.
I see that you also get a cupsd.conf not found so that may, or may not,
be your only problem.
I see in other replies that you have something about /var/sbin. Are you
running Debian??
WT
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
AG
> On Thu 16 Jun 2011 at 14:25:01 +0100, AG wrote:
>
>>> Check if the port is listening:
>>>
>>> netstat -ant | grep 631
>> No feedback from the command line.
> You can print, so CUPS has be listening for a connection. Please do
>
> /etc/init.d/cups restart
>
> and post the output of
>
> netstat -ant | grep LISTEN
>
>
As requested after restarting /etc/init.d/cups :
$ sudo netstat -ant | grep LISTEN
tcp 0 0 127.0.0.1:8118 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
tcp6 0 0 ::1:25 :::* LISTEN
Apparently, it *isn't* listening, and yet still printing ... ?
AG
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
AG
> On 06/16/2011 09:23 AM, AG wrote:
>> On 15/06/11 14:35, Wayne Topa wrote:
>>> On 06/15/2011 07:38 AM, AG wrote:
>>>> On Wheezy, I have lost the capability of connecting to the CUPS server
>>>> via the web-page using localhost:631. The error message is "cannot
>>>> connect: connection to the server refused".
>>>>
>>>> I have double-checked /etc/hosts and that seems fine, checking the Net
>>>> for help throws up suggestions on changing a setting in cupsd.conf but
>>>> the only cupsd.conf file I can find on my system is a binary file in
>>>> /var/sbin. I also tried system-config-printer but that didn't help.
>>>>
>>>> I have restarted the CUPS server and can print okay ... just cannot
>>>> connect to the server.
>>>>
>>>> Anything else that I can try?
>>> Is localhost allowed in /etc/hosys.allow?
>>>
>>>
>> Wayne
>>
>> /etc/hosts.allow is empty
>>
> ISTR a problem getting to localhost:631 when I installed squeeze. I had
> forgotten to allow localhost in /etc/hosts.allow.
Wayne
Perhaps it would work for me to fill this in, although to be fair, I
don't recall having to do so in previous installations/ upgrades.
However, this has been a problematic transition from squeeze to wheezy
thus far, and this may be more of the same.
Any quick leads on the correct layout/ terms to use in the relevant
stanza in the file?
> I see that you also get a cupsd.conf not found so that may, or may not,
> be your only problem.
>
> I see in other replies that you have something about /var/sbin. Are you
> running Debian??
Yes - my bad. I had my head somewhere else entirely when I wrote that.
Pls disregard.
Cheers
AG
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
AG
> AG<computin...@googlemail.com> writes:
>
>> On Wheezy, I have lost the capability of connecting to the CUPS server
>> via the web-page using localhost:631. The error message is "cannot
>> connect: connection to the server refused".
> Did you check the configuration of cups to see which port it�s using? Is
> cups actually running?
>
>
Yes, the server *is* running. Below is the cups.conf file - doesn't
seem to be anything about ports in here except for sockets in
/var/run/cups, nor permissions to access the server. Is this in a
different file?
LogLevel warn
MaxLogSize 0
SystemGroup lpadmin
Listen /var/run/cups/cups.sock
Listen /var/run/cups/cups.sock
Browsing On
BrowseOrder allow,deny
BrowseAllow all
BrowseLocalProtocols CUPS dnssd
DefaultAuthType Basic
<Location />
Order allow,deny
</Location>
<Location /admin>
Order allow,deny
</Location>
<Location /admin/conf>
AuthType Default
Require user @SYSTEM
Order allow,deny
</Location>
<Policy default>
<Limit Create-Job Print-Job Print-URI Validate-Job>
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job
Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription
Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job
Suspend-Current-Job Resume-Job CUPS-Move-Job CUPS-Get-Document>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class
CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer
Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs
Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer
Startup-Printer Promote-Job Schedule-Job-After CUPS-Accept-Jobs
CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Authenticate-Job>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
<Policy authenticated>
<Limit Create-Job Print-Job Print-URI Validate-Job>
AuthType Default
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job
Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription
Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job
Suspend-Current-Job Resume-Job CUPS-Move-Job CUPS-Get-Document>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class
CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer
Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs
Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer
Startup-Printer Promote-Job Schedule-Job-After CUPS-Accept-Jobs
CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
PreserveJobHistory No
Cheers
AG
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Brian
> As requested after restarting /etc/init.d/cups :
>
> $ sudo netstat -ant | grep LISTEN
> tcp 0 0 127.0.0.1:8118 0.0.0.0:* LISTEN
> tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
> tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN
> tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
> tcp6 0 0 ::1:25 :::* LISTEN
>
> Apparently, it *isn't* listening, and yet still printing ... ?
I wonder what's on ports 8118 and 9050? netstat -tulpan would say. If
CUPS isn't hiding there (and I can see why it should be!) it just may be
time to think how you can print without it and what it did when it was
restarted.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20110616163758.GR19572@desktop
Brian
> LogLevel warn
> MaxLogSize 0
> SystemGroup lpadmin
> Listen /var/run/cups/cups.sock
> Listen /var/run/cups/cups.sock
Naughty!
Listen localhost:631
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20110616164529.GT19572@desktop
Dom
> On 16/06/11 15:36, lee wrote:
>> AG<computin...@googlemail.com> writes:
>>
>>> On Wheezy, I have lost the capability of connecting to the CUPS server
>>> via the web-page using localhost:631. The error message is "cannot
>>> connect: connection to the server refused".
>> cups actually running?
>>
>>
>
> Yes, the server *is* running. Below is the cups.conf file - doesn't seem
> to be anything about ports in here except for sockets in /var/run/cups,
> nor permissions to access the server. Is this in a different file?
>
> LogLevel warn
> MaxLogSize 0
> SystemGroup lpadmin
> Listen /var/run/cups/cups.sock
> Listen /var/run/cups/cups.sock
You seem to have two of those socket Listen lines, but I doubt that will
cause a problem.
My cupsd.conf on wheezy has:
Listen localhost:631
Listen /var/run/cups/cups.sock
and accessing via the web page works.
--
Dom
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Camaleón
> On Thu 16 Jun 2011 at 17:08:04 +0100, AG wrote:
>
>> As requested after restarting /etc/init.d/cups :
>>
>> $ sudo netstat -ant | grep LISTEN
>> tcp 0 0 127.0.0.1:8118 0.0.0.0:* LISTEN
>> tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
>> tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN
>> tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
>> tcp6 0 0 ::1:25 :::* LISTEN
>>
>> Apparently, it *isn't* listening, and yet still printing ... ?
>
> I wonder what's on ports 8118 and 9050? netstat -tulpan would say.
(...)
As root, running "lsof -i :8118 -i :9050" will also tell.
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Wayne Topa
> On 16/06/11 15:36, lee wrote:
>> AG<computin...@googlemail.com> writes:
>>
>>> On Wheezy, I have lost the capability of connecting to the CUPS server
>>> via the web-page using localhost:631. The error message is "cannot
>>> connect: connection to the server refused".
>> Did you check the configuration of cups to see which port it�s using? Is
>> cups actually running?
>>
>>
>
> Yes, the server *is* running. Below is the cups.conf file - doesn't seem
> to be anything about ports in here except for sockets in /var/run/cups,
> nor permissions to access the server. Is this in a different file?
>
> LogLevel warn
> MaxLogSize 0
> SystemGroup lpadmin
> Listen /var/run/cups/cups.sock
> Listen /var/run/cups/cups.sock
> Browsing On
I have at the top of cupsd.conf a line it seems you are missing:
# Only listen for connections from the local machine.
Listen localhost:631
Wayne
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
AG
> On Thu, 16 Jun 2011 17:37:58 +0100, Brian wrote:
>
>> On Thu 16 Jun 2011 at 17:08:04 +0100, AG wrote:
>>
>>> As requested after restarting /etc/init.d/cups :
>>>
>>> $ sudo netstat -ant | grep LISTEN
>>> tcp 0 0 127.0.0.1:8118 0.0.0.0:* LISTEN
>>> tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
>>> tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN
>>> tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
>>> tcp6 0 0 ::1:25 :::* LISTEN
>>>
>>> Apparently, it *isn't* listening, and yet still printing ... ?
>> I wonder what's on ports 8118 and 9050? netstat -tulpan would say.
> (...)
>
> As root, running "lsof -i :8118 -i :9050" will also tell.
>
> Greetings,
>
Output of $ sudo lsof -i :8118 -i :9050
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
polipo 2061 proxy 0u IPv4 6654 0t0 TCP localhost:8118
(LISTEN)
tor 2674 debian-tor 7u IPv4 7055 0t0 TCP localhost:9050
(LISTEN)
But no cups ...
AG
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Camaleón
> On 16/06/11 18:30, Camaleón wrote:
>> On Thu, 16 Jun 2011 17:37:58 +0100, Brian wrote:
>>
>>> On Thu 16 Jun 2011 at 17:08:04 +0100, AG wrote:
>>>
>>>> As requested after restarting /etc/init.d/cups :
>>>>
>>>> $ sudo netstat -ant | grep LISTEN
>>>> tcp 0 0 127.0.0.1:8118 0.0.0.0:* LISTEN tcp
>>>> 0 0 127.0.0.1:25 0.0.0.0:* LISTEN tcp 0
>>>> 0 127.0.0.1:9050 0.0.0.0:* LISTEN tcp 0 0
>>>> 0.0.0.0:111 0.0.0.0:* LISTEN tcp6 0 0 ::1:25
>>>> :::* LISTEN
>>>>
>>>> Apparently, it *isn't* listening, and yet still printing ... ?
>>> I wonder what's on ports 8118 and 9050? netstat -tulpan would say.
>> (...)
>>
>> As root, running "lsof -i :8118 -i :9050" will also tell.
>>
>> Greetings,
>>
>>
> Output of $ sudo lsof -i :8118 -i :9050
>
> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME polipo
> 2061 proxy 0u IPv4 6654 0t0 TCP localhost:8118 (LISTEN)
> tor 2674 debian-tor 7u IPv4 7055 0t0 TCP localhost:9050
> (LISTEN)
>
> But no cups ...
Ah, polipo and tor. Nice, but this was just out of curiosity.
You already should have solved this! The anwswer is out there (I'm sure
I've read it some threads at the bottom) ;-)
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
AG
'Tis true ... and the line has been added, cups server restarted and viola!
Don't know why this wasn't done automagically, but there's more that I
don't know than that which I do ... so this adds to the list.
Thanks for your help.
AG
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
AG
> Listen localhost:631
Thanks Wayne
Added that to the top line and it works!!
Much appreciated.
AG
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Brian
[I meant '. . . cannot . . ' in my previous post]
> As root, running "lsof -i :8118 -i :9050" will also tell.
Indeed. It turns out netstat or lsof looking at unix domain sockets
would have been more fruitful. I always forget about the socket in var.
Something to remember: CUPS doesn't need a tcp connection to print
locally.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20110616191923.GU19572@desktop
Brian
> Don't know why this wasn't done automagically, but there's more that I
> don't know than that which I do ... so this adds to the list.
The First Law of System Configuration says: Nobody ever remembers what
they did.
I try to defeat this Law by documenting what I do in the file being
changed or by making notes. But my nature being what it is I often fail
to carry out this strategy and, when I do, the passage of even a few
hours is enough to dim my memory considerably. A year later any
recollections have disappeared.
My point: Upgrading to Wheezy does not touch cupsd.conf because it is a
conffile. The copy you have is from your Lenny days, but is not the
default it came with. There is no magic wand for Debian to wave. But
learning about something is magic.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20110616221434.GV19572@desktop
Wayne Topa
> On 16/06/11 19:04, Wayne Topa wrote:
>> Listen localhost:631
> Thanks Wayne
>
> Added that to the top line and it works!!
>
> Much appreciated.
Glad I could help.
Cheers
Wayne
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Camaleón
> On Thu 16 Jun 2011 at 17:30:09 +0000, Camaleón wrote:
>
> [I meant '. . . cannot . . ' in my previous post]
>
>> As root, running "lsof -i :8118 -i :9050" will also tell.
>
> Indeed. It turns out netstat or lsof looking at unix domain sockets
> would have been more fruitful. I always forget about the socket in var.
>
> Something to remember: CUPS doesn't need a tcp connection to print
> locally.
Well, we already knew that because AG said that he could print well in
his very first e-mail in the thread ;-)
What I was thinking (which finally had nothing to do with the problem) is
that Cups went binded to another port socket number, different than the
usual one (631).
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
AG
> On 06/16/2011 03:01 PM, AG wrote:
>> On 16/06/11 19:04, Wayne Topa wrote:
>>> Listen localhost:631
>> Thanks Wayne
>>
>> Added that to the top line and it works!!
>>
>> Much appreciated.
>
> Glad I could help.
>
> Cheers
> Wayne
>
>
Me too!! :)
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
AG
> On Thu 16 Jun 2011 at 20:03:14 +0100, AG wrote:
>
>> Don't know why this wasn't done automagically, but there's more that I
>> don't know than that which I do ... so this adds to the list.
> The First Law of System Configuration says: Nobody ever remembers what
> they did.
>
> I try to defeat this Law by documenting what I do in the file being
> changed or by making notes. But my nature being what it is I often fail
> to carry out this strategy and, when I do, the passage of even a few
> hours is enough to dim my memory considerably. A year later any
> recollections have disappeared.
>
> My point: Upgrading to Wheezy does not touch cupsd.conf because it is a
> conffile. The copy you have is from your Lenny days, but is not the
> default it came with. There is no magic wand for Debian to wave. But
> learning about something is magic.
>
>
Hi Brian
That's a good first rule - will have to remember that.
This was a brand new install from scratch - I backed up the relevant ~/
files and then formatted the drive and installed, so this is unlikely to
be an artefact, which is part of what makes this so puzzling, especially
given a number of changes that were quite unexpected and flummoxed me
from my experience with previous Debian installations. But, having said
that, there is just so much to learn/ understand about computers in
general and Debian in particular that if there is a problem with the
system, the first place I usually consider is whether it is PEBCAK ...
and that is usually the case!!
Thanks for your help.
Best
AG
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org