[GH-ISSUE #878] [QUESTION] Is there a way to view an event or status log? or maybe a debug mode? #547

New issue

Closed

opened 2026-02-25 20:36:00 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 20:36:00 +03:00

Owner

Originally created by @Jieiku on GitHub (Nov 4, 2022).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/878

Is there a way to view an event or status log? or maybe a debug mode?

I have installed whoogle into a proxmox lxc container, when I reboot the container no problem, but once I access the whoogle search page it goes to 100% usage, it still works, but 1 thread stays pegged at 100% usage, this was not always the case so I am not sure what happened, I have another install that does not do this, so I could technically clone that container to this location but I would like to find the cause if possible and just fix it.

I use haproxy as a reverse proxy with ssl termination, it forward the requests directly to the proxmox lxc container using the whoogle 5000 port.

For anyone curious, this is how I installed:

sudo apt install git python3 python3-venv
sudo reboot
sudo su
cd
git clone https://github.com/benbusby/whoogle-search.git
cd whoogle-search
git checkout tags/v0.7.1
cp whoogle.template.env whoogle.env
nano whoogle.env
WHOOGLE_CONFIG_URL=https://whoogle.example.com/
python3 -m venv venv
source venv/bin/activate
pip install wheel
pip install -r requirements.txt
./run

sudo nano /lib/systemd/system/whoogle.service

[Unit]
Description=Whoogle

[Service]
Environment=WHOOGLE_DOTENV=1
Type=simple
User=root
WorkingDirectory=/root/whoogle-search
ExecStart=/root/whoogle-search/venv/bin/python3 -um app --host 0.0.0.0 --port 5000
ExecReload=/bin/kill -HUP $MAINPID
Restart=always
RestartSec=3
SyslogIdentifier=whoogle

[Install]
WantedBy=multi-user.target

sudo systemctl start whoogle
sudo systemctl enable whoogle
sudo systemctl status whoogle

Originally created by @Jieiku on GitHub (Nov 4, 2022). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/878 Is there a way to view an event or status log? or maybe a debug mode? I have installed whoogle into a proxmox lxc container, when I reboot the container no problem, but once I access the whoogle search page it goes to 100% usage, it still works, but 1 thread stays pegged at 100% usage, this was not always the case so I am not sure what happened, I have another install that does not do this, so I could technically clone that container to this location but I would like to find the cause if possible and just fix it. ![2022-11-03_18-39-25](https://user-images.githubusercontent.com/106644/199867072-53348c87-9f68-414d-b8aa-b08cf7fc4ba2.png) I use haproxy as a reverse proxy with ssl termination, it forward the requests directly to the proxmox lxc container using the whoogle 5000 port. For anyone curious, this is how I installed: ```sh sudo apt install git python3 python3-venv sudo reboot sudo su cd git clone https://github.com/benbusby/whoogle-search.git cd whoogle-search git checkout tags/v0.7.1 cp whoogle.template.env whoogle.env nano whoogle.env WHOOGLE_CONFIG_URL=https://whoogle.example.com/ python3 -m venv venv source venv/bin/activate pip install wheel pip install -r requirements.txt ./run ``` ```sh sudo nano /lib/systemd/system/whoogle.service ``` ```ini [Unit] Description=Whoogle [Service] Environment=WHOOGLE_DOTENV=1 Type=simple User=root WorkingDirectory=/root/whoogle-search ExecStart=/root/whoogle-search/venv/bin/python3 -um app --host 0.0.0.0 --port 5000 ExecReload=/bin/kill -HUP $MAINPID Restart=always RestartSec=3 SyslogIdentifier=whoogle [Install] WantedBy=multi-user.target ``` ```sh sudo systemctl start whoogle sudo systemctl enable whoogle sudo systemctl status whoogle ```

kerem

2026-02-25 20:36:00 +03:00

closed this issue
added the
question

Stale
labels

kerem commented

2026-02-25 20:36:00 +03:00

Author

Owner

@Jieiku commented on GitHub (Nov 4, 2022):

hmmm I adjusted the haproxy ACL and now its no longer pegging out, would still like to know how to debug though incase it happens again.

@Jieiku commented on GitHub (Nov 4, 2022): hmmm I adjusted the haproxy ACL and now its no longer pegging out, would still like to know how to debug though incase it happens again.

kerem commented

2026-02-25 20:36:00 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 15, 2025):

This issue has been automatically marked as stale due to inactivity. If it is still valid please comment within 7 days or it will be auto-closed.

@github-actions[bot] commented on GitHub (Sep 15, 2025): This issue has been automatically marked as stale due to inactivity. If it is still valid please comment within 7 days or it will be auto-closed.

kerem commented

2026-02-25 20:36:00 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 23, 2025):

Closing this issue due to prolonged inactivity.

@github-actions[bot] commented on GitHub (Sep 23, 2025): Closing this issue due to prolonged inactivity.