Curious error about systemInfo.txt file not found ?
-
On our new ES we are getting this error. There does not appear to be a reason I can find.
'MangoES System': File not found: /opt/info/systemInfo.txt (No such file or directory)
yet the file is where it should be and has the following inside:with today's date.
##########CPU############
CPU UserSpace Load: 0.2
CPU Kernel Load: 0.6
CPU Total Load: 0.8
CPU0 Temp: 51.0
CPU1 Temp: 54.0
CPU2 Temp: 55.0
CPU3 Temp: 54.0
CPU4 Temp: 49.0
##########RAM############
Physical Memory Total: 1991
Physical Memory Used: 1372
Physical Memory Free: 618
Swap Memory Total: 0
Swap Memory Used: 0
Swap Memory Free: 0
########DISK##########
Disk Name: /dev/mmcblk0p2
Disk Total Size: 7149
Disk Space Used: 1947
Disk Space Left: 4820
Disk Percent Used: 29%
########SYSTEMTIME############
SystemTime: Thu Feb 15 20:23:02 MST 2018 -
Hi Phillip,
Only two things come to mind,
- Check that the file ownership / read permission is not the issue. (only likely if you get it every poll)
- It would be possible for things to be timed such that the ASCII reader tries to read the file at the same instant it is being recreated with new information, in which case there's an instant the file doesn't exist (would happen sporadically, and not be significant).
So, do the points have new data?
-
It doesn't happen on every poll . I did initially change the file permissions so it wasn't that causing it and the data is updating however the update seems sporadic as well.
-
That's the logging type being point value changes I would think. The default poll period is 30 seconds and I believe the file is regenerated at the same interval. If you happened to have started
Mangothe system info ASCII file data source on a second evenly divisible by 30, I would expect that error to be more likely. But, it shouldn't cause any issue and isn't different than that ASCII data source missing a poll. -
OK thanks Phil, I might restart it and see if the error continues and I won't worry about it.
-
Certainly!
I meant if the data source started (not Mango) on an second divisible by 30. You can just restart the data source to restart its poll timer.