Hi.
I've had a box running as a server for a few years.
It's been offline for a week for so because i relocated.
Now it's up again, but for some reason, it becomes nonresponsive from
time to time.
I find nothing in the logs (the ones I've looked in).
In syslog, I find only that there are no 'marks' after it dies:
Apr 2 19:31:27 localhost -- MARK --
Apr 2 19:51:27 localhost -- MARK --
Apr 2 20:11:27 localhost -- MARK --
Apr 5 10:16:05 localhost syslogd 1.4.1#18: restart.

daemon.log, messages, and syslog also have nothing that points out to me
what happened.

I attached a screen and a keyboard to the box. After a while, the screen
blanks, but comes to life when I touch a key (standard behaviour) - but
when it stops responding to requests (mail and http), it also does not
come to life on my keypresses.

Any ideas how I can find out what makes it die?

Thanks,
/Morten

Morten <dontreplytousenetmessagesbymail@mikkelsens.net> :
>
> I've had a box running as a server for a few years.
> It's been offline for a week for so because i relocated.
> Now it's up again, but for some reason, it becomes nonresponsive from
> time to time.
> I find nothing in the logs (the ones I've looked in).
> In syslog, I find only that there are no 'marks' after it dies:
> Apr 2 19:31:27 localhost -- MARK --
> Apr 2 19:51:27 localhost -- MARK --
> Apr 2 20:11:27 localhost -- MARK --
> Apr 5 10:16:05 localhost syslogd 1.4.1#18: restart.
>
> daemon.log, messages, and syslog also have nothing that points out to me
> what happened.
>
> I attached a screen and a keyboard to the box. After a while, the screen
> blanks, but comes to life when I touch a key (standard behaviour) - but
> when it stops responding to requests (mail and http), it also does not
> come to life on my keypresses.
>
> Any ideas how I can find out what makes it die?

Perhaps, if you described the hardware, we could offer suggestions for
queries to that hardware, presumably leading to correcting its, or its
associated software's, configuration.


--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://blinkynet.net/comp/uip5.html Linux Counter #80292
- - http://www.faqs.org/rfcs/rfc1855.html Please, don't Cc: me.

Morten <dontreplytousenetmessagesbymail@mikkelsens.net> :
>
> I've had a box running as a server for a few years.
> It's been offline for a week for so because i relocated.
> Now it's up again, but for some reason, it becomes nonresponsive from
> time to time.
> I find nothing in the logs (the ones I've looked in).
> In syslog, I find only that there are no 'marks' after it dies:
> Apr 2 19:31:27 localhost -- MARK --
> Apr 2 19:51:27 localhost -- MARK --
> Apr 2 20:11:27 localhost -- MARK --
> Apr 5 10:16:05 localhost syslogd 1.4.1#18: restart.
>
> daemon.log, messages, and syslog also have nothing that points out to me
> what happened.
>
> I attached a screen and a keyboard to the box. After a while, the screen
> blanks, but comes to life when I touch a key (standard behaviour) - but
> when it stops responding to requests (mail and http), it also does not
> come to life on my keypresses.
>
> Any ideas how I can find out what makes it die?

Perhaps, if you described the hardware, we could offer suggestions for
queries to that hardware, presumably leading to correcting its, or its
associated software's, configuration.


--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://blinkynet.net/comp/uip5.html Linux Counter #80292
- - http://www.faqs.org/rfcs/rfc1855.html Please, don't Cc: me.

Morten <dontreplytousenetmessagesbymail@mikkelsens.net> :
>
> I've had a box running as a server for a few years.
> It's been offline for a week for so because i relocated.
> Now it's up again, but for some reason, it becomes nonresponsive from
> time to time.
> I find nothing in the logs (the ones I've looked in).
> In syslog, I find only that there are no 'marks' after it dies:
> Apr 2 19:31:27 localhost -- MARK --
> Apr 2 19:51:27 localhost -- MARK --
> Apr 2 20:11:27 localhost -- MARK --
> Apr 5 10:16:05 localhost syslogd 1.4.1#18: restart.
>
> daemon.log, messages, and syslog also have nothing that points out to me
> what happened.
>
> I attached a screen and a keyboard to the box. After a while, the screen
> blanks, but comes to life when I touch a key (standard behaviour) - but
> when it stops responding to requests (mail and http), it also does not
> come to life on my keypresses.
>
> Any ideas how I can find out what makes it die?

Perhaps, if you described the hardware, we could offer suggestions for
queries to that hardware, presumably leading to correcting its, or its
associated software's, configuration.


--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://blinkynet.net/comp/uip5.html Linux Counter #80292
- - http://www.faqs.org/rfcs/rfc1855.html Please, don't Cc: me.

Morten <dontreplytousenetmessagesbymail@mikkelsens.net> :
>
> I've had a box running as a server for a few years.
> It's been offline for a week for so because i relocated.
> Now it's up again, but for some reason, it becomes nonresponsive from
> time to time.
> I find nothing in the logs (the ones I've looked in).
> In syslog, I find only that there are no 'marks' after it dies:
> Apr 2 19:31:27 localhost -- MARK --
> Apr 2 19:51:27 localhost -- MARK --
> Apr 2 20:11:27 localhost -- MARK --
> Apr 5 10:16:05 localhost syslogd 1.4.1#18: restart.
>
> daemon.log, messages, and syslog also have nothing that points out to me
> what happened.
>
> I attached a screen and a keyboard to the box. After a while, the screen
> blanks, but comes to life when I touch a key (standard behaviour) - but
> when it stops responding to requests (mail and http), it also does not
> come to life on my keypresses.
>
> Any ideas how I can find out what makes it die?

Perhaps, if you described the hardware, we could offer suggestions for
queries to that hardware, presumably leading to correcting its, or its
associated software's, configuration.


--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://blinkynet.net/comp/uip5.html Linux Counter #80292
- - http://www.faqs.org/rfcs/rfc1855.html Please, don't Cc: me.

s. keeling wrote:
> Morten <dontreplytousenetmessagesbymail@mikkelsens.net> :
>>
>> I've had a box running as a server for a few years.
>> It's been offline for a week for so because i relocated.
>> Now it's up again, but for some reason, it becomes nonresponsive from
>> time to time.
>> I find nothing in the logs (the ones I've looked in).
>> In syslog, I find only that there are no 'marks' after it dies:
>> Apr 2 19:31:27 localhost -- MARK --
>> Apr 2 19:51:27 localhost -- MARK --
>> Apr 2 20:11:27 localhost -- MARK --
>> Apr 5 10:16:05 localhost syslogd 1.4.1#18: restart.
>>
>> daemon.log, messages, and syslog also have nothing that points out to me
>> what happened.
>>
>> I attached a screen and a keyboard to the box. After a while, the screen
>> blanks, but comes to life when I touch a key (standard behaviour) - but
>> when it stops responding to requests (mail and http), it also does not
>> come to life on my keypresses.
>>
>> Any ideas how I can find out what makes it die?
>
> Perhaps, if you described the hardware, we could offer suggestions for
> queries to that hardware, presumably leading to correcting its, or its
> associated software's, configuration.
>
>
Aging hardware, like the cpu fan, or the case fan, can cause slowness,
and even hardware to shutdown... when is the last time you cleaned it,
vacuumed it out, and put in a new CPU fan?