delivery-slot-bot
delivery-slot-bot copied to clipboard
net::ERR_NETWORK_CHANGED
Hi,
Finally got this running on Raspberry Pi thanks to Paul's help - and managed to book a slot after running for about 12 hours - so thank you!
Noticed however that every 4 or 5 runs i'm getting the following error message:-
net::ERR_NETWORK_CHANGED at https://www.tesco.com/groceries/en-GB/slots/collection/.......
Does this point towards a local issue with my internet connection or is it something else? Not noticing any interruption to other devices connected to my wifi when this happens
Glad to hear you got it all work! I've not seen that error before though. It looks like Chrome had some issue with your local network connection..
Thanks Paul - any idea how I would go about investigating that? I'm currently running it every 5 minutes on the cron job thing and it's pretty much giving this error every 2nd run now - Cheers!
Try running a continuous ping on another screen to see if there is any packet loss on the network when the errors occur e.g.
% ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=54 time=23.638 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=23.020 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=27.376 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=54 time=17.943 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=54 time=23.483 ms
<snip>
^C
--- 8.8.8.8 ping statistics ---
28 packets transmitted, 28 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 16.022/25.910/47.368/6.926 ms
Leave it running until you've seen the error occur, then let us know the packet loss statistics.
Thanks Paul,
It seems to have calmed down since I last posted, but still popping up infrequently
Here is the packet loss statistics from earlier today
--- 8.8.8.8 ping statistics --- 4082 packets transmitted, 4079 received, 0.0734934% packet loss, time 4109ms rtt min/avg/max/mdev = 15.325/28.859/342.452/14.023 ms
Thanks!
ps your bot has helped quite a number of people in our mutual aid group get slots - so thank you from us all!
Just done another one, and after one error it didn't show any packet loss at all?
--- 8.8.8.8 ping statistics --- 208 packets transmitted, 208 received, 0% packet loss, time 519ms rtt min/avg/max/mdev = 16.497/29.315/221.133/19.847 ms
If you could try to get a ping going in the background before and during an error occurring that would be helpful to see if packet loss is the cause.
Glad to hear it's helping your aid group!
Thanks Paul will do!
Hi - this ping data was from a recent error, showing no packet loss when the error occurred
6 packets transmitted, 6 received, 0% packet loss, time 13ms rtt min/avg/max/mdev = 19.501/30.831/36.811/5.776 ms
The error message was
Opening https://www.tesco.com/groceries/en-GB/slots/collection/2020-05-22?locationId=7466&slotGroup=1 [May 22 - 28] net::ERR_NETWORK_CHANGED at https://www.tesco.com/groceries/en-GB/slots/collection/2020-05-22?locationId=7466&slotGroup=1