What has changed on this system since the services started failing 
after 3 days? Has this machine always done this?

What does "rpm -V netkit-base" show?

Start by checking your /etc/services file. Make sure that the file 
contains the necessary entries for the services you want to run and 
that it is world readable. You may want to diff this file with that
of another machine.

--Matt

--
  Matt Galgoci
  Job title: export title=`dd if=/dev/random bs=24 count=1`
             echo $title

On Wed, 24 Nov 1999, hUnTeR wrote:

> Gordon Messmer wrote:
> > 
> > hUnTeR wrote:
> > > After just about 3 days, inet starts failing,
> > 
> > This may be related to the number of connections made to the server,
> > look in /var/log/messages for messages from inetd about services failing
> > (looping).
> > 
> > > i get pam errors and when i try
> > > to restart inet with a killall -HUP inetd
> > 
> > No idea, are they logged?  Could you send me a sample of them?
> > 
> > > i get all the services back
> > > complaining that these are unknown services.
> > 
> > It would be odd, but it's possible that inetd isn't calling setservent()
> > when it should.  I've never delved into inetd.  Perhaps you could use
> > the script /etc/rc.d/init.d/inet to first stop, and then start the
> > service?  It seems likely that if rebooting works, this would also (and
> > be much faster).
> > 
> > MSG
> 
> Gordon - 
> 
> Thanks, i REALLY appreciate the thoughts and the response. Your latter
> suggestion makes 100% sense to me, and i hadnt thought of that. As for
> the looping errors, i do see them on occasion on /dev/tty8 which is
> where i pipe all the syslog stuff to. As for /var/log/messages here are
> a few:
> 
> Nov 24 17:54:30 ns1 inetd[16835]: getpwnam: root: No such user
> Nov 24 17:54:46 ns1 inetd[262]: ftp/tcp: unknown service
> Nov 24 17:54:46 ns1 inetd[262]: telnet/tcp: unknown service
> Nov 24 17:54:46 ns1 inetd[262]: gopher/tcp: unknown service
> Nov 24 17:54:46 ns1 inetd[262]: shell/tcp: unknown service
> Nov 24 17:54:46 ns1 inetd[262]: login/tcp: unknown service
> Nov 24 17:54:46 ns1 inetd[262]: talk/udp: unknown service
> Nov 24 17:54:46 ns1 inetd[262]: ntalk/udp: unknown service
> Nov 24 17:54:46 ns1 inetd[262]: pop-2/tcp: unknown service
> Nov 24 17:54:46 ns1 inetd[262]: pop-3/tcp: unknown service
> Nov 24 17:54:46 ns1 inetd[262]: imap/tcp: unknown service
> Nov 24 17:54:46 ns1 inetd[262]: finger/tcp: unknown service
> Nov 24 17:54:46 ns1 inetd[262]: time/tcp: unknown service
> Nov 24 17:54:46 ns1 inetd[262]: time/udp: unknown service
> Nov 24 17:54:46 ns1 inetd[262]: auth/tcp: unknown service
> Nov 24 17:54:46 ns1 inetd[262]: penguin/tcp: unknown service
> Nov 24 17:54:46 ns1 inetd[262]: nntp/tcp: unknown service
> Nov 24 17:54:46 ns1 inetd[262]: linuxconf/tcp: unknown service
> 
> And so on, when i try killall -HUP inetd
> 
> Thanks for the ideas and assistance....REALLY!!
> -- 
> Michael B. Weiner
> Systems Administrator/Partner
> The UserFriendly Network (UFN)
> --
> 
>              / /  (_)__  __ ____  __
>             / /__/ / _ \/ // /\ \/ /  
>            /____/_/_//_/\_,_/ /_/\_\ 
> 
>      * * * CHOICE OF A GNU GENERATION * * *
> 
> 
> -- 
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
> 


-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to