All devices down after LibreNMS restore

Help
1

We had a disk crash last night and had to restore our LibreNMS instance.
After the restore ALL our devices are down.
When using the debug feature it states the following:
[FPING] /usr/bin/fping -e -q -c 3 -p 500 -t 500 10.0.0.12

array (
  'xmt' => '3',
  'rcv' => '3',
  'loss' => '0',
  'min' => '0.46',
  'max' => '0.54',
  'avg' => '0.49',
  'exitcode' => 1,
)  

SQL[INSERT IGNORE INTO `device_perf` (`xmt`,`rcv`,`loss`,`min`,`max`,`avg`,`device_id`,`timestamp`,`debug`)  VALUES (:xmt,:rcv,:loss,:min,:max,:avg,:device_id,NOW(),:debug) {"xmt":"3","rcv":"3","loss":"0","min":"0.46","max":"0.54","avg":"0.49","device_id":7,"debug":"[]"} 3.32ms] 
  
Unpingable
/opt/librenms/discovery.php 10.0.0.12 2019-10-02 09:59:21 - 0 devices discovered in 1.160 secs  

MySQL [3/0.00s]: Cell[1/0.00s] Row[-1/-0.00s] Rows[2/0.00s] Column[0/0.00s] Update[0/0.00s] Insert[1/0.00s] Delete[0/0.00s]

It clearly states that it gets replies back but then states ‘unpingable’…

./validate.php:

Component Version
LibreNMS 1.56
DB Schema 2019_09_05_153524_create_notifications_attribs_index (141)
PHP 7.2.19-0ubuntu0.18.04.2
MySQL 10.1.41-MariaDB-0ubuntu0.18.04.1
RRDTool 1.7.0
SNMP NET-SNMP 5.7.3

====================================
[OK] Composer Version: 1.9.0
[OK] Dependencies up-to-date.
[OK] Database connection successful
[OK] Database schema correct

Anybody got any advice?

2

I think the issue has something to do with exitcode, fping is giving you 1, and 1 means no reply. Librenms interprets the exitcode so thats why you see unpingable.

can you run on cli

fping 10.0.0.12 -e -c 3

then

echo $?
3

This is probably from duplicate ping response. Most likely an issue after the restore.