Only had my FLM a few weeks and been running well, then this morning on the first day of Winter it stops reporting at 9:21am, checked FLM to find the Globe light is off.
Checked the Status page and everything shows OK, even the ping test to flukso.net and WIFI is connected fine
So not wanting to loose the last three hours data I went into the Sensor setting and saved to force a restart of the DAEMON
Resulting syslog was
Jun 1 02:18:06 flukso-5ddbba daemon.info avahi-daemon[775]: Files changed, reloading.
Jun 1 02:18:06 flukso-5ddbba user.err fsync[17811]: POST https://api.flukso.net/sensor/56cabcf0b107576de2c95774d50aef88: -151
Jun 1 02:18:07 flukso-5ddbba daemon.info fluksod[1194]: processed pulse 72f595e494f15304c533e5233c6c02f1:1401589087:251980
Jun 1 02:18:07 flukso-5ddbba daemon.info fluksod[1194]: processed pulse 5d9d1654db2c1a583d0bf1ffe0baba88:1401589087:81467
Jun 1 02:18:07 flukso-5ddbba user.err fsync[17811]: POST https://api.flukso.net/sensor/72f595e494f15304c533e5233c6c02f1: -151
Jun 1 02:18:08 flukso-5ddbba user.err fsync[17811]: POST https://api.flukso.net/sensor/5d9d1654db2c1a583d0bf1ffe0baba88: -151
Jun 1 02:18:08 flukso-5ddbba user.err fsync[17811]: POST https://api.flukso.net/sensor/9f2b6cab67706c6822bd8ee15b75474e: -151
Jun 1 02:18:09 flukso-5ddbba daemon.info fluksod[1194]: processed pulse 72f595e494f15304c533e5233c6c02f1:1401589089:251981
Jun 1 02:18:09 flukso-5ddbba user.err fsync[17811]: POST https://api.flukso.net/sensor/40ac18d29ab4e35b3a4b485c5b4cf27a: -151
Jun 1 02:18:10 flukso-5ddbba user.err fsync[17811]: POST https://api.flukso.net/sensor/018c94300d4b7bb4cd73576e4768ca13: -151
Jun 1 02:18:10 flukso-5ddbba user.err fsync[17811]: POST https://api.flukso.net/sensor/41a609e38982399fcbdf9307cbead641: -151
Jun 1 02:18:11 flukso-5ddbba daemon.info fluksod[1194]: processed pulse 72f595e494f15304c533e5233c6c02f1:1401589091:251982
Jun 1 02:18:11 flukso-5ddbba user.err fsync[17811]: POST https://api.flukso.net/sensor/a18da6c420d0a134744cdf93b649fca3: -151
Jun 1 02:18:11 flukso-5ddbba user.err fsync[17811]: fsync exit status: 7, synchronisation with Flukso server failed
Jun 1 02:18:12 flukso-5ddbba daemon.info parsed[1199]: Caught a SIGTERM. Exiting...
Jun 1 02:18:12 flukso-5ddbba daemon.info fluksod[1194]: Caught a SIGTERM. Exiting...
Jun 1 02:18:13 flukso-5ddbba daemon.info spid[1191]: Caught a SIGTERM. Exiting...
Jun 1 02:18:14 flukso-5ddbba daemon.info supd[1188]: Caught a SIGTERM. Exiting...
Jun 1 02:18:15 flukso-5ddbba daemon.info supd[17830]: Sucessfully started with DEAMON=supd and DAEMON_PATH=/var/run/supd
Jun 1 02:18:15 flukso-5ddbba daemon.info spid[17833]: Sucessfully started with DEAMON=spid and DAEMON_PATH=/var/run/spid
Jun 1 02:18:16 flukso-5ddbba daemon.info fluksod[17836]: Sucessfully started with DEAMON=fluksod and DAEMON_PATH=/var/run/fluksod
Jun 1 02:18:16 flukso-5ddbba daemon.info parsed[17841]: Sucessfully started with DEAMON=parsed and DAEMON_PATH=/var/run/parsed
Jun 1 02:18:20 flukso-5ddbba daemon.info fluksod[17836]: processed pulse 72f595e494f15304c533e5233c6c02f1:1401589100:251987
Jun 1 02:18:21 flukso-5ddbba user.info heartbeat[17844]: POST https://api.flukso.net/device/5ddbba6ed40dc604b70f12ef55725c06: 200
Jun 1 02:18:22 flukso-5ddbba daemon.info fluksod[17836]: processed pulse 72f595e494f15304c533e5233c6c02f1:1401589102:251988
Which from the second last line appeared to have fixed the issue
However GLOBE went out again and the the following syslog err for both sensors
Jun 1 02:23:21 flukso-5ddbba daemon.info fluksod[17836]: processed pulse 72f595e494f15304c533e5233c6c02f1:1401589401:252169
Jun 1 02:23:22 flukso-5ddbba daemon.err fluksod[17836]: POST https://api.flukso.net/sensor/72f595e494f15304c533e5233c6c02f1: -151
Jun 1 02:23:22 flukso-5ddbba daemon.err fluksod[17836]: POST https://api.flukso.net/sensor/5d9d1654db2c1a583d0bf1ffe0baba88: -151
Jun 1 02:23:22 flukso-5ddbba daemon.info fluksod[17836]: processed pulse 5d9d1654db2c1a583d0bf1ffe0baba88:1401589402:81522
If I completely power down the FLM do I loose the data ?
And is that the next step to try and rectify
Thanks for any assistance
Glenn
I don't think it is my FLM that has problem
Just checked Bazzle on PVOutput and his system has no info after 9:20 plus crtpsolar another Aussie system I follow
So big ?
I have the same same problem and another user 500Km from me has the same problem too. Yes, at 9:21 am AST that is 23:21 GST 31/5/14.
I did not notice your message and posted one myself...
Flukso data site appears to be "down"
Baz
Same here...
Same here...
Flukso data site appears to be "down"
OK, so thats the problem I suppose. Already restarted the FLM a few times but no data.
same here . server is not working ;(
Same problem :(
The api.flukso.net ssl certificate expired. Should be fixed now. Sorry for the inconvenience.
Cheers
/Bart
Just for next time:
How much data can the Flukso hold before it's buffer is full.
Tx
Bart
How does that happen?
That data is very important to a lot of us for many reasons ..
Baz
@Bazzle - if the data is "important" then you should not rely purely on a web service, but seek to persist it for yourself also... - Backup I would name the first law of computer science - everything is described around the forum and easily to be established; I run a RasPi for local storage and did not even realize the dropout...
@Gebhardm
What sort of answer is that.
I and im sure hundreds of other users didnt purchase our Flukso to have to run another pc or service to keep it working.
I and many others use pvoutput to copy the data to. When the primary site goes down, that other source of data is lost too.
You seem to think everyone can just russle up an pi etc "just in case"
@icarus75
You don't have a valid CA certificate installed on api.flukso.net so it's not trusted in all browsers.
I personally do not expect for 160Eur the FLM cost me a 99.9% reliable webservice over an infinite number of years. So indeed I think one should take care oneself for "important" data... and 30Eur for a Pi indeed provides me a plus on reliability - so, question back, "what sort of expectation do you have?" - I am grateful that Bart fixed the issue so incredibly fast - so, Thank You Bart!!!
+1 Thanks!
+2 Thanks to Bart for the quick rectification
Learnt something more about the internet today that we all take for granted !!
+3 and also thanks to Markus for pointing out. Curious thing though: there is no data gap in the Flukso Dash but PVOutput has a gap from 1:25 AM till 10:10 AM CET.