Time out uploading images

There are probably about 3017 different AWS service types involved with uploading and launching an eBay auction (through their website) and it could be some or just one of those, sometimes.

Factor in that it could be one of the many data centers, or even a few servers that aren’t updated yet, and

¯\_(ツ)_/¯

I suspect sometimes when GarageSale gets an auction all the way listed but it doesn’t get the acknowledgment message back (so there’s a running sale with no attached database entry locally, and vice versa) that they may even have a self-contained API “confirmer” process that occasionally hiccups. I’m especially suspicious when it’s exactly 10 listings that fail this way, since that sure sounds like a “batch” on the server side, but it’s definitely not a GarageSale “batch” size.

Some ”serverless” web architecture implies “more servers than you can possibly imagine”, IME.

1 Like

Looks like the problem maybe ex-Australia.

Traceroute took 21 hops to get there and ping 563ms.

I have been on to Optus but I had to give up when after 30mins their networking expert asked what Unix was.

Is there anyone in Australia using this image server at the moment?

David

I will try again later.

Hi GS Team

Still having enormous difficulty listing. Optus were hopeless to deal with.

Can you please tell me where this error message is being generated?

traCEROUTE

mygateway (192.168.0.1) 0.810 ms 0.775 ms 0.368 ms ME

2 static-n220-239-24-1.per2.wa.optusnet.com.au (220.239.24.1) 12.232 ms 11.604 ms 11.927 ms

3 * * *

4 * * *

5 * * 124.19.61.25 (124.19.61.25) 62.803 ms PERTH 2 HOPS

6 * 22bt-c93-ig-02-net-lo0.optus.net.au (61.88.33.47) 60.909 ms * SYDNEY 1 HOP

7 203.208.131.65 (203.208.131.65) 218.578 ms

59.154.18.77 (59.154.18.77)  62.185 ms

203.208.131.65 (203.208.131.65)  218.505 ms

8 203.208.149.58 (203.208.149.58) 218.510 ms

203.208.143.197 (203.208.143.197)  208.297 ms  209.578 ms

9 203.208.172.233 (203.208.172.233) 219.376 ms

203.208.142.189 (203.208.142.189)  322.578 ms

203.208.171.117 (203.208.171.117)  206.748 ms

10 203.208.158.205 (203.208.158.205) 442.827 ms

203.208.158.9 (203.208.158.9)  411.194 ms

203.208.142.161 (203.208.142.161)  332.406 ms

11 203.208.178.205 (203.208.178.205) 430.952 ms

203.208.158.9 (203.208.158.9)  401.062 ms

203.208.158.10 (203.208.158.10)  416.176 ms

12 * * 203.208.151.38 (203.208.151.38) 427.065 ms SINGAPORE 16 HOPS

13 ae1-2014.nbg40.core-backbone.com (81.95.9.14) 390.947 ms GERMANY 8 HOPS

203.208.183.90 (203.208.183.90)  423.295 ms

ae1-2014.nbg40.core-backbone.com (81.95.9.14)  395.584 ms

14 core-backbone.hetzner.com (5.56.20.254) 392.967 ms 410.923 ms *

15 * 203.208.183.90 (203.208.183.90) 412.787 ms

ae1-2014.nbg40.core-backbone.com (81.95.9.14)  382.785 ms

16 * * *

17 core23.fsn1.hetzner.com (213.239.252.246) 407.378 ms

core21.fsn1.hetzner.com (213.239.254.217)  396.752 ms

core21.fsn1.hetzner.com (213.239.254.213)  405.515 ms

18 * * *

19 * * *

20 21278.your-cloud.host (162.55.115.150) 380.041 ms

www.iwascoding.com (91.107.219.165)  398.674 ms  393.004 ms

Telstra traceroute from amazon EC2 VM network shows similar speeds.

and

russells@(i2):~$ ping iwascoding.com
PING iwascoding.com (91.107.219.165) 56(84) bytes of data.
From www.iwascoding.com (91.107.219.165) icmp_seq=1 Destination Port Unreachable
From www.iwascoding.com (91.107.219.165) icmp_seq=2 Destination Port Unreachable

You should be pinging img.iwascoding.com.
iwascoding.com is a completely different machine, which might in a different data center.

There error is generated on you Mac, when the a network request is not acknowledged by the other party within a certain time period.

1 Like

Getting a local website setup to host your images seems like the best way to keep your listings able to be viewed by others in your country. Using a VPN based in Europe might help you upload the images but they will not be viewable by customers [in your own country] on your eBay listings.

Here is something else I have just noticed. My listings are loading ok if the listing type is BIN. It is the AUC type that is failing. I have no idea where the problem lies so I have attached a spindump. I hope you can find something meaningful in it for me. Corrupt Database (again)?

The image belows shows two launch control lists running simultaneously. The one on the left are BIN listings and the one on the right are AUC listings.

Spindump.txt (3.9 MB)

PS. I just want to add that all is not perfect with BIN items as well. I just thought running BIN and AUC in parallel might help narrow down the issue.

What happens when you use a VPN with a node based in Europe? Do you get a 100% upload rate then?

Thanks for the suggestions, Vince. I have used that method before.
What I want is for my ISP to fix the problem they have created. In all likelihood the collisions are occurring as my cable meets the fibre at the bottom of my driveway.

Report in .progress.

David

1 Like

I would imagine the issues affect more than just GS’ image server if the issue proves to be local? Another, possible solution, would be to update your DNS to use a public one like 9.9.9.9. Bypass your ISP’s DNS and see if that helps [it is easy to change and change back…just make note in Notes or Text Edit, the current DNS IP you use eg: cut and paste, and then put 9.9.9.9 into the DNS of your Mac or your router and run some ping tests to img.iwascoding.com

It probably is not the cause of your issues, since you were able to resolve www.iwascoding before - usually DNS will present itself with errors that say “unable to find host” or resolve host [eg DNS is like a phone book for the internet - it translates text you type into the numbers that the internet uses - for img.iwascoding.com, the IP address is 65.21.22.97. If your ISP’s DNS is not working right, then one can see slowness either because the DNS for a hostname is not resolving quickly, or because it is timing out, unable to know where to ping/upload/etc because it can’t retrieve the IP number of the server.

If you have issues with lag visiting US or European hosted websites, then yeah, I would start looking at something local - your ISP or their upstream provider. :frowning:

It took 15 days but eventually Optus listened to me and fixed the line. Now to catch up.

Thanks everyone who had suggestions or tried to help me.
Just goes to show that the basic messages used to test line speeds are useless when uploading large files. I constantly had an upload speed of 20mbs but could not upload anything

2 Likes

So glad they fixed it! One thing I’ve learned [at least in the US] is to not trust speed test websites as ISPs partner with them. I tend to use librespeed.org - no idea if this is an issue for Australia too

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.