sensor board hardware compatibility check failed Internal error

by limpens on

Hi all,

I suddenly ran into issues with my Flukso (FLM02B, firmware version 250).

As written in another post (https://www.flukso.net/content/flm02b-version-250-inconsistent-number-se...) the dash only shows 2 active sensors.

In the flukso.net -> settings page, there are 12 (!). Now I noticed the following error on my flukso device:


sensor board hardware compatibility check failed Internal error.
Please report this error message to Flukso.

Any pointers how to fix this issue?

Eric

‹ FLM02B / version 250, inconsistent number of sensors, only 2 sensors in dash Flukso off-line ›
icarus75's picture
icarus75 |

Could you copy/paste the full log where this error message occurs into this forum thread?

limpens's picture
limpens |

In the UI, on the 'Status' tab:

  1. Sensor config synchronisation
  2. Last 4/18/2018, 8:41:34 AM
  3. Status sensor board hardware compatibility check failed Internal error. Please report this error message to Flukso.

And in the UI, when saving the sensor configuration:

  1. Saving sensor parameters: ......
  2. Committing changes: true
  3. Syncing configuration: gh 266 0 .. ok
  4. Hardware check (major: 266, minor: 0) .. nok
  5. Error. Major version does not match.
  6. Use -f to override this check at your own peril.

The contents of the syslog.gz report:

  1. May 28 15:07:54 flukso-d82e29 user.err fsync[31330]: fsync exit status: 4, sensor board hardware compatibility check failed
  2. May 28 15:07:57 flukso-d82e29 daemon.info fluksod[32549]: processed pulse f2c388864453ae8ed989128d5a43f5ab:1527520077:36496310
  3. May 28 15:07:57 flukso-d82e29 daemon.info kubed[32561]: Caught a SIGTERM. Exiting...
  4. May 28 15:08:00 flukso-d82e29 daemon.info parsed[32558]: Caught a SIGTERM. Exiting...
  5. May 28 15:08:01 flukso-d82e29 daemon.info tmpod[32552]: Caught a SIGTERM. Exiting...
  6. May 28 15:08:01 flukso-d82e29 daemon.info fluksod[32549]: processed pulse 83528867422c2453f1060eb2c6f1bb7c:1527520081:636071
  7. May 28 15:08:02 flukso-d82e29 daemon.info fluksod[32549]: Caught a SIGTERM. Exiting...
  8. May 28 15:08:03 flukso-d82e29 daemon.info spid[32546]: Caught a SIGTERM. Exiting...
  9. May 28 15:08:04 flukso-d82e29 daemon.info supd[32543]: Caught a SIGTERM. Exiting...
  10. May 28 15:08:05 flukso-d82e29 daemon.info supd[31356]: Sucessfully started with DEAMON=supd and DAEMON_PATH=/var/run/supd
  11. May 28 15:08:05 flukso-d82e29 daemon.info spid[31359]: Sucessfully started with DEAMON=spid and DAEMON_PATH=/var/run/spid
  12. May 28 15:08:06 flukso-d82e29 daemon.info fluksod[31362]: Sucessfully started with DEAMON=fluksod and DAEMON_PATH=/var/run/fluksod
  13. May 28 15:08:06 flukso-d82e29 daemon.info tmpod[31365]: Sucessfully started with DEAMON=tmpod and DAEMON_PATH=/var/run/tmpod
  14. May 28 15:08:07 flukso-d82e29 daemon.info parsed[31371]: Sucessfully started with DEAMON=parsed and DAEMON_PATH=/var/run/parsed
  15. May 28 15:08:08 flukso-d82e29 daemon.info kubed[31374]: Sucessfully started with DEAMON=kubed and DAEMON_PATH=/var/run/kubed

Thanks for looking into this, Eric.

icarus75's picture
icarus75 |

Root cause of the error messages was a defective sensor board.