[gentoo-amd64] cupsd wont start on boot.

[gentoo-amd64] cupsd wont start on boot.

[Mark Haney]

I'm having a bizarre issue with cupsd. On boot I get a 'Child exited 
status 99!' error.  After boot, when I use /etc/init.d/cupsd start, it 
doesnt' start.  However, if I rip the exact line from the init.d script 
to start cupsd, it starts just fine.

What's going on?

-- 
Me transmitte sursum, caledoni!

Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: cupsd wont start on boot.

[Duncan]

"Mark Haney" <mhaney@ercbroadband.org> posted
44D352E7.5070907@ercbroadband.org, excerpted below, on  Fri, 04 Aug 2006
10:00:07 -0400:

> I'm having a bizarre issue with cupsd. On boot I get a 'Child exited
> status 99!' error.  After boot, when I use /etc/init.d/cupsd start, it
> doesnt' start.  However, if I rip the exact line from the init.d script to
> start cupsd, it starts just fine.
> 
> What's going on?

If it's the exact same line both places, one works, the other doesn't,
it's almost certainly due to the difference in environment.  The
environment passed to the one started from initscript will be rather more
limited than a fully interactive bash prompt environment.

I'd suggest you put a debug statement in the initscript, right before the
command executes, that prints the environment to one file and the exported
environment to another.  Diff those against the same output from the
command line that works right, and you'll have a good start on tracking
down the culprit, since you'll have all the differences nicely listed, in
ordered to check.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: cupsd wont start on boot.

[Paul de Vrieze]

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

On Saturday 05 August 2006 07:50, Duncan wrote:
> If it's the exact same line both places, one works, the other doesn't,
> it's almost certainly due to the difference in environment.  The
> environment passed to the one started from initscript will be rather more
> limited than a fully interactive bash prompt environment.
>
> I'd suggest you put a debug statement in the initscript, right before the
> command executes, that prints the environment to one file and the exported
> environment to another.  Diff those against the same output from the
> command line that works right, and you'll have a good start on tracking
> down the culprit, since you'll have all the differences nicely listed, in
> ordered to check.

Additionally many init scripts use start-stop-daemon with the --quiet command 
line option. This suppresses all output from the command used. In this case 
we would like to see this output so remove "--quiet" from the init script.

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net

[-- Attachment #2: Type: application/pgp-signature, Size: 200 bytes --]

Re: [gentoo-amd64] Re: cupsd wont start on boot.

[Neil Stone]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul de Vrieze wrote:
> On Saturday 05 August 2006 07:50, Duncan wrote:
>> If it's the exact same line both places, one works, the other doesn't,
>> it's almost certainly due to the difference in environment.  The
>> environment passed to the one started from initscript will be rather more
>> limited than a fully interactive bash prompt environment.
>>
>> I'd suggest you put a debug statement in the initscript, right before the
>> command executes, that prints the environment to one file and the exported
>> environment to another.  Diff those against the same output from the
>> command line that works right, and you'll have a good start on tracking
>> down the culprit, since you'll have all the differences nicely listed, in
>> ordered to check.
> 
> Additionally many init scripts use start-stop-daemon with the --quiet command 
> line option. This suppresses all output from the command used. In this case 
> we would like to see this output so remove "--quiet" from the init script.
> 
> Paul
> 

what happens if you invoke the init script directly, ie not running the
commands contained within the script...

/etc/init.d/cupsd start

for example

- --
Neil Stone

Systems Administrator
FlashTek UK

- -----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d+(++) s: a-(?) C++++(--) UL++++$ P+ L+++ E- W+++ N+
o+ w--- O M PS+ Y+ PGP++ t+ 5+ X+ R+ tv+ b- DI++ D+++ G
e h--- r+++ y++++(**)
- -----END GEEK CODE BLOCK-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE1mn1z3Av8JKgzxQRAmxZAKCVMrcPvKCeFdG3UaCrbNZuS97aDACgsZmt
SeSCaw8XjSJX/xfs3N7TQV8=
=lI9m
-----END PGP SIGNATURE-----
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: cupsd wont start on boot.

[Mark Haney]

Neil Stone wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Paul de Vrieze wrote:
>> On Saturday 05 August 2006 07:50, Duncan wrote:
>>> If it's the exact same line both places, one works, the other doesn't,
>>> it's almost certainly due to the difference in environment.  The
>>> environment passed to the one started from initscript will be rather more
>>> limited than a fully interactive bash prompt environment.
>>>
>>> I'd suggest you put a debug statement in the initscript, right before the
>>> command executes, that prints the environment to one file and the exported
>>> environment to another.  Diff those against the same output from the
>>> command line that works right, and you'll have a good start on tracking
>>> down the culprit, since you'll have all the differences nicely listed, in
>>> ordered to check.
>> Additionally many init scripts use start-stop-daemon with the --quiet command 
>> line option. This suppresses all output from the command used. In this case 
>> we would like to see this output so remove "--quiet" from the init script.
>>
>> Paul
>>
> 
> what happens if you invoke the init script directly, ie not running the
> commands contained within the script...
> 
> /etc/init.d/cupsd start
> 
> for example
> 

If I invoke as root, I get nothing, not even a 'Child exited' error. 
But it doesn't start.  I'm going to remove the --quiet option and try it 
and see how it goes.


-- 
Me transmitte sursum, caledoni!

Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: cupsd wont start on boot.

[Mark Haney]

Neil Stone wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Paul de Vrieze wrote:
>> On Saturday 05 August 2006 07:50, Duncan wrote:
>>> If it's the exact same line both places, one works, the other doesn't,
>>> it's almost certainly due to the difference in environment.  The
>>> environment passed to the one started from initscript will be rather more
>>> limited than a fully interactive bash prompt environment.
>>>
>>> I'd suggest you put a debug statement in the initscript, right before the
>>> command executes, that prints the environment to one file and the exported
>>> environment to another.  Diff those against the same output from the
>>> command line that works right, and you'll have a good start on tracking
>>> down the culprit, since you'll have all the differences nicely listed, in
>>> ordered to check.
>> Additionally many init scripts use start-stop-daemon with the --quiet command 
>> line option. This suppresses all output from the command used. In this case 
>> we would like to see this output so remove "--quiet" from the init script.
>>
>> Paul
>>
> 
> what happens if you invoke the init script directly, ie not running the
> commands contained within the script...
> 
> /etc/init.d/cupsd start
> 
\
This is what I get:

* Caching service dependencies ... 
                                                                  [ ok ]
  * WARNING:  "cupsd" has already been started.

But it's not started.



-- 
Me transmitte sursum, caledoni!

Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: Re: cupsd wont start on boot.

[Duncan]

"Mark Haney" <mhaney@ercbroadband.org> posted
44D66CC4.6060307@ercbroadband.org, excerpted below, on  Sun, 06 Aug 2006
18:27:16 -0400:

>> what happens if you invoke the init script directly, ie not running the
>> commands contained within the script...
>> 
>> /etc/init.d/cupsd start
>> 
> \
> This is what I get:
> 
> * Caching service dependencies ...
>                                                                   [ ok ]
>   * WARNING:  "cupsd" has already been started.
> 
> But it's not started.
>

Ahhh!

Try /etc/init.d/cupsd zap

/then/

/etc/init.d/cupsd start


The "zap" thing is there to zap stale tracking files left behind in a
crash or something.  If it says it's started when it's not, that's
always the first thing to try.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: cupsd wont start on boot.

[Bob Slawson]

Mark Haney wrote:
> \
> This is what I get:
>
> * Caching service dependencies ... 
>                                                                  [ ok ]
>  * WARNING:  "cupsd" has already been started.
>
> But it's not started.
>
Try this:

# /etc/init.d/cupsd zap

# /etc/init.d/cupsd start

Explanation:

The rc-scripts place a link in `/var/lib/init.d/started/ ' pointing back 
to the script that was run.  Sometimes, particularly when a script fails 
to start, this link is left behind.  This fools the rc-scripts into 
thinking the service has already started.  The 'zap' option resets the 
service to the stopped state.  Of course, read the page from the fine 
manual at: 
<http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=4>

BobS

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: cupsd wont start on boot.

[Ferris McCormick]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, 6 Aug 2006, Mark Haney wrote:

> Neil Stone wrote:
>>  -----BEGIN PGP SIGNED MESSAGE-----
>>  Hash: SHA1
>>
>>  Paul de Vrieze wrote:
>> >  On Saturday 05 August 2006 07:50, Duncan wrote:
>> > >  If it's the exact same line both places, one works, the other doesn't,
>> > >  it's almost certainly due to the difference in environment.  The
>> > >  environment passed to the one started from initscript will be rather 
>> > >  more
>> > >  limited than a fully interactive bash prompt environment.
>> > > 
>>
=====
S N I P
=====

>>  what happens if you invoke the init script directly, ie not running the
>>  commands contained within the script...
>>
>>  /etc/init.d/cupsd start
>> 
> \
> This is what I get:
>
> * Caching service dependencies ...
>                                                                  [ ok ]
>  * WARNING:  "cupsd" has already been started.
>
> But it's not started.
>
>

When I run into this, I cheat.  If you look in /var/lib/init.d/started
you will notice a symbolic link cupsd, and the existence of that link is 
what triggers the "already started" message.  If it really isn't running, 
if you remove this link (rm /var/lib/init.d/started/cupsd), then
"/etc/init.d/cupsd start" should start it normally.

There are doubtless more elegant ways to handle the problem, and there are 
doubtless more prefered ways to handle it, but the little cheat I just 
mentioned works for me(tm).

>
> -- 
> Me transmitte sursum, caledoni!
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> (828) 350-2415
> -- 
> gentoo-amd64@gentoo.org mailing list
>

Regards,
Ferris
- --
Ferris McCormick (P44646, MI) <fmccor@gentoo.org>
Developer, Gentoo Linux (Devrel, Sparc)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5-ecc0.1.6 (GNU/Linux)

iD8DBQFE1onTQa6M3+I///cRAnFTAJsFp6W/GRFl4lAyPXlOTbqm7JYS/ACeJqFh
cXaiKuZAbHBT4m7YC0lSnEY=
=ZLnx
-----END PGP SIGNATURE-----
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: Re: cupsd wont start on boot.

[Mark Haney]

Duncan wrote:
> "Mark Haney" <mhaney@ercbroadband.org> posted
> 44D66CC4.6060307@ercbroadband.org, excerpted below, on  Sun, 06 Aug 2006
> 18:27:16 -0400:
> 
>>> what happens if you invoke the init script directly, ie not running the
>>> commands contained within the script...
>>>
>>> /etc/init.d/cupsd start
>>>
>> \
>> This is what I get:
>>
>> * Caching service dependencies ...
>>                                                                   [ ok ]
>>   * WARNING:  "cupsd" has already been started.
>>
>> But it's not started.
>>
> 
> Ahhh!
> 
> Try /etc/init.d/cupsd zap
> 
> /then/
> 
> /etc/init.d/cupsd start
> 
> 
> The "zap" thing is there to zap stale tracking files left behind in a
> crash or something.  If it says it's started when it's not, that's
> always the first thing to try.
> 

Well I'll be.  That worked. Except it still gives me the 'Child Exited' 
error on a reboot.  It's like cupsd isn't /stopping/ correctly (or at 
all) on a shutdown.






-- 
Me transmitte sursum, caledoni!

Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: Re: Re: cupsd wont start on boot.

[Duncan]

"Mark Haney" <mhaney@ercbroadband.org> posted
44D7301D.1080404@ercbroadband.org, excerpted below, on  Mon, 07 Aug 2006
08:20:45 -0400:

>> Try /etc/init.d/cupsd zap
>> 
> Well I'll be.  That worked. Except it still gives me the 'Child Exited'
> error on a reboot.  It's like cupsd isn't /stopping/ correctly (or at all)
> on a shutdown.

That could be.  I hadn't had any problems with it in the past, but have
never run cups regularly on Gentoo as I don't print that much, and
currently I don't even have a printer, so of course am not running cups. 
Thus, I have no current experience to help you with there, but indeed, it
/does/ seem as if something's not stopping correctly.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list