Daxiongmao87
commented
2 weeks ago hey thank you for the issue report. i have seen those errors regarding maximum number of instances and mostly ignored them. ive had my instance up for weeks without issue.
ill delve into my logs and see if i see anything similar.
I am running the program in docker setup in the exact way that is laid out in the ReadMe. After the program has been running for a while, it seems to hang and the webpage becomes unresponsive/doesn't load. The error I get in the console is:
Execution of job "update_instance_statuses (trigger: interval[0:01:00], next run at: 2024-10-08 17:38:28 UTC)" skipped: maximum number of running instances reached (1)I have tried to debug the issue, but have come up empty handed. However, while trying things I discovered three more errors that may (or may not) be related.
There was an error managing chromedriver (error sending request for url (https://googlechromelabs.github.io/chrome-for-testing/last-known-good-versions-with-downloads.json)); using driver found in the cacheUnable to obtain driver for chrome; For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors/driver_locationMessage: Service /root/.cache/selenium/chromedriver/linux64/129.0.6668.89/chromedriver unexpectedly exited. Status code was: -5These errors go away for a while when I restart the application. As a duct tape solution I have setup a bash script to restart the program every 2 hours, but this not a permanent solution since the root cause seems to occur at random and still occurs within the 2 hour window.
I apologize if this is user error.
P.s. Thank you for the great application, it has made it so much easier to navigate my multiple campaigns. (even if i have to restart it every so often)