Al right, never seen them before. Just strikes me a bit odd that they are printed when the server already has fully changed the map.
Saint K. ________________________________________ From: [email protected] [[email protected]] On Behalf Of ics [[email protected]] Sent: 17 August 2011 23:08 To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crash log message Those messages have been there for ages. If client connects to the server too fast, when the server isn't even yet loaded the map itself, the player will be forced to reconnect. It also happens if the player connects during mapchange. -ics 17.8.2011 23:55, Saint K. kirjoitti: > On further inspection of the servers console, right after a mapchange, before > a crash, I see these messages; > > Forcing client reconnect (2) > Forcing client reconnect (2) > > These errors are not logged. I can see them on the console of the frozen > server, but it's not in the log from that server. > > I have not yet seen those before. Anyone has any idea what those are about? > > Saint K. > ________________________________________ > From: [email protected] > [[email protected]] On Behalf Of Saint K. > [[email protected]] > Sent: 17 August 2011 20:07 > To: Half-Life dedicated Linux server mailing list > Subject: Re: [hlds_linux] Crash log message > > Currently not, but I'll enable it, thanks. > > Saint K. > ________________________________________ > From: [email protected] > [[email protected]] On Behalf Of ics > [[email protected]] > Sent: 17 August 2011 20:09 > To: Half-Life dedicated Linux server mailing list > Subject: Re: [hlds_linux] Crash log message > > If you have -debug enabled in the launch parameters (command line), some > crashes do get written with more detail into debug.log which is for > example in */orangebox/ folder. > > -ics > > 17.8.2011 20:49, Saint K. kirjoitti: >> You have a point there. >> >> That makes you wonder however why the crashID's aren't written to a >> (separate) log then. The server is still capable of uploading and receiving >> a crashID, so you'd think writing a log message would be in the line of >> possibilities. Fletch, maybe an idea? >> >> Saint K. >> ________________________________________ >> From: [email protected] >> [[email protected]] On Behalf Of ics >> [[email protected]] >> Sent: 17 August 2011 19:43 >> To: Half-Life dedicated Linux server mailing list >> Subject: Re: [hlds_linux] Crash log message >> >> 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 >> >> _______________________________________________ >> 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 _______________________________________________ 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
