starred/whoogle-search

Fork 0

mirror of https://github.com/benbusby/whoogle-search.git synced 2026-04-26 12:45:48 +03:00

[GH-ISSUE #272] Whoogle search has a permanent unhealty status in Portainer #184

New issue

Closed

opened 2026-02-25 20:35:07 +03:00 by kerem · 10 comments

kerem commented

2026-02-25 20:35:07 +03:00

Owner

Originally created by @wiebereu on GitHub (Apr 8, 2021).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/272

Since a couple of days after an update of the image i notice that the Whoogle container has a unhealty status in Portainer.
I search the log and i found this kind of error messages:

INFO:stem:Error while receiving a control message (SocketClosed): received exception "peek of closed file",
DEBUG:stem:GETCONF __owningcontrollerprocess (runtime: 0.0005),
INFO:stem:Error while receiving a control message (SocketClosed): received exception "read of closed file",
DEBUG:stem:GETCONF __owningcontrollerprocess (runtime: 0.0004),
INFO:stem:Error while receiving a control message (SocketClosed): received exception "[Errno 9] Bad file descriptor",
DEBUG:stem:GETCONF __owningcontrollerprocess (runtime: 0.0004),
INFO:stem:Error while receiving a control message (SocketClosed): received exception "[Errno 9] Bad file descriptor",
INFO:stem:Error while receiving a control message (SocketClosed): received exception "peek of closed file",

I tried to fix it by pulling the image again but to no avail. You can reach the container though. The only thing is the unhealty statys and the error messages.
I am running Docker on a Synology NAS.

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Deployment Method

Heroku (one-click deploy)
Docker
run executable
pip/pipx
Other: [describe setup]

Version of Whoogle Search

Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc)
Version [version number]
Not sure

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Originally created by @wiebereu on GitHub (Apr 8, 2021). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/272 Since a couple of days after an update of the image i notice that the Whoogle container has a unhealty status in Portainer. I search the log and i found this kind of error messages: **INFO:stem:Error while receiving a control message (SocketClosed): received exception "peek of closed file", DEBUG:stem:GETCONF __owningcontrollerprocess (runtime: 0.0005), INFO:stem:Error while receiving a control message (SocketClosed): received exception "read of closed file", DEBUG:stem:GETCONF __owningcontrollerprocess (runtime: 0.0004), INFO:stem:Error while receiving a control message (SocketClosed): received exception "[Errno 9] Bad file descriptor", DEBUG:stem:GETCONF __owningcontrollerprocess (runtime: 0.0004), INFO:stem:Error while receiving a control message (SocketClosed): received exception "[Errno 9] Bad file descriptor", INFO:stem:Error while receiving a control message (SocketClosed): received exception "peek of closed file",** I tried to fix it by pulling the image again but to no avail. You can reach the container though. The only thing is the unhealty statys and the error messages. I am running Docker on a Synology NAS. **Describe the bug** A clear and concise description of what the bug is. **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **Deployment Method** - [ ] Heroku (one-click deploy) - [ ] Docker - [ ] `run` executable - [ ] pip/pipx - [ ] Other: [describe setup] **Version of Whoogle Search** - [ ] Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc) - [ ] Version [version number] - [ ] Not sure **Desktop (please complete the following information):** - OS: [e.g. iOS] - Browser [e.g. chrome, safari] - Version [e.g. 22] **Smartphone (please complete the following information):** - Device: [e.g. iPhone6] - OS: [e.g. iOS8.1] - Browser [e.g. stock browser, safari] - Version [e.g. 22] **Additional context** Add any other context about the problem here.

kerem

2026-02-25 20:35:07 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 20:35:07 +03:00

Author

Owner

@benbusby commented on GitHub (Apr 9, 2021):

Which image are you using? I just pushed a change to latest and beta that should disable the error messages you were seeing. Can you try pulling the latest image to see if that helps?

@benbusby commented on GitHub (Apr 9, 2021): Which image are you using? I just pushed a change to `latest` and `beta` that should disable the error messages you were seeing. Can you try pulling the latest image to see if that helps?

kerem commented

2026-02-25 20:35:07 +03:00

Author

Owner

@wiebereu commented on GitHub (Apr 9, 2021):

I will try it and i will let you know of the results

@wiebereu commented on GitHub (Apr 9, 2021): I will try it and i will let you know of the results

kerem commented

2026-02-25 20:35:07 +03:00

Author

Owner

@wiebereu commented on GitHub (Apr 9, 2021):

I pulled the latest release and i don't see the error messages anymore in the log but the container stays unhealthy.
this is the information from the logs:

Starting tor daemon...done.
Serving on http://0.0.0.0:5000

I hope you don't suppress the error messages but that the problem was actually solved, cause disabling is not the same as solving.

@wiebereu commented on GitHub (Apr 9, 2021): I pulled the latest release and i don't see the error messages anymore in the log but the container stays unhealthy. this is the information from the logs: **Starting tor daemon...done. Serving on http://0.0.0.0:5000** I hope you don't suppress the error messages but that the problem was actually solved, cause disabling is not the same as solving.

kerem commented

2026-02-25 20:35:07 +03:00

Author

Owner

@benbusby commented on GitHub (Apr 9, 2021):

Well duh. I disabled the error messages from the stem library because they're overly verbose and aren't indicative of an actual problem. They've been around since Tor was integrated into the project, and have never shown to be linked to any errors. I got tired of users sending me the error logs over email, GitHub issues, etc and having to explain this every time, so now they're gone.

I'll look into why you're still seeing the unhealthy message. I can't replicate in my own Portainer environment, so I'll have to try something else later.

@benbusby commented on GitHub (Apr 9, 2021): Well duh. I disabled the error messages from the stem library because they're overly verbose and aren't indicative of an actual problem. They've been around since Tor was integrated into the project, and have never shown to be linked to any errors. I got tired of users sending me the error logs over email, GitHub issues, etc and having to explain this every time, so now they're gone. I'll look into why you're still seeing the unhealthy message. I can't replicate in my own Portainer environment, so I'll have to try something else later.

kerem commented

2026-02-25 20:35:07 +03:00

Author

Owner

@s3rverro0m commented on GitHub (Apr 10, 2021):

FWIW, I too get an "unhealthy" status every time. I even went as far as cloning your git repo and running docker-compose on it to make sure it wasn't my yaml, and I'm still seeing "unhealthy". Logs don't show much either.

@s3rverro0m commented on GitHub (Apr 10, 2021): FWIW, I too get an "unhealthy" status every time. I even went as far as cloning your git repo and running docker-compose on it to make sure it wasn't my yaml, and I'm still seeing "unhealthy". Logs don't show much either.

kerem commented

2026-02-25 20:35:07 +03:00

Author

Owner

@benbusby commented on GitHub (Apr 10, 2021):

Can either of you try running:

docker inspect --format "{{json .State.Health }}" <container name>

@benbusby commented on GitHub (Apr 10, 2021): Can either of you try running: ``` docker inspect --format "{{json .State.Health }}" <container name> ```

kerem commented

2026-02-25 20:35:07 +03:00

Author

Owner

@s3rverro0m commented on GitHub (Apr 10, 2021):

Sure, here is mine:

{"Status":"unhealthy","FailingStreak":3,"Log":[{"Start":"2021-04-09T20:25:54.697077194-07:00","End":"2021-04-09T20:25:55.383872137-07:00","ExitCode":1,"Output":"index.html: Permission denied\nCannot write to ‘index.html’ (Permission denied).\n"},{"Start":"2021-04-09T20:26:25.885549387-07:00","End":"2021-04-09T20:26:26.116638293-07:00","ExitCode":1,"Output":"index.html: Permission denied\nCannot write to ‘index.html’ (Permission denied).\n"},{"Start":"2021-04-09T20:26:56.71000216-07:00","End":"2021-04-09T20:26:56.923652082-07:00","ExitCode":1,"Output":"index.html: Permission denied\nCannot write to ‘index.html’ (Permission denied).\n"}]}

@s3rverro0m commented on GitHub (Apr 10, 2021): Sure, here is mine: ``` {"Status":"unhealthy","FailingStreak":3,"Log":[{"Start":"2021-04-09T20:25:54.697077194-07:00","End":"2021-04-09T20:25:55.383872137-07:00","ExitCode":1,"Output":"index.html: Permission denied\nCannot write to ‘index.html’ (Permission denied).\n"},{"Start":"2021-04-09T20:26:25.885549387-07:00","End":"2021-04-09T20:26:26.116638293-07:00","ExitCode":1,"Output":"index.html: Permission denied\nCannot write to ‘index.html’ (Permission denied).\n"},{"Start":"2021-04-09T20:26:56.71000216-07:00","End":"2021-04-09T20:26:56.923652082-07:00","ExitCode":1,"Output":"index.html: Permission denied\nCannot write to ‘index.html’ (Permission denied).\n"}]} ```

kerem commented

2026-02-25 20:35:07 +03:00

Author

Owner

@benbusby commented on GitHub (Apr 10, 2021):

Thanks, that's super helpful. I'll push a fix shortly.

@benbusby commented on GitHub (Apr 10, 2021): Thanks, that's super helpful. I'll push a fix shortly.

kerem commented

2026-02-25 20:35:07 +03:00

Author

Owner

@benbusby commented on GitHub (Apr 10, 2021):

Should be fixed in the latest and beta images once the build finishes.

@benbusby commented on GitHub (Apr 10, 2021): Should be fixed in the `latest` and `beta` images once the build finishes.

kerem commented

2026-02-25 20:35:07 +03:00

Author

Owner

@wiebereu commented on GitHub (Apr 12, 2021):

Thank you! I'm looking forward to it.

@wiebereu commented on GitHub (Apr 12, 2021): Thank you! I'm looking forward to it.