Can I borrow like $300?
Not super clear on what that is but its a standard Evo AIO tank.
www.reef2reef.com
Looking at the log CPU usage spiked right around the same time frame but didnt really climb or seem abnormal prior until I look at historical. Maybe I will upgrade the pi and do regular reboots... Running 4.1 btw. Will do some digging into logs tomorrow morning.Had a similar experience with my Reef-Pi but it was the calcium and I run a diluted solution and small reservoir so not much damage done. I searched a bit and there is at least 1 other instance in the build thread. I have only had this once and I was around when it was happening. I tried to SSH into the module at the time but it would not respond. I still run v4.1 I reboote the reef-pi and it has been fine since. I did notice my CPU and MEM use and pi CPU Temp creeping up prior. What ver are you running?
reef-pi :: An opensource reef tank controller based on Raspberry Pi.
I had ph interference from my light relays. I rerouted wires and moved the relays further from the ph board and ph become stable.
Tons of coralline and pretty high alk demand so I do have to dose atleast for alk/calcium. I have tried water change only but everything looked ticked off the last few days before a change and if I have a busy schedule then I am in real trouble.
Here is what my graph looked like. issue with the journctl and systemctl logs is that they do not persist across power boots by default so you may not seen any logs from that time it happened.
journalctl --since "2015-01-10 12:00" --until "2015-01-11 03:00"Hi - thanks for jumping in.
what happened during Mar 8-10. Something happened during that time which resulted into significantly higher cpu utilization (upwards of 2). That thing progressively got worse till it hit cpu limit of pi (4). That would cause it to freeze. Do you have "alert on health check" enabled ?Here is what my graph looked like. issue with the journctl and systemctl logs is that they do not persist across power boots by default so you may not seen any logs from that time it happened.
thats not a good sign. looks like the doser's schedule run has fired for 6 times. are there any other lines in the log? does logs before this show similar pattern (same time multiple trigger of the same thing)?
I think I VNC into my PI to look at it as I am going on vacation next week and wanted to check it. I normally do not use that feature but was getting ready. Hmmm...
There are more log lines than that repeating -I only copied a few. I guess that explains my graph - note most days it was 12 sec but the they got scaled out due to the high values of 5000. I see same pattern for the ALK doser too but it does not really run that long. I deleted my Calc and re-entered it so that graph is gone but it looked the same. It is triggering multiple times in a short period like you said.
Mar 20 07:05:02 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
Mar 20 07:05:02 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
Mar 20 07:05:02 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
Mar 20 07:05:02 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
Mar 20 07:05:02 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
Mar 20 07:05:02 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
Mar 20 07:05:02 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
Mar 20 07:05:02 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
Mar 20 07:05:02 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
Mar 20 07:05:02 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
Mar 20 07:05:02 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
Mar 20 07:05:02 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
Mar 20 07:05:02 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
Mar 20 07:05:02 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
Mar 20 07:05:03 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
Mar 20 07:05:03 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
Mar 20 07:05:03 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
Mar 20 07:05:03 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
Mar 20 07:05:03 LousReef reef-pi[281]: 2022/03/20 07:05:02 doser sub system: scheduled run Alk
i@LousReef:~/scripts $ sudo reef-pi db list doser
{
"5": {
"id": "5",
"name": "Calcium",
"jack": "1",
"pin": 0,
"regiment": {
"enable": true,
"schedule": {
"day": "*",
"hour": "10",
"minute": "10",
"second": "0",
"week": "*",
"month": "*"
},
"duration": 10,
"speed": 100
}
},
"6": {
"id": "6",
"name": "Alkalinity",
"jack": "2",
"pin": 1,
"regiment": {
"enable": true,
"schedule": {
"day": "*",
"hour": "8",
"minute": "55",
"second": "0",
"week": "*",
"month": "*"
},
"duration": 12,
"speed": 100
}
}
}
That’s odd. Just reload reef-pi , that should do
OK will try. I was hoping the "Cron for Go" had a text file you can edit or check for the list of events like the normal OS Crontab -e. But I am not able to find that file.
Rebooting PI fixed the multiple dose triggers. Very odd how that happened. I was experimenting with some POST commands to modify the dose duration based on PH (new feature suggest?) so this is the only cause I can think of.
