Closed AmadeusGraves closed 11 months ago
Hi there,
Thanks for the detailed description!
Thanks in advance, j
thanks @jokob-sk for the rapid response, I already discover what happens. Today I updated CasaOS to the versión 0.4.4-3 and installed Pi.alert on that version. That was the problem because when i roll back to the previous version of CasaOS (0.4.4-2), Pi.alert work again.
But, I found one strange problem, when Pi.alert are executing the ARP Scan, the ram that consumes Pi.alert, jump to 5.6 GB! I think it was because i add to arp scan the net 192.168.1.0/8 when is 192.168.1.0/24.
P.D.: Sorry for my English, still learning XD.
Thanks for the update!
Previously high RAM consumption was correlated with excessive database size. You can check the Maintenance section to see if the DB size is outside of normal values (<10MB depending on runtime).
I'll check that but i have one question, i see that for example, the network provider offline when i have connection to the network.
Suddenly some devices mark offline but in 30 seconds mark online. It's strange.
Please make sure the schedules are synchronized as per: https://github.com/jokob-sk/Pi.Alert/issues/462
Yes, I just put the comment and saw the same issue that you have given me. Thanks.
Great, let me know if you still need assistance, if not, please close this issue and consider supporting me;)
I assume this is solved. I will re-open if needed.
Yes, sorry @jokob-sk , it's solved. I'll close the issue and i'll buy you a coffee. Thanks for the help.
@AmadeusGraves it means a lot, thanks 🙏
Describe the issue
[describe your issue]
When I check the pi.alert configuration just after upgrading to the latest version, I see that the configuration is not displayed.
Paste your
pialert.conf
(remove personal info)Paste your
docker-compose.yml
and.env
(remove personal info)docker-compose.yml
Screenshots
[If applicable, add screenshots to help explain your problem.]
Paste last few lines from
pialert.log
paste code below