Author Topic: openLuup:.wsp files not updating?  (Read 564 times)

Offline a-lurker

  • Hero Member
  • *****
  • Posts: 872
  • Karma: +66/-8
openLuup:.wsp files not updating?
« on: May 05, 2017, 02:58:44 am »
That reminds me - I get this happening as well: As seen in the *.wsp files and in this order:
CPU
Mem
Uptime - note the uptime is not zero - it's days.

Note this has all worked in the past and seemed to act differently on an openLuup restart. Note thay I have not restarted openLuup in days, so as not to unsettle the scene timing issue. As you can see the two minute timer is working but what is the stuff in between?

Code: [Select]
1492213320,                    2.9
          0,                      0
 1492299840,                    5.4
          0,                      0
 1492299960,                    3.1
          0,                      0
 1492386480,                    6.4
          0,                      0
 1492386600,                    2.7
          0,                      0
 1492991520,                    5.7
          0,                      0
 1492991640,                    3.2
          0,                      0
 1492300560,                    3.1
          0,                      0
 1492300680,                    6.8
          0,                      0


Code: [Select]
1492213320,                   12.4
          0,                      0
 1492299840,                   16.1
          0,                      0
 1492299960,                     14
          0,                      0
 1492386480,                   13.5
          0,                      0
 1492386600,                   15.7
          0,                      0
 1492991520,                   12.9
          0,                      0
 1492991640,                   13.4
          0,                      0
 1492300560,                   10.2
          0,                      0
 1492300680,                   23.1
          0,                      0



Code: [Select]
          0,                      0
          0,                      0
          0,                      0
          0,                      0
          0,                      0
          0,                      0
          0,                      0
 1492981200,                      0
          0,                      0
          0,                      0
          0,                      0
          0,                      0
          0,                      0
          0,                      0
          0,                      0
 1492990800,                      0

« Last Edit: May 05, 2017, 03:02:38 am by a-lurker »

Online akbooer

  • Moderator
  • Master Member
  • *****
  • Posts: 6385
  • Karma: +290/-70
  • "Less is more"
Re: openLuup:.wsp files not updating?
« Reply #1 on: May 05, 2017, 03:34:04 am »
This is perfectly normal for .wsp files.  It simply means that the archive sampling definition is twice the rate that data is actually being written.

The non-monotonic nature of the entries may come from the fact that .wsp files are 'round robin' structures, so archive entries get reused after a while.

Let's split this into another thread.

3x Vera Lite-UI5/Edge-UI7, 25x Fibaro, 23x TKB, 9x MiniMote, 2x NorthQ Power, 2x Netatmo, 1x Foscam FI9831P, 9x Philips Hue,
Razberry, MySensors Arduino, HomeWave, AltUI, AltHue, DataYours, Grafana, openLuup, ZWay, ZeroBrane Studio.

Offline a-lurker

  • Hero Member
  • *****
  • Posts: 872
  • Karma: +66/-8
Re: openLuup:.wsp files not updating?
« Reply #2 on: May 05, 2017, 03:43:44 am »
I might be confusing the issue here - note those whisper files were last updated on the 30th April. I may have done a restart since then. So the files are not being updated at the moment at all, although other whisper files are working fine. According to the console the only DataYours timer running is UDP_listener_2003 at onsecond

The console also lists this device. The device is working perfectly but the console listing shows no name for the timer callback function. There is also another device that has no callback listed and it also works OK. I do note the 599s listed is meant to be 600s and that's what the timer variable says.

Code: [Select]
10  2017-05-05 17:08:41        10     Delay   599s :callback
The watches are in place but nothing happens in the log - implies the poll is not working; hence posting here.

Code: [Select]
   17     3   :watch   variableWatchCallback (2.openLuup.CpuLoad)
   18     3   :watch   variableWatchCallback (2.openLuup.Memory_Mb)
   19     3   :watch   variableWatchCallback (2.openLuup.Uptime_Days)