Re: [gentoo-user] startup woes with sshd, rsyncd, nfs, portmap

2007-06-13 Thread John Blinka

On 6/7/07, Hans-Werner Hilse [EMAIL PROTECTED] wrote:


Hi,

On Thu, 7 Jun 2007 15:55:45 -0400
John Blinka [EMAIL PROTECTED] wrote:

sshd doesn't start
nfs doesn't start
rsyncd doesn't start

Are those being started (i.e. tried to) at boot? Is it just fail then
for you? There should at least be a bit of debug info in the output at
startup... You might also try the interactive boot up (hit I) and see
what happens.



I used interactive bootup as you suggested, and discovered that
the system is not even attempting to start them, even though
rc-update thinks they're supposed to be started at the default
runlevel.  I can start them by hand without any errors, so the lack
of messages in the logs isn't surprising.


You _did_ run etc-update (or its siblings) in order to

get the new files in /etc/init.d/ activated? You're sure you have the
new versions of those files installed?



Yes, I ran etc-update, and revdep-rebuild.  I do have the latest versions
of the /etc/init.d files.

Since all of those daemons depend on network: Are there network

settings for interfaces that fail on boot up?



Network works fine.

John


Re: [gentoo-user] startup woes with sshd, rsyncd, nfs, portmap

2007-06-13 Thread Hans-Werner Hilse
Hi,

On Wed, 13 Jun 2007 07:29:41 -0400 John Blinka
[EMAIL PROTECTED] wrote:

 I used interactive bootup as you suggested, and discovered that
 the system is not even attempting to start them, even though
 rc-update thinks they're supposed to be started at the default
 runlevel.  I can start them by hand without any errors, so the lack
 of messages in the logs isn't surprising.

Can you provide the full output of rc-update show?

 Since all of those daemons depend on network: Are there network
  settings for interfaces that fail on boot up?
 
 Network works fine.

Does that mean: No there are no failing network related things on boot
up?

-hwh
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] startup woes with sshd, rsyncd, nfs, portmap

2007-06-13 Thread John Blinka

On 6/13/07, Hans-Werner Hilse [EMAIL PROTECTED] wrote:



Can you provide the full output of rc-update show?



-- rc-update show
  alsasound | boot
   bootmisc | boot
checkfs | boot
  checkroot | boot
  clock | boot
consolefont | boot
  courier-imapd |  default
  cupsd |  default
   dbus |  default
  dhcpd |  default
distccd |  default
  fetchmail |  default
   hostname | boot
keymaps | boot
  local |  default nonetwork
 localmount | boot
modules | boot
   net.eth0 |  default
 net.lo | boot
   netmount |  default
nfs |  default
 ntp-client |  default
   ntpd |  default
postfix |  default
  rmnologin | boot
 rsyncd |  default
  samba |  default
  slapd |  default
   sshd |  default
 svscan | boot
  syslog-ng |  default
urandom | boot
xdm |  default
 xinetd |  default


Since all of those daemons depend on network: Are there network
  settings for interfaces that fail on boot up?

 Network works fine.

Does that mean: No there are no failing network related things on boot
up?



Yes, that's what it means.

John Blinka


Re: [gentoo-user] startup woes with sshd, rsyncd, nfs, portmap

2007-06-13 Thread Hans-Werner Hilse
Hi,

On Wed, 13 Jun 2007 09:21:03 -0400 John Blinka
[EMAIL PROTECTED] wrote:

 On 6/13/07, Hans-Werner Hilse [EMAIL PROTECTED] wrote:
 
 
  Can you provide the full output of rc-update show?
 
 
  -- rc-update show
 [...]

looks pretty much normal, nothing that I would call an obvious glitch
in there.

I'm getting out of ideas, but there's one thing left: /etc/conf.d/rc
Check if using other values for RC_NET_STRICT_CHECKING,
RC_PARALLEL_STARTUP and maybe (if currently set) RC_PLUG_SERVICES have
any consequences. I'm not sure, but I think the other settings
shouldn't matter.

-hwh
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] startup woes with sshd, rsyncd, nfs, portmap

2007-06-13 Thread John Blinka

On 6/13/07, Hans-Werner Hilse [EMAIL PROTECTED] wrote:




looks pretty much normal, nothing that I would call an obvious glitch
in there.



It's the same as two other Gentoo boxes I run, both of which start
up normally, and it's the same as it was before the problems started,
so I agree: rc-update is not the source of the problem,

I'm getting out of ideas, but there's one thing left: /etc/conf.d/rc

Check if using other values for RC_NET_STRICT_CHECKING,
RC_PARALLEL_STARTUP and maybe (if currently set) RC_PLUG_SERVICES have
any consequences. I'm not sure, but I think the other settings
shouldn't matter.



It's also the same as all my other normal Gentoo boxes, so unlikely to be
the source of the problem.

John


Re: [gentoo-user] startup woes with sshd, rsyncd, nfs, portmap

2007-06-08 Thread Mick

...and revdep-rebuild, although if libs were broken you should get
some errors in your logs.

HTH.
--
Regards,
Mick

--
Regards,
Mick
--
[EMAIL PROTECTED] mailing list



[gentoo-user] startup woes with sshd, rsyncd, nfs, portmap

2007-06-07 Thread John Blinka

Hi, All,

After a long period of not updating one of my machines, I recently did a
fairly large emerge -DuNv world.  And now things don't work quite as they
used to.

Symptoms:

  sshd doesn't start
  nfs doesn't start
  rsyncd doesn't start

  system sometimes hangs on shutdown when it tries to unmount
  remote filesystems.

  There are no complaints in /var/log/messages.

  I can start all of these daemons by hand without a problem and all
  are in the default rc level.  Starting nfs is a bit different from
starting
  the others: I have to start portmap first

Any ideas on where to look for problems?

John Blinka


Re: [gentoo-user] startup woes with sshd, rsyncd, nfs, portmap

2007-06-07 Thread Hans-Werner Hilse
Hi,

On Thu, 7 Jun 2007 15:55:45 -0400
John Blinka [EMAIL PROTECTED] wrote:

sshd doesn't start
nfs doesn't start
rsyncd doesn't start

Are those being started (i.e. tried to) at boot? Is it just fail then
for you? There should at least be a bit of debug info in the output at
startup... You might also try the interactive boot up (hit I) and see
what happens. You _did_ run etc-update (or its siblings) in order to
get the new files in /etc/init.d/ activated? You're sure you have the
new versions of those files installed?

Since all of those daemons depend on network: Are there network
settings for interfaces that fail on boot up?

-hwh
-- 
[EMAIL PROTECTED] mailing list