Error connecting to database

[seelk07]

All of a sudden, I am no longer able to access the web interface. I believe this occurred after a recent update. I receive the message "Error connecting to database, will try in 3s". After pressing OK it still does not connect and produces the same message "Error connecting to database". Thoughts?

Below is the docker compose file I used.

version: "3"
services:
  pialert:
    container_name: pialert
    # use the below line if you want to test the latest dev image
    # image: "jokobsk/pi.alert_dev:latest"
    image: "jokobsk/pi.alert:latest"
    network_mode: "host"
    restart: unless-stopped
    volumes:
      - /config/pialert:/home/pi/pialert/config
      - /config/pialert/db:/home/pi/pialert/db
      # (optional) useful for debugging if you have issues setting up the container
      - /config/pialert/logs:/home/pi/pialert/front/log
    environment:
      - TZ=America/New_York
      # - HOST_USER_ID=1000
      # - HOST_USER_GID=1000
      - PORT=20211

[jokob-sk]

Hi @vladaurosh, can you suggest what might help to debug this issue?

The error is thrown from this PHP file:

https://github.com/jokob-sk/Pi.Alert/blob/7d18dd546ef485533e07fed24d3060b11934d820/front/php/server/db.php#L33

@seelk07 can you post a screenshot/log of your permissions on the pialert.db file?

[seelk07]

@jokob-sk see below:

-rw-rw-rw- 1 systemd-network 82 39100416 Mar 20 17:45 pialert.db

[vladaurosh]

@seelk07
I see db directory is inside directory that's mapped to /home/pi/pialert/config

• /config/pialert:/home/pi/pialert/config
• /config/pialert/db:/home/pi/pialert/db

Could you have something like this:

• /config/pialert/config:/home/pi/pialert/config
• /config/pialert/db:/home/pi/pialert/db

Also can you do ls -al in /config/pialert and /config directories?

[seelk07]

@vladaurosh changing to /config/pialert/config:/home/pi/pialert/config fixed the issue. Was my configuration file the issue?

For reference:

: ls -al /config/pialert
total 1016
drwxr-x---  4 systemd-network     82   4096 Mar 20 13:38 .
drwxrwxr-x 31 richie          richie   4096 Mar 20 18:06 ..
drw-r-----  2 systemd-network     82   4096 Dec 15 15:55 db
drw-r-----  2 systemd-network     82   4096 Mar 19 03:01 logs
-rw-r-----  1 systemd-network     82   9236 Dec 15 16:47 devices.csv
-rw-r-----  1 systemd-network     82  13300 Dec 20 02:00 devices_20231220020036.csv
-rw-r-----  1 systemd-network     82  14776 Dec 27 02:00 devices_20231227020047.csv
-rw-r-----  1 systemd-network     82  15546 Jan  3 02:00 devices_20240103020037.csv
-rw-r-----  1 systemd-network     82  16173 Jan 10 02:00 devices_20240110020026.csv
-rw-r-----  1 systemd-network     82  16173 Jan 17 02:01 devices_20240117020103.csv
-rw-r-----  1 systemd-network     82  16183 Jan 24 02:00 devices_20240124020048.csv
-rw-r-----  1 systemd-network     82  16183 Jan 31 02:00 devices_20240131020059.csv
-rw-r-----  1 systemd-network     82  16183 Feb  7 02:01 devices_20240207020118.csv
-rw-r-----  1 systemd-network     82  16183 Feb 14 02:00 devices_20240214020046.csv
-rw-r-----  1 systemd-network     82  16705 Feb 21 02:01 devices_20240221020103.csv
-rw-r-----  1 systemd-network     82  16705 Feb 28 02:00 devices_20240228020037.csv
-rw-r-----  1 systemd-network     82  16705 Mar  6 02:01 devices_20240306020115.csv
-rw-r-----  1 systemd-network     82  17193 Mar 13 02:00 devices_20240313020024.csv
-rw-r-----  1 systemd-network     82  17193 Mar 20 02:01 devices_20240320060118.csv
-rw-rw-rw-  1 systemd-network     82 188198 Mar 20 13:38 pialert.conf
-rw-r-----  1 systemd-network     82   3072 Dec 15 16:20 pialert.conf_2023-12-15_16-20-47.backup
-rw-r-----  1 systemd-network     82   3059 Dec 15 15:55 pialert.conf_old_setting_names_20231215155540.bak
-rw-r-----  1 systemd-network     82 188141 Dec 15 16:20 pialert.conf_old_setting_names_20231215162049.bak
-rw-r-----  1 systemd-network     82 188151 Jan 18 03:03 pialert.conf_old_setting_names_20240118030331.bak
-rw-r-----  1 systemd-network     82 188198 Mar 20 13:33 pialert.confe

[vladaurosh]

Thanks @seelk07

Just as I thought, since your db directory was inside directory that's mapped to config directory, permission were applied to db directory as well.

drw-r----- 2 systemd-network 82 4096 Dec 15 15:55 db
drw-r----- 2 systemd-network 82 4096 Mar 19 03:01 logs

Here we can see that these 2 directories (db and logs) do not have x bit set, so app can't actually read anything inside.

@jokob-sk that's being set here, second command that applies 640 to everything in ${INSTALL_DIR}/pialert/config:

chmod 750 "${INSTALL_DIR}"/pialert/{config,front/log,db}
chmod 640 "${INSTALL_DIR}"/pialert/{config,front/log,db}/*

and since in above example db directory was inside config directory, it was set to 640.

Maybe we update documentation with recommendation to have separate db and config directories. In the meantime I'll create PR so we apply 750 to directories only and 640 to files only.

[jokob-sk]

Great, I'll add a note in the Docker docs under the mapping table 👍 Thanks for the help

[seelk07]

@jokob-sk and @vladaurosh thank you for your help!

[seelk07]

@vladaurosh I'm now noticing all my devices are showing Down & Offline. Thoughts?

[seelk07]

Disregard my previous question. I needed to update the Arp-Scan SCAN_SUBNETS setting.