My server also just crashed with this message: *** glibc detected *** ./srcds_linux: free(): invalid pointer: 0x11e50008 *** /lib32/libc.so.6(+0x6bf31)[0xf7567f31] /lib32/libc.so.6(+0x6d7a8)[0xf75697a8] /lib32/libc.so.6(cfree+0x6d)[0xf756c88d] /home/gpanel/servers/ltclan_tf2/orangebox/bin/engine.so(+0x16cb10)[0xf6d5db10] (Full backtrace at http://pastebin.com/rruvfUY1 )
It also wouldn't restart on its own. :( 2011/7/21 ics <[email protected]>: > The update has been on all our servers now about 7 hours and counting. At > that time, 2 of the servers have crashed twice, two others once. They might > stay on from one hour to 5 hours but eventyally there is a crash, that is > caused by the last update. All servers are full of folks playing too so it's > more likely to get a crash while map changes OR while there is stuff > happening. 2 times i've had to restart server manually as they have just > been hanging and not rebooting themselves, 4 times, they restarted back up > alone. > > I looked at the console on the servers that left hanging and the screen > showed similiar crash listing than L4D servers used to pull out. While this > has nothing to do with TF2, im just mentioning it. > > -ics > > 21.7.2011 14:56, Yuki kirjoitti: >> >> Crashing here. >> >> *** glibc detected *** ./srcds_linux: malloc(): memory corruption: >> 0x0ae60118 *** >> >> ...and so on. >> >> Incidentally I'm hearing things of bugs with these new weapons and crashes >> relating to teleporters, though I'm not sure whether these are true. >> >> On 21 July 2011 12:47, Anthony Stoyanov<[email protected]> wrote: >> >>> No problems on debian 5.5 and debian 6.0.2 both 64bit. >>> >>> >>> On 21.7.2011 г. 14:38 ч., Evaldas wrote: >>> >>>> Once again, SLES11 SP1 and Ubuntu Server are running stable for about 5 >>>> hours. >>>> >>>> On Thu, 21 Jul 2011 14:08:12 +0300, E3pO<[email protected]> wrote: >>>> >>>> Whoever has the final call on releasing updates needs to be fired. It >>>> is >>>>> >>>>> illogical to release an update for such a widely used application >>>>> without >>>>> testing and then just walk away from the update station and go to >>>>> sleep.. >>>>> Hell, i'm willing to bet it was about 85% done uploading to the content >>>>> servers about to release the update and the guy just called it a night. >>>>> >>>>> And what the hell are they doing so different each time that breaks so >>>>> many >>>>> things? >>>>> >>>>> Added the items for Dr. Grordbort's Victory Pack >>>>> - Fixed hatless hats not working correctly >>>>> - Fixed a display issue with team color paints >>>>> - Updated the localization files >>>>> >>>>> So how many hats have they released now? You would think they would >>>>> have >>>>> that figured out by now. They fixed a display issue, seems like that is >>>>> client side and not related to the server.. and updated localization >>>>> files? >>>>> >>>>> What does any of that have anything to do with the server crashing? Is >>>>> there >>>>> some kind of offication change log we can have access to so we know >>>>> what >>>>> has >>>>> been modified? Maybe a more in depth update info instead of just "Added >>>>> some >>>>> items". That update did much more then that.. >>>>> >>>>> And I still don't see why Valve bothered making a TF2 BETA if they >>>>> don't >>>>> even use it. >>>>> >>>>> Make code changes and document the changes, build, test test test test >>>>> test >>>>> test test test and test more, then have someone else look over the code >>>>> and >>>>> say "Oh hell that will cause a buffer overflow if you have to many >>>>> sentries! >>>>> change that to this.." then fix and test test test test more and have >>>>> more >>>>> people look into it and once all the code changes have been reviewed >>>>> and >>>>> locked down send an email to the list telling everyone what has been >>>>> changed >>>>> and that there will be an update available in 1 hour of the email. make >>>>> a >>>>> build for TF2 BETA and update preferably sometime in the morning hours >>>>> so >>>>> that stuff doesn't break while you're sleeping and you wake up to >>>>> broken >>>>> servers. >>>>> Keep an eye out and check statistics for how many servers are running >>>>> and >>>>> how many are updating and how many have crashed after the update etc. >>>>> Keep >>>>> an eye on the list and after a few days of absolutely NO problems with >>>>> the >>>>> new build warn the TF2 server admins that it will be released 12 PM EST >>>>> (or >>>>> w\e time) so they can be prepared. >>>>> >>>>> Isn't that just common sense? Who the hell would build an artificial >>>>> heart >>>>> for their father and just give it to him without testing it out first. >>>>> Hell >>>>> he may of forgot battery.c >>>>> >>>>> On Thu, Jul 21, 2011 at 6:37 AM, Mart-Jan Reeuwijk<[email protected] >>>>>> >>>>>> wrote: >>>>> >>>>> Oh, don't you know? its for having a stable game... and if memory >>>>> serves >>>>>> >>>>>> me >>>>>> well, it doesn't even crash. >>>>>> >>>>>>> _____________________________**___ >>>>>>> From: E3pO<[email protected]> >>>>>>> To: Half-Life dedicated Linux server mailing list< >>>>>> >>>>>> [email protected].**com<[email protected]> >>>>>>> >>>>>>> Sent: Thursday, 21 July 2011, 8:21 >>>>>>> Subject: Re: [hlds_linux] Server crashes after today's update >>>>>>> >>>>>>> Valve, quick question. >>>>>>> >>>>>>> What is Team Fortress 2 Beta for? >>>>>>> >>>>>>> kthxbai. >>>>>>> >>>>>>> On Thu, Jul 21, 2011 at 12:38 AM, Tony Paloma<[email protected] >>>>>>> wrote: >>>>>>> >>>>>>>> Yes I crashed again >>>>>>>> *** glibc detected *** ./srcds_linux: double free or corruption >>>>>> >>>>>> (!prev): >>>>>>>> >>>>>>>> 0x1aeae148 *** >>>>>>>> >>>>>>>> The double free makes more sense. >>>>>>>> >>>>>>> *snip* >>>>>>> >>>>>> ______________________________**_________________ >>>>>> To unsubscribe, edit your list preferences, or view the list archives, >>>>>> please visit: >>>>>> >>>>>> http://list.valvesoftware.com/**mailman/listinfo/hlds_linux<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<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<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
