Hi there,
I scheduled upgrade to my Flukso and it happened. WebUI show version 232.
But now I keep receving message like:
{"message":"Method not found.","code":-32601}
And "Sensor config synchronization" shows:
"synchronisation with Flukso server failed"
every time I load the page. However Fluskso seems to be working very well besides this strange UI messages.
Any clue?
Thanks
Oh,
I'd like to add that sometimes WiFi config page on the webGUi shows these errors:
/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
×
/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
regards
Can you try loading the local UI again after flushing the browser cache? A double reload also works on some browsers. It might be that you're browser still presents you with the old UI from its cache.
@Icarus75
I have the exact same issue.
Some additional information.
On the FLM status page in the bottom field (status) it says
synchronisation with sensor board failed Internal error. Please report this error message to Flukso.
On the syslog page i see correct pulse processed messages and POST messages but i also have the following message.
Nov 6 10:25:04 flukso-569bd8 user.err fsync[1049]: fsync exit status: 3, synchronisation with sensor board failed
I thought this might be the same issue reported on https://www.flukso.net/content/no-heartbeat-or-data-after-upgrade but i checked the two files and there were no extra lines in the files. I did add my FLM's serial number to the /etc/config/system file to see if that was causing the problem. It was listed as Unknown before i added the correct serial number (FL02001982). Although the status page now reports the correct serial number it has not fixed any of the other issues.
I read an old forum post https://www.flukso.net/content/flukso-heart-beat-and-synchronisation-sen... with similar symptoms where you went in remotely and fixed the failed sensor board flash.
Might this be the same issue and require the same fix?
Well it is all working fine again. I didn't make any changes. Maybe someone did something remotely?
All FLM inbuilt web pages display with no errors. The syslog is clear of errors.
The main page status field was still showing "synchronisation with sensor board failed Internal error".
So i tried saving the sensors (with no changes) again and this time it worked without any errors and now the status field on the main FLM web page says "successful" and i agree. :)
Hi,
@Icarus75
Clear cache solved the exception issues however it did not solve the "sensor config ..." issue. After save the sensors again as suggested by Fusionpower it worked again.
Thanks
@FusionPower
Thanks! It worked for me.
Best regards,
Benito
Hmm. That's strange. This would mean that at first boot after a migration to r232 the sync to the sensor board fails, but when triggered from the UI, it completes successfully. A note to anyone experiencing a similar issue: please leave the FLM running as-is and notify me via this thread. I'll then try to debug this remotely.
For what it's worth I had the same issue. Cleared the cache and the errors on top disappeared but not the " sensor config" message. After saving the sensors the message disappeared again and all is working fine.
Hi Bart,
You wrote, "anyone experiencing a similar issue: please leave the FLM running as-is and notify me via this thread. I'll then try to debug this remotely."
I just updated to r232, and have not done anything except go to the flukso's local webpage.
This error indeed went away (browser cache, I suppose)
{"message":"Method not found.","code":-32601}
But the "Sensor config synchronization" still shows: "synchronisation with Flukso server failed"
Would you like to debug remotely?
Cheers,
- Gerrit
wrt to "method not found": In any case clear your browser cache to be sure to have the latest script version transferred from your FLM...
Michael - I was referring to the "synchronisation with Flukso server failed" issue which Bart wants to troubleshoot on an affected Flukso - well, mine's affected by this and untouched!
(Interestingly: Energy Control on Android is reporting all the sensors' live data; so the Flukso itself is very much operational and aware of its sensors!)
Hello Gerrit,
Just performed some remote investigation of your upgraded FLM.
A Fluksometer firmware upgrade will always trigger a synchronisation with its daughter board and the Flukso server (= fsync). In your case the fsync failed right at the end, when trying to communicate with flukso.net. Looking at flukso.fsync.time ntp was not yet able to set the system time correctly either. It seems that the network, most likely the wifi link, was still down when the fsync occurred. I just successfully re-ran the fsync.
Note that this error condition differs from fusionpower's. In his case the syncing with the sensor board failed. That caused his FLM to actually stop collecting data.
Thanks for reporting the issue!
/Bart
finally got around to going to r232 from r223, and experienced more or less all of these same error messages (including network sync failure as well as board sync failure). several reboots and then pressing "save" on the sensors page (without changing anything. worked first time on v2b, took 2 or 3 times on v2a to get a successful save/sync) later, seems to have cleaned everything up. thanks everyone!
side note: Guard Flukso / Guard Energia android app still works happily on my phone. awesome!
It seems that one of my Flukso FLMO2B is stop working sins two weeks.
There is no connection with the WiFi, and after restart I can't finding any SSID.
The code 32601 have I seen but olso a lot other tekst witch say nothing to me.
What can be the problem?
Thanks for responding,
Ariaen Jansen