Moving to 1.4 and issues I have come across

[Robbie Ferguson]

Yeah, odd one. Let's sit tight and see if anyone else reports the same issue.

You can also send me your backup.nems file and I'll check the logs to see if anything jumps out at me.

Cheers!

[ronjohntaylor]

Hi Robbie,

I just scrolled back and read all the posts... I had missed a few as I was just jumping to the latest one.

I just cleared all my caches and cookies on Chrome and now in Nagios Core
Host Detail works
Service Detail works

Hurrah!

I apologise for my oversight!

I will keep an eye on things and let you know if something does go astray.

Ron

[Robbie Ferguson]

Great, thanks for the update Ron. Glad my theory was correct. Not sure what I can do about that ... so I might add to the docs to tell people to clear their browser cache following a major upgrade :P

[ronjohntaylor]

Weird Things Happen...

This morning I decided to do a backup image of my 1.4 SD Card.

Procedure Followed:

1. Shutdown NEMS 1.4 with sudo shutdown -h now
2. Wait for RPi to flush and be ready for power off
3. Remove Power 
4. Remove SD CArd
5. Backup SD Card 
6. Replace SD Card
7. Power on
8. Wait for Boot... waiting waiting 
9. Check Browser access...waitingwaiting
10. Try to SSH... waiting waiting
11. Eventually this response on ssh

Linux nems 4.14.44-v7+ #1117 SMP Thu May 31 16:57:56 BST 2018 armv7l

Last login: Sun Jun 17 07:10:48 2018 from 10.0.0.102

Wi-Fi is disabled because the country is not set.
Use raspi-config to set the country before use.





[API Did Not Respond]PHP Notice:  Trying to get property of non-object in /usr/local/share/nems/nems-scripts/info2.sh on line 59
    while executing
"exec -- /usr/local/bin/nems-info platform-name"
    invoked from within
"set nemsplatform [exec -- /usr/local/bin/nems-info platform-name]"
    (file "/etc/motd.tcl" line 19)


Back to Browser and login and things seems to be normal.


Anyway I thought I would log it here.
Ron

[ronjohntaylor]

I have noticed an error in NConf.
When deploying and error is given saying that it failed to copy a collector file.
See attached screenshot 2018-06-22_5-57-01.jpg

[Robbie Ferguson]

Hey man,
Yeah, you reverted the magic change :)

I'll be patching this over the weekend as per the other thread about this bug. Your Pi will get the update along with everyone else.

Thanks!
Robbie

[Tech Dave]

Hi Robbie / Ron,

I too ( still ) have undefined values in RPI-Monitor for CPU Voltage, Freq and Scaling Gov.

This is apparent across three independent Pi 3 B + running 1.4.1. - two others, same hardware spec, but running 1.3.1, the values are there.

It's not the end of the world, but judging by your update process and the dialogue above, it should have been picked up on the daily update cycle by now - do you concur? FWIW, yes I have run a sudo nems-quickfix (and reboot) - no change.

Not a problem to me at all, but as it has been raised by Ron, I thought I might report it too.

All the best, and many thanks,

Dave.

[ronjohntaylor]

Robbie,
In response to TechDave's comments ...
My Rpi-Monitor does report correctly... However...
Every so often, whenever I click on that link, mt browser just sits at nems:8888 and nothing much happens.
If I drop that tab out and run MonitorIX, then run RPi-Monitor it comes up instantly.

I had not bothered reporting it as I figured you had bigger fish to fry but as Dave reported his problems I thought that for completeness I would.
Cheers
Ron

[Robbie Ferguson]

Thanks guys! Hmm, there must be a mixup in configs between perhaps one of your backups and the new conf. Can you email me your backup.nems file to have a look? The encrypted one should be fine (I don't need private info... just your rpi-monitor conf file).

Cheers,
Robbie

[Robbie Ferguson]

Thanks for sending me your file, Ron. Though yours looks fine in RPiMonitor. I may have to wait for Dave's.

For your problem, Ron... do you have more than one NEMS server running on your network? Also, could you experiment and see if nems.local works better then just nems? And if no difference, could you test with your NEMS IP address instead of hostname?

Your issue is different, but sounds to me like a DNS routing issue between your computer and the NEMS server.

Thanks,
Robbie