search

alaudet / raspi-sump

A sump pump monitoring system using Python and Raspberry Pi
https://www.linuxnorth.org/raspi-sump/
MIT License
92 stars 36 forks source link

Problem starting systemd after upgrade #81

Closed nickw56 closed 1 year ago

nickw56 commented 1 year ago

Failed to reload daemon: Process org.freedesktop.systemd1 exited with status 1 pi@raspberrypi:~ $ systemctl --user start raspisump Failed to start raspisump.service: Process org.freedesktop.systemd1 exited with status 1 See user logs and 'systemctl --user status raspisump.service' for details. pi@raspberrypi:~ $ systemctl --user restart raspisump Failed to restart raspisump.service: Process org.freedesktop.systemd1 exited with status 1 See user logs and 'systemctl --user status raspisump.service' for details.

nickw56 commented 1 year ago

I get the above errors when trying to start the upgraded raspi-sump. Any help gratefully received

nickw56 commented 1 year ago

did a reboot and it now seems to be working ok

nickw56 commented 1 year ago

except the chart is not working! here's the status message I am getting

pi@raspberrypi:~ $ systemctl --user status rsumpwebchart.timer ● rsumpwebchart.timer - RaspiSump Webchart Timer Loaded: loaded (/home/pi/.config/systemd/user/rsumpwebchart.timer; enabled; vendor preset: enabled Active: inactive (dead) Trigger: n/a

alaudet commented 1 year ago

are you able to run rsumpwebchart.py manually? Do you get errors?

Just type rsumpwebchart.py then check /home/pi/raspi-sump/charts for today.png

Also check /home/pi/raspi-sump/charts/2023/07 to see if it has charts in it.

Also what version are running. 

cat /home/pi/raspi-sump/VERSION
nickw56 commented 1 year ago

Several reboots later the chart is now working but there's another problem. The measurement interval is set in the conf file to 300 seconds (5 mins) but what I am seeing in the CSV file does not reflect this: the interval seems to vary between a few seconds up to a few minutes

20:56:45,5.9 20:56:54,5.6 20:57:01,6.2 20:57:08,6.2 20:57:16,6.3 20:57:24,6.1 20:57:32,6.7 20:57:40,6.7 20:57:47,6.8 20:57:55,6.5 20:58:02,6.8 20:58:09,7.1 20:58:16,7.2 20:58:23,7.1 20:58:30,6.9 20:58:36,7.1 20:58:44,7.4 20:58:51,7.6 20:58:58,7.4 20:59:05,7.6

nickw56 commented 1 year ago

Hi Al, I am running 1.9.2 on Bullseye. I got the chart working last night but nothing was running this morning. Does raspisump start automatically on a re-boot ? If not how can I make this happen? Also still having a problem with erratic measurement intervals.

alaudet commented 1 year ago

Are your crontab entries still active?

what does crontab -l return?

Also please provide the output of

systemctl --user status raspisump

and

systemctl --user status rsumpwebchart.timer

nickw56 commented 1 year ago

When I do a reboot I am getting an error message "No session for pid 890" but this may be related to the upgrade from buster to bullseye that I did before I upgraded raspisump to 1.9.2.

alaudet commented 1 year ago

it still sounds to me like you have remnants of your old install in crontab mixed in with systemd. Can you post the output of the commands I gave you in the previous message?

nickw56 commented 1 year ago

Hi Al

Are your crontab entries still active? No

what does crontab -l return?

here's the last few lines:

m h dom mon dow command

/5 * /usr/local/bin/rsump.py

59 /usr/local/bin/rsumpwebchart.py

Also please provide the output of

systemctl --user status raspisump

and

systemctl --user status rsumpwebchart.timer

@.:~ $ systemctl --user status raspisump ● raspisump.service - RaspiSump Service Loaded: loaded (/home/pi/.config/systemd/user/raspisump.service; enabled; ven Active: active (running) since Mon 2023-07-31 17:18:21 BST; 5s ago Main PID: 11391 (rsump.py) CGroup: @./raspisump.service └─11391 /usr/bin/python3 /usr/local/bin/rsump.py

Jul 31 17:18:21 raspberrypi systemd[692]: Started RaspiSump Service.

@.***:~ $ systemctl --user status rsumpwebchart.timer ● rsumpwebchart.timer - RaspiSump Webchart Timer Loaded: loaded (/home/pi/.config/systemd/user/rsumpwebchart.timer; enabled; v Active: active (waiting) since Mon 2023-07-31 13:50:27 BST; 3h 28min ago Trigger: Mon 2023-07-31 17:30:00 BST; 10min left

Warning: Journal has been rotated since unit was started. Log output is incomple lines 1-6/6 (END) Best regards

Nick m: 07771 994175

On Mon, 31 Jul 2023 at 16:23, Al Audet @.***> wrote:

Are your crontab entries still active?

what does crontab -l return?

Also please provide the output of

systemctl --user status raspisump

and

systemctl --user status rsumpwebchart.timer

— Reply to this email directly, view it on GitHub https://github.com/alaudet/raspi-sump/issues/81#issuecomment-1658592259, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJBUUJPGXDZKHAUKTTBLFQLXS7EWDANCNFSM6AAAAAA25KXKFM . You are receiving this because you authored the thread.Message ID: @.***>

alaudet commented 1 year ago

When it generates a reading every few seconds it indicates that rsump.py is starting, stopping and then systemd tries to restart the service. (over and over)

Are issues still present?

You wouldnt happen to have an old entry on /etc/rc.local that initiates rsump.py on startup of the pi would you?

Also the commands to make sure raspisump and rsumpwebchart.timer work on reboot are the following

systemctl --user enable raspisump systemctl --user enable rsumpwebchart.timer

But it looks to me like they are already enabled from your output.

nickw56 commented 1 year ago

Hi Al

Are your crontab entries still active? No

what does crontab -l return?

here's the last few lines:

m h dom mon dow command

/5 * /usr/local/bin/rsump.py

59 /usr/local/bin/rsumpwebchart.py

Also please provide the output of

systemctl --user status raspisump

and

systemctl --user status rsumpwebchart.timer

pi@raspberrypi:~ $ systemctl --user status raspisump ● raspisump.service - RaspiSump Service Loaded: loaded (/home/pi/.config/systemd/user/raspisump.service; enabled; ven Active: active (running) since Mon 2023-07-31 17:18:21 BST; 5s ago Main PID: 11391 (rsump.py) CGroup: /user.slice/user-1000.slice/user@1000.service/raspisump.service └─11391 /usr/bin/python3 /usr/local/bin/rsump.py

Jul 31 17:18:21 raspberrypi systemd[692]: Started RaspiSump Service.

pi@raspberrypi:~ $ systemctl --user status rsumpwebchart.timer ● rsumpwebchart.timer - RaspiSump Webchart Timer Loaded: loaded (/home/pi/.config/systemd/user/rsumpwebchart.timer; enabled; v Active: active (waiting) since Mon 2023-07-31 13:50:27 BST; 3h 28min ago Trigger: Mon 2023-07-31 17:30:00 BST; 10min left

Warning: Journal has been rotated since unit was started. Log output is incomple lines 1-6/6 (END)

nickw56 commented 1 year ago

Hi Al,

Nothing in rc.local - see below

rc.local

#

This script is executed at the end of each multiuser runlevel.

Make sure that the script will "exit 0" on success or any other

value on error.

#

In order to enable or disable this script just change the execution

bits.

#

By default this script does nothing.

Print the IP address

_IP=$(hostname -I) || true if [ "$_IP" ]; then printf "My IP address is %s\n" "$_IP"

Its been running fine all day, but problem is that rusump.py is running 4 or 5 times a minute when in the config file its set to runn every 300 secs - not a huge issue but a bit puzzling. Also noticed that I have raspisump.conf and a raspisump.conf.save file - is this intentional? I assume I could delete the .save version?

alaudet commented 1 year ago

ok

can we just recap quickly

What is working? What is not working?

nickw56 commented 1 year ago

Hi Al

Sump and chart.timer are both working fine. The remaining issue is the measurement interval. That is set to 300 secs in config but actually running every 15 seconds or so.

Thanks for your help

Best regards

Nick m: 07771 994175

On Mon, 31 Jul 2023 at 20:05, Al Audet @.***> wrote:

ok

can we just recap quickly

What is working? What is not working?

— Reply to this email directly, view it on GitHub https://github.com/alaudet/raspi-sump/issues/81#issuecomment-1658977911, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJBUUJOK7MRXLFR4232DQHTXS76ZPANCNFSM6AAAAAA25KXKFM . You are receiving this because you authored the thread.Message ID: @.***>

alaudet commented 1 year ago

ok let me test this on my end.

alaudet commented 1 year ago

In the meantime, can you upgrade to my latest development snapshot? I have included a troublshooting utility to better help me analyse the environment.

This will upgrade you to version 1.9.3rc1

To upgrade run the following

sudo pip3 install -U --no-binary :all: https://github.com/alaudet/raspi-sump/archive/refs/heads/devel.zip

Then run the following command

rsumpsupport

This will create a file called support.txt in the /home/pi/raspi-sump/support folder.

Email me that file at alaudet@linuxnorth.org

You can actually view the contents of that file, there is no personal info in it. It's currently a work in progress for my next release but could be helpful here to diagnose issues.

nickw56 commented 1 year ago

OK I will do that upgrade and send you the file should I shut down raspisump and the chart timer first?

Best regards

Nick m: 07771 994175

On Mon, 31 Jul 2023 at 20:28, Al Audet @.***> wrote:

In the meantime, can you upgrade to my latest development snapshot? I have included a troublshooting utility to better help me analyse the environment.

This will upgrade you to version 1.9.3rc1

To upgrade run the following

sudo pip3 install -U --no-binary :all: https://github.com/alaudet/raspi-sump/archive/refs/heads/devel.zip

Then run the following command

rsumpsupport

This will create a file called support.txt in the /home/pi/raspi-sump/support folder.

Email me that file at @.***

You can actually view the contents of that file, there is no personal info in it. It's currently a work in progress for my next release but could be helpful here.

— Reply to this email directly, view it on GitHub https://github.com/alaudet/raspi-sump/issues/81#issuecomment-1659005581, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJBUUJLRL3QHZMVOWCCVQJDXTABMTANCNFSM6AAAAAA25KXKFM . You are receiving this because you authored the thread.Message ID: @.***>

alaudet commented 1 year ago

yes please shutdown the raspisump and rsumpwebchart.timer, upgrade then start again.

nickw56 commented 1 year ago

Hi Al

Upgrade done.Here's the content of the support.txt file.

Date file generated: 2023-07-31 21:18:55 os version: 10 raspi-sump version: Version 1.9.3rc1 python version on system: Python 3.7.3

Systemctl status for raspisump: ● raspisump.service - RaspiSump Service Loaded: loaded (/home/pi/.config/systemd/user/raspisump.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2023-07-31 21:18:50 BST; 5s ago Main PID: 24720 (rsump.py) CGroup: @.***/raspisump.service └─24720 /usr/bin/python3 /usr/local/bin/rsump.py

Jul 31 21:18:50 raspberrypi systemd[692]: Started RaspiSump Service.

Systemctl status for rsumpwebchart.timer: ● rsumpwebchart.timer - RaspiSump Webchart Timer Loaded: loaded (/home/pi/.config/systemd/user/rsumpwebchart.timer; enabled; vendor preset: enabled) Active: active (waiting) since Mon 2023-07-31 21:17:47 BST; 1min 8s ago Trigger: Mon 2023-07-31 21:30:00 BST; 11min left

Jul 31 21:17:47 raspberrypi systemd[692]: Started RaspiSump Webchart Timer.

Raspi-Sump Variables: critical_water_level: 10 pit_depth: 35 reading_interval: 300 temperature: 15 trig_pin: 17 echo_pin: 27 unit: metric smtp_tls: 1 smtp_ssl: 0 alert_when: high alert_interval: 5 heartbeat: 1 heartbeat_interval: 10080 line_color: FB921D

User Crontab:

Edit this file to introduce tasks to be run by cron.

#

Each task to run has to be defined through a single line

indicating with different fields when the task will be run

and what command to run for the task

#

To define the time you can provide concrete values for

minute (m), hour (h), day of month (dom), month (mon),

and day of week (dow) or use '*' in these fields (for 'any').

#

Notice that tasks will be started based on the cron's system

daemon's notion of time and timezones.

#

Output of the crontab jobs (including errors) is sent through

email to the user the crontab file belongs to (unless redirected).

#

For example, you can run a backup of all your user accounts

at 5 a.m every week with:

0 5 1 tar -zcf /var/backups/home.tgz /home/

#

For more information see the manual pages of crontab(5) and cron(8)

#

m h dom mon dow command

/5 * /usr/local/bin/rsump.py

59 /usr/local/bin/rsumpwebchart.py

Logs/error_log content: 2021-03-14 21:25:03,ERROR - Signal not received. Possible cable or sensor problem. 2021-03-16 00:50:04,ERROR - Signal not received. Possible cable or sensor problem. 2021-04-02 20:35:06,ERROR - Signal not received. Possible cable or sensor problem. 2021-04-02 23:20:04,ERROR - Signal not received. Possible cable or sensor problem. 2021-04-06 14:55:03,ERROR - Signal not received. Possible cable or sensor problem. 2021-05-03 09:10:05,ERROR - Signal not received. Possible cable or sensor problem. 2021-06-03 03:10:04,ERROR - Signal not received. Possible cable or sensor problem. 2021-06-08 22:05:04,ERROR - Signal not received. Possible cable or sensor problem. 2021-06-17 01:20:03,ERROR - Signal not received. Possible cable or sensor problem. 2021-07-03 20:20:04,ERROR - Signal not received. Possible cable or sensor problem. 2021-07-11 15:15:04,ERROR - Signal not received. Possible cable or sensor problem. 2021-07-12 13:00:03,ERROR - Signal not received. Possible cable or sensor problem. 2021-07-13 21:35:05,ERROR - Signal not received. Possible cable or sensor problem. 2021-07-30 03:30:03,ERROR - Signal not received. Possible cable or sensor problem. 2021-08-15 04:40:03,ERROR - Signal not received. Possible cable or sensor problem. 2021-08-15 11:50:06,ERROR - Signal not received. Possible cable or sensor problem. 2021-08-17 12:40:04,ERROR - Signal not received. Possible cable or sensor problem. 2021-10-18 21:50:04,ERROR - Signal not received. Possible cable or sensor problem. 2021-11-08 08:25:04,ERROR - Signal not received. Possible cable or sensor problem. 2021-11-18 01:10:04,ERROR - Signal not received. Possible cable or sensor problem. 2021-11-27 00:15:04,ERROR - Signal not received. Possible cable or sensor problem. 2022-01-19 06:55:04,ERROR - Signal not received. Possible cable or sensor problem. 2022-01-25 15:00:04,ERROR - Signal not received. Possible cable or sensor problem. 2022-02-10 20:15:05,ERROR - Signal not received. Possible cable or sensor problem. 2022-02-14 00:35:03,ERROR - Signal not received. Possible cable or sensor problem. 2022-04-05 16:40:06,ERROR - Signal not received. Possible cable or sensor problem. 2022-09-02 22:15:03,ERROR - Signal not received. Possible cable or sensor problem. 2022-09-07 10:15:04,ERROR - Signal not received. Possible cable or sensor problem. 2022-10-06 18:05:04,ERROR - Signal not received. Possible cable or sensor problem. 2022-12-05 09:25:04,ERROR - Signal not received. Possible cable or sensor problem. 2022-12-15 07:00:06,ERROR - Signal not received. Possible cable or sensor problem. 2023-01-23 04:25:04,ERROR - Signal not received. Possible cable or sensor problem. 2023-04-02 13:00:04,ERROR - Signal not received. Possible cable or sensor problem. 2023-07-01 11:30:05,ERROR - Signal not received. Possible cable or sensor problem. 2023-07-05 11:55:07,**ERROR - Signal not received. Possible cable or sensor problem. 2023-07-30 19:13:52,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-30 19:23:32,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-30 19:23:39,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-30 19:33:04,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-30 19:33:11,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-30 19:42:39,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-30 19:42:46,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-30 19:52:11,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-30 19:52:18,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-30 19:52:25,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-30 20:02:14,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-30 20:02:21,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-30 20:12:16,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-30 20:12:22,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-30 20:22:02,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-30 20:31:44,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-30 20:41:18,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-30 20:50:59,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 13:09:28,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 13:09:35,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 13:18:24,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 13:18:31,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 13:18:38,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 13:27:33,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 13:27:40,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 14:02:57,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 14:03:04,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 14:11:59,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 14:20:51,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 14:20:58,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 14:29:52,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 14:29:58,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 14:38:21,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 14:38:28,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 14:38:34,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 14:47:55,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 14:48:02,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 14:48:08,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 14:57:21,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 14:57:27,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 15:05:57,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 15:06:04,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 15:06:10,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 15:15:03,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 15:15:11,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 15:23:46,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 15:23:52,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 15:23:59,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 15:33:08,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 15:33:14,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 15:33:21,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 15:42:21,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 15:42:28,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 15:48:11,ERROR - Signal not received. Possible cable or sensor problem. 2023-07-31 15:50:53,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 15:50:59,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 16:00:01,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 16:09:02,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 16:09:09,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 16:17:59,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 16:18:06,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 16:26:53,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 16:27:00,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 16:35:37,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 16:35:43,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 16:44:34,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 16:44:41,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 16:53:17,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 16:53:24,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 17:02:05,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 17:02:12,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 17:10:54,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 17:19:09,ERROR - Signal not received. Possible cable or sensor problem. 2023-07-31 17:28:44,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 17:37:47,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 17:46:42,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 17:46:50,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 18:04:39,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 18:04:46,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 18:10:27,ERROR - Signal not received. Possible cable or sensor problem. 2023-07-31 18:22:20,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 18:22:27,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 18:31:23,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 18:31:30,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 18:40:27,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 18:49:54,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 18:50:01,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 18:50:08,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 18:59:13,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 18:59:19,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 19:08:14,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 19:08:21,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 19:08:27,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 19:17:33,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 19:26:15,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 19:26:21,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 19:35:18,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 19:35:24,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 19:35:31,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 19:44:50,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 19:44:56,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 19:45:03,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 19:54:56,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 19:55:03,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 19:55:09,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 20:04:36,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 20:04:42,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 20:13:46,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 20:13:53,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 20:23:18,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 20:23:25,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 20:23:31,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 20:32:35,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 20:32:42,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 20:41:53,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 20:42:00,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 20:42:06,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 20:51:16,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 20:54:08,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 20:54:15,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 20:57:07,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 20:57:14,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 20:57:20,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 21:00:17,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 21:00:26,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 21:00:36,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 21:03:38,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 21:03:45,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 21:03:51,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 21:06:41,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 21:06:48,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 21:09:39,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 21:09:46,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor. 2023-07-31 21:09:53,ERROR - Negative reading adjusted to 0.0. Possible degrading sensor.

Logs/info_log content: Error executing command: ['cat', '/home/pi/raspi-sump/logs/info_log']. Return code: 1. Output:

Last 10 lines of logs/heartbeat.log: 2022-04-02 01:15:08,Heartbeat Email Sent 2022-04-09 01:20:09,Heartbeat Email Sent 2022-04-16 01:25:08,Heartbeat Email Sent 2022-04-23 01:30:09,Heartbeat Email Sent 2022-04-30 01:35:08,Heartbeat Email Sent 2022-05-07 01:40:09,Heartbeat Email Sent 2022-05-14 01:45:08,Heartbeat Email Sent 2022-05-21 01:50:09,Heartbeat Email Sent 2022-05-28 01:55:09,Heartbeat Email Sent 2022-06-04 02:00:09,Heartbeat Email Sent

Last 10 lines of logs/alert.log:

Best regards

Nick m: 07771 994175

On Mon, 31 Jul 2023 at 20:28, Al Audet @.***> wrote:

In the meantime, can you upgrade to my latest development snapshot? I have included a troublshooting utility to better help me analyse the environment.

This will upgrade you to version 1.9.3rc1

To upgrade run the following

sudo pip3 install -U --no-binary :all: https://github.com/alaudet/raspi-sump/archive/refs/heads/devel.zip

Then run the following command

rsumpsupport

This will create a file called support.txt in the /home/pi/raspi-sump/support folder.

Email me that file at @.***

You can actually view the contents of that file, there is no personal info in it. It's currently a work in progress for my next release but could be helpful here.

— Reply to this email directly, view it on GitHub https://github.com/alaudet/raspi-sump/issues/81#issuecomment-1659005581, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJBUUJLRL3QHZMVOWCCVQJDXTABMTANCNFSM6AAAAAA25KXKFM . You are receiving this because you authored the thread.Message ID: @.***>

alaudet commented 1 year ago

Well for one thing you definitely seem to have a degrading sensor as you have multiple 0.0 readings in your error_log. I am starting to expect that the program is exiting sometimes due to the sensor and systemd tries to restart it right away. But that doesnt make sense for negative values which are adjusted to 0.0. You wouldnt happen to have a new sensor laying around? This one is definitely looking like it is starting to fail.

If that is the issue then I have an issue in the code as well that is not handling this right.

Would also like to see the output of

journalctl -u raspisump

If that is too long

journalctl -u raspisump -b

will only show messages since last boot.

nickw56 commented 1 year ago

Hi AlI will order a new sensor and try that but I doubt that’s the problem as it’s been working ok until now. In the meantime, thanks for all your excellent support.Best RegardsNickOn 31 Jul 2023, at 22:13, Al Audet @.***> wrote: Well for one thing you definitely seem to have a degrading sensor as you have multiple 0.0 readings in your error_log. I am starting to expect that the program is exiting sometimes due to the sensor and systemd tries to restart it right away. But that doesnt make sense for negative values which are adjusted to 0.0. You wouldnt happen to have a new sensor laying around? This one is definitely looking like it is starting to fail. If that is the issue then I have an issue in the code as well that is not handling this right.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

alaudet commented 1 year ago

ok Nick, I will leave the issue open until then. In the meantime you could revert to crontab for handling the readings

Just stop and disable the services and change your crontab back. As well change your reading_interval back to 0 in your raspisump.conf file.

Al

alaudet commented 1 year ago

Hi Nick checking in. We're you ever able to get it going properly?

nickw56 commented 1 year ago

Hi Al, I reverted to running both processes using a cron task and it seems fine.  I think I have a water leak somewhere in or near my property as the sump pump is currently going 5 or 6 times per hour meaning that I am pumping out about 60 - 75 litres per hour and have been for many weeks.  So I am not going to do any more tinkering with the monitoring system until I find the source. The guys at the utility company were impressed when I told them about raspi-sump.Best RegardsNickOn 24 Aug 2023, at 14:01, Al Audet @.***> wrote: Hi Nick checking in. We're you ever able to get it going properly?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

alaudet commented 1 year ago

Thats probably a good idea. I will close this issue and if you need help at some later time we can revisit. thanks.