But if due to the SD problems (read only) sudo apt-get update can't write the updates in the SD, the error 404 automatically remains ..... don't you think it can work like this ?
But if due to the SD problems (read only) sudo apt-get update can't write the updates in the SD, the error 404 automatically remains ..... don't you think it can work like this ?
-- Roby
You can get 404 errors when doing an apt command with a very poor WiFi connection.
I've now got so many Pi's they need to be treated like a herd rather then pets, so I have scripts to simultaneously run commands on all of them. When using this to do a update there is so much WiFi traffic the Raspberry Pi in the shed at the bottom of the garden throws 404s. If I go back and kick it off manually, it succeeds, albeit slowly.
It only has a standard RPi WiFi dongle, I'll probably upgrade it to one with a large antenna, like the one I use for video streaming in the Family room. Although that is inside the house, its was in a complete dead zone as far as a standard dongle was concerned, but the one with the antenna has a better signal than the RPi3B's built in WiFi 15ft from the router.
---druck
On 2019 Mar 26 09:26:20, you wrote to Andy Burns:
Ro> Initially I also thought it was like that, but I'm not an expert on Ro> RPI3....
this is not specific to the RPi at all... you'd get the same on any other OS in the same situation...
)\/(ark
Always Mount a Scratch Monkey Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong... ... Don't Drink and Park; accidents cause people.
No. 404 means the server couldnt find what your pi asked it for, or whatever is masquerading as the server. It didnt mean the pi got it and failed to write it.
You can look in /var/log to see what if any other errors there are.
As I said last post the pi dioesnt store the update file list in itself either, it stores only what repostiories to check. Once it gets to the repository it downloads a list of all the files to itself and tries to download them one by one. For some reason its downloading a list of files some of which are not on the server. My guess is a stale cache in a transparent proxy.
i,e, there is a hierarchy
go to server download master list of listts download each list...but some lists in the master list of lists are apparently not on the server.
Except to other pis, they are?
What is unique to this pi?
Its internet connection is via a mobile signal.
Hpw could that make a difference?
Mobile ISPs masquerade IPs and use just a few ip addresses but that should NOT be an issue
Moble IP may cache web pages to avoid using huge amounts of internet bandwidth. Its shoddy but some do.
If the cache isnt well configured it might cache old data.
*shrug* my best guess.-- ?A leader is best When people barely know he exists. Of a good leader, who talks little,When his work is done, his aim fulfilled,They will say, ?We did this ourselves.? ? Lao Tzu, Tao Te Ching
On 2019 Mar 26 19:14:34, you wrote to q7bbjj$c3c$ snipped-for-privacy@dont-email.me:
IA> and see what happens, but I expect another 404. But, I just read that IA> https is not cachable, so maybe
it is cacheable if there's a MitM setup in place... i'm aware of many such setups specifically to protect the network from infestations if a nasty is attempted to be downloaded...
)\/(ark
Always Mount a Scratch Monkey Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong... ... The dough stops here.
Let me jump into the thread here, and let me be blunt ...
we *know* it can't work like that.
The 404 error is 100% certainly the server saying "I haven't got the file you asked for". It's possible you do have a faulty SD card, but it's impossible for your SD card (faulty or not) to cause a 404 error.
Thank you @Andy Burns for saying your opinion .... but from how you write it seems to be technically verified ... Initially I also thought it was like that, but I'm not an expert on RPI3.... Then I did various tests and I asked for advice (in this newsgroup) to people who have more experience than me with the RPI (... or at least it is assumed to be so ....) and having failed to find the reasons for the problems I stopped at the 'faulty SD' speech .... and some people shared it ... At this point, only when I go to the remote site will I be able to understand what happened (.. I hope). Surely the first thing I will do is replace the SD with a clone that I had prepared when the system worked well ... Thank you
-- Roby
In article (Dans l'article) , The Natural
i.e. the HTTP server
-- Jean-Pierre Kuypers
In article (Dans l'article) , mark lewis wrote
Please, set just BEFORE your signature a line with only:
--
i.e. hyphen hyphens space
Thanks
-- Jean-Pierre Kuypers
I think your assessment that some sort of ISP caching is a good one, since apt-get update is simply asking for the Packages file from
which we all know exists.
The OP might want to try from the pi account
wget \
and see what happens, but I expect another 404. But, I just read that https is not cachable, so maybe
wget \
might be just the trick to see if there is some caching going on.
-- Consulting Minister for Consultants, DNRC I can please only one person per day. Today is not your day. Tomorrow isn't looking good, either. I am BOFH. Resistance is futile. Your network will be assimilated.
@mark lewis one thing is certainly true .... He who does not understand your silence will probably not understand your words (Elbert Hubbard)
-- Roby
I tried: wget \
The result is this: wget \
--2017-06-24 01:48:41--
With https the result is this: wget \
--2017-06-24 01:44:18--
What do you think about it ?
-- Roby
As for your advice, I'm considering using an HD or SSD instead of SD Can you tell me please:
- what kind of HD did you use ? A 2.5" SATA3 with USB adapter ?
- brand, model, capacity ? WD ? Are all brands good ?
- the RPI3 USB port is not capable of powering HD, is it true ? The HD must have its own power supply, right ?....or powered USB hub...
What do you think if I install a Western Digital WDS120G2G0A Green SSD, or SanDisk Plus SSD 120G, or Crucial etc. Does the RPI3's USB port supply an SSD directly ?... or maybe even in this case a powered USB hub is recommended...
What do you think about it ? Thank you
-- Roby
I got a Seagate 1TB external 2.5" hdd for ?50, usb-powered by the 3B+ Pi without problem, that's with the RPi official 2.5A adapter. WD is fine, too, I'm sure (or some will say better). You can set "max_usb_current=1" in /boot/config.txt to double the available power via usb, but that wasn't necessary for me.
Mark, can you put a proper sig separator in your postings, please?
Dave
On Tue, 26 Mar 2019 21:07:54 +0100, Roby declaimed the following:
It appears that archive.raspberrypi.org is not a single host...
C:\Users\Wulfraed>ping archive.raspberrypi.org -4
Pinging lb.raspberrypi.org [93.93.130.104] with 32 bytes of data: Reply from 93.93.130.104: bytes=32 time=113ms TTL=48 Reply from 93.93.130.104: bytes=32 time=113ms TTL=48 Reply from 93.93.130.104: bytes=32 time=113ms TTL=48 Reply from 93.93.130.104: bytes=32 time=113ms TTL=48
Ping statistics for 93.93.130.104: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 113ms, Maximum = 113ms, Average = 113ms
C:\Users\Wulfraed>
yet...
pi-star@pi-star-3b(ro):~$ sudo ping archive.raspberrypi.org PING lb.raspberrypi.org (46.235.227.11) 56(84) bytes of data.
64 bytes from 46.235.227.11: icmp_seq=1 ttl=48 time=119 ms 64 bytes from 46.235.227.11: icmp_seq=2 ttl=48 time=116 ms 64 bytes from 46.235.227.11: icmp_seq=3 ttl=48 time=120 ms 64 bytes from 46.235.227.11: icmp_seq=4 ttl=48 time=123 ms 64 bytes from 46.235.227.11: icmp_seq=5 ttl=48 time=122 ms 64 bytes from 46.235.227.11: icmp_seq=6 ttl=48 time=120 ms 64 bytes from 46.235.227.11: icmp_seq=7 ttl=48 time=122 ms 64 bytes from 46.235.227.11: icmp_seq=8 ttl=48 time=121 ms ^C--- lb.raspberrypi.org ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 9959ms rtt min/avg/max/mdev = 116.215/120.671/123.239/2.035 ms pi-star@pi-star-3b(ro):~$ sudo ping archive.raspberrypi.org PING lb.raspberrypi.org (93.93.128.133) 56(84) bytes of data. 64 bytes from 93.93.128.133: icmp_seq=1 ttl=52 time=117 ms 64 bytes from 93.93.128.133: icmp_seq=2 ttl=52 time=112 ms 64 bytes from 93.93.128.133: icmp_seq=3 ttl=52 time=113 ms ^ZThat makes THREE IP# that are considered "archive.raspberrypi.org" -- not counting the one you are reaching.
pi-star@pi-star-3b(ro):~$ host archive.raspberrypi.org archive.raspberrypi.org is an alias for lb.raspberrypi.org. lb.raspberrypi.org has address 93.93.128.211 lb.raspberrypi.org has address 93.93.135.188 lb.raspberrypi.org has address 46.235.227.11 lb.raspberrypi.org has address 93.93.130.214 lb.raspberrypi.org has address 93.93.130.104 lb.raspberrypi.org has address 93.93.128.230 lb.raspberrypi.org has address 93.93.130.39 lb.raspberrypi.org has address 93.93.128.133 lb.raspberrypi.org has IPv6 address 2a00:1098:0:80:1000:13:0:6 lb.raspberrypi.org has IPv6 address 2a00:1098:0:80:1000:13:0:7 lb.raspberrypi.org has IPv6 address 2a00:1098:0:82:1000:13:0:9 lb.raspberrypi.org has IPv6 address 2a00:1098:0:82:1000:13:0:5 lb.raspberrypi.org has IPv6 address 2a00:1098:0:80:1000:13:0:5 lb.raspberrypi.org has IPv6 address 2a00:1098:0:82:1000:13:0:7 lb.raspberrypi.org has IPv6 address 2a00:1098:0:82:1000:13:0:6 lb.raspberrypi.org has IPv6 address 2a00:1098:0:80:1000:13:0:8 pi-star@pi-star-3b(ro):~$ host lb.raspberrypi.org lb.raspberrypi.org has address 93.93.128.230 lb.raspberrypi.org has address 46.235.227.11 lb.raspberrypi.org has address 93.93.135.188 lb.raspberrypi.org has address 93.93.130.104 lb.raspberrypi.org has address 93.93.130.214 lb.raspberrypi.org has address 93.93.130.39 lb.raspberrypi.org has address 93.93.128.211 lb.raspberrypi.org has address 93.93.128.133 lb.raspberrypi.org has IPv6 address 2a00:1098:0:80:1000:13:0:7 lb.raspberrypi.org has IPv6 address 2a00:1098:0:80:1000:13:0:6 lb.raspberrypi.org has IPv6 address 2a00:1098:0:82:1000:13:0:7 lb.raspberrypi.org has IPv6 address 2a00:1098:0:80:1000:13:0:5 lb.raspberrypi.org has IPv6 address 2a00:1098:0:80:1000:13:0:8 lb.raspberrypi.org has IPv6 address 2a00:1098:0:82:1000:13:0:6 lb.raspberrypi.org has IPv6 address 2a00:1098:0:82:1000:13:0:9 lb.raspberrypi.org has IPv6 address 2a00:1098:0:82:1000:13:0:5 pi-star@pi-star-3b(ro):~$
Total of 8 IP #s with no promise of which will be reached. Either your remote node is always hitting a host that is misconfigured compared to the others... or something strange is going on and your requests are being rerouted to some third-party spoofing the IP.
-- Wulfraed Dennis Lee Bieber AF6VN wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/
I actually suggested he do that, but not all packages are accessible via https..
-- "Socialist governments traditionally do make a financial mess. They always run out of other people's money. It's quite a characteristic of them" Margaret Thatcher
BBS practices v.s. usenet practices, often ends in tears ...
These are my results: pi@MyPi:~ $ sudo ping archive.raspberrypi.org PING lb.raspberrypi.org (46.235.227.11) 56(84) bytes of data.
64 bytes from 46.235.227.11: icmp_seq=1 ttl=45 time=46.3 ms 64 bytes from 46.235.227.11: icmp_seq=2 ttl=45 time=62.3 ms 64 bytes from 46.235.227.11: icmp_seq=3 ttl=45 time=59.3 ms 64 bytes from 46.235.227.11: icmp_seq=4 ttl=45 time=59.3 ms 64 bytes from 46.235.227.11: icmp_seq=5 ttl=45 time=60.1 ms 64 bytes from 46.235.227.11: icmp_seq=6 ttl=45 time=56.3 ms 64 bytes from 46.235.227.11: icmp_seq=7 ttl=45 time=55.3 ms 64 bytes from 46.235.227.11: icmp_seq=8 ttl=45 time=62.5 ms ^C--- lb.raspberrypi.org ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7010ms rtt min/avg/max/mdev = 46.363/57.724/62.546/4.910 mspi@MyPi:~ $ host archive.raspberrypi.org archive.raspberrypi.org is an alias for lb.raspberrypi.org. lb.raspberrypi.org has address 93.93.130.104 lb.raspberrypi.org has address 93.93.128.133 lb.raspberrypi.org has address 46.235.227.11 lb.raspberrypi.org has address 93.93.128.230 lb.raspberrypi.org has address 93.93.135.188 lb.raspberrypi.org has address 93.93.128.211 lb.raspberrypi.org has address 93.93.130.214 lb.raspberrypi.org has address 93.93.130.39 lb.raspberrypi.org has IPv6 address 2a00:1098:0:80:1000:13:0:7 lb.raspberrypi.org has IPv6 address 2a00:1098:0:82:1000:13:0:9 lb.raspberrypi.org has IPv6 address 2a00:1098:0:80:1000:13:0:5 lb.raspberrypi.org has IPv6 address 2a00:1098:0:82:1000:13:0:5 lb.raspberrypi.org has IPv6 address 2a00:1098:0:82:1000:13:0:6 lb.raspberrypi.org has IPv6 address 2a00:1098:0:80:1000:13:0:8 lb.raspberrypi.org has IPv6 address 2a00:1098:0:82:1000:13:0:7 lb.raspberrypi.org has IPv6 address 2a00:1098:0:80:1000:13:0:6
pi@MyPi:~ $ host lb.raspberrypi.org lb.raspberrypi.org has address 93.93.130.39 lb.raspberrypi.org has address 93.93.130.104 lb.raspberrypi.org has address 93.93.130.214 lb.raspberrypi.org has address 46.235.227.11 lb.raspberrypi.org has address 93.93.135.188 lb.raspberrypi.org has address 93.93.128.211 lb.raspberrypi.org has address 93.93.128.230 lb.raspberrypi.org has address 93.93.128.133 lb.raspberrypi.org has IPv6 address 2a00:1098:0:82:1000:13:0:6 lb.raspberrypi.org has IPv6 address 2a00:1098:0:80:1000:13:0:7 lb.raspberrypi.org has IPv6 address 2a00:1098:0:82:1000:13:0:7 lb.raspberrypi.org has IPv6 address 2a00:1098:0:80:1000:13:0:5 lb.raspberrypi.org has IPv6 address 2a00:1098:0:82:1000:13:0:9 lb.raspberrypi.org has IPv6 address 2a00:1098:0:80:1000:13:0:6 lb.raspberrypi.org has IPv6 address 2a00:1098:0:80:1000:13:0:8 lb.raspberrypi.org has IPv6 address 2a00:1098:0:82:1000:13:0:5
-- Roby
Thanks @A.Dumas for the info But from the site
Did I misunderstand or did you connect your Seagate 1TB directly to one of the RPI's USB ports ?? I don't understand your phrase: "usb-powered by the 3B + Pi without problem" What is '3B + Pi' ? It is a USB-SATA adapter with independent external power supply ? Thank you
-- Roby
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.