So my latest problem - I've been using Auction Lite for months now. In the last week, I've seen constant disconnects whenever I scan anything. Selling is fine. Browsing with the basic Bliz browsing screen is fine. But the fast browser instantly kicks me out of the game, almost always causing to the point where I need to reset my modem & router.
I thought this was an Auction Lite problem, maybe with a change in the last patch due to Bliz's new Armory/Auction app? But then I tried using Auction Master and got the same problem. So now I'm thinking maybe the problems on my end and I have no idea where to start. Nothing in my hardware set up changed this week.
When the disconnect happens, I don't get any error messages. Digging through my Buggrabber lua I found a brief mention to Auction Lite in this error code from Tomquest2, but I doubt it's relevant:
{
["message"] = {
"tomQuest2-3.3.3 release 4\\tomQuest2.lua:3255: Usage: GetQuestLogTitle(index)\ntomQuest2-3.3.3 release 4\\tomQuest2.lua:3255: in function <Interface\\AddOns\\tomQuest2\\tomQuest2.lua:3253>\n(tail call): ?:\n<in C code>: in function `RemoveQuestWatch'\nTourGuide-3.3.0.56\\Broker.lua:61: in function <Interface\\AddOns\\TourGuide\\Broker.lua:7>\n<in C code>: in function `pcall'\nTourGuide-3.3.0.56\\Dongle.lua:247: in function <Interface\\AddOns\\TourGuide\\Dongle.lua:246>\nTourGuide-3.3.0.56\\Dongle.lua:334: in function <Interface\\AddOns\\TourGuide\\Dongle.lua:328>\n\nLocals:|r\nself =
{\n TRACKED_ACHIEVEMENT_UPDATE = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:2956\n updateDQToText = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:3752\n modules =
{\n }\n CancelTimer = <function> defined @Interface\\AddOns\\DataStore\\libs\\AceTimer-3.0\\AceTimer-3.0.lua:311\n SecureHook = <function> defined @Interface\\AddOns\\AuctionLite\\Libs\\AceHook-3.0\\AceHook-3.0.lua:339\n ", -- [1]
"hideShowDefaultBlizTracker = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:4451\n PLAYER_REGEN_DISABLED = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:2123\n GetSinkAce3OptionsDataTable = <function> defined @Interface\\AddOns\\Chatter\\Libs\\LibSink-2.0\\LibSink-2.0.lua:536\n qTrInit = true\n tQ2toggleAchievementsTracker = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:5405\n computeQuestsTag = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:5055\n IsEnabled = <function> defined @Interface\\AddOns\\DataStore\\libs\\AceAddon-3.0\\AceAddon-3.0.lua:465\n ScheduleTimer = <function> defined @Interface\\AddOns\\DataStore\\libs\\AceTimer-3.0\\AceTimer-3.0.lua:276\n questsSort = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:197\n commHandler = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:3596\n RegisterMessage = <function> defined @Interface\\AddOns\\DataStore\\libs\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:117\n", -- [2]
" UnregisterMessage = <function> defined @Interface\\AddOns\\DataStore\\libs\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:180\n RegisterSink = <function> defined @Interface\\AddOns\\Chatter\\Libs\\LibSink-2.0\\LibSink-2.0.lua:647\n setAchievementsTrackerLayout = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:2003\n hooks =
{\n }\n achievementsCategories =
{\n }\n SendCommMessage = <function> defined @Interface\\AddOns\\DataStore\\libs\\AceComm-3.0\\AceComm-3.0.lua:73\n db =
{\n }\n updateQuestCategoryCell = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:2701\n UnregisterAllComm = <function> defined @Interface\\AddOns\\DataStore\\libs\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:201\n SetEnabledState = <function> defined @Interface\\AddOns\\DataStore\\libs\\AceAddon-3.0\\AceAddon-3.0.lua:438\n Hook = <function> defined @Interface\\AddOns\\AuctionLite\\Libs\\AceHook-3.0\\AceHook-3.0.lua:277\n questsByCategory =
{\n }\n moduleState =
{\n }\n OnEnab", -- [3]
"le = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:5252\n updateStatusbar = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:2627\n computeQuestsLevel = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:5044\n OnInitialize = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:5228\n NewModule = <function> defined @Interface\\AddOns\\DataStore\\libs\\AceAddon-3.0\\AceAddon-3.0.lua:255\n interactivityList =
{\n }\n RAID_ROSTER_UPDATE = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:5176\n Deserialize = <function> defined @Interface\\AddOns\\DataStore\\libs\\AceSerializer-3.0\\AceSerializer-3.0.lua:240\n GetName = <function> defined @Interface\\AddOns\\DataStore\\libs\\AceAddon-3.0\\AceAddon-3.0.lua:298\n updateQuestTextCell = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:2721\n name = \"tomQuest2\"\n setBackDrop = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:1836\n Pour = <function> defined @Interfa", -- [4]
"ce\\AddOns\\Chatter\\Libs\\LibSink-2.0\\LibSink-2.0.lua:375\n Disable = <function> defined @Interface\\AddOns\\DataStore\\libs\\AceAddon-3.0\\AceAddon-3.0.lua:328\n WatchFrame_Update = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:4447\n updateQuestCounter = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:3796\n Unhook = <function> defined @Interface\\AddOns\\AuctionLite\\Libs\\AceHook-3.0\\AceHook-3.0.lua:421\n Print = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:308\n PARTY_MEMBERS_CHANGED = <function> defined @Interface\\AddOns\\tomQuest2\\tomQuest2.lua:4986\n Serialize = <function> defined @Interface\\AddOns\\DataStore\\libs\\AceSerializer-3.0\\AceSerializer-3.0.lua:116\n RegisterComm = <function> defined \n ---", -- [5]
},
["type"] = "error",
["time"] = "2010/05/21 11:59:51",
["session"] = 172,
["counter"] = 179,
}, -- [48]
There's nothing at all in the last couple days about Auction Master.
I did find a few brief messages in my connections.log file, but I don't know what it means. Here's an example:
So now I don't know. I guess maybe I'll try Auctioneer next. It's hard to test because I'm not the only one who uses this server so I don't want to interfer with outher peoples service. Thanks in advance for any advice you can give me or things to try.
It sounds to me like you're only having problems when there is a lot of data involved. This is almost certainly a hardware issue. Addons likely have nothing to do with it. If you are using a wireless connection, try moving closer to the access point or just connecting directly with an ethernet connection.
If you are disconnected during scanning, try disabling the fast scan feature (use "/al config")
And, the first time you did a full scan, the following message was presented asking if you wanted to enable fast scanning:
AuctionLite's fast auction scan can scan the entire auction house in a few seconds.
However, depending on your connection, a fast scan can cause you to be disconnected from the server. If this happens, you can disable fast scanning on the AuctionLite options screen.
Enable fast auction scans?
It's not a hardware issue. It's an issue with trying to do things that Blizzard didn't really have in mind when they designed the API, which sometimes works, but sometimes disconnects you. If it disconnects you, don't do it.
If it disconnects you, its because the client couldn't receive the information fast enough. Blizzard designed that auction house feature with reliable broadband connections in mind.
On the connections I use, it doesn't sometimes not work, it ALWAYS works. I've never been disconnected during a fast scan and I do them several times a day.
What I was trying to say in the OP was that previously, my experience was like gamemaster's - I always used the fast scan feature and never had a problem. The problem has only developed in the last week. Furthermore, the problem doesn't seem to be just with one auction mod but several.
So I was wondering if there's a router setting or something I could do to help cut down on the disconnects. I agree it sounds sort of like a hardware problem. I wonder if the recent temperature spike is interfering. I'm already connected to the router via ethernet.
AFAIK the "fast scan" is a request using the standard API with no restriction, not even a limit on the number of rows. Blizzard servers only respond to such request once per 15 minutes for any given player (or account, or IP, or whatever). It is known to cause lags and/or disconnections.
From what I've been able to test in both Auctioneer and Auction Lite, the fast mode works great if you have a latency below 100ms. If your latency is higher, you could get disconnected.
Hm. I just now tried doing a scan after making sure my latency was below 100. It worked! I'll keep an eye on this and try again tomorrow night.
Late to the party, but...I've been able to "induce" disconnects by occupying API calls for extensive periods of time. This might be something the Auction-ish addon authors can design around, if it's a matter of processing time (rather than latency) causing disconnects.
Curiosity sake, does the "quick scan" interface give you any status updates? I've experience disconnects during the processing portion of this before, using the full Auctioneer suite; i.e. I get to about step 3/3 of a quick-scan before experiencing trouble. Presumably, the full once-every-15-minute dump was complete, and the addon was just chewing on the data in some important event that the API didn't want tied up.
Most of this is speculation. If true, check for background processes that are busier than before you started seeing the problem; maybe something is typing up CPU/memory cycles, to the point where processing is timing out.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I thought this was an Auction Lite problem, maybe with a change in the last patch due to Bliz's new Armory/Auction app? But then I tried using Auction Master and got the same problem. So now I'm thinking maybe the problems on my end and I have no idea where to start. Nothing in my hardware set up changed this week.
When the disconnect happens, I don't get any error messages. Digging through my Buggrabber lua I found a brief mention to Auction Lite in this error code from Tomquest2, but I doubt it's relevant:
There's nothing at all in the last couple days about Auction Master.
I did find a few brief messages in my connections.log file, but I don't know what it means. Here's an example:
5/23 00:46:54.819 Disconnected from 82ce810c
5/23 00:46:54.860 GRUNT: state: LOGIN_STATE_DISCONNECTED result: LOGIN_OK
5/23 00:46:54.874 Login program=WoW platform=Win locale=enUS
5/23 00:46:54.892 Component WoW.Win.11723
5/23 00:46:54.904 Component WoW.base.11723
5/23 00:46:54.904 Component WoW.enUS.11723
5/23 00:46:54.929 Component Tool.Win.1462
So now I don't know. I guess maybe I'll try Auctioneer next. It's hard to test because I'm not the only one who uses this server so I don't want to interfer with outher peoples service. Thanks in advance for any advice you can give me or things to try.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAnd, the first time you did a full scan, the following message was presented asking if you wanted to enable fast scanning:
It's not a hardware issue. It's an issue with trying to do things that Blizzard didn't really have in mind when they designed the API, which sometimes works, but sometimes disconnects you. If it disconnects you, don't do it.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumOn the connections I use, it doesn't sometimes not work, it ALWAYS works. I've never been disconnected during a fast scan and I do them several times a day.
So I was wondering if there's a router setting or something I could do to help cut down on the disconnects. I agree it sounds sort of like a hardware problem. I wonder if the recent temperature spike is interfering. I'm already connected to the router via ethernet.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHm. I just now tried doing a scan after making sure my latency was below 100. It worked! I'll keep an eye on this and try again tomorrow night.
Thanks everyone for the tips!
Curiosity sake, does the "quick scan" interface give you any status updates? I've experience disconnects during the processing portion of this before, using the full Auctioneer suite; i.e. I get to about step 3/3 of a quick-scan before experiencing trouble. Presumably, the full once-every-15-minute dump was complete, and the addon was just chewing on the data in some important event that the API didn't want tied up.
Most of this is speculation. If true, check for background processes that are busier than before you started seeing the problem; maybe something is typing up CPU/memory cycles, to the point where processing is timing out.