Reporting to flukso

Hi,
Does anybody know what might be a reason of freeze in reporting to flukso server?
Device sends data, after I don't see data for an hour or 30 minutes sometimes
and after data comes again

EDIT: I checked log file . Apparently pulses are stopping to come and after 3-2 hours they are back . What can be an issue?
thanks

bazzle's picture

It just seems flakey sometimes :(

Use pvoutput.org instead :)

Bazzle

sem's picture

Problem is not really with upload but with sensors reporting. Last day they are stable
but before they dropped every 4-6 hours

P.S. I didn't get you remark about pvoutput.org. How do you upload there ?

icarus75's picture

I think you're referring to your zero readings on Friday and Saturday morning. Flukso works with 'pulses' internally, even when using current clamps. When your consumption equals zero, nothing will be reported to the Flukso server until the next Wh is consumed.

You can check whether your FLM is working properly by looking at the LEDs. If the heartbeat LED is blinking and the globe LED is lit, then the FLM is operational and can connect to flukso.net.

sem's picture

I don't have zero consumption :) never. Problem dissapeared for now. But i was a bit confused on saturday. I check log files on the box and the hearbeat was ok but no pulses in the log. Or sometimes pulse from gaz sensor but not from electricity one.

icarus75's picture

Well, you might not have zero consumption, but there were zero readings for your electricity consumption. If you cannot explain these zero readings, then check whether the current clamp is properly closed (it most likely is) and whether the current clamp lead wire is firmly connected to the screw terminal (could be the case).

sem's picture

I'll check
because after almost 3 days of work I lost pulses again.
Would try reboot tonight see what happens

icarus75's picture

Seems like the heartbeats have stopped coming in as well. Hold off on the rebooting. Let's try to pinpoint the root issue first.

sem's picture

yep i see that heartbeats are stopped too
now I see version 998** in dashboard. don't know what this means

sem's picture

Any idea were to look to detect a problem ? i didn't reboot device yet. Just connect with ssh and find out it's very very slow for some reason.

sem's picture

device was very slow even in telnet session. I tried to restart fluksod . Didn't help
I did a reboot
10 minutes reporting and nothing again
would try powercycle now

icarus75's picture

1/ If the problem occurs again, please leave the system as is. Rebooting or power-cycling will prevent us from finding the root cause.
2/ I suspect you've ssh'ed into the FLM as telnet is not enabled by default.
3/ Did you try the 'top' command to see which processes were consuming lots of RAM/CPU?

sem's picture

yep it was ssh :)
I checked top and don't find anything strange. fluksod was on top but it was using like 10 % of cpu only
after powercycle it stable again
but before that it was even impossible to access flm via http