BeBot - An Anarchy Online and Age Of Conan chat automaton
Archive => Anarchy Online Archive => AO 0.6 support => Topic started by: Karsta on February 06, 2010, 10:57:46 am
-
bebot is version .67 and it didnt work on .65 either
Kbot [ROSTER] [UPDATE] Starting roster update for guild id: 4270081 on RK2
Kbot [ROSTER] [UPDATE] XML for the guild obtained
Kbot [ROSTER] [UPDATE] Roster update failed. Funcom XML returned 0 members.
I tried changing org id and it did work for another org but it doesnt work for our org.
We have had this same problem for some time and i tought its cos org is too big and i cleared ~200 members but it didnt help.
Number of members: 741, and 1 206 lines in kbot_users sql DB.
Karstas
-
Changed back to 0.65 and now roster update works.
Tried 0.67 and it doesn't work so theres something wrong i think.
-
Apologies for the late reply.
The timeout settings in 0.6.7 might be a bit agressive and this is likely what is causing your issues.
in main/14_Tools.php find line 94 function get_site($url, $strip_headers = 0, $server_timeout = 5, $read_timeout = 10)
Change the read timeout from 10 up to 15 or 20 and see if that helps you.
Please let me know which value works best for you.
In 0.6.6 and earlier the timeout value was never even paid attention to, which caused severe problems when funcom servers became unresponsive as the bot could hang for long enough to be disconnected by the server.
-
Apologies for the late reply.
np it was pretty quick.
and that timeout change helped thx.
Karstas
-
Did 15 do the trick for you or did you need to go to 20?
-
I just put 30 and it worked, but now tested with 15 and didnt work.
20 was good again.
-
I have been using 30 for the past month, but just recently the bots started lagging really bad... set it for 20 and they are working better...
Anyone heard of any changes FC has done to chat? Seems lots of bots are lagging badly.
-
It's probably People of Rubi-Ka.
I've noticed problems getting PoRK to load for the past two weeks or so.
It took 6 minutes just now to get a 503 error.
-
I emptied the users table in the database and that seems to have cured the lag... I am thinking that the member cleanup FC did confused the bot... I am now combing thru the exported data to see if I can recover the guestlist to re-import.
-
Cleaning up the roster table definitely helped. The bots are running much better now... Maybe not looking up the inactive members that FC modified did the trick. I also set the roster to "fallback" mode.
-
Found a tweak that seems to get the bot functioning properly again
Goto settings, tools
under tools:
set tools force_sockets Off
set tools get_site Sockets
restart the bot after that
once I did this, the bot started reacting like you'd expect it to again.
-
Thanks, but I am already set there that same as you suggested. But Also when I try to bring up a web browser to http://people.anarchy-online.com ... it just hangs. I am really starting to think this is an FC issue.
This is the only thing I get back from that site...
This webpage is not available.
The webpage at http://people.anarchy-online.com/ might be temporarily down or it may have moved permanently to a new web address.
*edit -- I set the bot to use curl instead of sockets (!set tools get_site Curl) and seems a bit more responsive. That was mentioned in a different thread.
-
It seems there is really something wrong with the FC servers... Perhaps they changed their ports again? The XML down load I got after clearing the member table was really quite old. And does not seem to be updating.
-
Wolfcomm [23:40:06] [ERROR] [tools] Coult not connect to server 208.82.193.43:80 (http://people.anarchy-online.com/character/bio/d/l/name/charactername/bio.xml) Reason (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)
^^^ Is the exact error on the bot. Return timer was set to 20 and sockets are off. It cycles 4 times on a character name found in the bot roster and then goes to the next name. The most interesting thing that I have found is that it errors/times out on buddies (non-org members but alts). Org members come up clean on the roster update.
-
The most interesting thing that I have found is that it errors/times out on buddies (non-org members but alts). Org members come up clean on the roster update.
The Org members are probably being populated by the XML cache and not the actual FC servers.
!settings Member
Roster: Fallback
Description: What should we use to look up organization information? (Fallback means that if XML fails the cache will be used)
Change to: [ XML | WhoisCache | Fallback ]
-and-
!settings Whois
LookupOrder: funcom_auno
Description: Which order should we use to look up players information?
Change to: [ funcom_auno | auno_funcom | funcom_only | auno_only ]
Just a semi-educated guess :)
-
my question is why does !rosterupdate go through and [BUDDY QUE] [BUDDY ADD] members that were !member del before/lately?
-
Shelly, my settings are correct. I hope they fix this soon because it is causing my bot to seriously lag.
-
Not a necro
This last couple of weeks I've had similar issues, new members are not added to the rooster. I see them pop up on BUDDY ADD. No matter what I try new members are not added to the bot.
Has anyone found a solution to this?
The same rooster update has been going for weeks, same members are being removed and added.
-
Krypto: Do you have over 1000 user in your db?
-
this can be solved by cleaning up old members in your database.
The reason for this occurring is that when you have over 1000 members, buddy-add refuses to actually work, thus your guild bot can't track the new people.
Running a large guild myself, I've written a little module to clean this up myself but its a little messy, so I haven't released it. It will also delete members that you used !member del on too. I'll post a cut-down version of it when I get home from work tonight.
-
This will list or delete users that haven't logged in for over 100 days. Really useful if your guild bot is full of dead users.
To just see who would be deleted:
!remove_old_members list
To actually delete them:
!remove_old_members delete
See attached file.