Restart mrss-web results in mrss-web getting stuck #1

New issue

Griefed · 2026-06-26T12:32:45+02:00

Griefed commented

2026-06-26 12:32:45 +02:00

@Griefed on GitLab · https://git.griefed.de/Griefed/MonitoRSS-Clone/-/issues/3

What is the current behavior?

After restarting mrss-web, the container gets stuckt at

INFO : [-] MonitoRSS-Web logged in as REDACTED

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

Start mrss as per the deploy example. After deployment and verification that mrss works, restart mrss-web and see that the container gets stuck

What is the expected behavior?

mrss-web restarting without issues and the webinterface being available

What is the motivation / use case for changing the behavior?

That it works, lol.

Please tell us about your environment:
- Docker Image: griefed/monitorss-clone
- docker & docker-compose Version:

Client: Docker Engine - Community
 Version:           20.10.2
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        2291f61
 Built:             Mon Dec 28 16:17:43 2020
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.2
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       8891c58
  Built:            Mon Dec 28 16:15:19 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.3
  GitCommit:        269548fa27e0089a8b8278fc4fc781d7f65a939b
 runc:
  Version:          1.0.0-rc92
  GitCommit:        ff819c7e9184c13b7c2607fe6c30ae19403a7aff
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
docker-compose version 1.25.0, build unknown
docker-py version: 4.1.0
CPython version: 3.8.5
OpenSSL version: OpenSSL 1.1.1f  31 Mar 2020

> **@Griefed** on **GitLab** · https://git.griefed.de/Griefed/MonitoRSS-Clone/-/issues/3 * **What is the current behavior?** After restarting mrss-web, the container gets stuckt at > INFO : [-] MonitoRSS-Web logged in as REDACTED * **If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem** Start mrss as per the deploy example. After deployment and verification that mrss works, restart mrss-web and see that the container gets stuck * **What is the expected behavior?** mrss-web restarting without issues and the webinterface being available * **What is the motivation / use case for changing the behavior?** That it works, lol. * **Please tell us about your environment:** - Docker Image: griefed/monitorss-clone - docker & docker-compose Version: ``` Client: Docker Engine - Community Version: 20.10.2 API version: 1.41 Go version: go1.13.15 Git commit: 2291f61 Built: Mon Dec 28 16:17:43 2020 OS/Arch: linux/amd64 Context: default Experimental: true Server: Docker Engine - Community Engine: Version: 20.10.2 API version: 1.41 (minimum version 1.12) Go version: go1.13.15 Git commit: 8891c58 Built: Mon Dec 28 16:15:19 2020 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.4.3 GitCommit: 269548fa27e0089a8b8278fc4fc781d7f65a939b runc: Version: 1.0.0-rc92 GitCommit: ff819c7e9184c13b7c2607fe6c30ae19403a7aff docker-init: Version: 0.19.0 GitCommit: de40ad0 docker-compose version 1.25.0, build unknown docker-py version: 4.1.0 CPython version: 3.8.5 OpenSSL version: OpenSSL 1.1.1f 31 Mar 2020 ```

Griefed closed this issue

2026-06-26 12:32:45 +02:00

Griefed commented

2026-06-26 12:32:46 +02:00

@Griefed on GitLab

Appears to be database related, though it is still unsure whether it is actually a problem with the databse (doubtful) or rather a problem with the way mrss-web is setup.
Will run tests regarding the configuration.

> **@Griefed** on **GitLab** Appears to be database related, though it is still unsure whether it is actually a problem with the databse (doubtful) or rather a problem with the way mrss-web is setup. Will run tests regarding the configuration.

Griefed commented

2026-06-26 12:32:46 +02:00

@Griefed on GitLab

Related to Discord's rate limit and not a bug of MRSS or this docker container. Tests showed that either waiting a not-specified amount of time and/or restarts of mrss-bot-web result in the webinterface being available again.
See https://github.com/synzen/MonitoRSS-Clone/issues/19#issuecomment-770311044

Nethertheless, I've made changes to the way this container works. Configs are no longer being written to file, saving volumes. Expanded the variables for the container. Example uses bot-web.

> **@Griefed** on **GitLab** Related to Discord's rate limit and not a bug of MRSS or this docker container. Tests showed that either waiting a not-specified amount of time and/or restarts of mrss-bot-web result in the webinterface being available again. See https://github.com/synzen/MonitoRSS-Clone/issues/19#issuecomment-770311044 Nethertheless, I've made changes to the way this container works. Configs are no longer being written to file, saving volumes. Expanded the variables for the container. Example uses bot-web.

Sign in to join this conversation.