01-28-2018, 02:05 PM
Hi Robbie,
I may be totally off track here, but while investigating this on my system I came across the following in the nagios.log file after I rebooted NEMS:
Now in my resource.cfg file, line 11 (if I also count the comment lines) is $USER3$ which in my case is blank as is the following line $USER4$.
$USER13$ and $USER14$ are also blank.
Could it be that nagios starts reading the resource file and crashes on the first NULL value and stops reading, because the next line is $USER5$ which is the 'From' address, so that would not be picked up, resulting in the error that we have...
BR
I may be totally off track here, but while investigating this on my system I came across the following in the nagios.log file after I rebooted NEMS:
Code:
[1517158341] Successfully shutdown... (PID=1578)
[1517158343] livestatus: Socket thread has terminated
[1517158343] Event broker module '/usr/lib/mk-livestatus-1.2.8p13/src/livestatus.o' deinitialized successfully
.
[1517158389] Error: NULL variable value - Line 11 of resource file '/etc/nagios3/resource.cfg' <<<<=========
[1517158389] Nagios 3.5.1 starting... (PID=1445)
Now in my resource.cfg file, line 11 (if I also count the comment lines) is $USER3$ which in my case is blank as is the following line $USER4$.
$USER13$ and $USER14$ are also blank.
Could it be that nagios starts reading the resource file and crashes on the first NULL value and stops reading, because the next line is $USER5$ which is the 'From' address, so that would not be picked up, resulting in the error that we have...
BR