Maitenance locking up during team fights

[dpezet]

My Usurper nightly maintenance has been locking up on my BBS pretty regularly. I can expect it probably one out of three times. It always hangs when processing the team fights. Has anyone else had this happen? I saw some other posts that made mention of it, but no fies.

I am running SynchronetBBS on Windows Server 2003 R2 with Usurper v0.20d.

Thanks,

Don

[Lenny of Repan]

Hayle thar dpezet,

I don't have a definitive answer othan maybe turning the Teams, OFF. IHowever that would also take away a lot of the game, so that's really not an answer. Some installations have this problem, some don't. There are several others that have nearly the same problem. While I was running my gameserver site with the last few versions, I had the on various computers on my network. Some computers would work fine for a while, and then start failing. It was so sporadic, that the only way I was confident to have playable games was to manually run daily mainrenance, and clean everything up afterward if it failed. At some points I was running more than 6 Usurper doors, each needing daily care. My free time became short at home, due my real JOB, so I unplugged the access. I was running on WIndows 98SE, ME, XP-Home and XP-Pro.
As far as I can tell, It didn't have anything to do with my BBS/Gameserver software. We used to be able to do daily events on my old GAP/BBS system. One afterthought, are your users disconnecting, not wanting to wait while it does maintenance. That might add to problems, and is why I started manual maintenance.

Have CHOPPED 16 SPAMMER messages to reach this real one. Thanks for your support and patience.

[dpezet]

For now, I just let it run automatically and check it first thing in the morning. If it is locked up, I reset it and manually run maintenance. If it ran fine, I leave it be. I may write a script to monitor how long the maintenance process has been running and if it runs for more than 30 minutes, can the process and rerun. We'll see.

Thanks,

Don

[dpezet]

I thought I would throw out a new observation here. The lockups always occured when the NPC gang \"Close Circle\" was fighting. I had a player team wipe out \"Close Circle\" and the error hasn't happened since. Also, the \"Close Circle\" team seems to have locked up. The NPCs in it no longer advance levels and they aren't being resurected at night.

Either way, I'll trade 4 NPCs for no lockups in over a week any day.

Don

[Lenny of Repan]

I thought I would throw out a new observation here. The lockups always occured when the NPC gang "Close Circle" was fighting. I had a player team wipe out "Close Circle" and the error hasn't happened since. Also, the "Close Circle" team seems to have locked up. The NPCs in it no longer advance levels and they aren't being resurected at night.

Either way, I'll trade 4 NPCs for no lockups in over a week any day.

Don

as the old sayin goes, veri interestin.. Close Circle is the "default" team that is automatically created on initialization. On early versions the team always had the same password. Before I started using MSDOS PC's I was able to determine that password, and would join the Close Circle team and wreek total havoc on the BBS where I dailedup to. I was also able to log in as one of the NPC's I believe it was Ugluk, and boot other team-members off and change the password. Anyway all that was part of my justification in getting a PC.
Anywhooo back on topic. As a SYSOP you might disolve that team, as they normally have but two members, and those two members are stored in the regular players data, not in the NPC data. You might consider eliminating the team, and even maybe the first two players in the players data file. When I was running the gameserver, I only had one door with default players. If you need detailed instructions on such surgery on the data files, let me know.