@ icarus If there is a planning for maintenance it can't be that difficult to send an email to all the users, can it?
B-Man |
does anyone have a script that can get the data directly from the flukso and upload it to pvoutput bypassing the flukso site if it goes down?
Fluc |
In BE, this morning no internet. After restarting the Bbox3, it worked again.
But the Flukso didn't report to the server. After restarting the Flukso by cutting and re-enabled the power, it began reporting. I can now read local and online on the dash but when i look on the status, it shows a fault
/usr/lib/lua/luci/sauth.lua:80: Security Exception: Session ID is invalid! stack traceback: [C]: in function 'assert' /usr/lib/lua/luci/sauth.lua:80: in function 'read' /usr/lib/lua/luci/controller/rpc.lua:28: in function 'authen' /usr/lib/lua/luci/dispatcher.lua:370: in function 'dispatch' /usr/lib/lua/luci/dispatcher.lua:195: in function
I re enabled the 3 services and click "save", but had the same fault. Session ID is invalid.
What could it be ?
Wizzopa |
@ B-man
That would be a nice trick.
B-Man |
@FLUC close the window and relogin in. it hasn't recognised you logging in with the user/pass
icarus75 |
The server was rebooted by the provider to apply Spectre and Meltdown patches. Not all services were properly started following the reboot. Please note that the FLM will buffer sensor readings and push them to the Flukso server when the connection can be re-established.
Wizzopa |
@Icarus75
Thanks for the info.
B-Man |
i rebooted mine. im guessing that caused me to lose all the sensor data?
Fluc |
@B-MAN, thanks, it worked after a while.
Wizzopa |
@Icarus75
And once again it stop logging.
Pjedr |
Yes. Indeed #metoo i noticed pvoutput was 1600watt less than it should, so i was looking in the forum.
alexvandenbogaard |
still no logging, is something being done to solve problem?
hansvk |
Almost seven hours no data. What's wrong?
databeestje |
My PVoutput was stuck at 14 o clock, just noticed and thought I actually found it because the UTP came out of the switch, but no go.
is there any way to get the missing data onto pvoutput when the server is back up? as im guessing pvoutput collects it from the api which probably only getting the "live" last 5 min increments
frumper |
any update please, i'm still not seeing any data for the past 16 hours :(
As far as I know - dont restart your Flukso meter. It holds data (not sure how many hours of data), so when the server will be up, the data will be recovered but it will be averaged per hour or per 15min.
mozreactor |
Looks like Flukso haven't purchased a new security certificate. I get this message when I try to navigate to the relevant Flukso address for my sensor:
07 to 14 here downunder :(
@ icarus If there is a planning for maintenance it can't be that difficult to send an email to all the users, can it?
does anyone have a script that can get the data directly from the flukso and upload it to pvoutput bypassing the flukso site if it goes down?
In BE, this morning no internet. After restarting the Bbox3, it worked again.
But the Flukso didn't report to the server. After restarting the Flukso by cutting and re-enabled the power, it began reporting. I can now read local and online on the dash but when i look on the status, it shows a fault
/usr/lib/lua/luci/sauth.lua:80: Security Exception: Session ID is invalid! stack traceback: [C]: in function 'assert' /usr/lib/lua/luci/sauth.lua:80: in function 'read' /usr/lib/lua/luci/controller/rpc.lua:28: in function 'authen' /usr/lib/lua/luci/dispatcher.lua:370: in function 'dispatch' /usr/lib/lua/luci/dispatcher.lua:195: in function
I re enabled the 3 services and click "save", but had the same fault. Session ID is invalid.
What could it be ?
@ B-man
That would be a nice trick.
@FLUC close the window and relogin in. it hasn't recognised you logging in with the user/pass
The server was rebooted by the provider to apply Spectre and Meltdown patches. Not all services were properly started following the reboot. Please note that the FLM will buffer sensor readings and push them to the Flukso server when the connection can be re-established.
@Icarus75
Thanks for the info.
i rebooted mine. im guessing that caused me to lose all the sensor data?
@B-MAN, thanks, it worked after a while.
@Icarus75
And once again it stop logging.
Yes. Indeed #metoo i noticed pvoutput was 1600watt less than it should, so i was looking in the forum.
still no logging, is something being done to solve problem?
Almost seven hours no data. What's wrong?
My PVoutput was stuck at 14 o clock, just noticed and thought I actually found it because the UTP came out of the switch, but no go.
From the syslog.
May 21 20:47:30 flukso-484865 daemon.err fluksod[679]: POST https://api.flukso.net/sensor/nnnnnnnnnnnnnnnnnnnnnnnn: -151
May 21 20:47:30 flukso-484865 daemon.err fluksod[679]: POST https://api.flukso.net/sensor/yyyyyyyyyyyyyyyyyyyyyyyyyyyyy: -151
is there any way to get the missing data onto pvoutput when the server is back up? as im guessing pvoutput collects it from the api which probably only getting the "live" last 5 min increments
any update please, i'm still not seeing any data for the past 16 hours :(
I wrote about the same problem 5.5 hours age here https://www.flukso.net/content/no-usage-data-displayed-no-access-flukso-...
As far as I know - dont restart your Flukso meter. It holds data (not sure how many hours of data), so when the server will be up, the data will be recovered but it will be averaged per hour or per 15min.
Looks like Flukso haven't purchased a new security certificate. I get this message when I try to navigate to the relevant Flukso address for my sensor:
https://www.dropbox.com/s/j2y0gk4saqiaje3/flukso%20security%20cert.jpg?dl=0
It's up again. Indeed, seems like a certificate renewal was needed. So, we're good for another two years now.
So once everything came back online, my flukso had the data but I lost a day of PVoutput data (did not upload the recorded data).
I ended up stuffing around with downloading my data from the dash, getting it into a nice format and uploading to PVoutput using:
https://pvoutput.org/loadlive.jsp
It took about 30 mins, which isn't ideal.