Constant "crashing", force restart of container helps but eventually stops

[kzndotsh]

Describe the bug Basically notice all the time in Discord that the bot is down, I'll go into SSH, restart the container and it comes back up. Then eventually down again.

Logs Here is some docker logs where you will find the constant errors. I had the idea today to set a cronjob to restart doplarr every few hours as a bandaid but dont think that helped lol.

https://pastebin.com/9tfTnpEv

My current settings:

  discord_token: XXXXXXXXXXXXXX
  overseerr_url: "http://overseerr:5055"
  overseerr_api: XXXXXXXXXXXXXX
  radarr_api:
  radarr_url:
  sonarr_api:
  sonarr_url:
  discord_max_results: 25
  discord_role_id:
  discord_requested_msg_style: ":embed"
  sonarr_quality_profile:
  radarr_quality_profile:
  sonarr_language_profile:
  overseer_default_id: 19
  partial_seasons: "false"
  log_level: ":info"

[kiranshila]

Well that's a new one. It seems the bot is having trouble hitting the discord websocket servers. I'll have to chew on that one.

[inrush-overload]

+1 same issue going on here. Frequently it doesn't log anything though, just have a dead container that, according to logs, looks like it should still be running

[seanmcbroom]

Any updates on this? I am facing the same issue

[Franscobec]

I have the same exact issue. Container just dies. The bot stays online, but does not accept commands. I need to restart the container once every hour which is extremely annoying. It might not be exactly the same error as kaizensh's but it is the same issue. Here's some screenshots:

[inrush-overload]

Fyi if you're running in docker, you can just set it to restart unless stopped which has resolved the issue for me effectively. Every time it goes down it just fires right back up and you don't realize any appreciable service outage.

Looked like the crashes were due to discord being slow to respond (and the app being too sensitive to those slow responses) causing it to error out

On Tue, May 23, 2023, 8:23 AM Franscobec @.***> wrote:

I have the same exact issue. Container just dies. The bot stays online, but does not accept commands. I need to restart the container once every hour which is extremely annoying. It might not be exactly the same error as kaizensh's but it is the same issue. Here's some screenshots: [image: Screenshot_20230523_091826_Discord] https://user-images.githubusercontent.com/87747518/240292951-2baaa270-50c0-44cb-9ea5-6255ad3ab320.jpg [image: Screenshot_20230523_091840_Discord] https://user-images.githubusercontent.com/87747518/240292953-42c9ba76-0e44-44ab-8d75-5b2c4bb76975.jpg [image: Screenshot_20230523_092010_Samsung Internet] https://user-images.githubusercontent.com/87747518/240293443-6c50f370-4c5d-4d06-af75-f824c5dc1184.jpg [image: Screenshot_20230523_092029_Samsung Internet] https://user-images.githubusercontent.com/87747518/240293446-3b779dc9-4c92-449c-86a2-c0a6a56471d3.jpg

— Reply to this email directly, view it on GitHub https://github.com/kiranshila/Doplarr/issues/96#issuecomment-1559342881, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2WC4TZL4ZRF5X7WMCYAAWTXHS24TANCNFSM6AAAAAAQBU7VMQ . You are receiving this because you commented.Message ID: @.***>

[Franscobec]

Fyi if you're running in docker, you can just set it to restart unless stopped which has resolved the issue for me effectively. Every time it goes down it just fires right back up and you don't realize any appreciable service outage. Looked like the crashes were due to discord being slow to respond (and the app being too sensitive to those slow responses) causing it to error out

I do not have enough knowledge to do that, can you explain how I can do this ? BTW my OS is TrueNAS Scale 22.12.2

[inrush-overload]

Sorry bud, I'm not familiar enough with TrueNAS Scale to walk you through. Generally in Docker it will look like "--restart unless-stopped ", you might have to add that in the truenas UI someplace, probably the same place you define other command line arguments

On Tue, May 23, 2023 at 6:55 PM Franscobec @.***> wrote:

Fyi if you're running in docker, you can just set it to restart unless stopped which has resolved the issue for me effectively. Every time it goes down it just fires right back up and you don't realize any appreciable service outage. Looked like the crashes were due to discord being slow to respond (and the app being too sensitive to those slow responses) causing it to error out

I do not have enough knowledge to do that, can you explain how I can do this ? BTW my OS is TrueNAS Scale 22.12.2

— Reply to this email directly, view it on GitHub https://github.com/kiranshila/Doplarr/issues/96#issuecomment-1560269118, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2WC4T3UL2UC4J6E3BC3QP3XHVFAXANCNFSM6AAAAAAQBU7VMQ . You are receiving this because you commented.Message ID: @.***>

[MFaroTusino]

+1 This started happening for me this week after using this without issue since June 2022.