Bug#742668: cups: Fails to install because can't listen to sockets

2014-05-21 Thread Giuseppe Bilotta
Hello Didier,

On Mon, May 12, 2014 at 6:38 PM, Didier 'OdyX' Raboud o...@debian.org wrote:
 # Matches 'Listen localhost:631' from cupsd.conf
 ListenStream=127.0.0.1:631
 ListenStream=[::1]:631
 # Matches 'Port 631' from cupsd.conf
 ListenStream=0.0.0.0:631
 ListenStream=[::]:631

 Ha. So apparently you have two overlapping instructions in
 /etc/cups/cupsd.conf: 'Port 631' and 'Listen localhost:631'.

 Can you try to remove the three last lines of the
 /etc/systemd/system/cups.socket.d/cupsd-listen.conf file and try to
 restart CUPS?

I've removed the first three (the ones derived from Listen
localhost:631) instead, in case listening only on 127.0.0.1 would
prevent other computers in the network from connecting to the CUPS
server, and now it starts and configuring finishes, so the problem was
indeed due to the doubled ListenStream specification.

-- 
Giuseppe Oblomov Bilotta


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#742668: cups: Fails to install because can't listen to sockets

2014-05-21 Thread Didier 'OdyX' Raboud
Control: tags -1 +confirmed +pending

Le mercredi, 21 mai 2014, 10.52:30 Giuseppe Bilotta a écrit :
 On Mon, May 12, 2014 at 6:38 PM, Didier 'OdyX' Raboud 
o...@debian.org wrote:
  # Matches 'Listen localhost:631' from cupsd.conf
  ListenStream=127.0.0.1:631
  ListenStream=[::1]:631
  # Matches 'Port 631' from cupsd.conf
  ListenStream=0.0.0.0:631
  ListenStream=[::]:631
  
  Ha. So apparently you have two overlapping instructions in
  /etc/cups/cupsd.conf: 'Port 631' and 'Listen localhost:631'.
  
  Can you try to remove the three last lines of the
  /etc/systemd/system/cups.socket.d/cupsd-listen.conf file and try to
  restart CUPS?
 
 I've removed the first three (the ones derived from Listen
 localhost:631) instead, in case listening only on 127.0.0.1 would
 prevent other computers in the network from connecting to the CUPS
 server, and now it starts and configuring finishes, so the problem was
 indeed due to the doubled ListenStream specification.

Great. I have a fix pending which I'll upload soon; thanks for your 
patience!

Cheers,
OdyX


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#742668: cups: Fails to install because can't listen to sockets

2014-05-12 Thread Didier 'OdyX' Raboud
Hi Giuseppe,

Le jeudi, 8 mai 2014, 12.34:13 Giuseppe Bilotta a écrit :
 There is only:
 
 /etc/systemd/system/cups.socket.d/cupsd-listen.conf -
 ../../../cups/cupsd-systemd-listen.conf
 
 Contents:
 
 [Socket]
 # This file was generated by CUPS and _WILL_ be deleted or overwritten
 by it! # It has to be kept in sync with the Port and Listen stanzas
 in /etc/cups/cupsd.conf
 # It is by default symlinked as cups-listen.conf in the
 # /etc/systemd/system/cups.socket.d/ directory. Remove the symlink
 # and write your own file there if you don't want this. See
 systemd.socket(5). # Matches 'Listen localhost:631' from cupsd.conf
 ListenStream=127.0.0.1:631
 ListenStream=[::1]:631
 # Matches 'Port 631' from cupsd.conf
 ListenStream=0.0.0.0:631
 ListenStream=[::]:631

Ha. So apparently you have two overlapping instructions in 
/etc/cups/cupsd.conf: 'Port 631' and 'Listen localhost:631'.

Can you try to remove the three last lines of the 
/etc/systemd/system/cups.socket.d/cupsd-listen.conf file and try to 
restart CUPS?

If that works, I'll see if I can address that in the Debian-specific 
patches.

Cheers,
OdyX


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#742668: cups: Fails to install because can't listen to sockets

2014-05-08 Thread Giuseppe Bilotta
Hello Didier, and thanks for your reply.

 Le mardi, 6 mai 2014, 14.23:41 Giuseppe Bilotta a écrit :
 I've just come across this issue during a dist-upgrade. The situation
 is the same as that of the original message: nothing is using port
 631 or the cups socket, but:

 Are you sure of that? Can you paste the output of the following command
 (run as root):
 netstat -lnptu | grep 631

There is no output (running under sudo).

 so cups-daemon, cups and cups-core-drivers fail to complete the
 upgrade/configure.

 Do you have a specific ipv6 configuration (module unloaded or
 blacklisted?

The module is not blacklisted, but it's not loaded either (I'm not in
an IPv6-enabled network).

 Can you attach the content of all files and symlinks in
 /etc/systemd/system/cups.socket.d ?

There is only:

/etc/systemd/system/cups.socket.d/cupsd-listen.conf -
../../../cups/cupsd-systemd-listen.conf

Contents:

[Socket]
# This file was generated by CUPS and _WILL_ be deleted or overwritten by it!
# It has to be kept in sync with the Port and Listen stanzas in
/etc/cups/cupsd.conf
# It is by default symlinked as cups-listen.conf in the
# /etc/systemd/system/cups.socket.d/ directory. Remove the symlink
# and write your own file there if you don't want this. See systemd.socket(5).
# Matches 'Listen localhost:631' from cupsd.conf
ListenStream=127.0.0.1:631
ListenStream=[::1]:631
# Matches 'Port 631' from cupsd.conf
ListenStream=0.0.0.0:631
ListenStream=[::]:631


 Could you also attach the output of `systemctl show cups.socket` ?

Here it is:

---8

Id=cups.socket
Names=cups.socket
Requires=sysinit.target -.mount
RequiredBy=cups.service configure-printer@usb-003-005.service
WantedBy=sockets.target
Conflicts=shutdown.target
Before=cups.service sockets.target shutdown.target
configure-printer@usb-003-005.service
After=sysinit.target -.mount
Triggers=cups.service
Description=CUPS Printing Service Sockets
LoadState=loaded
ActiveState=failed
SubState=failed
FragmentPath=/lib/systemd/system/cups.socket
DropInPaths=/etc/systemd/system/cups.socket.d/cupsd-listen.conf
UnitFileState=enabled
InactiveExitTimestampMonotonic=0
ActiveEnterTimestampMonotonic=0
ActiveExitTimestampMonotonic=0
InactiveEnterTimestampMonotonic=0
CanStart=yes
CanStop=yes
CanReload=no
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureIsolate=no
IgnoreOnIsolate=no
IgnoreOnSnapshot=no
NeedDaemonReload=no
JobTimeoutUSec=0
ConditionTimestamp=Wed 2014-05-07 19:32:51 CEST
ConditionTimestampMonotonic=496589287791
ConditionResult=yes
BindIPv6Only=ipv6-only
Backlog=128
TimeoutUSec=1min 30s
ControlPID=0
DirectoryMode=0755
SocketMode=0666
Accept=no
KeepAlive=no
Priority=-1
ReceiveBuffer=0
SendBuffer=0
IPTOS=-1
IPTTL=-1
PipeSize=0
FreeBind=no
Transparent=no
Broadcast=no
PassCredentials=no
PassSecurity=no
ListenStream=/var/run/cups/cups.sock
ListenStream=127.0.0.1:631
ListenStream=[::1]:631
ListenStream=0.0.0.0:631
ListenStream=[::]:631
Mark=-1
MaxConnections=64
NConnections=0
NAccepted=0
Result=resources
UMask=0022
LimitCPU=18446744073709551615
LimitFSIZE=18446744073709551615
LimitDATA=18446744073709551615
LimitSTACK=18446744073709551615
LimitCORE=18446744073709551615
LimitRSS=18446744073709551615
LimitNOFILE=4096
LimitAS=18446744073709551615
LimitNPROC=61379
LimitMEMLOCK=65536
LimitLOCKS=18446744073709551615
LimitSIGPENDING=61379
LimitMSGQUEUE=819200
LimitNICE=0
LimitRTPRIO=0
LimitRTTIME=18446744073709551615
OOMScoreAdjust=0
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=5
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SecureBits=0
CapabilityBoundingSet=18446744073709551615
MountFlags=0
PrivateTmp=no
PrivateNetwork=no
SameProcessGroup=no
ControlGroupModify=no
ControlGroupPersistent=no
IgnoreSIGPIPE=yes
NoNewPrivileges=no
KillMode=control-group
KillSignal=15
SendSIGKILL=yes
DefaultControlGroup=name=systemd:/system/cups.socket
ControlGroups=cpu:/system/cups.socket name=systemd:/system/cups.socket

---8


Cheers,

-- 
Giuseppe Oblomov Bilotta


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#742668: cups: Fails to install because can't listen to sockets

2014-05-06 Thread Didier 'OdyX' Raboud
Hi Giuseppe, and thanks for your followup,

Le mardi, 6 mai 2014, 14.23:41 Giuseppe Bilotta a écrit :
 I've just come across this issue during a dist-upgrade. The situation
 is the same as that of the original message: nothing is using port
 631 or the cups socket, but:

Are you sure of that? Can you paste the output of the following command 
(run as root):
netstat -lnptu | grep 631

 May 06 14:12:51 labrador systemd[1]: Starting CUPS Printing Service
 Sockets. May 06 14:12:51 labrador systemd[1]: cups.socket failed to
 listen on sockets: Address already in use May 06 14:12:51 labrador
 systemd[1]: Failed to listen on CUPS Printing Service Sockets. May 06
 14:12:56 labrador systemd[1]: Closed CUPS Printing Service Sockets.
 
 so cups-daemon, cups and cups-core-drivers fail to complete the
 upgrade/configure.

Do you have a specific ipv6 configuration (module unloaded or 
blacklisted?

Can you attach the content of all files and symlinks in 
/etc/systemd/system/cups.socket.d ?

Could you also attach the output of `systemctl show cups.socket` ?

Thanks in advance, cheers,
OdyX


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#742668: cups: Fails to install because can't listen to sockets

2014-05-06 Thread Giuseppe Bilotta
Package: cups
Version: 1.7.2-3
Followup-For: Bug #742668

I've just come across this issue during a dist-upgrade. The situation is the 
same as
that of the original message: nothing is using port 631 or the cups socket, but:

May 06 14:12:51 labrador systemd[1]: Starting CUPS Printing Service Sockets.
May 06 14:12:51 labrador systemd[1]: cups.socket failed to listen on sockets: 
Address already in use
May 06 14:12:51 labrador systemd[1]: Failed to listen on CUPS Printing Service 
Sockets.
May 06 14:12:56 labrador systemd[1]: Closed CUPS Printing Service Sockets.

so cups-daemon, cups and cups-core-drivers fail to complete the 
upgrade/configure.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cups depends on:
ii  cups-client1.7.2-3
ii  cups-common1.7.2-3
iu  cups-core-drivers  1.7.2-3
ih  cups-daemon1.7.2-3
ii  cups-filters   1.0.53-1
ii  cups-ppdc  1.7.2-3
ii  cups-server-common 1.7.2-3
ii  debconf [debconf-2.0]  1.5.53
ii  ghostscript9.05~dfsg-8.1
ii  libavahi-client3   0.6.31-4
ii  libavahi-common3   0.6.31-4
ii  libc-bin   2.18-5
ii  libc6  2.18-5
ii  libcups2   1.7.2-3
ii  libcupscgi11.7.2-3
ii  libcupsimage2  1.7.2-3
ii  libcupsmime1   1.7.2-3
ii  libcupsppdc1   1.7.2-3
ii  libgcc11:4.9.0-2
ii  libstdc++6 4.9.0-2
ii  libusb-1.0-0   2:1.0.18-2
ii  lsb-base   4.1+Debian12
ii  poppler-utils  0.24.5-3
ii  procps 1:3.3.9-4

Versions of packages cups recommends:
ii  avahi-daemon 0.6.31-4
ii  colord   1.0.6-1
ii  cups-filters [ghostscript-cups]  1.0.53-1
ii  printer-driver-gutenprint5.2.9-2

Versions of packages cups suggests:
ii  cups-bsd   1.7.2-3
ii  cups-pdf   2.6.1-9
ii  foomatic-db20140325-1
ii  hplip  3.14.1-1
ii  printer-driver-hpcups  3.14.1-1
ii  smbclient  2:4.1.7+dfsg-2
ii  udev   204-10

-- debconf information:
* cupsys/backend: lpd, socket, usb, snmp, dnssd
* cupsys/raw-print: true


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#742668: cups: Fails to install because can't listen to sockets

2014-04-02 Thread Didier 'OdyX' Raboud
Hi Wojciech,

Le mardi, 1 avril 2014, 20.23:02 Wojciech Margas a écrit :
 I upgraded cups from sid to version 1.7.1-12, and now printing is
 working. (…) However, cups-daemon still cannot finish post-install
 configuration:

 running dpkg --pending --configure ...
 Setting up cups-daemon (1.7.1-12) ...
 gzip: /var/log/cups/error_log.1: No such file or directory

Ah, that's interesting: my postinst code assumed that cups would have 
run for enough time to have all rotated logfiles. I have a patch pending 
to solve that.

Cheers,
OdyX


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#742668: cups: Fails to install because can't listen to sockets

2014-04-01 Thread Didier 'OdyX' Raboud
Control: tags -1 +moreinfo

Hi Adrian,

Le mercredi, 26 mars 2014, 05.15:38 Adrian Immanuel Kiess a écrit :
* What led up to the situation?
  Upgrading system
* What exactly did you do (or not do) that was effective (or
  ineffective)?
  apt-get -u dist-upgrade
* What was the outcome of this action?
  New cups version can't be installed, cups service no more running
 * What outcome did you expect instead?
  Working cups service
 
 by upgrading Debian/testing this day I get the following error:
 
 Do you want to continue? [Y/n] Y
 Setting up cups-daemon (1.7.1-10) ...
 A dependency job for cups.service failed. See 'journalctl -xn' for
 details.
 (…(
 -- Unit cups.socket has begun starting up.
 Mar 26 05:10:16 g6 systemd[1]: cups.socket failed to listen on
 sockets: Address already in use
 Mar 26 05:10:16 g6 systemd[1]: Failed to listen on CUPS Printing
 Service Sockets.
 
 Cups can't listen to default sockets (ports) but no other process is
 listening there. I guess this is a bug.

Would this be solved by cups 1.7.1-12? I've closed a gap which could 
allow these types of bugs in -11 and then -12.

Can you confirm?

Thanks in advance, cheers,
OdyX

signature.asc
Description: This is a digitally signed message part.


Bug#742668: cups: Fails to install because can't listen to sockets

2014-04-01 Thread Wojciech Margas

Hi OdyX,

I upgraded cups from sid to version 1.7.1-12, and now printing is 
working. Also all the cups links to /dev/null in /etc/systemd/system/ 
have disappeared, now it looks like:


/etc/systemd/system/cups.socket.d$ ls -al
total 12
drwxr-xr-x 2 root root 4096 Apr  1 19:27 .
drwxr-xr-x 8 root root 4096 Mar 31 19:21 ..
lrwxrwxrwx 1 root root   39 Apr  1 07:30 cupsd-listen.conf - 
../../../cups/cupsd-systemd-listen.conf

-rw-r--r-- 1 root root  687 Mar 29 19:51 cupsd-listen.conf~

However, cups-daemon still cannot finish post-install configuration:

dselect
running dpkg --pending --configure ...
Setting up cups-daemon (1.7.1-12) ...
gzip: /var/log/cups/error_log.1: No such file or directory
dpkg: error processing package cups-daemon (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of cups:
 cups depends on cups-daemon (= 1.7.1-12); however:
  Package cups-daemon is not configured yet.

dpkg: error processing package cups (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of cups-core-drivers:
 cups-core-drivers depends on cups-daemon (= 1.7.1-12); however:
  Package cups-daemon is not configured yet.

dpkg: error processing package cups-core-drivers (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 cups-daemon
 cups
 cups-core-drivers

dselect: warning: subprocess dpkg --configure returned error exit status 1
Press enter to continue.

Thank you for fixing CUPS. Although it cannot finish configuration, CUPS 
is fully functional again.


Wojciech


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#742668: cups: Fails to install because can't listen to sockets

2014-03-25 Thread Adrian Immanuel Kiess
Package: cups
Version: 1.7.1-10
Severity: important

Dear Maintainer,

   * What led up to the situation?
 Upgrading system
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 apt-get -u dist-upgrade
   * What was the outcome of this action?
 New cups version can't be installed, cups service no more running
   * What outcome did you expect instead?
 Working cups service

by upgrading Debian/testing this day I get the following error:

Do you want to continue? [Y/n] Y
Setting up cups-daemon (1.7.1-10) ...
A dependency job for cups.service failed. See 'journalctl -xn' for details.
invoke-rc.d: initscript cups, action start failed.
configured to not write apport reports
  configured to not write apport reports
configured to not write apport reports
 dpkg: error processing package cups-daemon (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of cups-core-drivers:
 cups-core-drivers depends on cups-daemon (= 1.7.1-10); however:
  Package cups-daemon is not configured yet.

dpkg: error processing package cups-core-drivers (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of cups:
 cups depends on cups-core-drivers (= 1.7.1-10); however:
  Package cups-core-drivers is not configured yet.
 cups depends on cups-daemon (= 1.7.1-10); however:
  Package cups-daemon is not configured yet.

dpkg: error processing package cups (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 cups-daemon
 cups-core-drivers
 cups
E: Sub-process /usr/bin/dpkg returned an error code (1)


journalctl -xn shows:

Mar 26 05:10:16 g6 systemd[1]: Starting CUPS Printing Service Sockets.
-- Subject: Unit cups.socket has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit cups.socket has begun starting up.
Mar 26 05:10:16 g6 systemd[1]: cups.socket failed to listen on sockets: Address
already in use
Mar 26 05:10:16 g6 systemd[1]: Failed to listen on CUPS Printing Service
Sockets.
-- Subject: Unit cups.socket has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation:
http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f0
3d
--
-- Unit cups.socket has failed.
--
-- The result is failed.
Mar 26 05:10:16 g6 systemd[1]: Dependency failed for CUPS Printing Service.
-- Subject: Unit cups.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation:
http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f0
3d
--
-- Unit cups.service has failed.
--
-- The result is dependency.


Cups can't listen to default sockets (ports) but no other process is listening
there. I guess this is a bug.

Because of this, cups is no more working.

Thanks for your efforts,

Adrian Immanuel KIESS




-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cups depends on:
ii  cups-client1.7.1-10
ii  cups-common1.7.1-10
iu  cups-core-drivers  1.7.1-10
ih  cups-daemon1.7.1-10
ii  cups-filters   1.0.47-2
ii  cups-ppdc  1.7.1-10
ii  cups-server-common 1.7.1-10
ii  debconf [debconf-2.0]  1.5.52
ii  ghostscript9.05~dfsg-8+b1
ii  libavahi-client3   0.6.31-4
ii  libavahi-common3   0.6.31-4
ii  libc-bin   2.18-4
ii  libc6  2.18-4
ii  libcups2   1.7.1-10
ii  libcupscgi11.7.1-10
ii  libcupsimage2  1.7.1-10
ii  libcupsmime1   1.7.1-10
ii  libcupsppdc1   1.7.1-10
ii  libgcc11:4.8.2-16
ii  libstdc++6 4.8.2-16
ii  libusb-1.0-0   2:1.0.17-1+b1
ii  lsb-base   4.1+Debian12
ii  poppler-utils  0.22.5-4
ii  procps 1:3.3.9-2

Versions of packages cups recommends:
ii  avahi-daemon 0.6.31-4
ii  colord   1.0.6-1
ii  cups-filters [ghostscript-cups]  1.0.47-2
ii  printer-driver-gutenprint5.2.9-1

Versions of packages cups suggests:
ii  cups-bsd   1.7.1-10
ii  cups-pdf   2.6.1-9
ii  foomatic-db20140218-1
pn  hplip  none
ii  printer-driver-hpcups  3.14.1-1
pn  smbclient  none
ii  udev   204-8

-- debconf information:
  cupsys/backend: lpd, socket, usb, snmp, dnssd
  cupsys/raw-print: true


-- 
To UNSUBSCRIBE,