Snipe time jbidwatcher password#
Snipe will be retried, but is unlikely to fire.' Since it didn't say that, I have to guess that you went into the configuration and set the username and password to better values. If the login information had remained bad, it should have failed the presnipe with the message 'Pre-snipe login failed. It should have displayed that within about two and a half minutes of startup.
On Windows, it would have popped an alert out as well, noting the same thing. This would have indicated that it wasn't going to snipe successfully. The text in the upper right should have said, 'Not logged in'. Unfortunately, it looks like 'debugging' wasn't on, so the log details are scarce, and I'm extrapolating a LOT here.Īt the 12:56:47 point, it noted, 'Your sign in information is not valid.' Looking at the log file, your login information was bad on startup. On Linux), and look for the log file which would have included those time frames, you can either attach them to the bug, or look through them for more details on the attempted snipes and pass along what you find. It's not firing the snipe late, it's just canceling the unfired snipe after the auction is ended.Ĭ:\Documents and Settings\\.jbidwatcher
Snipe time jbidwatcher update#
The first time JBidwatcher tries to update the auction after it's completed, it'll recognize that it's done and a snipe is still outstanding, and cancel the snipe. It doesn't add everything to the status, because that would get spammy, but it does log its attempts to the log files if you have logging and debug enabled. Behind the scenes, JBidwatcher recognized that it wasn't the post-bid-preparation page, and tried a few things (because that page was titled and written differently when I put out the current version), but failed to extract a bid key, and probably kept retrying, until after the auction was done. The problem is that it's not clear from the auction info what went wrong here, but I'll give you an educated guess, and that is that the auction's price is sufficiently high that eBay put up an interstitial page during the bid preparation requesting that you confirm that you know what you're doing, bidding on an item this expensive. In fact, I hadn't noticed the lack of a 'Firing' line until it was pointed out. It is, and I've been following it as it comes into my email box, but db1ras is generally very knowledgeable on the program, which I'm very grateful for, as I can't manage it all myself. Sat Mar 10 23:56:: Cancelling snipe, auction is reported as ended. Sony HDR-HC1 2.8MP HiDef MiniDV Camcorder w/10x Zoom Sat Mar 10 19:42:: Cancelling snipe, auction is reported as ended. Panasonic 3 CCD Camcorder PV-GS250 ** EXTRAS **
Here is the status information for the two failed snipes:ġ.
Snipe time jbidwatcher how to#
I imagine this is part of why the snipes are failing, although it can't be the whole reason, given the 22 sec miss on one of the snipes! (Which also means that bumping up the lead time will not necessarily solve the problem, right?)Īny suggestions on how to get around the problem? I sure hope there is either a workaround or a fix coming soon, as I really LOVE this program, and need to use it in the next few days. I can observe this when I select Time Information from the Servers menu, and as soon as the little window comes up, compare the time to the eBay clock displayed in the upper-right corner of the JBidWatcher window.
After synchronizing the system time (by clicking on the corresponding option in the Servers menu), the system clock still appears to trail eBay by about 9-10 seconds. I have the sniping lead time set to 30 secs. Two of my snipes failed as they were apparently late by 9 secs in one case and 22 secs in the other.
0 kommentar(er)
