[gentoo-user] Confusing boot up messages

[gentoo-user] Confusing boot up messages

[gentuxx]

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

I just ran an update today, and after rebooting, I get a bunch of odd
errors when all of the services are starting.  I wasn't able to
capture the exact warnings, and I couldn't find a log that contained
them.  But it was something to the effect of "WARNING: foo service was
scheduled to start after net.eth0".  It builds as services are
started, so that by the time I get to the login prompt, there's 6-10
service that I'm getting warned about.  Once I login, I'm able to
manually start gdm, and login to KDE.  Everything *appears* normal.  I
have the right IP for eth0, /some/ of the services that I was warned
about were started and some were not.  The only package that I can
think of that might have been even remotely related was
sys-apps/baselayout-1.12.4-r2.

What gives?

- --
gentux
echo "hfouvyyAhnbjm/dpn" | perl -pe 's/(.)/chr(ord($1)-1)/ge'

gentux's gpg fingerprint ==> 5495 0388 67FF 0B89 1239  D840 4CF0 39E2
18D3 4A9E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFE3+MMTPA54hjTSp4RAhm/AJ4oiXVcf1IQcGOpQbbIUyFwYnBqVwCg3Ewl
cmHkvzqhGww+YfZHDaT0tAw=
=f0pW
-----END PGP SIGNATURE-----

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Confusing boot up messages

[Nick Rout]

has baselayout recently been updated? If so etc-update (or one of its
clones) should fix things.


On Sun, 13 Aug 2006 19:42:21 -0700
gentuxx wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I just ran an update today, and after rebooting, I get a bunch of odd
> errors when all of the services are starting.  I wasn't able to
> capture the exact warnings, and I couldn't find a log that contained
> them.  But it was something to the effect of "WARNING: foo service was
> scheduled to start after net.eth0".  It builds as services are
> started, so that by the time I get to the login prompt, there's 6-10
> service that I'm getting warned about.  Once I login, I'm able to
> manually start gdm, and login to KDE.  Everything *appears* normal.  I
> have the right IP for eth0, /some/ of the services that I was warned
> about were started and some were not.  The only package that I can
> think of that might have been even remotely related was
> sys-apps/baselayout-1.12.4-r2.
> 
> What gives?
> 
> - --
> gentux
> echo "hfouvyyAhnbjm/dpn" | perl -pe 's/(.)/chr(ord($1)-1)/ge'
> 
> gentux's gpg fingerprint ==> 5495 0388 67FF 0B89 1239  D840 4CF0 39E2
> 18D3 4A9E
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
> 
> iD8DBQFE3+MMTPA54hjTSp4RAhm/AJ4oiXVcf1IQcGOpQbbIUyFwYnBqVwCg3Ewl
> cmHkvzqhGww+YfZHDaT0tAw=
> =f0pW
> -----END PGP SIGNATURE-----
> 
> -- 
> gentoo-user@gentoo.org mailing list

-- 
Nick Rout <nick@rout.co.nz>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Confusing boot up messages

[gentuxx]

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

Nick Rout wrote:
> has baselayout recently been updated? If so etc-update (or one of its
> clones) should fix things.
>

Yeah, baselayout was one of the packages updated.  I prefer
dispatch-conf, which I ran.  I use a script that I wrote that runs
emerge -DuatvN world, emerge --depclean, revdep-rebuild, dispatch-conf
and updates AIDE, all in series.  I ran it again, just to check, but
it doesn't pick up anything.  So, how do I find out which config file
hosed me?

Incidentally, I looked at `rc-update show boot' and `rc-update show
default' and realized that some of the packages that require "net"
were starting at "boot" AND "default".  A while back, I remember
seeing that net.eth0 couldn't start until the "default" runlevel, so I
(re)moved those service that were attempting to start at boot.  I get
fewer errors, but I still get some.  One of my OCD tendencies is to
have a "clean" boot, so I would really like to get this resolved.

TIA

>
> On Sun, 13 Aug 2006 19:42:21 -0700
> gentuxx wrote:
>
> I just ran an update today, and after rebooting, I get a bunch of odd
> errors when all of the services are starting.  I wasn't able to
> capture the exact warnings, and I couldn't find a log that contained
> them.  But it was something to the effect of "WARNING: foo service was
> scheduled to start after net.eth0".  It builds as services are
> started, so that by the time I get to the login prompt, there's 6-10
> service that I'm getting warned about.  Once I login, I'm able to
> manually start gdm, and login to KDE.  Everything *appears* normal.  I
> have the right IP for eth0, /some/ of the services that I was warned
> about were started and some were not.  The only package that I can
> think of that might have been even remotely related was
> sys-apps/baselayout-1.12.4-r2.
>
> What gives?
>
> >>
> --
> gentoo-user@gentoo.org mailing list
>
> --
> gentux
> echo "hfouvyyAhnbjm/dpn" | perl -pe 's/(.)/chr(ord($1)-1)/ge'
>
> gentux's gpg fingerprint ==> 5495 0388 67FF 0B89 1239  D840 4CF0
> 39E2 18D3 4A9E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFE3/BZTPA54hjTSp4RAqWGAJ94RqCMt34lpExoJqAEdLAXQxCp4gCgzfBA
0yD2J8ncxzYKd1+7uGUm2sc=
=XCCS
-----END PGP SIGNATURE-----

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Confusing boot up messages

[Neil Bothwick]

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

On Sun, 13 Aug 2006 20:39:07 -0700, gentuxx wrote:

> Yeah, baselayout was one of the packages updated.

From what to what? genlop will tell you. If it was a path level update,
it is unlikely anything has changed significantly in the configs.

> I prefer
> dispatch-conf, which I ran.  I use a script that I wrote that runs
> emerge -DuatvN world, emerge --depclean, revdep-rebuild, dispatch-conf
> and updates AIDE, all in series.  I ran it again, just to check, but
> it doesn't pick up anything.  So, how do I find out which config file
> hosed me?

If you didn't accept updates to the default config files, emerging
baselayout again should pull them back in.

If you know which services were affected but didn't catch the exact
messages, try stopping and starting them manually so the output doesn't
get buried in all the other startup information. Setting RC_VERBOSE="yes"
in /etc/conf.d/rc may help.


-- 
Neil Bothwick

"Do you reply to our surveys.?"
[X]Never [ ]Always [ ]Sometimes

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Confusing boot up messages

[gentuxx]

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

Neil Bothwick wrote:
> On Sun, 13 Aug 2006 20:39:07 -0700, gentuxx wrote:
>
>> Yeah, baselayout was one of the packages updated.
>
> From what to what? genlop will tell you. If it was a path level update,
> it is unlikely anything has changed significantly in the configs.
>
- From v1.11.15-r3 to v1.12.4-r2.  How do I know if it was a "path level
update"?
>> I prefer
>> dispatch-conf, which I ran.  I use a script that I wrote that runs
>> emerge -DuatvN world, emerge --depclean, revdep-rebuild, dispatch-conf
>> and updates AIDE, all in series.  I ran it again, just to check, but
>> it doesn't pick up anything.  So, how do I find out which config file
>> hosed me?
>
> If you didn't accept updates to the default config files, emerging
> baselayout again should pull them back in.
>
> If you know which services were affected but didn't catch the exact
> messages, try stopping and starting them manually so the output doesn't
> get buried in all the other startup information. Setting RC_VERBOSE="yes"
> in /etc/conf.d/rc may help.
>
>
The config files were accepted.  There didn't appear to be any
significant changes which would have caused something like this.  I'll
try the RC_ setting and see if that provides any more clues.

Thanks.

- --
gentux
echo "hfouvyyAhnbjm/dpn" | perl -pe 's/(.)/chr(ord($1)-1)/ge'

gentux's gpg fingerprint ==> 5495 0388 67FF 0B89 1239  D840 4CF0 39E2
18D3 4A9E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFE4JSkTPA54hjTSp4RAhjrAJ9ua0Q5xXvgiJ1/lx1ZsiGMnfj4tgCgrFSN
WiDCIZyo5qzgk7UC0lzg3QE=
=3+Re
-----END PGP SIGNATURE-----

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Confusing boot up messages

[Willie Wong]

On Sun, Aug 13, 2006 at 07:42:21PM -0700, Penguin Lover gentuxx squawked:
> I just ran an update today, and after rebooting, I get a bunch of odd
> errors when all of the services are starting.  I wasn't able to
> capture the exact warnings, and I couldn't find a log that contained
> them.  But it was something to the effect of "WARNING: foo service was
> scheduled to start after net.eth0".  It builds as services are
> started, so that by the time I get to the login prompt, there's 6-10
> service that I'm getting warned about.  Once I login, I'm able to
> manually start gdm, and login to KDE.  Everything *appears* normal.  I
> have the right IP for eth0, /some/ of the services that I was warned
> about were started and some were not.  The only package that I can
> think of that might have been even remotely related was
> sys-apps/baselayout-1.12.4-r2.
> 
> What gives?

You are running stable (not testing) right? 

Look at /etc/conf.d/rc, I think you might want RC_PLUG_SERVICES="!net.*"

It is a new option.

HTH, 

W
-- 
When my cats aren't happy, I'm not happy. Not because I care about their mood 
but because I know they're just sitting there thinking up ways to get even.
    ~Penny Ward Moser
Sortir en Pantoufles: up 18 days, 18:33
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Confusing boot up messages

[Neil Bothwick]

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

On Mon, 14 Aug 2006 08:20:04 -0700, gentuxx wrote:

> >> Yeah, baselayout was one of the packages updated.
> >
> > From what to what? genlop will tell you. If it was a path level
> > update, it is unlikely anything has changed significantly in the
> > configs.
> >
> - From v1.11.15-r3 to v1.12.4-r2.  How do I know if it was a "path level
> update"?

Sorry, typo. I meant to type "patch level upgrade", as in pkg-x.y.z-r1 to
pkg-x.y.z-r4.

There were some significant changes between baselayout 1.11 and 1.12, this
is probably the cause of the problems.

> > If you know which services were affected but didn't catch the exact
> > messages, try stopping and starting them manually so the output
> > doesn't get buried in all the other startup information. Setting
> > RC_VERBOSE="yes" in /etc/conf.d/rc may help.
> >
> >
> The config files were accepted.  There didn't appear to be any
> significant changes which would have caused something like this.  I'll
> try the RC_ setting and see if that provides any more clues.

It should do, with some scripts at least, but starting the services
manually will also let you see what's going on.


-- 
Neil Bothwick

DCE seeks DTE for mutual exchange of data.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]