The Natural Philosopher wrote:
> On 25/03/2019 15:14, Roby wrote:
>> If my hypothesis were correct (I can only verify the problem when I will
>> physically go to the remote site) it would mean for example that the 404
>> errors actually occur not because the file does not exist in the repository
>> but because the RPI3 cannot write to the SD card !!! In the remote RPI3 I
>> had inserted a Samsung MB-MP16D Evo and with the command def -h I see that
>> there are still 8 G free!
>>
>> Can my hypothesis be true ?
>
> I'd say not.
> You are getting tangled up in stuff you dont really undersatnd.
>
> error 404 is not something the Pi generates because it has run out of 'disk]
> or has something mounted read only (whichg mount would tell you anyway). It
> is something coming back from the remote server.
>
> Since we know that the remote server is OK, the inference is that it is in
> fact somethining between the Pi and the server.
>
> It cant be basic networking because you can obviously log into the pi.
>
> It cant be DNS because 404 is not 'I cant find the server; it is the server
> saying 'I cant find that file'
>>
> So we are left with a mal formed request because you have a corrupt database
> or a corrupt proxy, that you still havent checked
>
> With respect, if you want us to help, follow our damned instructions to the
> letter.

I acknowledge that you do not share my hypothesis and that in your
opinion 404 errors cannot be generated due to SD problems ...
I am available to make other checks .... but I don't know how ...
Can you write me what commands to type to check if there are corrupt
databases or a corrupt proxy?
To avoid problems I ask you to write me the exact syntax of the
commands, so that I can make a copy and paste ...
Thank you

--
Roby

--- SoupGate-Win32 v1.05