Pi-hole hangs when failed to update lists

Is it normal that Pi-hole hangs when it gets no update list from a server ?

I had this several times now.
Pi-Hole is waiting for the update and does not respond any more.

I need to login with SSH and do a manual reboot.
Or cut power...........


Getting raw.githubusercontent.com list... done
::: Status: Success (OK)
::: List updated, transport successful!
::: Getting mirror1.malwaredomains.com list... done
::: Status: Not modified
::: No changes detected, transport skipped!
::: Getting sysctl.org list... done
::: Status: Not modified
::: No changes detected, transport skipped!
::: Getting zeustracker.abuse.ch list... done
::: Status: Not modified
::: No changes detected, transport skipped!
::: Getting s3.amazonaws.com list...

When you run

pihole -g

via SSH, do you get a more detailed error message?

It might just be a long timeout waiting for details from the list server.
It looks like curl doesn't have a default timeout as long as the connection succeeds: Does curl have a timeout? - Unix & Linux Stack Exchange

Here (on Debian) it stops trying to connect after 2 minutes [...] although the default connect timeout value seems to be 5 minutes according to the DEFAULT_CONNECT_TIMEOUT macro in lib/connect.h.
...
A default value for --max-time doesn't seem to exist, making curl wait forever for a response if the initial connect succeeds.

I use the web interface for update and there are no errors, it just hangs.
I waited for 5 minutes without success.
Then the Pi-hole is no longer accessible thru the interface.

I had this problem only 2 times.

Is there no failsafe for timeouts ?

Well, there is a failsafe, but maybe you have found a special install or situation where it is not able to catch the error properly. Please run the command

pihole -g

via SSH if you can reproduce the failure.

3 posts were split to a new topic: Hangs while updating lists