Re: strange log messages/behavior
On Sun, 14 Mar, 1999 à 06:12:57PM -0600, Chris R. Martin wrote: > Has anyone ever seen these messages before? Does anyone know what they mean? > > Mar 14 17:27:19 server init: Id "1" respawning too fast: disabled for 5 > minutes > Mar 14 17:28:50 server init: Id "2" respawning too fast: disabled for 5 > minutes > Mar 14 17:29:39 server init: Id "3" respawning too fast: disabled for 5 > minutes > Mar 14 17:29:42 server init: Id "4" respawning too fast: disabled for 5 > minutes > Mar 14 17:29:45 server init: Id "5" respawning too fast: disabled for 5 > minutes > Mar 14 17:29:49 server init: Id "6" respawning too fast: disabled for 5 > minutes I had this problem once : it was due to an error of syntax int he lines 1:2345:respawn:/sbin/getty 38400 tty1 2:23:respawn:/sbin/getty 38400 tty2 3:23:respawn:/sbin/getty 38400 tty3 4:23:respawn:/sbin/getty 38400 tty4 5:23:respawn:/sbin/getty 38400 tty5 6:23:respawn:/sbin/getty 38400 tty6 in /etc/inittab. Doublecheck them. > Mar 14 17:29:49 server init: no more processes left in this runlevel > For this problem I'm clueless. -- ( >- Laurent PICOULEAU -< ) /~\ [EMAIL PROTECTED] /~\ | \)Linux : mettez un pingouin dans votre ordinateur !(/ | \_|_Seuls ceux qui ne l'utilisent pas en disent du mal. _|_/
Re: strange log messages/behavior
"Chris R. Martin" wrote: > > Has anyone ever seen these messages before? Does anyone know what they mean? > > Mar 14 17:27:19 server init: Id "1" respawning too fast: disabled for 5 > minutes > Mar 14 17:28:50 server init: Id "2" respawning too fast: disabled for 5 > minutes > Mar 14 17:29:39 server init: Id "3" respawning too fast: disabled for 5 > minutes > Mar 14 17:29:42 server init: Id "4" respawning too fast: disabled for 5 > minutes > Mar 14 17:29:45 server init: Id "5" respawning too fast: disabled for 5 > minutes > Mar 14 17:29:49 server init: Id "6" respawning too fast: disabled for 5 > minutes > Mar 14 17:29:49 server init: no more processes left in this runlevel > If you take a look in your /etc/inittab file you will see lines like 1:2345:respawn:/sbin/getty 38400 tty1 2:23:respawn:/sbin/getty 38400 tty2 3:23:respawn:/sbin/getty 38400 tty3 4:23:respawn:/sbin/getty 38400 tty4 5:23:respawn:/sbin/getty 38400 tty5 6:23:respawn:/sbin/getty 38400 tty6 This is what sets up your virtual terminals. The init process detects when you are done with a terminal and respawns getty to run on the terminal. The most likely problem is that getty was terminating abnormally or was not being loaded properly so init will just keep retying to respawn it. That is what will cause the errors you saw. > How should I have dealt with this problem? Any ideas how it occured? > I usually have the luck of one of the terminals still being functional for me to kill the offending getty and all is OK. As for your situation, you could have waited the five minutes and see if the getties respawned properly. Beyond that I'm sure I would have reached for the reset button myself. As for what actually causes the problem I have not been able to figure out. It does not happen to me often enough. Hope this is usefull. -- Paul Miller [EMAIL PROTECTED]begin:vcard n:Miller;Paul x-mozilla-html:FALSE org:Talons adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:President note:The Spirit of the University of North Texas x-mozilla-cpt:;0 fn:Paul Miller end:vcard
RE: strange log messages/behavior
On Mon, 15 Mar 1999, Kris Van Heghe wrote: > * Sometimes, after playing around for a while on the machine, if some > command gives me an error, subsequent commands (whatever it is) produce > only one output: 'Segmentation fault'. From that moment, there is only one > solution: restarting the machine, the 'dirty way'. Have had that problem (along with several others like crashing X servers every few minutes, rendering the entire system inoperable) too. The solution was to underclock my AMD K6-2 / 300 downto 250 MHz (3*83). Now everything seems to work OK. I didn't yet have time (didn't want to create the time for it...) to check out what piece of hardware is causing the trouble, but it may also be the combination of several components... Hope this help... Regards, Maarten.
RE: strange log messages/behavior
Hello, As i read your message i realized you're stuck with the same problem as i do for some time on hamm, without finding a solution. That's why I launched a similar cry for help a few days ago, without any luck until now Here's a copy of my original message: Hi, While I installed Linux some time ago with a lot of 'trial and error', I got things working finally, Including xdm and kdm, on an old Deskpro386, 20 Mhz, 12 Mb memory with SVGA card, . Two curious things keep me bothering from the beginning, however: * Sometimes, even during or just after starting the machine, at one of the virtual terminals, there is a message saying "INIT respawning to fast, disabled for 5 minutes". Logging in on that vt is then impossible, trying on another vt gives me the same strange message. Only one solution: power off, restarting 'dirty' and hoping for better lucks this a hardware-dependent problem or a configuration error ? * Sometimes, after playing around for a while on the machine, if some command gives me an error, subsequent commands (whatever it is) produce only one output: 'Segmentation fault'. From that moment, there is only one solution: restarting the machine, the 'dirty way'. I hope some Linux-guru can give a little advice to solve these 'destabilizing' phenomena. TIA -Original Message- From: Chris R. Martin [SMTP:[EMAIL PROTECTED] Sent: maandag 15 maart 1999 1:13 To: debian-user@lists.debian.org Subject:strange log messages/behavior Has anyone ever seen these messages before? Does anyone know what they mean? Mar 14 17:27:19 server init: Id "1" respawning too fast: disabled for 5 minutes Mar 14 17:28:50 server init: Id "2" respawning too fast: disabled for 5 minutes Mar 14 17:29:39 server init: Id "3" respawning too fast: disabled for 5 minutes Mar 14 17:29:42 server init: Id "4" respawning too fast: disabled for 5 minutes Mar 14 17:29:45 server init: Id "5" respawning too fast: disabled for 5 minutes Mar 14 17:29:49 server init: Id "6" respawning too fast: disabled for 5 minutes Mar 14 17:29:49 server init: no more processes left in this runlevel My server stoped responding to telnet and ftp (it would immediately close the connection). SAMBA and NFS still seemed to work however. So I got access to the console, and tried to log in, it gave me the above messages on the screen (and I found these in /var/log/syslog). Anyway, I did not see any recourse other than to hit reset, because Ctrl-Alt-Del did not respond either. How should I have dealt with this problem? Any ideas how it occured? Chris -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: strange log messages/behavior
At 06:12 PM 3/14/99 -0600, Chris R. Martin wrote: >Has anyone ever seen these messages before? Does anyone know what they mean? IIRC the answer to both questions is "YES". Unfortunately, I don't have the answers :) There was some discussion on this issue just recently. It may pay to check the March archives. Ivan. > >Mar 14 17:27:19 server init: Id "1" respawning too fast: disabled for 5 >minutes >Mar 14 17:28:50 server init: Id "2" respawning too fast: disabled for 5 >minutes >Mar 14 17:29:39 server init: Id "3" respawning too fast: disabled for 5 >minutes >Mar 14 17:29:42 server init: Id "4" respawning too fast: disabled for 5 >minutes >Mar 14 17:29:45 server init: Id "5" respawning too fast: disabled for 5 >minutes >Mar 14 17:29:49 server init: Id "6" respawning too fast: disabled for 5 >minutes >Mar 14 17:29:49 server init: no more processes left in this runlevel > >My server stoped responding to telnet and ftp (it would immediately close >the connection). SAMBA and NFS still seemed to work however. So I got >access to the console, and tried to log in, it gave me the above messages >on the screen (and I found these in /var/log/syslog). Anyway, I did not see >any recourse other than to hit reset, because Ctrl-Alt-Del did not respond >either. > >How should I have dealt with this problem? Any ideas how it occured? > >Chris > > >-- >Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > >
