Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su
On Wed 01 Feb 2017 at 21:55:00 +0000, Roba wrote:
> I hope you don't mind helping me still even most of this makes little
> sense to me. I still don't want all my ip stuff going out to the list
> So here is the output
>
> Brian:$ systemctl status cups
> �� cups.service - CUPS Scheduler
> Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor
> preset: ena
> Active: active (running) since Wed 2017-02-01 @@T; xh ymin ago
> Docs: man:cupsd(8)
> Main PID: 353 (cupsd)
> Tasks: 2 (limit: 4915)
> CGroup: /system.slice/cups.service
> ������ 353 /usr/sbin/cupsd -l
> ������5428 /usr/lib/cups/notifier/dbus dbus://
>
> Feb 01 zzzzz systemd[1]: Started CUPS Scheduler.
This shows that the main managing process, cupsd, is running. Without
it, you can do no printing. It looks good up to now. But see later.
> $ netstat -tulpan
> (Not all processes could be identified, non-owned process info
> will not be shown, you would have to be root to see it all.)
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address Foreign Address
> State PID/Program name
> tcp 0 0 0.0.0.0:38837 0.0.0.0:*
> LISTEN -
> tcp 0 0 0.0.0.0:22 0.0.0.0:*
> LISTEN -
> tcp 0 0 127.0.0.1:9050 0.0.0.0:*
> LISTEN -
> tcp 0 0 127.0.0.1:2013 0.0.0.0:*
> LISTEN -
> tcp 0 0 127.0.0.1:7070 0.0.0.0:*
> LISTEN -
> tcp 0 0 127.0.0.1:1984 0.0.0.0:*
> LISTEN -
> tcp 0 0 0.0.0.0:46465 0.0.0.0:*
> LISTEN -
> tcp 0 0 0.0.0.0:2049 0.0.0.0:*
> LISTEN -
> tcp 0 0 0.0.0.0:51395 0.0.0.0:*
> LISTEN -
> tcp 0 0 0.0.0.0:48197 0.0.0.0:*
> LISTEN -
> tcp 0 0 127.0.0.1:9000 0.0.0.0:*
> LISTEN -
> tcp 0 0 127.0.0.1:9001 0.0.0.0:*
> LISTEN -
> tcp 0 0 0.0.0.0:111 0.0.0.0:*
> LISTEN -
> tcp 0 0 192.168.1.45:53730 93.184.220.29:80
> TIME_WAIT -
> tcp 0 0 127.0.0.1:34794 127.0.0.1:9001
> ESTABLISHED -
> tcp 0 0 127.0.0.1:9001 127.0.0.1:34794
> ESTABLISHED -
> tcp 0 0 192.168.1.45:53728 93.184.220.29:80
> TIME_WAIT -
> tcp 0 0 192.168.1.45:53998 93.184.220.29:80
> TIME_WAIT -
> tcp 0 0 127.0.0.1:9000 127.0.0.1:44002
> ESTABLISHED -
> tcp 0 0 127.0.0.1:44002 127.0.0.1:9000
> ESTABLISHED -
> tcp 0 0 192.168.1.45:48406 54.192.217.183:443
> TIME_WAIT -
> tcp 0 0 192.168.1.45:45126 54.192.217.224:443
> TIME_WAIT -
> tcp 0 0 192.168.1.45:48584 54.192.217.207:443
> TIME_WAIT -
> tcp6 0 0 :::36915 :::*
> LISTEN -
> tcp6 0 0 :::22 :::*
> LISTEN -
> tcp6 0 0 :::60153 :::*
> LISTEN -
> tcp6 0 0 :::2049 :::*
> LISTEN -
> tcp6 0 0 :::51429 :::*
> LISTEN -
> tcp6 0 0 :::50731 :::*
> LISTEN -
> tcp6 0 0 :::111 :::*
> LISTEN -
> tcp6 0 0 2a02:2149:864a:4d:47310 2a00:1450:4017:803:::80
> TIME_WAIT -
> tcp6 0 0 2a02:2149:864a:4d:42114 2a00:1450:4017:804::443
> TIME_WAIT -
> tcp6 0 0 2a02:2149:864a:4d:33574 2a00:1450:4017:803::443
> TIME_WAIT -
> tcp6 0 0 2a02:2149:864a:4d:46414 2a00:1450:4017:803::443
> TIME_WAIT -
> udp 0 0 0.0.0.0:33645 0.0.0.0:*
> -
> udp 0 0 0.0.0.0:927 0.0.0.0:*
> -
> udp 0 0 0.0.0.0:5353 0.0.0.0:*
> -
> udp 0 0 0.0.0.0:48658 0.0.0.0:*
> -
> udp 0 0 0.0.0.0:34484 0.0.0.0:*
> -
> udp 0 0 0.0.0.0:2049 0.0.0.0:*
> -
> udp 0 0 0.0.0.0:68 0.0.0.0:*
> -
> udp 0 0 0.0.0.0:111 0.0.0.0:*
> -
> udp 0 0 0.0.0.0:35347 0.0.0.0:*
> -
> udp 0 0 0.0.0.0:35403 0.0.0.0:*
> -
> udp 0 0 0.0.0.0:631 0.0.0.0:*
> -
> udp6 0 0 :::927 :::*
> -
> udp6 0 0 :::5353 :::*
> -
> udp6 0 0 :::40494 :::*
> -
> udp6 0 0 :::42937 :::*
> -
> udp6 0 0 :::2049 :::*
> -
> udp6 0 0 :::111 :::*
> -
> udp6 0 0 :::47399 :::*
> -
> udp6 0 0 :::49449 :::*
> -
> udp6 0 0 :::41524 :::*
> -
>
> as root
>
> netstat -tulpan
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address Foreign Address
> State PID/Program name
> tcp 0 0 0.0.0.0:38837 0.0.0.0:*
> LISTEN 963/rpc.mountd
> tcp 0 0 0.0.0.0:22 0.0.0.0:*
> LISTEN 957/sshd
> tcp 0 0 127.0.0.1:9050 0.0.0.0:*
> LISTEN 1123/tor
> tcp 0 0 127.0.0.1:2013 0.0.0.0:*
> LISTEN 1803/bitmask
> tcp 0 0 127.0.0.1:7070 0.0.0.0:*
> LISTEN 1803/bitmask
> tcp 0 0 127.0.0.1:1984 0.0.0.0:*
> LISTEN 1803/bitmask
> tcp 0 0 0.0.0.0:46465 0.0.0.0:*
> LISTEN -
> tcp 0 0 0.0.0.0:2049 0.0.0.0:*
> LISTEN -
> tcp 0 0 0.0.0.0:51395 0.0.0.0:*
> LISTEN 963/rpc.mountd
> tcp 0 0 0.0.0.0:48197 0.0.0.0:*
> LISTEN 963/rpc.mountd
> tcp 0 0 127.0.0.1:9000 0.0.0.0:*
> LISTEN 1803/bitmask
> tcp 0 0 127.0.0.1:9001 0.0.0.0:*
> LISTEN 1803/bitmask
> tcp 0 0 0.0.0.0:111 0.0.0.0:*
> LISTEN 327/rpcbind
> tcp 0 0 127.0.0.1:34794 127.0.0.1:9001
> ESTABLISHED 1803/bitmask
> tcp 0 0 127.0.0.1:9001 127.0.0.1:34794
> ESTABLISHED 1803/bitmask
> tcp 0 0 127.0.0.1:9000 127.0.0.1:44002
> ESTABLISHED 1803/bitmask
> tcp 0 0 127.0.0.1:44002 127.0.0.1:9000
> ESTABLISHED 1803/bitmask
> tcp6 0 0 :::36915 :::*
> LISTEN -
> tcp6 0 0 :::22 :::*
> LISTEN 957/sshd
> tcp6 0 0 :::60153 :::*
> LISTEN 963/rpc.mountd
> tcp6 0 0 :::2049 :::*
> LISTEN -
> tcp6 0 0 :::51429 :::*
> LISTEN 963/rpc.mountd
> tcp6 0 0 :::50731 :::*
> LISTEN 963/rpc.mountd
> tcp6 0 0 :::111 :::*
> LISTEN 327/rpcbind
> udp 0 0 0.0.0.0:33645 0.0.0.0:*
> 963/rpc.mountd
> udp 0 0 0.0.0.0:927 0.0.0.0:*
> 327/rpcbind
> udp 0 0 0.0.0.0:5353 0.0.0.0:*
> 357/avahi-daemon: r
> udp 0 0 0.0.0.0:48658 0.0.0.0:*
> -
> udp 0 0 0.0.0.0:34484 0.0.0.0:*
> 357/avahi-daemon: r
> udp 0 0 0.0.0.0:2049 0.0.0.0:*
> -
> udp 0 0 0.0.0.0:68 0.0.0.0:*
> 683/dhclient
> udp 0 0 0.0.0.0:111 0.0.0.0:*
> 327/rpcbind
> udp 0 0 0.0.0.0:35347 0.0.0.0:*
> 963/rpc.mountd
> udp 0 0 0.0.0.0:35403 0.0.0.0:*
> 963/rpc.mountd
> udp 0 0 0.0.0.0:631 0.0.0.0:*
> 442/cups-browsed
> udp6 0 0 :::927 :::*
> 327/rpcbind
> udp6 0 0 :::5353 :::*
> 357/avahi-daemon: r
> udp6 0 0 :::40494 :::*
> -
> udp6 0 0 :::42937 :::*
> 357/avahi-daemon: r
> udp6 0 0 :::2049 :::*
> -
> udp6 0 0 :::111 :::*
> 327/rpcbind
> udp6 0 0 :::47399 :::*
> 963/rpc.mountd
> udp6 0 0 :::49449 :::*
> 963/rpc.mountd
> udp6 0 0 :::41524 :::*
> 963/rpc.mountd
When cupsd starts (as yours has done) it listens for incoming connections
on port 631 for tcp and tcp6. Print jobs are sent to port 631. A browser
connects to tcp port 631. Your netstat output shows no listening on tcp
port 631. No wonder http://localhost:631 will not work.
Reason? No idea, but that is problem. It could lie with your cupsd.conf
in /etc/cups. Or something you have done with the networking setup.
You have cups-browsed listening on udp port 631 but it has nothing to do
with cupsd.
--
Brian.
Reply to: