Re: wtmp problem
I take it your logging into this box via a serial port? I believe that's the cause of it - Consoles and telnet logins appear fine for me. -- Karl Ferguson Here's how it hits my machine (kernel: 2.0.30) I login to vt1 (alt F1), do a 'finger': I'm logged on. I login to vt2 (alt F2), do a 'finger': I'm logged twice. I logout vt1, do a 'finger': nobody logged on. I do this on vt2. Downgrade (pkg: sysvinit) fixes all syptoms, upon cold boot. I never restore corrupt files, because I can't see any corruption once I downgrade. Note there's no direct involvment with mgetty, though it is running in the background; I don't get many inbound calls. I only have two gettys acquiring terminals (on vt1 and vt2); to gain a 3rd, 4th terminal I use /bin/open. -- Christopher W. Hafey (1:142/540) - [EMAIL PROTECTED]| 1078 New Britain Ave Apt 217 WA1TNR since 1974 | W Hartford Ct USA 06110-2434 http://www.tingri.ml.org | tel. 860-236-5400 - -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: wtmp problem
Probably it's nothing but I know for sure my utmp file got corrupted when my /var partition got full after the guys here at the office sent lots of e-mails with large attachments. I just started over with a zero length utmp and everything went fine. E.- OK, which log file gets corrupted - the wtmp or the utmp file? Or both? I've heard reports about corrupted utmp files, and I'll try to fix that in 2.71 I run mgetty for the dialin lines, I hooked up a vt100 terminal to a serial port on a different machine with 2.70-1 and used plain getty (well, really agetty in disguise) and found the exact same thing - if I downgrade, it works a treat. Oh great, you can reproduce it. Can you tell me 1. which logfile gets corrupted 2. When (before login, during session, after logout) -- Eloy A. Paris Information Technology Department Rockwell Automation de Venezuela Telephone: +58-2-9432311 Fax: +58-2-9430323 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: wtmp problem
At 12:56 AM 27/04/97 -0400, Eloy A. Paris wrote: Probably it's nothing but I know for sure my utmp file got corrupted when my /var partition got full after the guys here at the office sent lots of e-mails with large attachments. I just started over with a zero length utmp and everything went fine. That's certainly not the case with me :-) I take it your logging into this box via a serial port? I believe that's the cause of it - Consoles and telnet logins appear fine for me. -- Karl Ferguson Tower Networking Pty Ltd Tel: +61-8-9456- [EMAIL PROTECTED] t/a STAR Online Services Fax: +61-8-9455-2776 [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: wtmp problem
In article [EMAIL PROTECTED], Karl Ferguson [EMAIL PROTECTED] wrote: At 10:30 AM 25/04/97 +0300, Daniel MOSMONDOR - Mosh wrote: Hi! I am kind of new to this mailing list, so please excuse me if this subject is running around for some time. I have a strange wtmp problem, and something suggests that is has something to do with different versions of important system files. I don't consider myself as a linux guru (yet) so please help me with information you posses. Here is the copy of last log: onyx:~ last -10 ***~**2 !g`3 Fri Apr 25 10:13 still logged in ppp ttyD1 Fri Apr 25 10:12 still logged in ***~**2 !***cf`3 Fri Apr 25 10:07 - 10:13 (00:06) ppp ttyD3 Fri Apr 25 09:47 still logged in ***~**2 !^`3 Fri Apr 25 09:36 - 10:07 (00:31) mosh ftp mosh.bbm.hr Fri Apr 25 09:20 - 09:20 (00:00) ppp ttyD2 Fri Apr 25 09:00 still logged in mosh ttyp0mosh.bbm.hr Fri Apr 25 08:51 still logged in ppp ttyD4 Fri Apr 25 08:44 still logged in ppp ttyD0 Fri Apr 25 08:40 still logged in wtmp begins Tue Apr 22 15:41:03 1997 onyx:~ This is a problem with the sysvinit package version 2.70 and it's new glibc6 compatability. If you downgrade to 2.69-1 in the rex distribution it should solve this problem. I don't think so. I've seen this behaviour before. The wtmp code didn't change between 2.69 and 2.70 - the utmp code did (but very slightly, and I still can't find anything wrong with it). Anyway for 2.71 the new code will be used for utmp in init. But that won't solve this problem. I think it's just the fact that his /var/log/wtmp file is corrupt ie. not a multiple of sizeof(struct utmp). There are some rogue programs out there that do not write the 56 bytes of the current struct utmp atomically, I think. Just truncate the wtmp file with cp /dev/null /var/log/wtmp and it will start working again. Mike. -- |Miquel van |I know one million ways, to always pick| | [EMAIL PROTECTED] |the wrong fantasy --- the Black Crowes| | PGP fingerprint: FE 66 52 4F CD 59 A5 36 7F 39 8B 20 F1 D6 74 02 | -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: wtmp problem
At 09:12 PM 26/04/97 +0200, Miquel van Smoorenburg wrote: I don't think so. I've seen this behaviour before. The wtmp code didn't change between 2.69 and 2.70 - the utmp code did (but very slightly, and I still can't find anything wrong with it). Anyway for 2.71 the new code will be used for utmp in init. But that won't solve this problem. I think it's just the fact that his /var/log/wtmp file is corrupt ie. not a multiple of sizeof(struct utmp). There are some rogue programs out there that do not write the 56 bytes of the current struct utmp atomically, I think. Just truncate the wtmp file with cp /dev/null /var/log/wtmp and it will start working again. H - if the code doesn't change then can you explain this:- I just installed 2.70-1 and started getting corruption on my dialin serial ports. I go back to 2.69-1 and it's fine - no resetting of the log files, nothing. If there's something else I can try (yes, I've been through resetting wtmp/utmp back in March when I first reported it to debian-devel) please enlighten me :-) I run mgetty for the dialin lines, I hooked up a vt100 terminal to a serial port on a different machine with 2.70-1 and used plain getty (well, really agetty in disguise) and found the exact same thing - if I downgrade, it works a treat. Baffling. -- Karl Ferguson Tower Networking Pty Ltd Tel: +61-8-9456- [EMAIL PROTECTED] t/a STAR Online Services Fax: +61-8-9455-2776 [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: wtmp problem
In article [EMAIL PROTECTED], Karl Ferguson [EMAIL PROTECTED] wrote: At 09:12 PM 26/04/97 +0200, Miquel van Smoorenburg wrote: I don't think so. I've seen this behaviour before. The wtmp code didn't change between 2.69 and 2.70 - the utmp code did (but very slightly, and I still can't find anything wrong with it). Anyway for 2.71 the new code will be used for utmp in init. H - if the code doesn't change then can you explain this:- I just installed 2.70-1 and started getting corruption on my dialin serial ports. I go back to 2.69-1 and it's fine - no resetting of the log files, nothing. OK, which log file gets corrupted - the wtmp or the utmp file? Or both? I've heard reports about corrupted utmp files, and I'll try to fix that in 2.71 I run mgetty for the dialin lines, I hooked up a vt100 terminal to a serial port on a different machine with 2.70-1 and used plain getty (well, really agetty in disguise) and found the exact same thing - if I downgrade, it works a treat. Oh great, you can reproduce it. Can you tell me 1. which logfile gets corrupted 2. When (before login, during session, after logout) Mike. -- |Miquel van |I know one million ways, to always pick| | [EMAIL PROTECTED] |the wrong fantasy --- the Black Crowes| | PGP fingerprint: FE 66 52 4F CD 59 A5 36 7F 39 8B 20 F1 D6 74 02 | -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: wtmp problem
At 10:26 PM 26/04/97 +0200, Miquel van Smoorenburg wrote: Oh great, you can reproduce it. Can you tell me 1. which logfile gets corrupted Both the wtmp and utmp. 2. When (before login, during session, after logout) Upon login it seems fine, but upon logout it seems to write two enteries into the wtmp file which corrupts that one. On the utmp side, it seems that after someone has logged in it writes a normal record - if another user logs in it corrupts the last entry and it's replaced with the new users entry until either someone else logs out or a new user logs in. It seems like it's a real mess. I'm not *entirely* sure about the sequence of the utmp corruption - but the wtmp I'm sure of. However, they're both corrupted - suddenly a user appears in a 'who' and then they disappear into thin air (after another user logs in). Regards -- Karl Ferguson Tower Networking Pty Ltd Tel: +61-8-9456- [EMAIL PROTECTED] t/a STAR Online Services Fax: +61-8-9455-2776 [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: wtmp problem
At 10:30 AM 25/04/97 +0300, Daniel MOSMONDOR - Mosh wrote: Hi! I am kind of new to this mailing list, so please excuse me if this subject is running around for some time. I have a strange wtmp problem, and something suggests that is has something to do with different versions of important system files. I don't consider myself as a linux guru (yet) so please help me with information you posses. Here is the copy of last log: onyx:~ last -10 ***~**2 !g`3 Fri Apr 25 10:13 still logged in ppp ttyD1 Fri Apr 25 10:12 still logged in ***~**2 !***cf`3 Fri Apr 25 10:07 - 10:13 (00:06) ppp ttyD3 Fri Apr 25 09:47 still logged in ***~**2 !^`3 Fri Apr 25 09:36 - 10:07 (00:31) mosh ftp mosh.bbm.hr Fri Apr 25 09:20 - 09:20 (00:00) ppp ttyD2 Fri Apr 25 09:00 still logged in mosh ttyp0mosh.bbm.hr Fri Apr 25 08:51 still logged in ppp ttyD4 Fri Apr 25 08:44 still logged in ppp ttyD0 Fri Apr 25 08:40 still logged in wtmp begins Tue Apr 22 15:41:03 1997 onyx:~ This is a problem with the sysvinit package version 2.70 and it's new glibc6 compatability. If you downgrade to 2.69-1 in the rex distribution it should solve this problem. In the meantime I'll examine some bug reports on this package and see if it's been reported, if not I'll do so. Regards -- Karl Ferguson Tower Networking Pty Ltd Tel: +61-8-9456- [EMAIL PROTECTED] t/a STAR Online Services Fax: +61-8-9455-2776 [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
