next »

[TimberW]

For weeks, if not months, my group has been experiencing problems with B3 1.7.1 not registering commands issued against a specific slot (17). No commands will work on whomever is in slot 17.
Short of re-installing the server, I'm at a loss as to what to do. Any advice or help anyone can offer would be greatly appreciated.

I found these lines several times, but I'm not sure if they are relevant or not...

111207 12:53:17   VERBOSE   'cid: 17 already in authentication queue. Aborting Join.'

111207 12:53:17   DEBUG   'slot 17 has disconnected or was forwarded to our http download location, removing from authentication queue...'

83rd-12-7-11-b3.rar - Log file and b3.xml (without passwords/log-ins).

Again, any help would be appreciated. Please and thank you.  

-[83rd]TimberWolf

PS I didn't put the log info into the Pastebin, as it's 10MB.

EDIT- Fixed link, and specified version.

[82ndAB.Bravo17]

Link doesn't work I'm afraid.

nvm, it's missing the www.

Can you set loglevel to 8 and post another log.

When did you last restart the server?

[TimberW]

<set name="log_level">8</set> done

The server was last restarted on 11/23. games_mp.log is about 80MB.

I'll restart the server and the B3 instance, and once there are more than 18 people on the server I'll try to run some commands on slot 17, and then post the log. Might be 12-24 hours though.

-TW

PS Just realized, I forgot to specify I'm running B3 1.7.1

[MordyT]

@82ndAB.Bravo17, did that pnkbuster patch you made/tested ever make it into 1.7.1? I had the same issue (against slot 13) on our server a while back if you remember...

@TimberW, when you upgraded to 1.7.1 did you overwrite all files? How do you do your updates?

[82ndAB.Bravo17]

@82ndAB.Bravo17, did that pnkbuster patch you made/tested ever make it into 1.7.1? I had the same issue (against slot 13) on our server a while back if you remember...

I was wondering that, but I didn't think that your problem lasted so long, and it wouldn't have been specifically with one slot all the time, which sounds like what is happening. But no, I don't think that it is in 1.7.1

[MordyT]

I was wondering that, but I didn't think that your problem lasted so long, and it wouldn't have been specifically with one slot all the time, which sounds like what is happening. But no, I don't think that it is in 1.7.1

Maybe he should try it, just in case?
In my case, I think it was always in slot13 that this issue occurred...

[TimberW]

@82ndAB.Bravo17, did that pnkbuster patch you made/tested ever make it into 1.7.1? I had the same issue (against slot 13) on our server a while back if you remember...

@TimberW, when you upgraded to 1.7.1 did you overwrite all files? How do you do your updates?

I upgraded by extracting the 1.7.1 files to a new directory. I copied over the custom plug-in files, and then I edited the new configs so that the contents matched the old configs. I didn't copy and paste everything, I only transferred the values.

Were you suggesting I try the PB patch you mentioned?

-TW

[MordyT]

I upgraded by extracting the 1.7.1 files to a new directory. I copied over the custom plug-in files, and then I edited the new configs so that the contents matched the old configs. I didn't copy and paste everything, I only transferred the values.

Were you suggesting I try the PB patch you mentioned?

-TW

Excellent upgrade method, ensures clean files everytime...

Try at your own risk: http://forum.bigbrotherbot.net/general-usage-support/(new)-missing-clients/msg28337/#msg28337

If it doesn't fix it, revert and make sure to get 82nd the logs he needs.

[TimberW]

Oy vey...

OK, just tried using a !poke and !lt on slot 17, and it worked. Unless the log_level fixed it, it's probably dormant right now. The last few restarts and log purges* having fixed this, so it will probably pop up again when we need to warn 17... I'll wait for reports of it not working, and will get the related log posted ASAP after the report.

I'll try the patch after I get the log posted.

-TW

*Log Purge: archiving the console_mp.log and games_mp.log files, and then deleting them.

[TimberW]

So, after taking a lengthy time away from gaming, I'm back.

Since the server was still having trouble with a few slots 16-17-18, I decided I would try something drastic. I did a fresh install of CoD4 and B3v1.7.1. It worked, for 2 days, and the problems have resurfaced. Below are two .Rar files containing the most recent log, and its truncated version containing log entries during and after my attempts to !lt 16 and !lt 18.

Full Log
Truncated Log

Now that the logs are posted, I'll install the patch.

-TW

[MordyT]

i can confirm that a fresh install of 18b seems to not have this patch. I have reinstall it and not heard a pep about the issue so far.

@op, let us know how it goes.

[82ndAB.Bravo17]

i can confirm that a fresh install of 18b seems to not have this patch. I have reinstall it and not heard a pep about the issue so far.

@op, let us know how it goes.

Mordy, do you mean that it doesn't have this patch, or this problem?

[MordyT]

@82nd,
It seems (though I have not done proper testing) that 1.8b does have the missing players bug you fixed.

I re-applied the cod.py from your earlier post and the bug seems to have disappeared...

[82ndAB.Bravo17]

Could you post the cod.py that you got with 1.80b, as the copy that I have does have the fix in it, but I d/l the source code version.

[MordyT]

I also dled the source version from groupware from your post asking for the link.
I will check my master (what I setup B3 bots from) and see the version numbers...
I don't know, maybe it was a one time glitch, but my admins haven't said boo since.