My snipe was at least $5 above the final price ($100), yet jbid tells me my bid was too low and didn’t bid?

Sun Jun 20 11:32:24 PDT 2010: Getting the sign in cookie for ebay.com
Sun Jun 20 11:32:25 PDT 2010: Done getting the sign in cookie for ebay.com
Sun Jun 20 11:32:25 PDT 2010: **** – Loading bid request…
Sun Jun 20 11:32:26 PDT 2010: Checking sign in as bid key load failed!
Sun Jun 20 11:32:26 PDT 2010: **** – Snipe was too low, and was not accepted.
Sun Jun 20 11:32:26 PDT 2010: Snipe was too low, and was not accepted.
Sun Jun 20 11:32:26 PDT 2010: Snipe appears to have failed; cancelling.

Oh, and I increased the price of the bid in the last 3 minutes before sniping. The original bid was below. My snipe time is set to 6 seconds.

Hmmm, actually I think this may be a “sniping after auction ended” synch issue like Torque had. Further in the log (Auction ended at 11:34:27 PDT):

Sun Jun 20 11:34:24 PDT 2010: Time delta with ebay.com is -2557
Sun Jun 20 11:34:24 PDT 2010: Time delta with ebay.co.uk is -2809
Sun Jun 20 11:34:33 PDT 2010: * – Cancelling snipe, auction is reported as ended.
Sun Jun 20 11:34:33 PDT 2010: Cancelling Snipe for: **
Sun Jun 20 11:34:33 PDT 2010: * – Cancelling snipe.

Greetings,
I don’t understand why you blocked out the item numbers; I generally need that information to dig into it; the item number and the amount your snipe bid was set for.

That error Snipe was too low, and was not accepted. specifically comes from a response that reads either: Your bid must be at least or Enter {amount} or more both of which mean the same thing. That your bid was too low at 2 minutes out.

Now it’s possible that when you changed your bid, it still sniped with the old value (presumably IT was below the ending price?), and a snipe with the new value didn’t get fired for some reason, but that shouldn’t be the case. (As in, I’ve looked at the code and can’t find a path that will cause that, but it’s a theoretical possibility.) The only reason I think that is your reference to the canceling snipe message, which suggests that there was still an outstanding snipe, despite it attempting to cancel it at 11:32:26 PDT.

I’m not sure what would lead to that behavior… Anyhow, item number, initial snipe price and adjusted (what you increased it to at 3 minutes out) snipe price would be helpful. Submitting the log to a ticket (as an attachment!) on the JBidwatcher issue tracker would also help me debug the problem.

— Morgan Schweers, CyberFOX!

Yes, mine is the same problem.
Here is all what appears on information

Vtg Wool Baseball Car Club Award BUTWIN Jacket Coat (190405167918)
Currently $19.01 (3 Bids)
High bidder o***e
Your max bid $31.79
Shipping $28.95
Seller mattrinc
Listing ended at Wed Jun 23 03:30:50 CEST 2010
Listing has ended.

Events
Sun Jun 20 09:46:17 CEST 2010: Failed to load from server!
Sun Jun 20 09:46:17 CEST 2010: Communications failure talking to the server. (2)
Mon Jun 21 21:55:43 CEST 2010: Failed to load from server!
Wed Jun 23 03:28:44 CEST 2010: Preparing snipe.
Wed Jun 23 03:28:57 CEST 2010: Loading bid request...
Wed Jun 23 03:29:00 CEST 2010: Done loading bid request, got form...
Wed Jun 23 03:30:44 CEST 2010: Submitting bid form.
Wed Jun 23 03:30:44 CEST 2010: Firing actual snipe.
Wed Jun 23 03:30:47 CEST 2010: Snipe apparently failed, as the auction cannot be bid on anymore: Vtg Wool Baseball Car Club Award BUTWIN Jacket Coat
Wed Jun 23 03:30:47 CEST 2010: Done loading post-bid data.
Wed Jun 23 03:30:47 CEST 2010: Loading post-bid data.
Wed Jun 23 03:30:47 CEST 2010: Done submitting bid form.

Hope it helps

Greetings,
@Torque – Your snipe timing seems to be set to about 6 seconds? It looks like your system clock is more than 4 seconds off from eBay’s clock, so when it took 3 seconds to fire the actual snipe, it was too long.

Specifically, from 03:28:44 to 03:28:57, it was logging in and pulling up the necessary pages. It took 13 seconds to do all that. Then, it loaded the bid request (essentially getting to the ‘confirmation’ page on eBay), which took another 3 seconds. Then, at 6 seconds before the auction end (or so it believed), it started the process of sending the confirmation form. It finished in 3 seconds, and loaded the post-bid response, which indicated that the auction was ended. Since its end time was, it believed, 3 seconds before the auction was supposed to end, that means that your computer’s clock is at least 4 seconds off from eBay’s. Worse, it’s apparently not being adjusted for by JBidwatcher, either because it’s disabled or the last time JBidwatcher synchronized the time, it wasn’t as badly off. I’d need to see your log file (attached as a file, to a ticket or in email, rather than just dumped up here!) to know more.

This is why I don’t recommend sniping with 6 seconds. Your computer’s clock, extra latency on your connection, a program slowing your system down, anything can kick in to make a snipe fail at that short a timeframe.

— Morgan Schweers, CyberFOX!

Hi Morgan:
I goes to send-you the log in a e-mail, sorry but I’m a begginer here, but I want to let-you know a few details for if those helps too:
Now I’m sniping on 7 seconds, but on 2.1pre6, I was doing that on 5 seconds, and jbidwatcher never failed, even with a download program running at the same time.
I have activated Time Syncronisation, but I supposed, who jbidwatcher syncronise with the Ebay clock, and not with my own clock.It´s possible to change that and do who the clock of jbidwatcher, only syncronise with the Ebay clock?
I ask-you that, because all this happens since the last update, and in some other bids, the delay was of more than 1 minute.
I goes to send-you the log to cyberfox@users.sourceforge.net
Thanks again.

P.D. I have read right now on the activity log, who Jbidwatcher is syncronising time with Ebay.com, and with Ebay.co.uk also, 2 seconds later, but at the time of snipe, the clock isn’t syncronised

Hi Morgan:
I have been looking at the tiickets, and if it helps , I have exactly the same problem as Hal boddington and Brad, and as you can see, Hal is using MAC OS, I’m on Windows XP, so maybe something don’t goes as supposed.

Greetings,
@Torque – Brad’s bug report is specifically a problem that he hasn’t upgraded to 2.1pre8. Hal didn’t give any log files, so there’s no way for me to know what his issue is.

— Morgan Schweers, CyberFOX!