Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Diagnose remote hangups
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo
View previous topic :: View next topic  
Author Message
Habbit
Apprentice
Apprentice


Joined: 01 Sep 2007
Posts: 237
Location: 3.7137 W, 40.3873 N

PostPosted: Fri Jun 13, 2008 11:23 am    Post subject: Diagnose remote hangups Reply with quote

Hello everyone,

I'm trying to diagnose some strange hangups on a headless Gentoo box that I access through SSH. Until now, I had thought that the sudden disappearances of the box from the network were due to its poor wireless card, but I put some effort into scripting my way out of networklessness and I thought I had solved it. However, yesterday the machine dropped out of my LAN again. Annoyed, I hooked up an USB keyboard to it (it already has a screen), but the display wouldn't give any life signals and it would not even respond to magic SysRq combinations (that I made sure, were enabled in kernel). Thus, it was hung up hard and for good. Is there any way I can diagnose what happens previous to the hangup? (i.e. with logfiles or such) I don't fear kernel recompiles or such, so any option is welcome.

The box has the latest updates in stable x86, with kernel gentoo-2.6.24-r8 (I think). Thanks in advance.
_________________
Code:
~ $ objdump -d ./habbit_mind
90      xchg %rax, %rax
EB FD   jmp $-3
Back to top
View user's profile Send private message
vps
n00b
n00b


Joined: 19 Dec 2007
Posts: 9
Location: Hannover, Germany

PostPosted: Fri Jun 13, 2008 12:29 pm    Post subject: Reply with quote

There is probably already a syslog daemon running on that headless machine, right? Configure it to forward all messages to another machine on your LAN. Perhaps this will show the reason for the hang.

Vitus

PS: /etc/syslog-ng/syslog-ng.conf
_________________
Thinkpad R51e: Atheros Wifi, Broadcom Ethernet, Radeon Xpress 200M
Back to top
View user's profile Send private message
Habbit
Apprentice
Apprentice


Joined: 01 Sep 2007
Posts: 237
Location: 3.7137 W, 40.3873 N

PostPosted: Fri Jun 13, 2008 12:46 pm    Post subject: Reply with quote

vps wrote:
Configure it to forward all messages to another machine on your LAN.

I've taken a look at the man pages for syslog-ng and it appears that I should set up a tcp or udp "destination" line. However, I don't know how to configure the other machine to receive the logs - it runs Ubuntu 8.04, so I don't know if it uses syslog-ng or another syslogger.
_________________
Code:
~ $ objdump -d ./habbit_mind
90      xchg %rax, %rax
EB FD   jmp $-3
Back to top
View user's profile Send private message
deathcon1
Apprentice
Apprentice


Joined: 30 Aug 2007
Posts: 182
Location: Canada

PostPosted: Fri Jun 13, 2008 1:46 pm    Post subject: Reply with quote

Sounds like it might be hardware failure of some kind. Have you tried memtest or does MCELOG give any output?
Back to top
View user's profile Send private message
Habbit
Apprentice
Apprentice


Joined: 01 Sep 2007
Posts: 237
Location: 3.7137 W, 40.3873 N

PostPosted: Fri Jun 13, 2008 4:40 pm    Post subject: Reply with quote

Memory and HD are both fine, as far as memtest and the HD manufacturer's tools go. Other hardware should be OK too, since the CPU has never been overclocked and the MB has been working without a flaw for years. Any other options? How do I redirect the logs to another computer?
_________________
Code:
~ $ objdump -d ./habbit_mind
90      xchg %rax, %rax
EB FD   jmp $-3
Back to top
View user's profile Send private message
vps
n00b
n00b


Joined: 19 Dec 2007
Posts: 9
Location: Hannover, Germany

PostPosted: Fri Jun 13, 2008 4:55 pm    Post subject: Reply with quote

Habbit wrote:
vps wrote:
Configure it to forward all messages to another machine on your LAN.

I've taken a look at the man pages for syslog-ng and it appears that I should set up a tcp or udp "destination" line. However, I don't know how to configure the other machine to receive the logs - it runs Ubuntu 8.04, so I don't know if it uses syslog-ng or another syslogger.


You usually use UDP to send syslog data, the well known port for this is 514 (see /etc/services). See http://gentoo-wiki.com/TIP_System_Logging_with_syslog-ng how to relay to a remote_server.



If Ubuntu runs syslog-ng you have to add a line udp(ip("0.0.0.0") port(514)); to /etc/syslog-ng.conf

Code:

source src {
        # ... keep everything else ...

        # process log messages from network:
        udp(ip("0.0.0.0") port(514));
};



If it's another syslogger you have to RTFM :)
_________________
Thinkpad R51e: Atheros Wifi, Broadcom Ethernet, Radeon Xpress 200M
Back to top
View user's profile Send private message
Habbit
Apprentice
Apprentice


Joined: 01 Sep 2007
Posts: 237
Location: 3.7137 W, 40.3873 N

PostPosted: Fri Jun 13, 2008 6:23 pm    Post subject: Reply with quote

It used sysklogd, but I was able to hook both of them pretty nicely. Thanks! Now, I just have to wait for it to hang...
_________________
Code:
~ $ objdump -d ./habbit_mind
90      xchg %rax, %rax
EB FD   jmp $-3
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum