#2081 new
Dodgy Geezer

Snipe fail - no bid

Reported by Dodgy Geezer | March 17th, 2019 @ 10:11 AM | in 2.1 Release

Had a snipe set up - but no snipe happened. Happened twice in the same way - snipe entered ok but JbidWatcher made no attempt to action it at the time. Using Windows 10 UK Ebay.

Logs are enclosed.

Thanks for the software!

Comments and changes to this ticket

  • Dodgy Geezer

    Dodgy Geezer March 18th, 2019 @ 07:40 AM

    To make things a bit clearer, Jbidwatcher accepted the snipe input which was for a valid item at a valid snipe price, tracked it over time, and then at the auction time, did not prepare or fire a snipe, but simply moved the item into the 'complete' section. It was as if I had input an item but not entered any snipe price - except that I had.

  • Dodgy Geezer

    Dodgy Geezer March 18th, 2019 @ 01:10 PM

    This may have something to do with the problem - I have a time delta of 10.5 secs, and when I try to synchronise, it does not change this. I am sniping at 7 secs, so 10.5 will make me out of range...

    Mon Mar 18 20:04:22 GMT 2019: Parsing URL https://www.ebay.co.uk/p/The-Eye-of-Zoltar-by-Jasper-Fforde-Paperba...
    Mon Mar 18 20:04:23 GMT 2019: Potential quote error!
    Mon Mar 18 20:04:39 GMT 2019: Saving to: C:\Users\fred.jbidwatcher\JBidWatch.cfg
    Mon Mar 18 20:04:44 GMT 2019: [Show Time Info]
    Mon Mar 18 20:04:47 GMT 2019: [Resync]
    Mon Mar 18 20:04:47 GMT 2019: Did not know how to handle GETTIME
    Mon Mar 18 20:04:47 GMT 2019: Parsing URL http://viv.ebay.com/ws/eBayISAPI.dll?EbayTime
    Mon Mar 18 20:04:47 GMT 2019: Time delta with ebay.co.uk is 10514
    Mon Mar 18 20:04:57 GMT 2019: [Show Time Info]

  • Dodgy Geezer

    Dodgy Geezer March 18th, 2019 @ 01:45 PM

    Seems that there is an issue with time - either just on my machine, or in the software. The system will accept a synchronise command after I have rebooted, but it seems to connect randomly at about 1.5 secs slow. Resynchronising just alters the time randomly...

    Mon Mar 18 20:40:16 GMT 2019: Last 10 from addEntry: 0, 0, 0, 0, 16, 0, 0, 0, 0, 0 Mon Mar 18 20:40:17 GMT 2019: Scripting is enabled.
    Mon Mar 18 20:40:20 GMT 2019: Parsing URL http://viv.ebay.com/ws/eBayISAPI.dll?EbayTime
    Mon Mar 18 20:40:21 GMT 2019: Time delta with ebay.co.uk is -1475
    Mon Mar 18 20:40:22 GMT 2019: Getting the sign in cookie for ebay.co.uk
    Mon Mar 18 20:40:22 GMT 2019: Parsing URL https://signin.ebay.co.uk/ws2/eBayISAPI.dll?SignIn
    Mon Mar 18 20:40:22 GMT 2019: Parsing URL https://signin.ebay.co.uk/ws/eBayISAPI.dll?co_partnerId=2&sitei...
    Mon Mar 18 20:40:24 GMT 2019: Done getting the sign in cookie for ebay.co.uk
    Mon Mar 18 20:40:28 GMT 2019: Parsing URL http://www.jbidwatcher.com/jbidwatcher2.xml
    Mon Mar 18 20:40:32 GMT 2019: [Show Time Info]
    Mon Mar 18 20:40:34 GMT 2019: [Resync]
    Mon Mar 18 20:40:34 GMT 2019: Did not know how to handle GETTIME
    Mon Mar 18 20:40:34 GMT 2019: Parsing URL http://viv.ebay.com/ws/eBayISAPI.dll?EbayTime
    Mon Mar 18 20:40:35 GMT 2019: Time delta with ebay.co.uk is -1022
    Mon Mar 18 20:40:46 GMT 2019: [Show Time Info]
    Mon Mar 18 20:40:54 GMT 2019: [View Activity]
    Mon Mar 18 20:41:00 GMT 2019: [View Activity]
    Mon Mar 18 20:41:06 GMT 2019: [View Log]
    Mon Mar 18 20:41:28 GMT 2019: [Show Time Info]
    Mon Mar 18 20:41:30 GMT 2019: [Resync]
    Mon Mar 18 20:41:30 GMT 2019: Did not know how to handle GETTIME
    Mon Mar 18 20:41:30 GMT 2019: Parsing URL http://viv.ebay.com/ws/eBayISAPI.dll?EbayTime
    Mon Mar 18 20:41:31 GMT 2019: Time delta with ebay.co.uk is -1363
    Mon Mar 18 20:41:38 GMT 2019: [Show Time Info]

  • Dodgy Geezer

    Dodgy Geezer March 20th, 2019 @ 04:10 AM

    It now looks as if the time delta can wander quite a lot if Jbidwatcher is left on on my machine. The synchronisation command changes the time, but does not reset it to zero. Instead, it sets it to a figure usually between 1 and 2 seconds out. if I leave it on the synchronisation will change - often getting worse. I assume that occasionally it exceeds my snipe time, upon which I miss a snipe.

    I note that the error log contains the message "Did not know how to handle GETTIME". Does this mean that the Jbidwatcher time command has a problem?

  • Dodgy Geezer

    Dodgy Geezer March 21st, 2019 @ 01:07 AM

    I used to use Time.NIST.Gov for my computer and the synchronisation was always between 1-2 seconds out - sometimes much more. And it varied a lot.

    I have just changed to time-a.nist.gov, and immediately the time difference has dropped to sub 1 second levels. Looks as if this could be a problem with external time data?

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Shared Ticket Bins

People watching this ticket

Attachments

Pages