hey, i tried to set up hbrelog today, but it fails on the login process for me. it starts the wow client, a error-message inside the client pops up (see attached image), and then after some seconds it restarts the wow client with the same problem. logs and a screenshot of the wow error are attached. since the error-mesasge states something about account selection, i tried with both WoW1 and blank in the accountname field of the config, both with the same problem. the accounts are new bnet accounts created with raf, they only have one classic wow account on them and nothing else.
Hey highvoltz, did you check this? arelog is working like designed but I fear for my accounts so it would be nice if you can check the source again. Regards frost
I have exacly same problem HBRelog thinks that Honorbuddy is frozen while its running fine and HBRelog start in infinite numbers of Honorbuddy... Win 7 64bit
looks like i found my problem - hbrelog seems to mess up with account-passwords that contain some 'special' characters
This is my log for the continually opening windows - this is new since the svn v 60 or 61 (with this log from the 62 version) Through all these reopening Hb is still running the quest bot without problems. Even after closing Hbrelog and closing the duplicate windows, Hb keeps working (it is still running now). View attachment Log[2012-03-20_09-37-02].txt
No, the SVN has not been compromised. I'm the only person with commit access to it and all the svn commits were done by me.
Attach a HB log please. There is something going wrong on HB's side because HBRelog doesn't think HB is attached and tries to restart HB.
Code: ! \ : > # " ' , @ im not sure if all of them cause the problem, i had the issue with 2 accounts and both passwords contained a random combination of these symbols plus upper/lower case letters and numbers i changed both to only upper/lower letters + numbers and now they work.
a few logs in sequence - sorry that some are just "max sessions" ones, but at least show timings?! (might be helpful?) View attachment 20-03-2012_19_21 4168 Log.txt View attachment 20-03-2012_19_23 5032 Log.txt View attachment 20-03-2012_19_23 10196 Log.txt View attachment 20-03-2012_19_24 10164 Log.txt View attachment 20-03-2012_19_27 1760 Log.txt View attachment 20-03-2012_19_54 5888 Log.txt
Thanks for attaching the logs. It looks like the HBrelog log message 'Closing Honorbuddy because it took too long to attach' is caused by the HB not being able to log into a session after 1 min. HBRelog will restart HB if it isn't attached after 1 min. This can be ignored since eventually the HB session will timeout (takes up to 3 mins) and it's able to login. What i'm trying to figure out is why HBRelog isn't closing the HB windows. I did make an attempt to fix this in Rev 62 and the log you posted earlier seems to be a from a version older then revision 62 so if you would, update from SVN (which is now at revision 65 I think), Also the revision is now shown in the HBRelog log on startup on the 1st line e.g. 1.0.0.REVISION
I've grabbed the latest svn (66), and will run and report. Thanks for your continued work on this project Just hoping the servers come back up before I have to go out.
The last revision was freezing HB a lot for me. I'll try the new version and see if its been fixed. Could you also add if there is no connection to a network (router disconnected) don't do anything till there is?
Here's a copy of the log. Lots of HB's keep on opening. It'll start one session of honorbuddy and it'll farm, but I guess it does not think that its open and continues to open a lot more Honorbuddy windows.
Could you test Latest SVN release? made some changes that should hopefully close a HB instance before opening up another one. If you still have issues then please attach the HB log file as well
I have the problem that, because i have a slow laptop, it takes a while for HB to get all the way through with its processes, even though HB is going through the startup process, HBrelog closes it and tries again. Is there a way to increase the time it takes for it to stop and try again?
