Hello,
I am having the same kind of problems I guess. Every minute or so the plugin restarts. I can see this in the logs.
This is the last log I could copy:
[ INFO ] DSMR release: v4.19.0
[ INFO ] Removing existing PID files...
[ INFO ] Creating log directory...
[ INFO ] Setting architecture requirements...
[ INFO ] X64 Architecture
[ INFO ] Enabling IFrame...
[ INFO ] Fixing /dev/ttyUSB* security...
chmod: /dev/ttyUSB0: Read-only file system
[ INFO ] Verifying if the DSMR web credential variables have been set...
[ INFO ] Verifying database connectivity to host: 77b2833f-timescaledb with port: 5432...
[ INFO ] Database connectivity successfully verified!
[ INFO ] Running post configuration...
Operations to perform:
Apply all migrations: admin, auth, contenttypes, dsmr_api, dsmr_backend, dsmr_backup, dsmr_consumption, dsmr_datalogger, dsmr_dropbox, dsmr_frontend, dsmr_influxdb, dsmr_mindergas, dsmr_mqtt, dsmr_notification, dsmr_pvoutput, dsmr_stats, dsmr_weather, sessions
Running migrations:
No migrations to apply.
563 static files copied to '/var/www/dsmrreader/static'.
Updating password of superuser "XXXXXX"
Deactivating any other existing superusers
[ INFO ] Checking for NGINX SSL configuration...
[ INFO ] ENABLE_NGINX_SSL is disabled, nothing to see here. Continuing...
[ INFO ] Checking for HTTP AUTHENTICATION configuration...
[ INFO ] ENABLE_HTTP_AUTH is disabled, nothing to see here. Continuing...
[ INFO ] Configuring DSMR in standlone datalogger mode....
[ INFO ] Starting supervisord...
[ INFO ] Logfiles can be found at: /var/log/supervisor/*.log and /tmp/supervisord.log
2022-01-11 11:22:02,946 INFO Set uid to user 0 succeeded
2022-01-11 11:22:02,946 INFO Set uid to user 0 succeeded
2022-01-11 11:22:02,958 INFO RPC interface 'supervisor' initialized
2022-01-11 11:22:02,958 INFO RPC interface 'supervisor' initialized
2022-01-11 11:22:02,959 INFO supervisord started with pid 35
2022-01-11 11:22:02,959 INFO supervisord started with pid 35
2022-01-11 11:22:03,964 INFO spawned: 'processes' with pid 37
2022-01-11 11:22:03,964 INFO spawned: 'processes' with pid 37
2022-01-11 11:22:03,969 INFO spawned: 'dsmr_backend' with pid 38
2022-01-11 11:22:03,969 INFO spawned: 'dsmr_backend' with pid 38
2022-01-11 11:22:03,976 INFO spawned: 'dsmr_datalogger' with pid 39
2022-01-11 11:22:03,976 INFO spawned: 'dsmr_datalogger' with pid 39
2022-01-11 11:22:03,984 INFO spawned: 'dsmr_webinterface' with pid 40
2022-01-11 11:22:03,984 INFO spawned: 'dsmr_webinterface' with pid 40
2022-01-11 11:22:03,991 INFO spawned: 'nginx' with pid 41
2022-01-11 11:22:03,991 INFO spawned: 'nginx' with pid 41
[2022-01-11 11:22:04 +0100] [40] [INFO] Starting gunicorn 20.1.0
[2022-01-11 11:22:04 +0100] [40] [INFO] Listening at: unix:/var/tmp/gunicorn--dsmr_webinterface.socket (40)
[2022-01-11 11:22:04 +0100] [40] [INFO] Using worker: sync
[2022-01-11 11:22:04 +0100] [46] [INFO] Booting worker with pid: 46
2022-01-11 11:22:05,611 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-11 11:22:05,611 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-11 11:22:05,613 INFO success: dsmr_backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-11 11:22:05,613 INFO success: dsmr_backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-11 11:22:05,615 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-11 11:22:05,615 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Current logging level set to "ERROR". More information can be found here: https://dsmr-reader.readthedocs.io/en/latest/how-to/troubleshooting/enabling-debug-logging.html
Current logging level set to "ERROR". More information can be found here: https://dsmr-reader.readthedocs.io/en/latest/how-to/troubleshooting/enabling-debug-logging.html
2022-01-11 11:22:07,140 INFO success: dsmr_webinterface entered RUNNING state, process has stayed up for > than 3 seconds (startsecs)
2022-01-11 11:22:07,140 INFO success: dsmr_webinterface entered RUNNING state, process has stayed up for > than 3 seconds (startsecs)
2022-01-11 11:22:09,143 INFO success: nginx entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2022-01-11 11:22:09,143 INFO success: nginx entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2022-01-11 11:26:24,611 ERROR mixins run_once 103 | dsmr_datalogger.management.commands.dsmr_datalogger: [!] Exception raised. Traceback (most recent call last):
File "/dsmr/dsmr_backend/mixins.py", line 92, in run_once
self.run(data=self.data, **options)
File "/dsmr/dsmr_datalogger/management/commands/dsmr_datalogger.py", line 29, in run
telegram = next(self.telegram_generator)
File "/dsmr/dsmr_datalogger/scripts/dsmr_datalogger_api_client.py", line 50, in read_telegram
incoming_bytes = serial_handle.read(MAX_BYTES_PER_READ)
File "/usr/local/lib/python3.10/site-packages/serial/serialposix.py", line 595, in read
raise SerialException(
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2022-01-11 11:26:29,855 INFO exited: dsmr_datalogger (exit status 0; expected)
2022-01-11 11:26:29,855 INFO exited: dsmr_datalogger (exit status 0; expected)
2022-01-11 11:26:30,860 INFO spawned: 'dsmr_datalogger' with pid 47
2022-01-11 11:26:30,860 INFO spawned: 'dsmr_datalogger' with pid 47
2022-01-11 11:26:30,862 WARN received SIGQUIT indicating exit request
2022-01-11 11:26:30,862 WARN received SIGQUIT indicating exit request
2022-01-11 11:26:30,863 INFO waiting for processes, dsmr_backend, dsmr_datalogger, dsmr_webinterface, nginx to die
2022-01-11 11:26:30,863 INFO waiting for processes, dsmr_backend, dsmr_datalogger, dsmr_webinterface, nginx to die
2022-01-11 11:26:30,880 INFO stopped: nginx (exit status 0)
2022-01-11 11:26:30,880 INFO stopped: nginx (exit status 0)
[2022-01-11 11:26:30 +0100] [40] [INFO] Handling signal: term
[2022-01-11 11:26:30 +0100] [46] [INFO] Worker exiting (pid: 46)
[2022-01-11 11:26:31 +0100] [40] [INFO] Shutting down: Master
2022-01-11 11:26:32,253 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-11 11:26:32,253 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-11 11:26:32,255 INFO stopped: dsmr_webinterface (exit status 0)
2022-01-11 11:26:32,255 INFO stopped: dsmr_webinterface (exit status 0)
Current logging level set to "ERROR". More information can be found here: https://dsmr-reader.readthedocs.io/en/latest/how-to/troubleshooting/enabling-debug-logging.html2022-01-11 11:26:32,379 INFO stopped: dsmr_datalogger (terminated by SIGTERM)
2022-01-11 11:26:32,379 INFO stopped: dsmr_datalogger (terminated by SIGTERM)
2022-01-11 11:26:33,626 INFO stopped: dsmr_backend (exit status 0)
2022-01-11 11:26:33,626 INFO stopped: dsmr_backend (exit status 0)
2022-01-11 11:26:33,627 INFO stopped: processes (terminated by SIGTERM)
2022-01-11 11:26:33,627 INFO stopped: processes (terminated by SIGTERM)
This is my TimescaleDB config:
databases:
- homeassistant
- dsmrreader
timescale_enabled:
- homeassistant
- dsmrreader
timescaledb:
telemetry: basic
maxmemory: 512MB
maxcpus: '4'
max_connections: 20
system_packages: []
init_commands: []
(A side question: does the dsmrreader database need timescale enabled?)
Does anyone know what is going on and how I can fix this??