[FAQ] Make Pi.Alert useable in offline Networks

[leiweibau]

[FAQ] Make Pi.Alert useable in offline Networks

[leiweibau]

Please check the Permissions. Have you checked the FAQ/Help section? There is an entry about "read only" db.

[intheshell]

Thanks, but I have a question. It turns out that the database is not locked when I remove the "offline mode", it will be that some process takes the database by modifying the lines:

# Get Internet IP
print ('\nRetrieving Internet IP...')
internet_IP = get_internet_IP()
# TESTING - Force IP
    # internet_IP = "1.2.3.4"

to:

# Get Internet IP
print ('\nRetrieving Internet IP...')
# internet_IP = get_internet_IP()
# TESTING - Force IP
internet_IP = "0.0.0.0"

Also the section beginning in line 702 from:

# Check Internet connectivity
internet_IP = get_internet_IP()
    # TESTING - Force IP
    # internet_IP = ""

to

# Check Internet connectivity
# internet_IP = get_internet_IP()
    # TESTING - Force IP
internet_IP = "0.0.0.0"

[leiweibau]

Can you show me you pialert.conf, especially the Pi-hole Configuration?

[intheshell]

Yes ,sure 👍

Pi-hole Configuration

----------------------

PIHOLE_ACTIVE = True
PIHOLE_DB = '/etc/pihole/pihole-FTL.db'
DHCP_ACTIVE = False
DHCP_LEASES = '/etc/pihole/dhcp.leases'

[leiweibau]

Why is PIHOLE_ACTIVE = True when you are in an offline network? Please set it to False

[intheshell]

ok thanks, i Disable the pihole_active, but persist:

arp-scan Method...
Pi-hole Method...
DHCP Leases Method...

Processing scan results...
Traceback (most recent call last):
File "/root/pialert/back/pialert.py", line 1776, in
sys.exit(main())
File "/root/pialert/back/pialert.py", line 97, in main
res = scan_network()
File "/root/pialert/back/pialert.py", line 465, in scan_network
save_scanned_devices (arpscan_devices, cycle_interval)
File "/root/pialert/back/pialert.py", line 654, in save_scanned_devices
sql.execute ("DELETE FROM CurrentScan WHERE cur_ScanCycle = ?",
sqlite3.OperationalError: database is locked
^@^@^@^@^@^@^@^@^@^@................

thanks for help me

[leiweibau]

With the "offline" fix and disabling Pi-Hole, I can't reproduce your error unfortunately. Here everything works as it should.
At this point I would try to either restore a backup of my database or start again with an empty database from my fork.

[intheshell]

Hi Master, I have been looking for the reason why it could eventually be failing and I noticed that the database session is taken and apparently it is due to the process of... Trying to resolve devices without name...

will it be so?

Devices Detected.......: 63
arp-scan Method....: 61
Pi-hole Method.....: +0
New Devices........: 0

Devices in this cycle..: 63
    Down Alerts........: 0
    New Down Alerts....: 0
    New Connections....: 1
    Disconnections.....: 2
    IP Changes.........: 0

Updating DB Info...
Sessions Events (connect / discconnect) ...
Creating new devices...
Updating Devices Info...
Trying to resolve devices without name....

root@rle2ag-1:/pialert/log# cd ..
root@rle2ag-1:/pialert# cd db
root@rle2ag-1:/pialert/db# sudo fuser -v pialert.db
USER PID ACCESS COMMAND
/root/pialert/db/pialert.db:
root 6157 F.... python3
root@rle2ag-1:/pialert/db#

[leiweibau]

Based on your findings, you can try the following. Search

    print_log ('   Resolve devices names...')
    update_devices_names()

and change it to

    print_log ('   Resolve devices names...')
    # update_devices_names()

It is possible that you have to kill running scans.
But I admit that it hurts a bit to cripple the software more and more :(

[intheshell]

If you are absolutely right, I believe that now the software is 100% in offline mode, since it does not make queries outside its network, therefore it is useful in case of having a panel to manage alerts without internet access (there are still , believe it or not) .

Thank you very much, it is solved.

[leiweibau]

I'm happy to hear that.
Please note that you have to repeat these changes when you install an update. I will rename this issue so that it is obvious that there is information worth knowing here. At this time, I do not plan to "officially" include this mode.