-
-
Notifications
You must be signed in to change notification settings - Fork 501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VirtualHere does not install on DietPi #3492
Comments
Hi, many thanks for report. Pls can you check your local internet connection and/or DNS server setting because you are not able to resolve host name for |
DNS is working fine. Internet connection is ok too. I do not have PiHole and I can reach raspbian.raspberrypi.org form my router/gateway as well as form Raspebrry Pi itself (see messages below) `PING mirrordirector.raspbian.org (93.93.128.193): 56 data bytes --- mirrordirector.raspbian.org ping statistics --- `root@DietPi:~# nslookup raspbian.raspberrypi.org Non-authoritative answer: root@DietPi:~# ping raspbian.raspberrypi.org |
pls try to run your software installation again. Maybe it was a temp issue to resolve |
I already did try (several trimes). Same result |
and you still get |
Sometimes I get:
Other times i get: In both cases, immediately after the error I can ping raspbian.raspberrypi.org. As a matter of fact, during the installation attempt I have another PC in the same subnet pinging raspbian.raspberrypi.org continuously, with no flaws |
ok at least the issue with resolving the host name is gone. Do you have the possibility to connect your SBC to another network? Could be |
I have two internet connections at my gateway. Here it is what I have done: |
A test that closer matches APT btw is:
or
ping uses ICMP protocol while APT connects via HTTP. wget or curl can be used to test this connection/procotol explicitly.
That is strange, since
So the initial setup was to have a local network gateway at one ISP and the SBC connected outside the local network directly to the gateway on the other ISP? |
@lhrique |
It is not the way I see it. dietpi-software has not been able to update/upgrade even outside local network |
Well dietpi is doing nothing else than calling apt-get same way as it would be running on CLI. But I guess @MichaIng could comment on this better than I |
That is strange, since as Joulinar said,
So the initial setup was to have a local network gateway at one ISP and the SBC connected outside the local network directly to the gateway on the other ISP? |
Gentlemen, I cannot explain why apt-get does not work well when called by dietpi-software. My setup comprises one local network attached to a gateway with two internet connections in load-balance/failover. I have only connected the SBC outside the gateway to try to implement a suggestion you have made. Now, it is back to where it should be (behind the gateway). Yesterday, I flashed dietpi again and started configuration from scratch. Once again, I experienced difficulties using dietpi-software to update/upgrade and install virtualhere -- tasks that I accomplished via CLI. |
@lhrique
|
Here it is the result of g_AGUP: `root@DietPi:~# G_AGUP root@DietPi:~# ping mirror.ox.ac.uk |
But, after some minutes, result was different... `root@DietPi:~# G_AGUP root@DietPi: |
I think so. However feel free to reopen if you face this issue again. |
Details:
Steps to reproduce:
Expected behaviour:
Actual behaviour:
Extra details:
Additional logs:
The text was updated successfully, but these errors were encountered: