Trends visualization issue

[gdimaria]

Hi, it's a while I have problems to visualize trends on a wiser Schneiders:

   

I checked every single trends and memory usage is really low... it was working until a week ago...  so what could be the reason?

Thanks

Peppe

[Daniel]

Did you try rebooting?

[gdimaria]

many times...

---

is it possible if the object of the trend had a datatype change like i.e. from 09. 2 byte floating poit to 09.001 temperature ?

[admin]

Send your backup via PM

[gdimaria]

I don't know how to attach it to the PM.... I don't see the relative button.

[Daniel]

use wetransfer.com or similar. You cant attach it as file here.

[domotiqa]

I have the same issue to a customer !

First time  !
Try to clear cache...

It was a 6 month project old.
I update from 2.3 to 2.5.1 firmware and add new trend (and created category for the trend)

Here the PS:

* string:  PID USER      VSZ STAT COMMAND
    1 root      1060 S    /sbin/init
  693 root      1080 S    /sbin/syslogd -C16
  695 root      1060 S    /sbin/klogd
  697 root      860 S    /sbin/hotplug2 --override --persistent --set-rules-f
  885 root      1060 S    /sbin/watchdog -t 5 /dev/watchdog
  956 root      692 S    /usr/sbin/gpiod -l /lib/restore/defaults.sh -d /lib/
  967 root      1256 S    dropbear -p 22 -K 300
  971 root      1064 S    /usr/sbin/ntpd -n -p pool.ntp.org -p 1.schneider.poo
  982 root      3272 S<  /usr/bin/eibd -e 1.1.251 -q 100 -F n,n,n,n,0,0 tpuar
  988 root      2780 S    /usr/sbin/redis-server /etc/redis.conf
1041 root      2444 S    lua /lib/genohm-scada/core/scenes.lua
1042 root      1316 S    lua /lib/genohm-scada/core/ipblocker.lua
1044 root      2768 S    lua /lib/genohm-scada/core/groupmonitor.lua
1050 root      2944 S    lua /lib/genohm-scada/plugins/modbus/daemon.lua 0
1064 root      1872 S    lua /lib/apps/daemon.lua presence-simulation /home/a
1075 root      4196 S    nginx: master process nginx -c /tmp/nginx.conf
1077 root      8740 S    nginx: worker process
1083 root      1064 S    /usr/sbin/crond -l 20 -c /etc/crontabs
1089 root      1324 S    /usr/bin/dbus-daemon --system
1120 root      3352 S    openvpn --daemon --config /etc/openvpn/client.conf -
1187 root      1708 S    lua /lib/apps/daemon.lua processes /home/apps/store/
1246 root      4368 S    lua /lib/apps/daemon.lua sonos /home/apps/store/daem
2708 root      4696 S    lua /lib/genohm-scada/core/scripting-resident.lua 88
2897 root      1060 R    ps

   

[admin]

This happens when the trend storage file is missing probably due to a power loss during write operation. The only thing that can be done is deleting the trend that does not load and creating it again.

[domotiqa]

ok, so if I see in the backup a trend file missing, this is the one ?
Or I jsut delete trend until I found ...

Should be great to auto create the file ...

[gdimaria]

ok, so if I see in the backup a trend file missing, this is the one ?
Or I jsut delete trend until I found ...

Should be great to auto create the file ...

I found a shortway to restore all the trends: you just need an old backup in which trends are still working and then using 7-zip, overwrite the trends directory of the present time backup. You can also verify the integrity of file with 7-zip. Then restore the updated backup file and... that's it!


What you say? have I a cygar? 

[admin]

Automatic creation if the trend file is missing has already been implemented recently.
You can use 7-Zip to modify the backup file, you can also replace only the missing files not the whole directory so existing newer data is not lost.

[gdimaria]

Yes, you are right... replacing the whole directory is the shortest way if you want to restart all trends at same date.