Constant issues with locked database ...

[andersnordh]

Hi guys,

I have two installations, both "fresh", on two different Raspberry Pi's, one Pi 4 and one Pi Zero 2W.

The Pi Zero is connected over wifi to a small guest network with 5-20 simultaneity connected devices, normally no problem but an occasional "Cannot update due to a lead only database" when editing devices. I always disable ARP scan when updating or rebooting, no other scan is running. Still the database gets locked, especially while running the upgrade of Pi.Alert.

The Pi 4 is connected using Ethernet, same scenario as above but 50-100 simultaneously connected clients, and way worse when I try to edit devices, I seem to have a 10 second window each minute, the rest of the time the database is in read only mode. The strange thing now is that when I last did run the Pi.Alert update I had to load an old database to manage to get the update to run. Today, same thing but now when I load the same old backed up database that one is also locked. I give up but would really like to see this work ...

... and yes, I follow the advice int the FAQ but still no luck.

Have a nice day,
Anders

[leiweibau]

From my experience in the past, I have to say that Pi Zero has shown clear weaknesses in connection with Pi.Alert. Although I have not installed Pi.Alert on a Pi Zero, the Pi Zero was one of the hosts used in a network scanned by Pi.Alert. Whenever a scan was running, the connection to the Pi Zero broke down. With this experience, I can imagine that the scans are simply taking too long and the Pi Zero is getting more and more bogged down from scan to scan. Added to this is the poor performance of the WLAN interface.

https://notenoughtech.com/raspberry-pi/raspberry-pi-zero-w-wifi-performance/

[andersnordh]

Thanks a lot for your reply.
In a week or so I will reinstall everything from scratch using a Pi 5 with nvme drive, just to see if I can get it back up, really like the work you put in and that you provide a raw install guide as well.
To be continued :-)
Have a good one,
Anders

[andersnordh]

Hi again,
Have now had the time to make a fresh install using a Raspberry Pi 5 with a m.2 hat and a 256 GB nvme drive. The unit is much faster that a Pi 4 with a micro SD card but still, I have about 20-25 seconds every minute do do changes, the rest of the time the db is "locked". It has only been running for a day or so, have not seen any total freezes yet where Pi.Alert stopped noting any changes yet ... without me or anything interfeering. Will have to see because that was a real problem.
I have approximately 70 devices in my network ...
Have a good one.
//Anders

[leiweibau]

The scan starts every 5 minutes. Depending on the size of the network and the additional functions used, a scan can take a large part of this time. In addition, sqlite3 is a single user database in which only one user/process can write. Of course, there may be a short time window during the scan to write a change, but more intensive editing will always be interrupted. So if you want to make larger changes and want this to happen without interruptions, you should pause Pi.Alert in the settings.
For classification: With 65 hosts, 6 web services and 4 ICMP monitoring hosts, a scan takes about 3 minutes for me

[andersnordh]

Hi again, great idea, I will definitely use that method in the future, was too simple for me to figure that out ... and good to understand how it work with its scans, thanks.
Have a good one.
//Anders