Closed CplPwnies closed 10 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Same here, in addition: the GeoIP.dat file looks empty:
root@f69205991f3c:/# ls -l /usr/share/GeoIP/
total 12
-rw-r--r-- 1 root root 8486 Dec 11 15:37 GeoIP.dat
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Why would it be stale when there is a pending PR to correct this issue?
This issue is locked due to inactivity
Is there an existing issue for this?
Current Behavior
When I view the docker logs for my container, I am constantly seeing the error:
Error Traversing Database for ipnum = NUMBER - Perhaps database is corrupt?
and due to this, none of the IPs viewed in the WebUI are able to to be geo-locatedExpected Behavior
No error, and IPs successfully geo-located in the WebUI
Steps To Reproduce
Run the latest
image: lscr.io/linuxserver/deluge:latest
Have it connect to peers and attempt to geo-locate
Environment
CPU architecture
x86-64
Docker creation
Container logs