Sponsored Content
Full Discussion: suse 9 crashed
Operating Systems Linux SuSE suse 9 crashed Post 302295012 by upengan78 on Friday 6th of March 2009 10:14:48 AM
Old 03-06-2009
suse 9 crashed

Hi,

Running SLES 9 (update 4) on dell's poweredge 1950 server.
Kernel: 2.6.5-7.315-smp #1 SMP Wed Nov 26 13:03:18 UTC 2008 x86_64 x86_64 x86_64 GNU/Linux

Yesterday night my monitoring service emailed me system(ssh/smtp) unreachable...I tried connection through ssh, it did not let me through and close connection.

then I tried system console ( I connect to text console remotely) that would ask me for authentication but after using root login also it gave error can not fork process or something along those lines.

Forunately I have ipmi configured, power soft did not work so I did power cycle or reset.

I am pasting a link to the relevent lines from /var/log/messages below,

Could someone please go through that link and tell me if this OS bug. ( am sure some users were programming on it, but crashing the system is not affordable) I would like to know if I can do anything for protecting from such a crash

Thanks!

Last edited by upengan78; 03-06-2009 at 11:19 AM..
 

We Also Found This Discussion For You

1. Linux

Suse Linux System Crashed

Friends please let me know. How we can check the reason why system restarted automatically or rebooted. Suggest me some way other than messag log. Thankx Bryan (1 Reply)
Discussion started by: bryanabhay
1 Replies
DBD::Gofer::Transport::stream(3)			User Contributed Perl Documentation			  DBD::Gofer::Transport::stream(3)

NAME
DBD::Gofer::Transport::stream - DBD::Gofer transport for stdio streaming SYNOPSIS
DBI->connect('dbi:Gofer:transport=stream;url=ssh:username@host.example.com;dsn=dbi:...',...) or, enable by setting the DBI_AUTOPROXY environment variable: export DBI_AUTOPROXY='dbi:Gofer:transport=stream;url=ssh:username@host.example.com' DESCRIPTION
Without the "url=" parameter it launches a subprocess as perl -MDBI::Gofer::Transport::stream -e run_stdio_hex and feeds requests into it and reads responses from it. But that's not very useful. With a "url=ssh:username@host.example.com" parameter it uses ssh to launch the subprocess on a remote system. That's much more useful! It gives you secure remote access to DBI databases on any system you can login to. Using ssh also gives you optional compression and many other features (see the ssh manual for how to configure that and many other options via ~/.ssh/config file). The actual command invoked is something like: ssh -xq ssh:username@host.example.com bash -c $setup $run where $run is the command shown above, and $command is . .bash_profile 2>/dev/null || . .bash_login 2>/dev/null || . .profile 2>/dev/null; exec "$@" which is trying (in a limited and fairly unportable way) to setup the environment (PATH, PERL5LIB etc) as it would be if you had logged in to that system. The ""perl"" used in the command will default to the value of $^X when not using ssh. On most systems that's the full path to the perl that's currently executing. PERSISTENCE
Currently gofer stream connections persist (remain connected) after all database handles have been disconnected. This makes later connections in the same process very fast. Currently up to 5 different gofer stream connections (based on url) can persist. If more than 5 are in the cache when a new connection is made then the cache is cleared before adding the new connection. Simple but effective. TO DO
Document go_perl attribute Automatically reconnect (within reason) if there's a transport error. Decide on default for persistent connection - on or off? limits? ttl? AUTHOR
Tim Bunce, <http://www.tim.bunce.name> LICENCE AND COPYRIGHT
Copyright (c) 2007, Tim Bunce, Ireland. All rights reserved. This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See perlartistic. SEE ALSO
DBD::Gofer::Transport::Base DBD::Gofer perl v5.16.2 2010-12-21 DBD::Gofer::Transport::stream(3)

Featured Tech Videos

All times are GMT -4. The time now is 11:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy