Bug#738801: cups: /etc/init.d/cups stop/start hang when systemd is installed

2014-02-13 Thread Damyan Ivanov
-=| Nye Liu, 12.02.2014 17:51:19 -0800 |=-
 Package: cups
 Version: 1.7.1-4
 Severity: important
 
 Dear Maintainer,
 
* What led up to the situation?
 
 running /etc/init.d/cups stop or start (for example, as root, or by
 logrotate)
 
* What exactly did you do (or not do) that was effective (or
  ineffective)?
 
 with cups running:
 # /etc/init.d/cups stop
 with cups not running:
 # /etc/init.d/cups start
 
* What was the outcome of this action?
 
 # /etc/init.d/cups stop
 [] Stopping cups (via systemctl): cups.service
 
 hangs indefinitely
 
 If I kill it by hand, then
 # /etc/init.d/cups start
 [] Starting cups (via systemctl): cups.service
 
 hangs indefinitely
 
* What outcome did you expect instead?
 
 The cups daemon should start/stop as expected.
 
 Also, systemctl start/stop cups.service acts the same.

Here's some additional info:

In my case when aptitude is truing to configure cups-daemon, there is 
a hang that lasts for some 10 minutes, then things fail:

  Setting up cups-daemon (1.7.1-4) ...
  Job for cups.service failed. See 'systemctl status cups.service' and 
'journalctl -xn' for details.
  invoke-rc.d: initscript cups, action start failed.
  dpkg: error processing package cups-daemon (--configure):
   subprocess installed post-installation script returned error exit status 1

If I try to start cups-daemon by hand, it fails immediately:

  $ sudo service cups-daemon start  
 ~
  Failed to issue method call: Unit cups-daemon.service failed to load: No such 
file or directory. See system logs and 'systemctl status cups-daemon.service' 
for details.

  $ sudo systemctl status cups-daemon.service   
 ~
  cups-daemon.service
 Loaded: error (Reason: No such file or directory)
 Active: inactive (dead)

Heh, fiddling with /etc/init.d/cups I purged xprint-common and this 
seems to have fixed the cups problem:

  $ sudo dpkg -P xprint-common  
 ~
  (Reading database ... 491921 files and directories currently installed.)
  Removing xprint-common (2:1.4.2-11) ...
  Purging configuration files for xprint-common (2:1.4.2-11) ...

  $ sudo dpkg --configure -a
 ~
  Setting up man-db (2.6.6-1) ...
  Updating database of manual pages ...
  Setting up cups-daemon (1.7.1-4) ...  - this was hanging/failing 
before
  Setting up cups-core-drivers (1.7.1-4) ...
  Setting up cups (1.7.1-4) ...
  Updating PPD files for cups ...
  Updating PPD files for cups-filters ...
  Updating PPD files for cups-pdf ...
  Updating PPD files for foomatic-db ...
  Updating PPD files for foomatic-db-engine ...
  Updating PPD files for hpcups ...
  Updating PPD files for postscript-hp ...


I hope this helps to pinpoint the problem.

-- dam


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



Bug#738801: cups: /etc/init.d/cups stop/start hang when systemd is installed

2014-02-13 Thread Didier 'OdyX' Raboud
Control: tags -1 +unreproducible +moreinfo

Hi Nye, and thanks for your bugreport,

Le mercredi, 12 février 2014, 17.51:19 Nye Liu a écrit :
* What led up to the situation?
 
 running /etc/init.d/cups stop or start (for example, as root, or by
 logrotate)
 
* What was the outcome of this action?
 
 # /etc/init.d/cups stop
 [] Stopping cups (via systemctl): cups.service
 
 hangs indefinitely

Note that for administrators, the proper interface is service, not 
/etc/init.d, as the former makes sure that the environment is 
sanitized, but that doesn't seem to be the problem.

I can't reproduce this here, with systemd as init.

 If I kill it by hand, then
 # /etc/init.d/cups start
 [] Starting cups (via systemctl): cups.service
 
 hangs indefinitely

Can you post excerpts of /var/log/syslog and /var/log/cups/error_log 
from around when you start and stop cups?

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#738801: cups: /etc/init.d/cups stop/start hang when systemd is installed

2014-02-13 Thread Didier 'OdyX' Raboud
Nye; do you happen to have xprint-common unpurged? (Please paste the 
result of $ dpkg -l xprint-common)

Le jeudi, 13 février 2014, 11.04:16 Damyan Ivanov a écrit :
 Heh, fiddling with /etc/init.d/cups I purged xprint-common and this
 seems to have fixed the cups problem:

Ha. That looks interesting. There's indeed some xprint handling in 
cups.init. As xprint disappeared from Debian before Wheezy, I think it's 
probably safe to drop this handling code from the init script. If Nye 
can confirm he has the same conditions than you, then that'd be the fix.

Damyan: Could you re-install, remove (but not purge) xprint from 
oldstable, edit your /etc/init.d/cups.init to drop all instances of 
restart_xprint and see if it works for you?

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#738801: cups: /etc/init.d/cups stop/start hang when systemd is installed

2014-02-13 Thread Damyan Ivanov
-=| Didier 'OdyX' Raboud, 13.02.2014 10:25:39 +0100 |=-
 Nye; do you happen to have xprint-common unpurged? (Please paste the 
 result of $ dpkg -l xprint-common)
 
 Le jeudi, 13 février 2014, 11.04:16 Damyan Ivanov a écrit :
  Heh, fiddling with /etc/init.d/cups I purged xprint-common and this
  seems to have fixed the cups problem:
 
 Ha. That looks interesting. There's indeed some xprint handling in 
 cups.init. As xprint disappeared from Debian before Wheezy, I think it's 
 probably safe to drop this handling code from the init script. If Nye 
 can confirm he has the same conditions than you, then that'd be the fix.
 
 Damyan: Could you re-install, remove (but not purge) xprint from 
 oldstable, edit your /etc/init.d/cups.init to drop all instances of 
 restart_xprint and see if it works for you?

 $ sudo dpkg -r xprint-common   ~
 (Reading database ... 492747 files and directories currently installed.)
 Removing xprint-common (2:1.6.0-4) ...
 $ sudo service cups restart
--- hang, ctrl-C
 $ sudo vim /etc/init.d/cups# remove mentions of restart_xprint
 $ sudo service cups restart~
 Warning: Unit file of cups.service changed on disk, 'systemctl --system 
daemon-reload' recommended.
 $ sudo systemctl --system daemon-reload
 $ sudo service cups restart~
 $

IOW, removing invocations of restart_xprint from /etc/init.d/cups 
helped.

\o/


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



Bug#738801: cups: /etc/init.d/cups stop/start hang when systemd is installed

2014-02-13 Thread Nye Liu

On 2/13/2014 1:25 AM, Didier 'OdyX' Raboud wrote:

Nye; do you happen to have xprint-common unpurged? (Please paste the
result of $ dpkg -l xprint-common)

Le jeudi, 13 février 2014, 11.04:16 Damyan Ivanov a écrit :

Heh, fiddling with /etc/init.d/cups I purged xprint-common and this
seems to have fixed the cups problem:

Ha. That looks interesting. There's indeed some xprint handling in
cups.init. As xprint disappeared from Debian before Wheezy, I think it's
probably safe to drop this handling code from the init script. If Nye
can confirm he has the same conditions than you, then that'd be the fix.

Damyan: Could you re-install, remove (but not purge) xprint from
oldstable, edit your /etc/init.d/cups.init to drop all instances of
restart_xprint and see if it works for you?

Cheers,
OdyX


As predicted, removing xprint-common fixed the issue.

Thanks all!


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



Bug#738801: cups: /etc/init.d/cups stop/start hang when systemd is installed

2014-02-12 Thread Nye Liu
Package: cups
Version: 1.7.1-4
Severity: important

Dear Maintainer,

   * What led up to the situation?

running /etc/init.d/cups stop or start (for example, as root, or by
logrotate)

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

with cups running:
# /etc/init.d/cups stop
with cups not running:
# /etc/init.d/cups start

   * What was the outcome of this action?

# /etc/init.d/cups stop
[] Stopping cups (via systemctl): cups.service

hangs indefinitely

If I kill it by hand, then
# /etc/init.d/cups start
[] Starting cups (via systemctl): cups.service

hangs indefinitely

   * What outcome did you expect instead?

The cups daemon should start/stop as expected.

Also, systemctl start/stop cups.service acts the same.


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (x86_64)

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

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

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

Versions of packages cups suggests:
ii  cups-bsd   1.7.1-4
pn  cups-pdf   none
ii  foomatic-db20131129-1
pn  hplip  none
pn  printer-driver-hpcups  none
ii  smbclient  2:4.1.3+dfsg-2
ii  udev   204-5

-- debconf-show failed


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