I can't keep it up!

[Troy McClure]

My server that is

I am running the server on WinXP, completely up to date with the 399h executable. Here is the odd thing, if people are playing on it, no problem at all, it just runs but if it is idle it will crash out in just a half hour. The only thing I can think of is a network timeout or something? I do not allow the server to go into sleep mode or anything.

This is the command line I use, wqpro399.exe -game artifact-rjs3.2 -dedicated 12 -noipx -heapsize 32768 -zone 1024 -udpport 26000

Anyone have any suggestions?

Thanks,

Troy

[Baker]

Swap it out with ProQuake 3.50 (wqpro) and let me know if you have the problem. I've heard you've tried winquake.exe as the server, does it happen with that?

/It is important to determine if this is

1. something I somehow introduced in the updates to ProQuake
2. Or #2: is either a mod flaw or pre-existing engine flaw

If it is something I somehow introduced in ProQuake 3.99 and not present in ProQuake 3.50, it can be found and eliminated.

Can you upload a .zip of your entire mod folder (the artifact-rjs3.2 folder) and make it available in this thread (upload to filefront if you need to)?

I'd like to test it out first hand since it seems to crash within 30 minutes, shouldn't take too long

[Troy McClure]

It seemed reliable with the old winquake but I did not put alot of time in it as I wanted to run the newer versions due to the wall hack.

I get the same results with both the old artifact and the new runes so I don't think I can blame it on a mod. I can upload the artifact directory to one of my websites but there is only progs.dat and config.cfg in it, that's it, not much to it.

I just DL'd 3.5 and have it running right now. I'll keep an eye on it and report back in the morning.

Thank you for your help!

Troy

[Baker]

I've had it running non-stop for an hour with ProQuake 3.99k (not available yet) with no problems. I'll try the version you were using next and see what happens.

Let me know about how it works with pq3.50.

/I don't think it's the mod. Artifact 3.2 has been widely used.

[Troy McClure]

Using 3.50 and artifact it went down, I can't tell you how long as I checked it this morning although I did start it late last night.

Just for yucks I am trying 3.5 with the latest version of runes and it's been up about 2 hours. I know I said it happened with both mods but to be honest I've switched from one executable to another as well as one mod to another so frequently that I want to do more testing.

If it continues to stay up I'll switch back to 3.99 with the latest version of runes and see what that result is. If the results are the same as what I've been seeing I'll run it on another machine and see what happens there.

Thanks for the help! I'll be back.

Troy

[Baker]

Just for yucks I am trying 3.5 with the latest version of runes and it's been up about 2 hours.

Slot Zero has debugged Artifact for maybe 5 years. If there are any server crashing problems with 3.2, they have been certainly fixed in RuneQuake.

If it continues to stay up I'll switch back to 3.99 with the latest version of runes and see what that result is. If the results are the same as what I've been seeing I'll run it on another machine and see what happens there.

Here is the 3.99k I mentioned earlier in the thread (Download).

Thanks for the help! I'll be back.

No problem

[IEEE 802.11]

I guess another good test would be to have Troy run the latest version of Rune Quake and see if the problem exists there as well. Although that won't be Gooland!

[Troy McClure]

With 3.50 and the newer version of runes it went down. I don't think I can point to the .exe or the mod, I think it has to do with my machine although figuring that out is a bear. It literally has nothing on it except a fresh install of XP that is up to date.

Is there anything in ANY of the executables that tells it to fail in the event of a conection timeout?

Like I said in my first post, if there is activity on the server it just runs......

For the record, I just grabbed the latest and am trying that although I do not expect a difference.......

Troy

[IEEE 802.11]

I wonder if this is something happening when the level changes. Set the level change time to something like 30 seconds and watch it for awhile to see if it crashes when the level changes.

[Troy McClure]

Going 2 hours on the new executable.....keeping fingers crossed.

I'll try your suggestion IEEE.

Thanks,

Troy

[=peg=]

make sure your machine does not power down any hardware if its sitting idle..

control panel -> power options -> disable hibernate and set all other options to "never"

[Troy McClure]

make sure your machine does not power down any hardware if its sitting idle..

control panel -> power options -> disable hibernate and set all other options to "never"

Thanks Peg. I did do that previously but last night I remembered that sometimes network cards can sleep or idle so I went into the settings, told it to always stay connected and viola, the server has been up all night, 10 hours straight.

Although I have to admit, I do not understand how a network setting will cause Quake to crash, if it were a timeout situation that finally quits because it cannot make a connection that would make sense but Quake does not update to server lists like Q3 so I am scratching my head?

Ayways, 10 hours is a record for me right now. Hopefully this was the trick. I'll report back and update in a day or so.

Troy

[Troy McClure]

18 Hours now, I'd say I have the problem solved.

Thanks for the help guys. As I thought in my earlier post, it was a machine issue, I think I just got lucky finding the problem right off the bat because something like this can plague for a while.

Thanks,

Troy