Starting issues

[mononym]

Hello. After the update to 1.13.2 the app is hanging during startup:
(Repeatedly)

Dec 29 11:21:31 2024-12-29 10:21:31.416 | INFO | __main__:stats_thread_func:320 - Connections: Active count 0 of max 10, Total processed: 0.
Dec 29 11:21:31 2024-12-29 10:21:31.417 | INFO | __main__:stats_thread_func:325 - Memory: Used 85.2% (Limit 90%) - Available 136.1MB.

Restoring the backup throws the same error.

Memory issues ?

[robi]

Have you tried bumping up the memory limit in the App config?

[nebulon]

As @robi suggested, this may just be a memory issue. Also check the system memory itself, the limit for apps is only a upper limit, but not related to the actually available memory on the system as a whole.

[mononym]

Augmenting the memory from 2GB to 5GB does not solve the issue. Still looping with these messages:

Dec 30 12:14:39 2024-12-30 11:14:39.597 | INFO | __main__:stats_thread_func:320 - Connections: Active count 0 of max 10, Total processed: 0.
Dec 30 12:14:39 2024-12-30 11:14:39.598 | INFO | __main__:stats_thread_func:325 - Memory: Used 70.8% (Limit 90%) - Available 557.0MB.

[nebulon]

Is a fresh installation of the app starting up fine? I just did a test install and that at least worked, also a fresh old version updated to the latest works. Maybe there is some data migration issue in your case?

[mononym]

@nebulon said in Starting issues:

Is a fresh installation of the app starting up fine?

A fresh installation has exactly the same issues in the starting sequence.

Dec 30 14:56:25 154.28.229.125,172.18.0.1 - - [30/Dec/2024 13:56:25] "GET /login%3Fnext%3D/ HTTP/1.1" 404 405 0.002353
Dec 30 14:56:25 2024-12-30 13:56:25.980 | INFO | __main__:stats_thread_func:320 - Connections: Active count 0 of max 10, Total processed: 0.
Dec 30 14:56:25 2024-12-30 13:56:25.981 | INFO | __main__:stats_thread_func:325 - Memory: Used 78.2% (Limit 90%) - Available 324.7MB.
Dec 30 14:56:26 (49) accepted ('172.18.0.1', 51802)
Dec 30 14:56:26 154.28.229.125,172.18.0.1 - - [30/Dec/2024 13:56:26] "GET /static/js/csrf.js HTTP/1.1" 200 689 0.015858
Dec 30 14:56:35 2024-12-30 13:56:35.989 | INFO | __main__:stats_thread_func:320 - Connections: Active count 0 of max 10, Total processed: 0.
Dec 30 14:56:35 2024-12-30 13:56:35.989 | INFO | __main__:stats_thread_func:325 - Memory: Used 78.3% (Limit 90%) - Available 318.7MB.

[nebulon]

that is indeed odd, and you have checked the system does not run out of memory?

[mononym]

@nebulon said in Starting issues:

you have checked the system does not run out of memory?

There's no notification or other indication that the system is running out of memory.

[nebulon]

And there are no further error logs or anything around the restarting?

Unfortunately the app is already defaulting to logleven DEBUG for what its worth.

Can you maybe put the app in recovery mode from the repair tab i your cloudron dashboard and then open a webterminal, where you run /app/pkg/start.sh manually? Does this reveal more?

[mononym]

The app seems to start normally. And starts the checking of the watched websites until this point:

[...]
2024-12-30 21:29:31.529 | INFO     | changedetectionio.store:__init__:93 - Tag: c23a2ba5-4b69-4c79-a999-75f9046ad745 events
2024-12-30 21:29:31.530 | INFO     | changedetectionio.store:sync_to_json:384 - Saving JSON..
(46) wsgi starting up on http://0.0.0.0:5000
2024-12-30 21:29:31.667 | DEBUG    | changedetectionio.flask_app:ticker_thread_check_time_launch_checks:1766 - System env MINIMUM_SECONDS_RECHECK_TIME 3
2024-12-30 21:29:40.633 | INFO     | __main__:stats_thread_func:320 - Connections: Active count 0 of max 10, Total processed: 0.
2024-12-30 21:29:40.633 | INFO     | __main__:stats_thread_func:325 - Memory: Used 84.4% (Limit 90%) - Available 125.8MB.
[...]
(46) accepted ('172.18.0.1', 59538)
2024-12-30 21:31:52.623 | DEBUG    | changedetectionio.model.Watch:history:188 - Reading watch history index for ffed72ab-b794-4480-8fe5-386f93606401
[...]
2024-12-30 21:31:53.162 | DEBUG    | changedetectionio.model.Watch:history:188 - Reading watch history index for 72e8402e-aec7-413a-be65-352e1ac71608
172.18.20.151,172.18.0.1 - - [30/Dec/2024 21:31:53] "GET /rss?token=a241cfb4fe6a2db2dbe59b627b3299c3 HTTP/1.1" 200 22333 0.575938
(46) accepted ('172.18.0.1', 59552)
172.18.20.151,172.18.0.1 - - [30/Dec/2024 21:31:53] "GET / HTTP/1.1" 302 610 0.002872
(46) accepted ('172.18.0.1', 59560)
172.18.20.151,172.18.0.1 - - [30/Dec/2024 21:31:53] "GET / HTTP/1.1" 302 610 0.002134
2024-12-30 21:32:00.767 | INFO     | __main__:stats_thread_func:320 - Connections: Active count 0 of max 10, Total processed: 0.
2024-12-30 21:32:00.768 | INFO     | __main__:stats_thread_func:325 - Memory: Used 85.4% (Limit 90%) - Available 124.8MB.
[...]

[mononym]

Waited for the night and a reboot of the server did the trick. Could even scale the memory back to 2Gb

[nebulon]

Hm very strange, but sometimes things just get stuck without apparent reason and a reboot skips some lengthy investigation...glad it worked out in the end for now!