ET Pro 3.1.12 Public Beta Release
Moderators: Forum moderators, developers
I'd just like to add that I too have been experiencing crashes on Linux. The strange part was, it was running from 9AM-5PM or so, with people most of the day, and not a crash. I then rebooted the server for changing the autodownload URL, I've now gotten approx. 5 crashes from 5PM till now, 11PM. Nothing seemed to trigger this.
Unfortunately, I too was using screen, so was unable to grab a good logfile.
Unfortunately, I too was using screen, so was unable to grab a good logfile.
-
- Posts: 12
- Joined: Tue Aug 17, 2004 11:56 am
- Location: Belgium
- Contact:
Found 2 major bugs myself:
-The text "Mines have been detected here" show up everywhere where mines from the opposing team are, but nobody had to trigger one to get the warning. I'm pretty sure because it was a 1-1 match.
-When going prone or coming back to normal from prone freezes the aim for about 2 seconds, just like when being revived... (Or is this a new 'feature' to stop people abusing this function for close fights?)
-The text "Mines have been detected here" show up everywhere where mines from the opposing team are, but nobody had to trigger one to get the warning. I'm pretty sure because it was a 1-1 match.
-When going prone or coming back to normal from prone freezes the aim for about 2 seconds, just like when being revived... (Or is this a new 'feature' to stop people abusing this function for close fights?)
- |TGT|Rodent|
- Posts: 8
- Joined: Wed Apr 06, 2005 12:33 pm
Prone delay, been available from 3.1.0 I think.
!!!!!!THANKS BANI AND ET PRO TEAM!!!!!!
!!!!!!THANKS BANI AND ET PRO TEAM!!!!!!
Visit our website or join 69.56.128.51 | 207.218.249.168
- HarryHirsch
- Posts: 92
- Joined: Mon Sep 01, 2003 9:28 am
- Location: Germany
Code: Select all
------------- CUT HERE --------------
Version: etpro 3.1.12
Platform: Linux
Signal: Segmentation violation (11)
Signal code: 128
fault address: (nil)
Load addresses:
0x4001c000 /lib/libdl.so.2
0x4001f000 /lib/libm.so.6
0x40041000 /lib/libc.so.6
0x40000000 /lib/ld-linux.so.2
0x519ff000 /lib/libnss_compat.so.2
0x51a07000 /lib/libnsl.so.1
0x51a1c000 /lib/libnss_nis.so.2
0x51a25000 /lib/libnss_files.so.2
0x51a2e000 /home/et/et/pb/pbsv.so
0x54cb9000 /lib/libnss_dns.so.2
0x54cbd000 /lib/libresolv.so.2
0x54ccf000 /home/et/et/pb/pbcls.so
0x54de6000 /home/et/et/pb/pbags.so
0x52758000 /home/et/et/etpro/qagame.mp.i386.so
EIP: 400b2069
edi:bff91d80 esi:00000001 ebp:bff91958 esp:bff91944
eax:fffffff9 ebx:401705e0 ecx:00000000 edx:00000000
stack:
5280e110 bff91980 52820c38 bff91d80 bff91d80 5490dcd8 527d736f 00000001
549101a8 00000400 00000000 30303030 00303030 52ee5840 5490f2ac 3935312d
37383839 00313331 46414130 42463841 32374330 44373735 39413645 45373444
46314235 31444200 34343532 36303842 33324545 6c635c36 6e75705f 7375626b
code:
8b 50 04 f6 c2 02 75 4f f6 c2 04 8d bb 80 0a 00 00 74 07 25 00 00 f0 ff 8b 38
8b 83 8c 2b 00 00 85 c0 75 2b c7 07 01 00 00 00 89 74 24 04 89 3c 24 e8 71 11
Stack trace: 1 entries
/home/et/et/etpro/qagame.mp.i386.so[0x5276c157]
------------- CUT HERE --------------
debian testing
i thought this had always been like this - correct me if i'm wrongsucker_pvn wrote:Found 2 major bugs myself:
-The text "Mines have been detected here" show up everywhere where mines from the opposing team are, but nobody had to trigger one to get the warning. I'm pretty sure because it was a 1-1 match.
- Ragnar_40k
- Posts: 394
- Joined: Thu Mar 18, 2004 5:18 pm
- Location: Berlin, birthplace of the Döner
- Contact:
This is the HQ-Bonus when you constructed a command post. The text "Mines have been reported in this area." appears when you close to enemy mines.sucker_pvn wrote:-The text "Mines have been detected here" show up everywhere where mines from the opposing team are, but nobody had to trigger one to get the warning. I'm pretty sure because it was a 1-1 match.
The Emperor watch over you.
-
- Posts: 12
- Joined: Tue Aug 17, 2004 11:56 am
- Location: Belgium
- Contact:
Ok, I always played on some specific servers which probably didn't activate the prone delay, and with the latest etpro it's activated by default perhaps?
And the mines being reported, I just though somebody had to trip those first after which everybody gets the message. the way it happened to me the other time is: Going through a path I didn't take before, and the message appeared, on a 1-1 fight so nobody could have seen those mines. I didn't know the command post needed to be constructed (which seems pretty obvious now I think about it), but isn't it a bug then that nobody needs to trip mines for the warning to show up? Seams like a brain-dead design to me.
PS. I know having level 4 for Battle Sense makes mines show up near you, but that only happens if you have earned that level 4. Not all the random 'noobs' (:)) need to know where mines are...
And the mines being reported, I just though somebody had to trip those first after which everybody gets the message. the way it happened to me the other time is: Going through a path I didn't take before, and the message appeared, on a 1-1 fight so nobody could have seen those mines. I didn't know the command post needed to be constructed (which seems pretty obvious now I think about it), but isn't it a bug then that nobody needs to trip mines for the warning to show up? Seams like a brain-dead design to me.
PS. I know having level 4 for Battle Sense makes mines show up near you, but that only happens if you have earned that level 4. Not all the random 'noobs' (:)) need to know where mines are...
- Lekdevil.NL
- Posts: 89
- Joined: Fri Sep 12, 2003 8:59 am
Sorry. The server just crashed again, but no malloc/free info was shown. Maybe that's because the server is running FreeBSD instead of Linux? I had set the MALLOC_CHECK_ environment variable.zinx wrote:If there was output about malloc/free above this, it would be incredibly useful.Lekdevil.NL wrote:Code: Select all
-------- UNRECOVERABLE ERROR -------- This may be due to a bug in etpro Information to be used in a bug report is being generated: ------------- CUT HERE --------------
Here's the console output (last few lines before the crash included):
Code: Select all
DF101 just lost 3.000000 skill points for skill Covert Ops
^3PunkBuster Server: CORRUPT Screenshot /home/wet/et27961/pb/svss/pb000050.png received from 11 ^0th^1e^0J^1a^0ck^1a^0L
Client 86 connecting with 300 challenge ping
^3PunkBuster Server: Screenshot /home/wet/et27961/pb/svss/pb000038.png TIMED OUT after 225 seconds (slot=16)
^3PunkBuster Server: Screenshot /home/wet/et27961/pb/svss/pb000037.png TIMED OUT after 225 seconds (slot=11)
^3PunkBuster Server: Screenshot /home/wet/et27961/pb/svss/pb000038.png TIMED OUT after 225 seconds (slot=16)
Kill: 13 14 10: Matze killed Zuleczek by MOD_THOMPSON
^3PunkBuster Server: Screenshot /home/wet/et27961/pb/svss/pb000037.png TIMED OUT after 226 seconds (slot=11)
^3PunkBuster Server: Screenshot /home/wet/et27961/pb/svss/pb000037.png TIMED OUT after 226 seconds (slot=11)
Kill: 8 4 11: ^1-=^7OS^1=-^7ke^1NT killed dziadu by MOD_STEN
Client 86 connecting with 300 challenge ping
-------- UNRECOVERABLE ERROR --------
This may be due to a bug in etpro
Information to be used in a bug report is being generated:
------------- CUT HERE --------------
Version: etpro 3.1.12
Platform: Linux
Signal: Abort (6)
Signal code: 0
Load addresses:
0x28104000 /lib/libdl.so.2
0x28108000 /lib/libm.so.6
0x28129000 /lib/libc.so.6
0x280ef000 /lib/ld-linux.so.2
0x2d2f3000 /lib/libnss_files.so.2
0x2d2fd000 /home/wet/et27961/pb/pbsv.so
0x2d6bc000 /lib/libnss_nisplus.so.2
0x2d6c6000 /lib/libnsl.so.1
0x2d6da000 /lib/libnss_nis.so.2
0x2d6e4000 /lib/libnss_dns.so.2
0x2d6e8000 /lib/libresolv.so.2
0x2d6f8000 /home/wet/et27961/pb/pbcls.so
0x2d80f000 /home/wet/et27961/pb/pbags.so
0x2df2c000 /home/wet/et27961/etpro/qagame.mp.i386.so
EIP: 281510a1
edi:00000001 esi:00000000 ebp:bfb91298 esp:00000000
eax:00000000 ebx:000102d3 ecx:00000006 edx:2824b30c
stack:
---------- RECURSIVE CRASH ----------
Exiting hard.
Abort trap
bash-2.05b$
Last edited by Lekdevil.NL on Tue Apr 26, 2005 8:01 am, edited 1 time in total.
Bloody hell I set this ENV_MALLOC thing Zinx asked for and on the next crash of ETPro it pulled the plug on my entire server at 8:51:11 am this morning... .
Our servers now run on 64 bit steroids. Point your ET to:
- Forgotten Ground StopWatch Server with occasional wolfrof 1
- Fraggle Rock ETPub Server - Mix up ET/UT & Duke Nukem
- Forgotten Ground StopWatch Server with occasional wolfrof 1
- Fraggle Rock ETPub Server - Mix up ET/UT & Duke Nukem
I used:
env MALLOC_CHECK_=2 ./etded +set fs_game etpro + set dedicated 2 +set net_ip 212.112.232.88 +set net_port 27960 +exec etpro_hirntot.cfg
and i get that error. Hope it helps..
env MALLOC_CHECK_=2 ./etded +set fs_game etpro + set dedicated 2 +set net_ip 212.112.232.88 +set net_port 27960 +exec etpro_hirntot.cfg
and i get that error. Hope it helps..
Code: Select all
-------- UNRECOVERABLE ERROR --------
This may be due to a bug in etpro
Information to be used in a bug report is being generated:
------------- CUT HERE --------------
Version: etpro 3.1.12
Platform: Linux
Signal: Abort (6)
Signal code: 0
Load addresses:
0x40018000 /lib/libdl.so.2
0x4001b000 /lib/libm.so.6
0x4003d000 /lib/libc.so.6
0x40000000 /lib/ld-linux.so.2
0x451e6000 /lib/libnss_compat.so.2
0x451f1000 /lib/libnsl.so.1
0x45205000 /lib/libnss_files.so.2
0x4520e000 /home/gameserver/.etwolf/pb/pbsv.so
0x487bd000 /lib/libnss_dns.so.2
0x487c1000 /lib/libresolv.so.2
0x487d1000 /home/gameserver/.etwolf/pb/pbcls.so
0x488e8000 /home/gameserver/.etwolf/pb/pbags.so
0x4625c000 /home/gameserver/.etwolf/etpro/qagame.mp.i386.so
EIP: 40066781
edi:00000001 esi:00000000 ebp:bff911d8 esp:bff911ac
eax:00000000 ebx:0000104c ecx:00000006 edx:40154e48
stack:
40066464 0000104c 00000006 4004d1b3 4006644c 40154e48 400097c0 00001b62
451e2000 40066440 4003c000 bff91318 40067be1 00000006 bff9120c 00000000
40067b20 40154e48 00000001 000003ff 400a833d 40154e48 bff917d9 00000000
00000020 00000000 00000000 00000000 00000000 00000000 00000000 00000000
code:
89 d3 3d 01 f0 ff ff 73 01 c3 53 e8 00 00 00 00 5b 31 d2 81 c3 b7 e6 0e 00 29
c2 52 e8 4e f3 fe ff 59 5b 89 08 83 c8 ff eb df 90 8d 74 26 00 55 89 e5 83 ec
Stack trace: 1 entries
/home/gameserver/.etwolf/etpro/qagame.mp.i386.so[0x46270157]
------------- CUT HERE --------------
Trying to clean up...
---------- RECURSIVE CRASH ----------
Exiting hard.
Aborted
I've posted an updated qagame which also has the clientkick fix at:
http://zinx.xmms.org/misc/tmp/qagame.mp.i386.so
Which will hopefully solve the crashing problems; please report any crashes that happen while using this updated version.
http://zinx.xmms.org/misc/tmp/qagame.mp.i386.so
Which will hopefully solve the crashing problems; please report any crashes that happen while using this updated version.
Zinx Verituse http://zinx.xmms.org/
Should those of us not experiencing crashes update the file too?zinx wrote:I've posted an updated qagame which also has the clientkick fix at:
http://zinx.xmms.org/misc/tmp/qagame.mp.i386.so
Which will hopefully solve the crashing problems; please report any crashes that happen while using this updated version.
I mean, I hate to mess with it if it ain't broke.
BBr|ET Clan Leader
BroadbandReports.com
BroadbandReports.com