I was installing real time clock on Orange Pi One board ... , after some unsuccessful tries I found that the battery has bad solder and all is fine now

date was set "up" and "down" ...

from Sat Jan 1 02:06:23 EET 2000 to Thu Jul 8 21:37:42 EEST 2032 several times ... and during all this time armbianmonitor was running (I did not check it every time ... I made many reboots )

 

now armbianmonitor shows some "static" data , in which the time is always  0:18.50 ...

and I am thinking that may be it is showing the "last" recorded , I mean the higher date/time ...which is somewhere in the future  2032...

I try reinstalling armbianmonitor ... did not helped

how to remove it (reinstall it)? where is the data stored to edit it ... or any suggestions ?

 

p.s. when with  "-m" seems working ... showing the temp ... Mhz

 

sorry for error in topic  "DATE" not "data changes" 

found solution

$ cd /var/lib/rpimonitor/stat
$ rm *
$ armbianmonitor -r

Installing RPi-Monitor. This can take up to 5 minutes. Be patient please
Now patching RPi-Monitor to deal correctly with H3

Now you're able to enjoy RPi-Monitor at http://192.168.100.30:8888
 

now everything is working !   

It should be noted that armbianmonitor and RPi-Monitor (you mentioned now the first time) are two completely different things. And armbianmonitor just knows one switch to install RPi-Monitor.

 

And the normal way is to simply stop the rpimonitord daemon, then delete /var/lib/rpimonitor/stat/* and then start the daemon again if you want to get rid of collected data. There's no need to install everything again.

There is something strange with the temperature reading in armbianmonitor -m

In the below capture at 15:52:15  I stopped a CPU intensive task and instantly temperature fell by

10 degrees.

 

PS :the wrong characters are due to doing the capture via SSH and PUTTY

 

15:51:52: 1440MHz  4.97  90%   9%  80%   0%   0%   0%   53°C
15:51:57: 1440MHz  4.65  90%   9%  80%   0%   0%   0%   53°C
15:52:02: 1440MHz  5.08  90%   9%  80%   0%   0%   0%   54°C
15:52:08: 1440MHz  5.07  89%   9%  79%   0%   0%   0%   53°C
15:52:13: 1440MHz  5.47  89%   9%  79%   0%   0%   0%   53°C
15:52:18: 1440MHz  5.43  92%  10%  81%   0%   0%   0%   43°C
15:52:23: 1440MHz  4.99  38%   4%  33%   0%   0%   0%   41°C
15:52:28: 1440MHz  4.59  38%   4%  33%   0%   0%   0%   41°C
15:52:33: 1440MHz  4.23  38%   4%  33%   0%   0%   0%   41°C

 

Also the permissions of  /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq

are read only for root and there is a problem for a normal user.

Changing permissions solves the problem until the next reboot.

Of course may be armbianmonitor is not the culprit at all