* John [09-20-04 06:34]:

Is that a bug?

----- Original Message ----- From: "peter Nikolic" To: Sent: Monday, September 20, 2004 2:01 PM Subject: Re: [SLE] Why did my server reboot? - newbie

...

On Sunday 19 Sep 2004 23:52, Dan wrote:

...

Hi all. A newbie here. I have a little Suse 9.0 apache, mysql, php server running. I just noticed that the uptime is currently at 13 hours. How do I find out what happened 13 hours ago that cause my server to reboot? I have a UPS attached to it, so think that I can rule out power problems.

Regards from Denmark Dan

Hi

How long had the macine been up for prior to the reboot and was it actually an reboot ..

If you look back thru the archives recently there is an thread about running times and the uptime clock gets reset after so long can't remember how long but it is worth chasing up if oyu had no other signs of power failure then it may well be the uptime timer has reset automatically ..

Pete .

-- Linux user No: 256242 Machine No: 139931 G6NJR Pete also MSA registered "Quinton 11" A Linux Only area Happy bug hunting M$ clan PGN

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

no -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos

David, John & Dan, On Monday 20 September 2004 07:53, David SMITH wrote:

On Mon, Sep 20, 2004 at 02:28:44PM +0300, John wrote:

...

Is that a bug?

It's a feature.

Check your /var/log/messages to see if there are any signs of an actual reboot.

You can use the "last" command to look for reboots and crashes, as well ("last reboot" will show just reboots, just as "last user" shows only logins by "user"). "man last" for details, of course. Keep in mind that the lastlog file is rolled periodically. On my system, it seems to happen mid-month. I've never bother to track down where that particular date or interval is configure, but I'm sure it can be changed.

-- David Smith Work Email: Dave.Smith@st.com

Randall Schulz

Hi, On Monday 20 September 2004 08:49, Patrick Shanahan wrote:

* Randall R Schulz [09-20-04 10:13]:

...

Keep in mind that the lastlog file is rolled periodically. On my system, it seems to happen mid-month. I've never bother to track down where that particular date or interval is configure, but I'm sure it can be changed.

What a collection of mistakes: - The pertinent file is /var/adm/wtmp (and /var/adm/btmp for the bad login attempts log displayed via the "lastb" command). There is a file called "lastlog" ("/var/log/lastlog"), but it's not used for quite the same thing--it holds a record of when each defined user last logged in and is displayed in human-readable form by the "lastlog" command. - Typos left as an exercise for the reader...

/etc/logrotate.d/syslog /etc/logrotate.conf

-- Patrick Shanahan Registered Linux User #207535

Randall Schulz

Patrick, On Monday 20 September 2004 10:48, Patrick Shanahan wrote:

* Randall R Schulz [09-20-04 11:21]:

...

On Monday 20 September 2004 08:49, Patrick Shanahan wrote:

What a collection of mistakes:

- The pertinent file is /var/adm/wtmp (and /var/adm/btmp for the bad login attempts log displayed via the "lastb" command).

...

...

/etc/logrotate.d/syslog /etc/logrotate.conf

Then /etc/logrotate.d/wtmp, not /etc/logrotate.d/syslog

I didn't mean to insinuate that the mistakes were yours!

-- Patrick Shanahan Registered Linux User #207535

RRS