grr typo'

CPU  is  2 of them at 3.06gig each.


On Thu, Jul 14, 2011 at 7:47 AM, clad iron <[email protected]> wrote:

> i have seen this on a Ubuntu server. it's happened 3 times with in about 3
> weeks.
> Ram is fine.  Each time i was messing with it,i was working on the relay
> stuff.  ( thats not saying that the relay was the issue)
>
> 6 gig ram
> 2 - 3.6gig Xeon CPU
> 32bit Ubuntu 10
>
> Is yours 32bit ?
>
>
>
> On Thu, Jul 14, 2011 at 12:26 AM, E3pO <[email protected]> wrote:
>
>> Memory is fine, i ran memory tests before setting up the server. That
>> shouldn't be the issue, :\.
>>
>> Just crashed again..
>>
>> ----------------------------------------------
>> CRASH: Thu Jul 14 00:35:20 EDT 2011
>> Start Line: ./srcds_linux -debug -console -game tf +ip 65.18.168.205+port
>> 27015 +map surf_supersurf_v2 +maxplayers 32
>> [New Thread 8713]
>> [New Thread 8716]
>> [New Thread 8723]
>> [New Thread 8726]
>> [New Thread 8749]
>> [New Thread 8711]
>> [New Thread 8717]
>> [New Thread 8714]
>> [New Thread 8715]
>> [New Thread 8712]
>> [New Thread 8724]
>> #0  0x00811602 in ?? ()
>> No symbol table info available.
>> eax            0xf0 240
>> ecx            0x0 0
>> edx            0x2 2
>> ebx            0xafb10acc -1347351860
>> esp            0xafa3ad20 0xafa3ad20
>> ebp            0xafa3ad58 0xafa3ad58
>> esi            0x0 0
>> edi            0x0 0
>> eip            0x811602 0x811602
>> eflags         0x10202 [ IF RF ]
>> cs             0x73 115
>> ss             0x7b 123
>> ds             0x7b 123
>> es             0x7b 123
>> fs             0x0 0
>> gs             0x33 51
>> End of Source crash report
>> ----------------------------------------------
>>
>> (gdb) core core
>> BFD: Warning: /home/srcds/srcds_new_surf/orangebox/core is truncated:
>> expected core file size >= 496525312, found: 1040384.
>> [New Thread 8713]
>> [New Thread 8716]
>> [New Thread 8723]
>> [New Thread 8726]
>> [New Thread 8749]
>> [New Thread 8711]
>> [New Thread 8717]
>> [New Thread 8714]
>> [New Thread 8715]
>> [New Thread 8712]
>> [New Thread 8724]
>> Failed to read a valid object file image from memory.
>> Core was generated by `./srcds_linux -debug -console -game tf +ip
>> 65.18.168.205 +port 27015 +map surf_'.
>> Program terminated with signal 11, Segmentation fault.
>> #0  0x00811602 in ?? ()
>> (gdb) thread apply all bt
>>
>> Thread 11 (Thread 8724):
>> #0  0xb77a5430 in ?? ()
>> Cannot access memory at address 0xab8d6e4c
>>
>> Thread 10 (Thread 8712):
>> #0  0xb77a5430 in ?? ()
>> Cannot access memory at address 0xb7023214
>>
>> Thread 9 (Thread 8715):
>> #0  0xb77a5430 in ?? ()
>> Cannot access memory at address 0xaf3f1214
>>
>> Thread 8 (Thread 8714):
>> #0  0xb77a5430 in ?? ()
>> Cannot access memory at address 0xaf4f2214
>>
>> Thread 7 (Thread 8717):
>> #0  0xb77a5430 in ?? ()
>> Cannot access memory at address 0xaf1ef214
>>
>> Thread 6 (Thread 8711):
>> #0  0xb77a5430 in ?? ()
>> Cannot access memory at address 0xafa3b210
>>
>> Thread 5 (Thread 8749):
>> #0  0xb77a5430 in ?? ()
>> Cannot access memory at address 0xae4270f4
>>
>> Thread 4 (Thread 8726):
>> #0  0xb77a5430 in ?? ()
>> Cannot access memory at address 0xaab35084
>>
>> Thread 3 (Thread 8723):
>> #0  0xb77a5430 in ?? ()
>> Cannot access memory at address 0xad4252f0
>>
>> Thread 2 (Thread 8716):
>> #0  0xb77a5430 in ?? ()
>> Cannot access memory at address 0xaf2f0214
>>
>> Thread 1 (Thread 8713):
>> #0  0x00811602 in ?? ()
>> Cannot access memory at address 0xafa3ad20
>> (gdb)
>>
>> It would be great if someone can help me out with this. It's really
>> killing
>> the players... filling up to the top and then only having 20 or so come
>> back.
>>
>> On Wed, Jul 13, 2011 at 7:33 PM, Tony Paloma <[email protected]
>> >wrote:
>>
>> > Hardware problem? Run a memory testing tool and let it go all day.
>> >
>> > -----Original Message-----
>> > From: [email protected]
>> > [mailto:[email protected]] On Behalf Of E3pO
>> > Sent: Wednesday, July 13, 2011 4:16 PM
>> > To: Half-Life dedicated Linux server mailing list
>> > Subject: Re: [hlds_linux] My Server keeps crashing non stop.
>> >
>> > Still is crashing randomly. It fills up to 32\32 and for hours and hours
>> > and
>> > then just crashes.
>> >
>> > Weirdly enough the last crash actually didn't crash the server.. It
>> crashed
>> > all the clients in the server? every single person.
>> >
>> > On Wed, Jul 13, 2011 at 3:10 AM, E3pO <[email protected]> wrote:
>> >
>> > > (gdb) thread apply all bt
>> > >
>> > > Thread 11 (Thread 31279):
>> > > #0  0xb7706430 in ?? ()
>> > > Cannot access memory at address 0xab83de4c
>> > >
>> > > Thread 10 (Thread 31208):
>> > > #0  0xb7706430 in ?? ()
>> > > Cannot access memory at address 0xaf99c210
>> > >
>> > > Thread 9 (Thread 31243):
>> > > #0  0xb7706430 in ?? ()
>> > > Cannot access memory at address 0xaf251214
>> > >
>> > > Thread 8 (Thread 31209):
>> > > #0  0xb7706430 in ?? ()
>> > > Cannot access memory at address 0xb6f84214
>> > >
>> > > Thread 7 (Thread 4419):
>> > > #0  0xb7706430 in ?? ()
>> > > Cannot access memory at address 0xad38c2f0
>> > >
>> > > Thread 6 (Thread 31241):
>> > > #0  0xb7706430 in ?? ()
>> > > Cannot access memory at address 0xaf453214
>> > >
>> > > Thread 5 (Thread 2449):
>> > > #0  0xb7706430 in ?? ()
>> > > Cannot access memory at address 0xae38e0f4
>> > >
>> > > Thread 4 (Thread 31244):
>> > > ---Type <return> to continue, or q <return> to quit---
>> > > #0  0xb7706430 in ?? ()
>> > > Cannot access memory at address 0xaf150214
>> > >
>> > > Thread 3 (Thread 31281):
>> > > #0  0xb7706430 in ?? ()
>> > > Cannot access memory at address 0xaaa9c084
>> > >
>> > > Thread 2 (Thread 31242):
>> > > #0  0xb7706430 in ?? ()
>> > > Cannot access memory at address 0xaf352214
>> > >
>> > > Thread 1 (Thread 31238):
>> > > #0  0x00811602 in ?? ()
>> > > Cannot access memory at address 0xaf99bd20
>> > > (gdb)
>> > >
>> > >
>> > _______________________________________________
>> > 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

Reply via email to