There is a way to get around this if you use screen/tmux. You can
basically tee the output to a file. I forget how you do that with
screen, but with tmux, it's the "pipe-pane" option.
This would give you the crash notification as you would get it on the
console, the startup errors, and the whole bit.
Otherwise, yea, you get nothing, even if you were to redirect
stderr/stdout. Once the program exits, it's gone and your pipes are broken.
ics wrote:
You will never see such log message either by looking at the logs
because the server has already crashed and it wont write to log at that
state. Only time when you see msg like that is when you look the server
console while it crashes or make screen log the stuff in it into a file
from which you can see much more.
-ics
17.8.2011 20:12, Saint K. kirjoitti:
I missed your last line. I've also searched for the crashID, no such
info in the logs.
On further inspection, another interesting note, the crashes with the
crashdumps seem to sometimes be happening in sync on 2 different
machines, like the last one mentioned.
Saint K.
________________________________________
From: Saint K.
Sent: 17 August 2011 19:07
To: Half-Life dedicated Linux server mailing list
Subject: RE: Crash log message
Thanks for that.
Interestingly enough, my servers make crashdumps but no log messages
such as that. I've grepped the log directory (case-insensitive) for
parts of that log message, but nothing comes back in result.
To summarize the crashes we still experience;
- Mystery crashes, creating crashdumps, no log entry (However, I
haven't seen a crash with a crashdump since 15th, 09:53CET - might be
fixed with last update - just mentioning it because I haven't seen any
update notes claiming to fix a crash)
- Freezes right after mapchange. Process just sits there doing
nothing, client's receive a timeout. Last log message is a cut-off
message from client's joining right after the mapchange. The freezes
generally only seem to occur on full (20+ players) servers.
Saint K.
________________________________________
From: [email protected]
[[email protected]] On Behalf Of Fletcher Dunn
[[email protected]]
Sent: 17 August 2011 18:54
To: 'Half-Life dedicated Linux server mailing list'
Subject: Re: [hlds_linux] Crash log message
Something like:
PreMinidumpCallback: updating dump comment Uploading dump (in-process)
[proxy ''] /tmp/dumps/crash_20110723191817_1.dmp
success = yes
response: CrashID=bp-445d6055-e9e7-420a-93b8-688a92110723
If you have dump filenames in your dumps folder, then just search for
those filenames.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Saint K.
Sent: Wednesday, August 17, 2011 9:45 AM
To: Half-Life dedicated Linux server mailing list
Subject: [hlds_linux] Crash log message
Does anyone know what the log message looks like which contains the
minidump ID of a crash? I need it to know what to grep for through my
logs to find the crashes and match them with the minidumps.
Cheers,
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
--
# Jesse Molina
# Mail = [email protected]
# Page = [email protected]
# Cell = 1.602.323.7608
# Web = http://www.opendreams.net/jesse/
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
