Readings spasmodic

by bazzle on

Having issues with readings. Not always showing today.
Doe this log make sense to any one?

Nov 5 05:50:25 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPACK(br-lan) 192.168.255.197 00:24:81:6d:b4:f1 MINI
Nov 5 05:50:33 flukso-4d93ce kern.info kernel: [ 339.530000] eth0: Configuring MAC for full duplex
Nov 5 05:50:34 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPREQUEST(br-lan) 192.168.255.197 00:24:81:6d:b4:f1
Nov 5 05:50:34 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPACK(br-lan) 192.168.255.197 00:24:81:6d:b4:f1 MINI
Nov 5 05:50:41 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPINFORM(br-lan) 192.168.255.197 00:24:81:6d:b4:f1
Nov 5 05:50:41 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPACK(br-lan) 192.168.255.197 00:24:81:6d:b4:f1 MINI
Nov 5 05:51:11 flukso-4d93ce user.notice root: toggled to eth mode
Nov 5 05:51:11 flukso-4d93ce kern.info kernel: [ 377.260000] device eth0 left promiscuous mode
Nov 5 05:51:11 flukso-4d93ce kern.info kernel: [ 377.260000] br-lan: port 1(eth0) entered disabled state
Nov 5 05:51:11 flukso-4d93ce daemon.notice netifd: Interface 'lan' is now down
Nov 5 05:51:11 flukso-4d93ce daemon.info avahi-daemon[795]: Withdrawing address record for 192.168.255.1 on br-lan.
Nov 5 05:51:11 flukso-4d93ce daemon.info avahi-daemon[795]: Leaving mDNS multicast group on interface br-lan.IPv4 with address 192.168.255.1.
Nov 5 05:51:11 flukso-4d93ce daemon.info avahi-daemon[795]: Interface br-lan.IPv4 no longer relevant for mDNS.
Nov 5 05:51:12 flukso-4d93ce daemon.notice netifd: wan (676): Sending renew...
Nov 5 05:51:12 flukso-4d93ce daemon.notice netifd: wan (676): Received SIGTERM
Nov 5 05:51:12 flukso-4d93ce daemon.notice netifd: Interface 'wan' is now down
Nov 5 05:51:12 flukso-4d93ce daemon.info avahi-daemon[795]: Withdrawing address record for 192.168.0.29 on wlan0.
Nov 5 05:51:12 flukso-4d93ce daemon.info avahi-daemon[795]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.29.
Nov 5 05:51:12 flukso-4d93ce daemon.info avahi-daemon[795]: Interface wlan0.IPv4 no longer relevant for mDNS.
Nov 5 05:51:13 flukso-4d93ce kern.info kernel: [ 379.270000] wlan0: deauthenticating from 10:0d:7f:d4:b3:68 by local choice (reason=3)
Nov 5 05:51:13 flukso-4d93ce daemon.info supd[814]: Received event DISCONNECTED for wlan0
Nov 5 05:51:14 flukso-4d93ce daemon.notice netifd: wan (1028): udhcpc (v1.19.4) started
Nov 5 05:51:14 flukso-4d93ce daemon.notice netifd: wan (1028): Sending discover...
Nov 5 05:51:17 flukso-4d93ce daemon.notice netifd: wan (1028): Sending discover...
Nov 5 05:51:20 flukso-4d93ce daemon.notice netifd: wan (1028): Sending discover...
Nov 5 05:51:26 flukso-4d93ce daemon.warn dnsmasq[787]: no servers found in /tmp/resolv.conf.auto, will retry
Nov 5 05:51:26 flukso-4d93ce user.err heartbeat[1072]: POST https://api.flukso.net/device/4d93ceb43bd2b2ef3a262d241f529838: -2
Nov 5 05:51:26 flukso-4d93ce user.err heartbeat[1072]: Name or service not known
Nov 5 05:52:03 flukso-4d93ce daemon.warn dnsmasq-dhcp[787]: DHCP packet received on eth0 which has no address
Nov 5 05:52:06 flukso-4d93ce daemon.warn dnsmasq-dhcp[787]: DHCP packet received on eth0 which has no address
Nov 5 05:52:27 flukso-4d93ce user.notice root: toggled to wifi mode
Nov 5 05:52:27 flukso-4d93ce kern.info kernel: [ 453.530000] device eth0 entered promiscuous mode
Nov 5 05:52:27 flukso-4d93ce kern.info kernel: [ 453.530000] br-lan: port 1(eth0) entered forwarding state
Nov 5 05:52:27 flukso-4d93ce kern.info kernel: [ 453.530000] br-lan: port 1(eth0) entered forwarding state
Nov 5 05:52:27 flukso-4d93ce daemon.info avahi-daemon[795]: Joining mDNS multicast group on interface br-lan.IPv4 with address 192.168.255.1.
Nov 5 05:52:27 flukso-4d93ce daemon.info avahi-daemon[795]: New relevant interface br-lan.IPv4 for mDNS.
Nov 5 05:52:27 flukso-4d93ce daemon.info avahi-daemon[795]: Registering new address record for 192.168.255.1 on br-lan.IPv4.
Nov 5 05:52:27 flukso-4d93ce daemon.notice netifd: Interface 'lan' is now up
Nov 5 05:52:28 flukso-4d93ce daemon.notice netifd: wan (1028): Received SIGTERM
Nov 5 05:52:28 flukso-4d93ce daemon.notice netifd: Interface 'wan' is now down
Nov 5 05:52:29 flukso-4d93ce kern.info kernel: [ 455.530000] br-lan: port 1(eth0) entered forwarding state
Nov 5 05:52:29 flukso-4d93ce user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Nov 5 05:52:36 flukso-4d93ce kern.info kernel: [ 462.590000] wlan0: authenticate with 10:0d:7f:d4:b3:68
Nov 5 05:52:36 flukso-4d93ce kern.info kernel: [ 462.600000] wlan0: send auth to 10:0d:7f:d4:b3:68 (try 1/3)
Nov 5 05:52:36 flukso-4d93ce kern.info kernel: [ 462.610000] wlan0: authenticated
Nov 5 05:52:36 flukso-4d93ce kern.info kernel: [ 462.660000] wlan0: associate with 10:0d:7f:d4:b3:68 (try 1/3)
Nov 5 05:52:36 flukso-4d93ce kern.info kernel: [ 462.660000] wlan0: RX AssocResp from 10:0d:7f:d4:b3:68 (capab=0x411 status=0 aid=1)
Nov 5 05:52:36 flukso-4d93ce kern.info kernel: [ 462.670000] wlan0: associated
Nov 5 05:52:37 flukso-4d93ce daemon.info supd[814]: Received event CONNECTED for wlan0
Nov 5 05:52:39 flukso-4d93ce daemon.notice netifd: wan (1313): udhcpc (v1.19.4) started
Nov 5 05:52:40 flukso-4d93ce daemon.notice netifd: wan (1313): Sending discover...
Nov 5 05:52:40 flukso-4d93ce daemon.notice netifd: wan (1313): Sending select for 192.168.0.29...
Nov 5 05:52:41 flukso-4d93ce daemon.notice netifd: wan (1313): Lease of 192.168.0.29 obtained, lease time 3600
Nov 5 05:52:41 flukso-4d93ce daemon.info avahi-daemon[795]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.29.
Nov 5 05:52:41 flukso-4d93ce daemon.info avahi-daemon[795]: New relevant interface wlan0.IPv4 for mDNS.
Nov 5 05:52:41 flukso-4d93ce daemon.info avahi-daemon[795]: Registering new address record for 192.168.0.29 on wlan0.IPv4.
Nov 5 05:52:41 flukso-4d93ce daemon.notice netifd: Interface 'wan' is now up
Nov 5 05:52:42 flukso-4d93ce user.notice firewall: Reloading firewall due to ifup of wan (wlan0)
Nov 5 05:52:50 flukso-4d93ce daemon.info dnsmasq[787]: reading /tmp/resolv.conf.auto
Nov 5 05:52:50 flukso-4d93ce daemon.info dnsmasq[787]: using nameserver 198.142.235.14#53
Nov 5 05:52:50 flukso-4d93ce daemon.info dnsmasq[787]: using nameserver 208.67.220.220#53
Nov 5 05:52:50 flukso-4d93ce daemon.info dnsmasq[787]: using nameserver 208.67.220.222#53
Nov 5 05:52:50 flukso-4d93ce daemon.info dnsmasq[787]: using local addresses only for domain lan
Nov 5 05:52:52 flukso-4d93ce user.info heartbeat[1345]: POST https://api.flukso.net/device/4d93ceb43bd2b2ef3a262d241f529838: 200
Nov 5 06:00:01 flukso-4d93ce cron.info crond[667]: crond: USER root pid 1395 cmd /usr/bin/fcheck
Nov 5 06:01:01 flukso-4d93ce cron.info crond[667]: crond: USER root pid 1441 cmd /usr/bin/heartbeat 0
Nov 5 06:01:05 flukso-4d93ce user.info heartbeat[1442]: POST https://api.flukso.net/device/4d93ceb43bd2b2ef3a262d241f529838: 200
Nov 5 06:01:31 flukso-4d93ce daemon.info fluksod[821]: processed pulse 8492153f1144dba9fecf777466fdc508:1415167291:4033247
Nov 5 06:01:34 flukso-4d93ce daemon.info fluksod[821]: POST https://api.flukso.net/sensor/8492153f1144dba9fecf777466fdc508: 200
Nov 5 06:02:12 flukso-4d93ce daemon.info fluksod[821]: processed pulse b4a04e554f01781b518eeae703abebb8:1415167332:3914153
Nov 5 06:02:14 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPINFORM(br-lan) 192.168.255.197 00:24:81:6d:b4:f1
Nov 5 06:02:14 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPACK(br-lan) 192.168.255.197 00:24:81:6d:b4:f1 MINI
Nov 5 06:06:08 flukso-4d93ce daemon.info fluksod[821]: processed pulse b4a04e554f01781b518eeae703abebb8:1415167568:3914255
Nov 5 06:10:35 flukso-4d93ce kern.info kernel: [ 1541.780000] wlan0: deauthenticating from 10:0d:7f:d4:b3:68 by local choice (reason=3)
Nov 5 06:10:35 flukso-4d93ce daemon.info avahi-daemon[795]: Interface wlan0.IPv4 no longer relevant for mDNS.
Nov 5 06:10:35 flukso-4d93ce daemon.info avahi-daemon[795]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.29.
Nov 5 06:10:35 flukso-4d93ce daemon.info avahi-daemon[795]: Withdrawing address record for 192.168.0.29 on wlan0.
Nov 5 06:10:36 flukso-4d93ce daemon.info supd[814]: Received event DISCONNECTED for wlan0
Nov 5 06:10:37 flukso-4d93ce daemon.notice netifd: wan (1313): udhcpc: SIOCGIFINDEX: No such device
Nov 5 06:10:37 flukso-4d93ce daemon.notice netifd: wan (1313): Received SIGTERM
Nov 5 06:10:37 flukso-4d93ce daemon.notice netifd: Interface 'wan' is now down
Nov 5 06:10:42 flukso-4d93ce kern.info kernel: [ 1548.090000] wlan0: authenticate with 10:0d:7f:d4:b3:68
Nov 5 06:10:42 flukso-4d93ce kern.info kernel: [ 1548.110000] wlan0: send auth to 10:0d:7f:d4:b3:68 (try 1/3)
Nov 5 06:10:42 flukso-4d93ce kern.info kernel: [ 1548.120000] wlan0: authenticated
Nov 5 06:10:42 flukso-4d93ce kern.info kernel: [ 1548.160000] wlan0: associate with 10:0d:7f:d4:b3:68 (try 1/3)
Nov 5 06:10:42 flukso-4d93ce kern.info kernel: [ 1548.160000] wlan0: RX AssocResp from 10:0d:7f:d4:b3:68 (capab=0x411 status=0 aid=1)
Nov 5 06:10:42 flukso-4d93ce kern.info kernel: [ 1548.170000] wlan0: associated
Nov 5 06:10:42 flukso-4d93ce daemon.info supd[814]: Received event CONNECTED for wlan0
Nov 5 06:10:47 flukso-4d93ce daemon.info avahi-daemon[795]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.29.
Nov 5 06:10:47 flukso-4d93ce daemon.info avahi-daemon[795]: New relevant interface wlan0.IPv4 for mDNS.
Nov 5 06:10:47 flukso-4d93ce daemon.info avahi-daemon[795]: Registering new address record for 192.168.0.29 on wlan0.IPv4.
Nov 5 06:10:47 flukso-4d93ce daemon.warn dnsmasq[787]: no servers found in /tmp/resolv.conf.auto, will retry
Nov 5 06:10:47 flukso-4d93ce daemon.notice netifd: Interface 'wan' is now up
Nov 5 06:10:47 flukso-4d93ce daemon.info dnsmasq[787]: reading /tmp/resolv.conf.auto
Nov 5 06:10:47 flukso-4d93ce daemon.info dnsmasq[787]: using nameserver 198.142.235.14#53
Nov 5 06:10:47 flukso-4d93ce daemon.info dnsmasq[787]: using nameserver 208.67.220.220#53
Nov 5 06:10:47 flukso-4d93ce daemon.info dnsmasq[787]: using nameserver 208.67.220.222#53
Nov 5 06:10:47 flukso-4d93ce daemon.info dnsmasq[787]: using local addresses only for domain lan
Nov 5 06:10:48 flukso-4d93ce user.notice firewall: Reloading firewall due to ifup of wan (wlan0)
Nov 5 06:12:17 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPINFORM(br-lan) 192.168.255.197 00:24:81:6d:b4:f1
Nov 5 06:12:17 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPACK(br-lan) 192.168.255.197 00:24:81:6d:b4:f1 MINI
Nov 5 06:15:01 flukso-4d93ce cron.info crond[667]: crond: USER root pid 1715 cmd /usr/bin/fcheck
Nov 5 06:15:26 flukso-4d93ce daemon.info supd[814]: Received event DISCONNECTED for wlan0
Nov 5 06:16:11 flukso-4d93ce kern.info kernel: [ 1877.680000] wlan0: authenticate with 10:0d:7f:d4:b3:68
Nov 5 06:16:11 flukso-4d93ce kern.info kernel: [ 1877.690000] wlan0: send auth to 10:0d:7f:d4:b3:68 (try 1/3)
Nov 5 06:16:11 flukso-4d93ce kern.info kernel: [ 1877.690000] wlan0: authenticated
Nov 5 06:16:11 flukso-4d93ce kern.info kernel: [ 1877.720000] wlan0: associate with 10:0d:7f:d4:b3:68 (try 1/3)
Nov 5 06:16:11 flukso-4d93ce kern.info kernel: [ 1877.720000] wlan0: RX AssocResp from 10:0d:7f:d4:b3:68 (capab=0x411 status=0 aid=1)
Nov 5 06:16:11 flukso-4d93ce kern.info kernel: [ 1877.730000] wlan0: associated
Nov 5 06:16:12 flukso-4d93ce daemon.info supd[814]: Received event CONNECTED for wlan0
Nov 5 06:20:39 flukso-4d93ce daemon.info fluksod[821]: processed pulse b4a04e554f01781b518eeae703abebb8:1415168439:3914331
Nov 5 06:20:42 flukso-4d93ce daemon.info fluksod[821]: POST https://api.flukso.net/sensor/b4a04e554f01781b518eeae703abebb8: 200
Nov 5 06:21:27 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPINFORM(br-lan) 192.168.255.197 00:24:81:6d:b4:f1
Nov 5 06:21:27 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPACK(br-lan) 192.168.255.197 00:24:81:6d:b4:f1 MINI
Nov 5 06:21:31 flukso-4d93ce daemon.info fluksod[821]: processed pulse 8492153f1144dba9fecf777466fdc508:1415168491:4033356
Nov 5 06:22:48 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPINFORM(br-lan) 192.168.255.197 00:24:81:6d:b4:f1
Nov 5 06:22:48 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPACK(br-lan) 192.168.255.197 00:24:81:6d:b4:f1 MINI
Nov 5 06:29:05 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPINFORM(br-lan) 192.168.255.197 00:24:81:6d:b4:f1
Nov 5 06:29:05 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPACK(br-lan) 192.168.255.197 00:24:81:6d:b4:f1 MINI
Nov 5 06:30:01 flukso-4d93ce cron.info crond[667]: crond: USER root pid 2661 cmd /usr/bin/fcheck
Nov 5 06:32:50 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPINFORM(br-lan) 192.168.255.197 00:24:81:6d:b4:f1
Nov 5 06:32:50 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPACK(br-lan) 192.168.255.197 00:24:81:6d:b4:f1 MINI
Nov 5 06:32:51 flukso-4d93ce daemon.info fluksod[821]: processed pulse b4a04e554f01781b518eeae703abebb8:1415169171:3914381
Nov 5 06:32:54 flukso-4d93ce daemon.info fluksod[821]: POST https://api.flukso.net/sensor/8492153f1144dba9fecf777466fdc508: 200
Nov 5 06:32:54 flukso-4d93ce daemon.info fluksod[821]: POST https://api.flukso.net/sensor/b4a04e554f01781b518eeae703abebb8: 200
Nov 5 06:36:34 flukso-4d93ce daemon.info fluksod[821]: processed pulse b4a04e554f01781b518eeae703abebb8:1415169394:3914393
Nov 5 06:37:25 flukso-4d93ce daemon.info fluksod[821]: processed pulse b4a04e554f01781b518eeae703abebb8:1415169445:3914407
Nov 5 06:37:33 flukso-4d93ce daemon.info fluksod[821]: processed pulse b4a04e554f01781b518eeae703abebb8:1415169453:3914412
Nov 5 06:39:33 flukso-4d93ce kern.info kernel: [ 3279.020000] eth0: Configuring MAC for full duplex
Nov 5 06:39:37 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPREQUEST(br-lan) 192.168.255.197 00:24:81:6d:b4:f1
Nov 5 06:39:37 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPACK(br-lan) 192.168.255.197 00:24:81:6d:b4:f1 MINI
Nov 5 06:39:43 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPINFORM(br-lan) 192.168.255.197 00:24:81:6d:b4:f1
Nov 5 06:39:43 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPACK(br-lan) 192.168.255.197 00:24:81:6d:b4:f1 MINI
Nov 5 06:41:04 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPINFORM(br-lan) 192.168.255.197 00:24:81:6d:b4:f1
Nov 5 06:41:04 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPACK(br-lan) 192.168.255.197 00:24:81:6d:b4:f1 MINI
Nov 5 06:43:07 flukso-4d93ce daemon.info fluksod[821]: processed pulse 8492153f1144dba9fecf777466fdc508:1415169787:4033415
Nov 5 06:43:10 flukso-4d93ce daemon.info fluksod[821]: POST https://api.flukso.net/sensor/b4a04e554f01781b518eeae703abebb8: 200
Nov 5 06:43:11 flukso-4d93ce daemon.info fluksod[821]: POST https://api.flukso.net/sensor/8492153f1144dba9fecf777466fdc508: 200
Nov 5 06:45:01 flukso-4d93ce cron.info crond[667]: crond: USER root pid 7982 cmd /usr/bin/fcheck
Nov 5 06:50:00 flukso-4d93ce daemon.info fluksod[821]: processed pulse b4a04e554f01781b518eeae703abebb8:1415170200:3914585
Nov 5 06:50:03 flukso-4d93ce daemon.info fluksod[821]: POST https://api.flukso.net/sensor/b4a04e554f01781b518eeae703abebb8: 200
Nov 5 06:51:06 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPINFORM(br-lan) 192.168.255.197 00:24:81:6d:b4:f1
Nov 5 06:51:06 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPACK(br-lan) 192.168.255.197 00:24:81:6d:b4:f1 MINI
Nov 5 06:52:31 flukso-4d93ce kern.info kernel: [ 4057.570000] eth0: Configuring MAC for full duplex
Nov 5 06:52:38 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPDISCOVER(br-lan) 00:21:00:dd:c6:ca
Nov 5 06:52:38 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPOFFER(br-lan) 192.168.255.164 00:21:00:dd:c6:ca
Nov 5 06:52:38 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPREQUEST(br-lan) 192.168.0.19 00:21:00:dd:c6:ca
Nov 5 06:52:38 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPNAK(br-lan) 192.168.0.19 00:21:00:dd:c6:ca wrong server-ID
Nov 5 06:52:46 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPINFORM(br-lan) 192.168.0.19 00:21:00:dd:c6:ca
Nov 5 06:52:46 flukso-4d93ce daemon.info dnsmasq-dhcp[787]: DHCPACK(br-lan) 192.168.0.19 00:21:00:dd:c6:ca MINI

‹ Din rail s0 meter problems Averaging ›
bazzle's picture
bazzle |

Well.. seems to be reading ok now. Just a hiccup?
Lets give it a day of usage and solar :).

petur's picture
petur |

Looks like it is dropping off the wlan - bad signal?

I remember having something similar, turned out the neighbour had installed a wireless AP the other side of the wall, on the same channel. So maybe check how the wireless is doing at the location...

bazzle's picture
bazzle |

Thanks for the heads up.
Ill run "inSSIDer" to see if anything else is running during the day when Im not home..

bazzle's picture
bazzle |

... same again. Nothing else shows with signal anywhere nearby :(

No output to Flukso at all this time? 13.30 here.

bazzle's picture
bazzle |

I have reset, tried 2 SSID'd, good signal 42/70. I can get to Flukso site thru laptop and cat5 lead.
All lights are on, all services ticked, heart beat flashing, sys status and ping OK on 192.168.255.1

Log similar to above :(

Absolutely stuck.. Im guessing something has failed in Flukso...hope not.

Bart can you get into my Flukso?

Baz

bazzle's picture
bazzle |

Bart

I tried to send you an email but got this message:

Unable to send e-mail. Please contact the site administrator if the problem persists.
Im guessing your the site Administrator....

bazzle's picture
bazzle |

f1144dba9fecf777466fdc508:1415252044:4051576
Nov 6 05:34:08 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252048:4051577
Nov 6 05:34:12 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252052:4051578
Nov 6 05:34:13 flukso-4d93ce daemon.info fluksod[799]: processed pulse b4a04e554f01781b518eeae703abebb8:1415252053:3923215
Nov 6 05:34:15 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252055:4051579
Nov 6 05:34:19 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252059:4051580
Nov 6 05:34:23 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252063:4051581
Nov 6 05:34:26 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252066:4051582
Nov 6 05:34:27 flukso-4d93ce daemon.info fluksod[799]: processed pulse b4a04e554f01781b518eeae703abebb8:1415252067:3923216
Nov 6 05:34:30 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252070:4051583
Nov 6 05:34:34 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252074:4051584
Nov 6 05:34:38 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252078:4051585
Nov 6 05:34:41 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252081:4051586
Nov 6 05:34:42 flukso-4d93ce daemon.info fluksod[799]: processed pulse b4a04e554f01781b518eeae703abebb8:1415252082:3923217
Nov 6 05:34:45 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252085:4051587
Nov 6 05:34:49 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252089:4051588
Nov 6 05:34:53 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252093:4051589
Nov 6 05:34:56 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252096:4051590
Nov 6 05:34:56 flukso-4d93ce daemon.info fluksod[799]: processed pulse b4a04e554f01781b518eeae703abebb8:1415252096:3923218
Nov 6 05:35:00 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252100:4051591
Nov 6 05:35:04 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252104:4051592
Nov 6 05:35:08 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252108:4051593
Nov 6 05:35:09 flukso-4d93ce daemon.info fluksod[799]: processed pulse b4a04e554f01781b518eeae703abebb8:1415252109:3923219
Nov 6 05:35:12 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252112:4051594
Nov 6 05:35:16 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252116:4051595
Nov 6 05:35:20 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252120:4051596
Nov 6 05:35:23 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252123:4051597
Nov 6 05:35:23 flukso-4d93ce daemon.info fluksod[799]: processed pulse b4a04e554f01781b518eeae703abebb8:1415252123:3923220
Nov 6 05:35:27 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252127:4051598
Nov 6 05:35:31 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252131:4051599
Nov 6 05:35:35 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252135:4051600
Nov 6 05:35:36 flukso-4d93ce daemon.info fluksod[799]: processed pulse b4a04e554f01781b518eeae703abebb8:1415252136:3923221
Nov 6 05:35:38 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252138:4051601
Nov 6 05:35:42 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252142:4051602
Nov 6 05:35:46 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252146:4051603
Nov 6 05:35:50 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252150:4051604
Nov 6 05:35:50 flukso-4d93ce daemon.info fluksod[799]: processed pulse b4a04e554f01781b518eeae703abebb8:1415252150:3923222
Nov 6 05:35:54 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252154:4051605
Nov 6 05:35:57 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252157:4051606
Nov 6 05:36:01 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252161:4051607
Nov 6 05:36:04 flukso-4d93ce daemon.info fluksod[799]: processed pulse b4a04e554f01781b518eeae703abebb8:1415252164:3923223
Nov 6 05:36:05 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252165:4051608
Nov 6 05:36:09 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252169:4051609
Nov 6 05:36:13 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252173:4051610
Nov 6 05:36:16 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252176:4051611
Nov 6 05:36:17 flukso-4d93ce daemon.info fluksod[799]: processed pulse b4a04e554f01781b518eeae703abebb8:1415252177:3923224
Nov 6 05:36:20 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252180:4051612
Nov 6 05:36:24 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252184:4051613
Nov 6 05:36:28 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252188:4051614
Nov 6 05:36:30 flukso-4d93ce daemon.info fluksod[799]: processed pulse b4a04e554f01781b518eeae703abebb8:1415252190:3923225
Nov 6 05:36:32 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252192:4051615
Nov 6 05:36:36 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPINFORM(br-lan) 192.168.0.14 08:11:96:91:a5:68
Nov 6 05:36:36 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPACK(br-lan) 192.168.0.14 08:11:96:91:a5:68 Bazzle-PC
Nov 6 05:36:36 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252196:4051616
Nov 6 05:36:39 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252199:4051617
Nov 6 05:36:43 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252203:4051618
Nov 6 05:36:43 flukso-4d93ce daemon.info fluksod[799]: processed pulse b4a04e554f01781b518eeae703abebb8:1415252203:3923226
Nov 6 05:36:47 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252207:4051619
Nov 6 05:36:51 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252211:4051620
Nov 6 05:36:55 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252215:4051621
Nov 6 05:36:57 flukso-4d93ce daemon.info fluksod[799]: processed pulse b4a04e554f01781b518eeae703abebb8:1415252217:3923227
Nov 6 05:36:59 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252219:4051622
Nov 6 05:37:02 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252222:4051623
Nov 6 05:37:05 flukso-4d93ce daemon.info fluksod[799]: POST https://api.flukso.net/sensor/8492153f1144dba9fecf777466fdc508: 200
Nov 6 05:37:06 flukso-4d93ce daemon.info fluksod[799]: POST https://api.flukso.net/sensor/b4a04e554f01781b518eeae703abebb8: 200
Nov 6 05:37:06 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252226:4051624
Nov 6 05:37:56 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPINFORM(br-lan) 192.168.0.14 08:11:96:91:a5:68
Nov 6 05:37:56 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPACK(br-lan) 192.168.0.14 08:11:96:91:a5:68 Bazzle-PC
Nov 6 05:38:22 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPREQUEST(br-lan) 192.168.0.32 5c:95:ae:ae:c9:5a
Nov 6 05:38:22 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPNAK(br-lan) 192.168.0.32 5c:95:ae:ae:c9:5a wrong address
Nov 6 05:38:22 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPDISCOVER(br-lan) 5c:95:ae:ae:c9:5a
Nov 6 05:38:22 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPOFFER(br-lan) 192.168.255.240 5c:95:ae:ae:c9:5a
Nov 6 05:38:23 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPREQUEST(br-lan) 192.168.255.240 5c:95:ae:ae:c9:5a
Nov 6 05:38:23 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPACK(br-lan) 192.168.255.240 5c:95:ae:ae:c9:5a Bazzles-iPhone
Nov 6 05:39:03 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252343:4051655
Nov 6 05:39:06 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252346:4051656
Nov 6 05:39:09 flukso-4d93ce daemon.info fluksod[799]: processed pulse b4a04e554f01781b518eeae703abebb8:1415252349:3923237
Nov 6 05:39:10 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252350:4051657
Nov 6 05:39:14 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252354:4051658
Nov 6 05:39:18 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252358:4051659
Nov 6 05:39:21 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252361:4051660
Nov 6 05:39:23 flukso-4d93ce daemon.info fluksod[799]: processed pulse b4a04e554f01781b518eeae703abebb8:1415252363:3923238
Nov 6 05:39:25 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252365:4051661
Nov 6 05:39:59 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPREQUEST(br-lan) 192.168.0.31 c8:b5:b7:21:80:c4
Nov 6 05:39:59 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPNAK(br-lan) 192.168.0.31 c8:b5:b7:21:80:c4 wrong network
Nov 6 05:40:17 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPINFORM(br-lan) 192.168.0.14 08:11:96:91:a5:68
Nov 6 05:40:17 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPACK(br-lan) 192.168.0.14 08:11:96:91:a5:68 Bazzle-PC
Nov 6 05:40:41 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252441:4051680
Nov 6 05:40:44 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252444:4051681
Nov 6 05:40:47 flukso-4d93ce daemon.info fluksod[799]: processed pulse b4a04e554f01781b518eeae703abebb8:1415252447:3923244
Nov 6 05:40:49 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252449:4051682
Nov 6 05:40:53 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252453:4051683
Nov 6 05:40:58 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252458:4051684
Nov 6 05:41:02 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252462:4051685
Nov 6 05:41:02 flukso-4d93ce daemon.info fluksod[799]: processed pulse b4a04e554f01781b518eeae703abebb8:1415252462:3923245
Nov 6 05:41:07 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252467:4051686
Nov 6 05:42:07 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252527:4051699
Nov 6 05:42:10 flukso-4d93ce daemon.info fluksod[799]: POST https://api.flukso.net/sensor/8492153f1144dba9fecf777466fdc508: 200
Nov 6 05:42:10 flukso-4d93ce daemon.info fluksod[799]: POST https://api.flukso.net/sensor/b4a04e554f01781b518eeae703abebb8: 200
Nov 6 05:42:34 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252554:4051704
Nov 6 05:42:40 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252560:4051705
Nov 6 05:42:42 flukso-4d93ce daemon.info fluksod[799]: processed pulse b4a04e554f01781b518eeae703abebb8:1415252562:3923251
Nov 6 05:42:45 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252565:4051706
Nov 6 05:42:51 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252571:4051707
Nov 6 05:42:56 flukso-4d93ce daemon.info fluksod[799]: processed pulse 8492153f1144dba9fecf777466fdc508:1415252576:4051708
Nov 6 05:45:01 flukso-4d93ce cron.info crond[667]: crond: USER root pid 871 cmd /usr/bin/fcheck
Nov 6 05:45:54 flukso-4d93ce daemon.notice netifd: wan (675): Sending renew...
Nov 6 05:45:55 flukso-4d93ce daemon.notice netifd: wan (675): Lease of 192.168.0.29 obtained, lease time 3600
Nov 6 05:46:57 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPINFORM(br-lan) 192.168.0.14 08:11:96:91:a5:68
Nov 6 05:46:57 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPACK(br-lan) 192.168.0.14 08:11:96:91:a5:68 Bazzle-PC
Nov 6 05:48:20 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPINFORM(br-lan) 192.168.0.14 08:11:96:91:a5:68
Nov 6 05:48:20 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPACK(br-lan) 192.168.0.14 08:11:96:91:a5:68 Bazzle-PC
Nov 6 05:48:46 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPREQUEST(br-lan) 192.168.255.240 5c:95:ae:ae:c9:5a
Nov 6 05:48:46 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPACK(br-lan) 192.168.255.240 5c:95:ae:ae:c9:5a Bazzles-iPhone
Nov 6 05:48:48 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPREQUEST(br-lan) 192.168.0.32 5c:95:ae:ae:c9:5a
Nov 6 05:48:48 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPNAK(br-lan) 192.168.0.32 5c:95:ae:ae:c9:5a wrong address
Nov 6 05:48:48 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPDISCOVER(br-lan) 5c:95:ae:ae:c9:5a
Nov 6 05:48:48 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPOFFER(br-lan) 192.168.255.240 5c:95:ae:ae:c9:5a
Nov 6 05:48:49 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPREQUEST(br-lan) 192.168.255.240 5c:95:ae:ae:c9:5a
Nov 6 05:48:49 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPACK(br-lan) 192.168.255.240 5c:95:ae:ae:c9:5a Bazzles-iPhone
Nov 6 05:50:20 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPINFORM(br-lan) 192.168.0.14 08:11:96:91:a5:68
Nov 6 05:50:20 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPACK(br-lan) 192.168.0.14 08:11:96:91:a5:68 Bazzle-PC
Nov 6 05:51:40 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPINFORM(br-lan) 192.168.0.14 08:11:96:91:a5:68
Nov 6 05:51:40 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPACK(br-lan) 192.168.0.14 08:11:96:91:a5:68 Bazzle-PC
Nov 6 05:52:14 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPDISCOVER(br-lan) 00:21:00:dd:c6:ca
Nov 6 05:52:14 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPOFFER(br-lan) 192.168.255.164 00:21:00:dd:c6:ca
Nov 6 05:52:14 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPREQUEST(br-lan) 192.168.0.19 00:21:00:dd:c6:ca
Nov 6 05:52:14 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPNAK(br-lan) 192.168.0.19 00:21:00:dd:c6:ca wrong server-ID
Nov 6 05:52:22 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPINFORM(br-lan) 192.168.0.19 00:21:00:dd:c6:ca
Nov 6 05:52:22 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPACK(br-lan) 192.168.0.19 00:21:00:dd:c6:ca MINI
Nov 6 05:53:06 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPINFORM(br-lan) 192.168.0.14 08:11:96:91:a5:68
Nov 6 05:53:06 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPACK(br-lan) 192.168.0.14 08:11:96:91:a5:68 Bazzle-PC
Nov 6 05:53:27 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPINFORM(br-lan) 192.168.0.19 00:21:00:dd:c6:ca
Nov 6 05:53:27 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPACK(br-lan) 192.168.0.19 00:21:00:dd:c6:ca MINI

icarus75's picture
icarus75 |

Not sure what your network setup is, but if you take a look at the dhcp entries in the last syslog dump, then it seems you're using two IP-networks (192.168.255.0 and 192.168.0.0) on the same LAN? That's bound to give you a headache:

  1. Nov 6 05:48:48 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPNAK(br-lan) 192.168.0.32 5c:95:ae:ae:c9:5a wrong address
  2. Nov 6 05:52:14 flukso-4d93ce daemon.info dnsmasq-dhcp[769]: DHCPNAK(br-lan) 192.168.0.19 00:21:00:dd:c6:ca wrong server-ID

Then again, this trace shows that the FLM is successfully POSTing data to the Flukso server (status 200):
  1. Nov 6 05:42:10 flukso-4d93ce daemon.info fluksod[799]: POST https:/api.flukso.net/sensor/8492153f1144dba9fecf777466fdc508: 200

petur's picture
petur |

Nice catch, I had totally missed that...

bazzle's picture
bazzle |

Strange. Dont know whats going on there?
I dont understand exactly what it means.
I have 2 wireless routers but both have never been touched.
I can set the Flukso to use either. Was working fine until the last 2 days.

bazzle's picture
bazzle |

My wireless router has the 1st lan setting as 192.168.0.1 It allocates addys from 192.168.0.10. Dont know where the 192.168.0.0 fits in ?

bazzle's picture
bazzle |

Bart

Im a little bit stuck with this. Only started happening over last 2 days. Nothing has been changed on my network or associated parts. Everthing has been rebooted last night.
I opened flm to check pcb connection, aerial etc. All seems to be ok
Ive noticed its only sending data from one of the two senors every hour or so.
Both are pulse type and flashing away nicely as current flows thru them.
Can you look into my Flukso externally and see if all is as it should be ?

Ta Bazzle

bazzle's picture
bazzle |

There is another issue as well. I cant log into the flm all the time either. It just times out. Makes reading the syslog very frustrating.
Im going to try a complete reset and reboot.7:42 pm here.

Ok. Now 8:40

Status
synchronisation with sensor board failed Internal error. Please report this error message to Flukso.

Now Im really lost :)

Jan 1 00:01:13 flukso daemon.info avahi-daemon[765]: Server startup complete. Host name is flukso.local. Local service cookie is 4290213216.
Jan 1 00:01:16 flukso user.info sysinit: setting up led wlan
Jan 1 00:01:17 flukso daemon.info avahi-daemon[765]: Service "Secure Shell on flukso" (/etc/avahi/services/ssh.service) successfully established.
Jan 1 00:01:17 flukso daemon.info avahi-daemon[765]: Service "MQTT Broker on flukso" (/etc/avahi/services/mqtt.service) successfully established.
Jan 1 00:01:17 flukso daemon.info avahi-daemon[765]: Service "Web Server on flukso" (/etc/avahi/services/http.service) successfully established.
Jan 1 00:01:17 flukso daemon.info avahi-daemon[765]: Service "Flukso RESTful API on flukso" (/etc/avahi/services/flukso.service) successfully established.
Jan 1 00:01:20 flukso user.notice root: copying flukso package version into system uci file at firstboot
Jan 1 00:01:45 flukso user.notice root: configuring flukso device and sensor ids at firstboot
Jan 1 00:02:29 flukso user.notice root: flashing the sensor board at firstboot
Jan 1 00:02:30 flukso user.info sysinit: Daemon returned 0 as return value.
Jan 1 00:02:30 flukso daemon.info supd[1139]: Sucessfully started with DEAMON=supd and DAEMON_PATH=/var/run/supd
Jan 1 00:02:30 flukso user.info sysinit: Daemon returned 0 as return value.
Jan 1 00:02:30 flukso daemon.info spid[1142]: Sucessfully started with DEAMON=spid and DAEMON_PATH=/var/run/spid
Jan 1 00:02:30 flukso user.info sysinit: Daemon returned 0 as return value.
Jan 1 00:02:30 flukso daemon.info fluksod[1145]: Sucessfully started with DEAMON=fluksod and DAEMON_PATH=/var/run/fluksod
Jan 1 00:02:31 flukso user.info sysinit: Daemon returned 0 as return value.
Jan 1 00:02:31 flukso daemon.info parsed[1150]: Sucessfully started with DEAMON=parsed and DAEMON_PATH=/var/run/parsed
Jan 1 00:02:40 flukso user.info sysinit: wget: can't connect to remote host (192.168.255.2): No route to host
Jan 1 00:02:43 flukso user.err heartbeat[1169]: POST https://api.flukso.net/device/4d93ceb43bd2b2ef3a262d241f529838: -2
Jan 1 00:02:43 flukso user.err heartbeat[1169]: Name or service not known
Jan 1 00:02:44 flukso daemon.info supd[1139]: Received event START for ntp
Jan 1 00:04:08 flukso kern.info kernel: [ 248.110000] eth0: Configuring MAC for full duplex
Jan 1 00:04:10 flukso daemon.info dnsmasq-dhcp[759]: DHCPDISCOVER(br-lan) 00:24:81:6d:b4:f1
Jan 1 00:04:10 flukso daemon.info dnsmasq-dhcp[759]: DHCPOFFER(br-lan) 192.168.255.197 00:24:81:6d:b4:f1
Jan 1 00:04:10 flukso daemon.info dnsmasq-dhcp[759]: DHCPREQUEST(br-lan) 192.168.255.197 00:24:81:6d:b4:f1
Jan 1 00:04:10 flukso daemon.info dnsmasq-dhcp[759]: DHCPACK(br-lan) 192.168.255.197 00:24:81:6d:b4:f1 MINI
Jan 1 00:04:12 flukso authpriv.info dropbear[1296]: Running in background
Jan 1 00:04:14 flukso daemon.info dnsmasq-dhcp[759]: DHCPINFORM(br-lan) 192.168.255.197 00:24:81:6d:b4:f1
Jan 1 00:04:14 flukso daemon.info dnsmasq-dhcp[759]: DHCPACK(br-lan) 192.168.255.197 00:24:81:6d:b4:f1 MINI
Jan 1 00:06:17 flukso daemon.notice netifd: wan (689): Read error: Network is down, reopening socket
Jan 1 00:06:18 flukso daemon.notice netifd: wan (689): udhcpc: bind: No such device
Jan 1 00:06:18 flukso daemon.notice netifd: Interface 'wan' is now down
Jan 1 00:06:23 flukso kern.info kernel: [ 383.900000] wlan0: authenticate with 10:0d:7f:d4:b3:68
Jan 1 00:06:23 flukso kern.info kernel: [ 383.920000] wlan0: send auth to 10:0d:7f:d4:b3:68 (try 1/3)
Jan 1 00:06:23 flukso kern.info kernel: [ 383.920000] wlan0: authenticated
Jan 1 00:06:23 flukso kern.info kernel: [ 383.960000] wlan0: associate with 10:0d:7f:d4:b3:68 (try 1/3)
Jan 1 00:06:23 flukso kern.info kernel: [ 383.960000] wlan0: RX AssocResp from 10:0d:7f:d4:b3:68 (capab=0x411 status=0 aid=8)
Jan 1 00:06:23 flukso kern.info kernel: [ 383.970000] wlan0: associated
Jan 1 00:06:24 flukso daemon.info supd[1139]: Received event CONNECTED for wlan0
Jan 1 00:06:42 flukso daemon.info avahi-daemon[765]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.29.
Jan 1 00:06:42 flukso daemon.info avahi-daemon[765]: New relevant interface wlan0.IPv4 for mDNS.
Jan 1 00:06:42 flukso daemon.info avahi-daemon[765]: Registering new address record for 192.168.0.29 on wlan0.IPv4.
Jan 1 00:06:42 flukso daemon.notice netifd: Interface 'wan' is now up
Jan 1 00:06:44 flukso daemon.info dnsmasq[759]: reading /tmp/resolv.conf.auto
Jan 1 00:06:44 flukso daemon.info dnsmasq[759]: using nameserver 198.142.235.14#53
Jan 1 00:06:44 flukso daemon.info dnsmasq[759]: using nameserver 208.67.220.220#53
Jan 1 00:06:44 flukso daemon.info dnsmasq[759]: using nameserver 208.67.220.222#53
Jan 1 00:06:44 flukso daemon.info dnsmasq[759]: using local addresses only for domain lan
Jan 1 00:06:45 flukso user.notice firewall: Reloading firewall due to ifup of wan (wlan0)
Nov 7 09:20:20 flukso cron.err crond[679]: time disparity of 23589194 minutes detected
Nov 7 09:20:22 flukso daemon.info dnsmasq-dhcp[759]: DHCPINFORM(br-lan) 192.168.255.197 00:24:81:6d:b4:f1
Nov 7 09:20:22 flukso daemon.info dnsmasq-dhcp[759]: DHCPACK(br-lan) 192.168.255.197 00:24:81:6d:b4:f1 MINI
Nov 7 09:21:28 flukso kern.info kernel: [ 489.110000] eth0: Configuring MAC for full duplex
Nov 7 09:21:33 flukso daemon.info dnsmasq-dhcp[759]: DHCPINFORM(br-lan) 192.168.0.19 00:21:00:dd:c6:ca
Nov 7 09:21:33 flukso daemon.info dnsmasq-dhcp[759]: DHCPACK(br-lan) 192.168.0.19 00:21:00:dd:c6:ca MINI
Nov 7 09:21:52 flukso daemon.info dnsmasq-dhcp[759]: DHCPINFORM(br-lan) 192.168.0.14 08:11:96:91:a5:68
Nov 7 09:21:52 flukso daemon.info dnsmasq-dhcp[759]: DHCPACK(br-lan) 192.168.0.14 08:11:96:91:a5:68 Bazzle-PC
Nov 7 09:24:52 flukso user.err fsync[1765]: fsync exit status: 3, synchronisation with sensor board failed
Nov 7 09:24:54 flukso daemon.info parsed[1150]: Caught a SIGTERM. Exiting...
Nov 7 09:24:54 flukso daemon.info fluksod[1145]: Caught a SIGTERM. Exiting...
Nov 7 09:24:55 flukso daemon.info spid[1142]: Caught a SIGTERM. Exiting...
Nov 7 09:24:56 flukso daemon.info supd[1139]: Caught a SIGTERM. Exiting...
Nov 7 09:24:57 flukso daemon.info supd[1784]: Sucessfully started with DEAMON=supd and DAEMON_PATH=/var/run/supd
Nov 7 09:24:57 flukso daemon.info spid[1787]: Sucessfully started with DEAMON=spid and DAEMON_PATH=/var/run/spid
Nov 7 09:24:57 flukso daemon.info fluksod[1790]: Sucessfully started with DEAMON=fluksod and DAEMON_PATH=/var/run/fluksod
Nov 7 09:24:58 flukso daemon.info parsed[1795]: Sucessfully started with DEAMON=parsed and DAEMON_PATH=/var/run/parsed
Nov 7 09:25:03 flukso user.info heartbeat[1799]: POST https://api.flukso.net/device/4d93ceb43bd2b2ef3a262d241f529838: 200
Nov 7 09:25:43 flukso user.err fsync[1820]: fsync exit status: 3, synchronisation with sensor board failed
Nov 7 09:25:44 flukso daemon.info parsed[1795]: Caught a SIGTERM. Exiting...
Nov 7 09:25:45 flukso daemon.info fluksod[1790]: Caught a SIGTERM. Exiting...
Nov 7 09:25:46 flukso daemon.info spid[1787]: Caught a SIGTERM. Exiting...
Nov 7 09:25:47 flukso daemon.info supd[1784]: Caught a SIGTERM. Exiting...
Nov 7 09:25:48 flukso daemon.info supd[1839]: Sucessfully started with DEAMON=supd and DAEMON_PATH=/var/run/supd
Nov 7 09:25:48 flukso daemon.info spid[1842]: Sucessfully started with DEAMON=spid and DAEMON_PATH=/var/run/spid
Nov 7 09:25:48 flukso daemon.info fluksod[1845]: Sucessfully started with DEAMON=fluksod and DAEMON_PATH=/var/run/fluksod
Nov 7 09:25:48 flukso daemon.info parsed[1850]: Sucessfully started with DEAMON=parsed and DAEMON_PATH=/var/run/parsed
Nov 7 09:25:53 flukso user.info heartbeat[1853]: POST https://api.flukso.net/device/4d93ceb43bd2b2ef3a262d241f529838: 200
Nov 7 09:26:44 flukso user.err fsync[1874]: fsync exit status: 3, synchronisation with sensor board failed
Nov 7 09:26:45 flukso daemon.info parsed[1850]: Caught a SIGTERM. Exiting...
Nov 7 09:26:45 flukso daemon.info fluksod[1845]: Caught a SIGTERM. Exiting...
Nov 7 09:26:46 flukso daemon.info spid[1842]: Caught a SIGTERM. Exiting...
Nov 7 09:26:47 flukso daemon.info supd[1839]: Caught a SIGTERM. Exiting...
Nov 7 09:26:48 flukso daemon.info supd[1893]: Sucessfully started with DEAMON=supd and DAEMON_PATH=/var/run/supd
Nov 7 09:26:48 flukso daemon.info spid[1896]: Sucessfully started with DEAMON=spid and DAEMON_PATH=/var/run/spid
Nov 7 09:26:48 flukso daemon.info fluksod[1899]: Sucessfully started with DEAMON=fluksod and DAEMON_PATH=/var/run/fluksod
Nov 7 09:26:49 flukso daemon.info parsed[1904]: Sucessfully started with DEAMON=parsed and DAEMON_PATH=/var/run/parsed
Nov 7 09:26:54 flukso user.info heartbeat[1907]: POST https://api.flukso.net/device/4d93ceb43bd2b2ef3a262d241f529838: 200
Nov 7 09:27:23 flukso daemon.info dnsmasq-dhcp[759]: DHCPREQUEST(br-lan) 192.168.0.31 5c:95:ae:ae:c9:5a
Nov 7 09:27:23 flukso daemon.info dnsmasq-dhcp[759]: DHCPNAK(br-lan) 192.168.0.31 5c:95:ae:ae:c9:5a wrong network
Nov 7 09:27:26 flukso daemon.info dnsmasq-dhcp[759]: DHCPDISCOVER(br-lan) 5c:95:ae:ae:c9:5a
Nov 7 09:27:26 flukso daemon.info dnsmasq-dhcp[759]: DHCPOFFER(br-lan) 192.168.255.240 5c:95:ae:ae:c9:5a
Nov 7 09:27:26 flukso daemon.info dnsmasq-dhcp[759]: DHCPREQUEST(br-lan) 192.168.0.31 5c:95:ae:ae:c9:5a
Nov 7 09:27:26 flukso daemon.info dnsmasq-dhcp[759]: DHCPNAK(br-lan) 192.168.0.31 5c:95:ae:ae:c9:5a wrong server-ID
Nov 7 09:27:26 flukso daemon.info dnsmasq-dhcp[759]: DHCPREQUEST(br-lan) 192.168.0.31 5c:95:ae:ae:c9:5a
Nov 7 09:27:26 flukso daemon.info dnsmasq-dhcp[759]: DHCPNAK(br-lan) 192.168.0.31 5c:95:ae:ae:c9:5a wrong server-ID
Nov 7 09:27:37 flukso user.err fsync[1928]: fsync exit status: 3, synchronisation with sensor board failed
Nov 7 09:27:38 flukso daemon.info parsed[1904]: Caught a SIGTERM. Exiting...
Nov 7 09:27:38 flukso daemon.info fluksod[1899]: Caught a SIGTERM. Exiting...
Nov 7 09:27:39 flukso daemon.info spid[1896]: Caught a SIGTERM. Exiting...
Nov 7 09:27:40 flukso daemon.info supd[1893]: Caught a SIGTERM. Exiting...
Nov 7 09:27:41 flukso daemon.info supd[1947]: Sucessfully started with DEAMON=supd and DAEMON_PATH=/var/run/supd
Nov 7 09:27:41 flukso daemon.info spid[1950]: Sucessfully started with DEAMON=spid and DAEMON_PATH=/var/run/spid
Nov 7 09:27:42 flukso daemon.info fluksod[1953]: Sucessfully started with DEAMON=fluksod and DAEMON_PATH=/var/run/fluksod
Nov 7 09:27:42 flukso daemon.info parsed[1958]: Sucessfully started with DEAMON=parsed and DAEMON_PATH=/var/run/parsed
Nov 7 09:27:47 flukso user.info heartbeat[1961]: POST https://api.flukso.net/device/4d93ceb43bd2b2ef3a262d241f529838: 200
Nov 7 09:30:01 flukso cron.info crond[679]: crond: USER root pid 2007 cmd /usr/bin/fcheck
Nov 7 09:31:49 flukso daemon.info dnsmasq-dhcp[759]: DHCPINFORM(br-lan) 192.168.0.14 08:11:96:91:a5:68
Nov 7 09:31:49 flukso daemon.info dnsmasq-dhcp[759]: DHCPACK(br-lan) 192.168.0.14 08:11:96:91:a5:68 Bazzle-PC
Nov 7 09:33:09 flukso daemon.info dnsmasq-dhcp[759]: DHCPINFORM(br-lan) 192.168.0.14 08:11:96:91:a5:68
Nov 7 09:33:09 flukso daemon.info dnsmasq-dhcp[759]: DHCPACK(br-lan) 192.168.0.14 08:11:96:91:a5:68 Bazzle-PC
Nov 7 09:36:20 flukso user.err fsync[2061]: fsync exit status: 3, synchronisation with sensor board failed
Nov 7 09:36:21 flukso daemon.info parsed[1958]: Caught a SIGTERM. Exiting...
Nov 7 09:36:22 flukso daemon.info fluksod[1953]: Caught a SIGTERM. Exiting...
Nov 7 09:36:23 flukso daemon.info spid[1950]: Caught a SIGTERM. Exiting...
Nov 7 09:36:24 flukso daemon.info supd[1947]: Caught a SIGTERM. Exiting...
Nov 7 09:36:25 flukso daemon.info supd[2080]: Sucessfully started with DEAMON=supd and DAEMON_PATH=/var/run/supd
Nov 7 09:36:25 flukso daemon.info spid[2083]: Sucessfully started with DEAMON=spid and DAEMON_PATH=/var/run/spid
Nov 7 09:36:25 flukso daemon.info fluksod[2086]: Sucessfully started with DEAMON=fluksod and DAEMON_PATH=/var/run/fluksod
Nov 7 09:36:25 flukso daemon.info parsed[2091]: Sucessfully started with DEAMON=parsed and DAEMON_PATH=/var/run/parsed
Nov 7 09:36:31 flukso user.info heartbeat[2094]: POST https://api.flukso.net/device/4d93ceb43bd2b2ef3a262d241f529838: 200
Nov 7 09:36:52 flukso user.err fsync[2116]: fsync exit status: 3, synchronisation with sensor board failed
Nov 7 09:36:53 flukso daemon.info parsed[2091]: Caught a SIGTERM. Exiting...
Nov 7 09:36:53 flukso daemon.info fluksod[2086]: Caught a SIGTERM. Exiting...
Nov 7 09:36:54 flukso daemon.info spid[2083]: Caught a SIGTERM. Exiting...
Nov 7 09:36:55 flukso daemon.info supd[2080]: Caught a SIGTERM. Exiting...
Nov 7 09:36:56 flukso daemon.info supd[2135]: Sucessfully started with DEAMON=supd and DAEMON_PATH=/var/run/supd
Nov 7 09:36:56 flukso daemon.info spid[2138]: Sucessfully started with DEAMON=spid and DAEMON_PATH=/var/run/spid
Nov 7 09:36:57 flukso daemon.info fluksod[2141]: Sucessfully started with DEAMON=fluksod and DAEMON_PATH=/var/run/fluksod
Nov 7 09:36:57 flukso daemon.info parsed[2146]: Sucessfully started with DEAMON=parsed and DAEMON_PATH=/var/run/parsed
Nov 7 09:37:02 flukso user.info heartbeat[2149]: POST https://api.flukso.net/device/4d93ceb43bd2b2ef3a262d241f529838: 200
Nov 7 09:37:24 flukso user.err fsync[2170]: fsync exit status: 3, synchronisation with sensor board failed
Nov 7 09:37:25 flukso daemon.info parsed[2146]: Caught a SIGTERM. Exiting...
Nov 7 09:37:26 flukso daemon.info fluksod[2141]: Caught a SIGTERM. Exiting...
Nov 7 09:37:27 flukso daemon.info spid[2138]: Caught a SIGTERM. Exiting...
Nov 7 09:37:28 flukso daemon.info supd[2135]: Caught a SIGTERM. Exiting...
Nov 7 09:37:29 flukso daemon.info supd[2189]: Sucessfully started with DEAMON=supd and DAEMON_PATH=/var/run/supd
Nov 7 09:37:29 flukso daemon.info spid[2192]: Sucessfully started with DEAMON=spid and DAEMON_PATH=/var/run/spid
Nov 7 09:37:29 flukso daemon.info fluksod[2195]: Sucessfully started with DEAMON=fluksod and DAEMON_PATH=/var/run/fluksod
Nov 7 09:37:29 flukso daemon.info parsed[2200]: Sucessfully started with DEAMON=parsed and DAEMON_PATH=/var/run/parsed
Nov 7 09:37:35 flukso user.info heartbeat[2203]: POST https://api.flukso.net/device/4d93ceb43bd2b2ef3a262d241f529838: 200
Nov 7 09:37:47 flukso daemon.info dnsmasq-dhcp[759]: DHCPREQUEST(br-lan) 192.168.0.31 5c:95:ae:ae:c9:5a
Nov 7 09:37:47 flukso daemon.info dnsmasq-dhcp[759]: DHCPNAK(br-lan) 192.168.0.31 5c:95:ae:ae:c9:5a wrong network
Nov 7 09:37:50 flukso daemon.info dnsmasq-dhcp[759]: DHCPDISCOVER(br-lan) 5c:95:ae:ae:c9:5a
Nov 7 09:37:50 flukso daemon.info dnsmasq-dhcp[759]: DHCPOFFER(br-lan) 192.168.255.240 5c:95:ae:ae:c9:5a
Nov 7 09:37:50 flukso daemon.info dnsmasq-dhcp[759]: DHCPREQUEST(br-lan) 192.168.0.31 5c:95:ae:ae:c9:5a
Nov 7 09:37:50 flukso daemon.info dnsmasq-dhcp[759]: DHCPNAK(br-lan) 192.168.0.31 5c:95:ae:ae:c9:5a wrong server-ID
Nov 7 09:37:50 flukso daemon.info dnsmasq-dhcp[759]: DHCPREQUEST(br-lan) 192.168.0.31 5c:95:ae:ae:c9:5a
Nov 7 09:37:50 flukso daemon.info dnsmasq-dhcp[759]: DHCPNAK(br-lan) 192.168.0.31 5c:95:ae:ae:c9:5a wrong server-ID
Nov 7 09:37:54 flukso user.err fsync[2224]: fsync exit status: 3, synchronisation with sensor board failed
Nov 7 09:37:55 flukso daemon.info parsed[2200]: Caught a SIGTERM. Exiting...
Nov 7 09:37:55 flukso daemon.info fluksod[2195]: Caught a SIGTERM. Exiting...
Nov 7 09:37:56 flukso daemon.info spid[2192]: Caught a SIGTERM. Exiting...
Nov 7 09:37:57 flukso daemon.info supd[2189]: Caught a SIGTERM. Exiting...
Nov 7 09:37:58 flukso daemon.info supd[2243]: Sucessfully started with DEAMON=supd and DAEMON_PATH=/var/run/supd
Nov 7 09:37:59 flukso daemon.info spid[2246]: Sucessfully started with DEAMON=spid and DAEMON_PATH=/var/run/spid
Nov 7 09:37:59 flukso daemon.info fluksod[2249]: Sucessfully started with DEAMON=fluksod and DAEMON_PATH=/var/run/fluksod
Nov 7 09:37:59 flukso daemon.info parsed[2254]: Sucessfully started with DEAMON=parsed and DAEMON_PATH=/var/run/parsed
Nov 7 09:38:04 flukso user.info heartbeat[2257]: POST https://api.flukso.net/device/4d93ceb43bd2b2ef3a262d241f529838: 200

bazzle's picture
bazzle |

3rd time lucky. Lucky for me having short hair or it would of been pulled out by now .. :) ..
Completely reset and reloaded sensors etc 3 times.
"seems" to be working now. Will check in the morning, bedtime now 22:28.

Latest log below.
??

Cant get back in to check..grrr.

adamcowin's picture
adamcowin |

baz,

you said you have two wireless routers - are they both offering DHCP? would explain why you are getting two different ip address's (on different subnets) and why sometimes it works and sometimes it doesnt.

another thing to look for is if you are running two routers and two different networks, there may be a new device on the network that is issuing dhcp addresses by default. i've seen this before where someone will bring in their router from home to use as a "switch" when they dont have enough data wall points. They plug it in, and it starts issuing IP addresses to devices on the network..

adam

bazzle's picture
bazzle |

Yes 2 routers, one used as a switch. It has always been there though. I turned it off earlier tonight.
Issue only started happening over last couple of days?

petur's picture
petur |

I agree with adam, make 200% that only one has the DHCP server active.

Yes, it may have worked well before, maybe because the flukso had a long lease before the second one was added, and a reboot brought the issue...

bazzle's picture
bazzle |

Hi Bart

I need help.

I have reset the Flm and get 2 lights, heartbeat and power. The heartbeat flashes very weakly.
When I open 192.168.255.1 the ssid box is empty.
I have tried to toggle the button, through all 3 settings including resets to load firmware but get the same result.

I cannot get the Flm to work at all now.
Please advise.

Best regards Bazzle

bazzle's picture
bazzle |

Ok
After another round of power off. On, another full reload of firmware, readd sensors etc it seems to be up and running again.. errrr.
Lasted over 5 minutes now O)

Bloody... bloody need to get my life back :(

bazzle's picture
bazzle |

Sadly starting to play up again. One sensor not being picked up, heart beat comes and goes ..
Can anyone make sense of the log?
Thanks Baz

Nov 7 21:51:21 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397081:1189
Nov 7 21:51:24 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397084:1190
Nov 7 21:51:27 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397087:1191
Nov 7 21:51:27 flukso-4d93ce daemon.info fluksod[1261]: processed pulse b4a04e554f01781b518eeae703abebb8:1415397087:497
Nov 7 21:51:30 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397090:1192
Nov 7 21:51:33 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397093:1193
Nov 7 21:51:36 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397096:1194
Nov 7 21:51:37 flukso-4d93ce daemon.info fluksod[1261]: processed pulse b4a04e554f01781b518eeae703abebb8:1415397097:498
Nov 7 21:51:39 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397099:1195
Nov 7 21:51:42 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397102:1196
Nov 7 21:51:45 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397105:1197
Nov 7 21:51:45 flukso-4d93ce daemon.info fluksod[1261]: processed pulse b4a04e554f01781b518eeae703abebb8:1415397105:499
Nov 7 21:51:48 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397108:1198
Nov 7 21:51:51 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397111:1199
Nov 7 21:51:52 flukso-4d93ce daemon.info fluksod[1261]: processed pulse b4a04e554f01781b518eeae703abebb8:1415397112:500
Nov 7 21:51:54 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397114:1200
Nov 7 21:51:57 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397117:1201
Nov 7 21:52:00 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397120:1202
Nov 7 21:52:00 flukso-4d93ce daemon.info fluksod[1261]: processed pulse b4a04e554f01781b518eeae703abebb8:1415397120:501
Nov 7 21:52:03 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397123:1203
Nov 7 21:52:06 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397126:1204
Nov 7 21:52:09 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397129:1205
Nov 7 21:52:12 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397132:1206
Nov 7 21:52:15 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397135:1207
Nov 7 21:52:18 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397138:1208
Nov 7 21:52:18 flukso-4d93ce daemon.info fluksod[1261]: processed pulse b4a04e554f01781b518eeae703abebb8:1415397138:502
Nov 7 21:52:21 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397141:1209
Nov 7 21:52:24 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397144:1210
Nov 7 21:52:27 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397147:1211
Nov 7 21:52:30 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397150:1212
Nov 7 21:52:33 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397153:1213
Nov 7 21:52:36 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397156:1214
Nov 7 21:52:38 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397158:1215
Nov 7 21:52:39 flukso-4d93ce daemon.info fluksod[1261]: processed pulse b4a04e554f01781b518eeae703abebb8:1415397159:503
Nov 7 21:52:41 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397161:1216
Nov 7 21:52:44 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397164:1217
Nov 7 21:52:46 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397166:1218
Nov 7 21:52:49 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397169:1219
Nov 7 21:52:52 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397172:1220
Nov 7 21:52:55 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397175:1221
Nov 7 21:52:57 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397177:1222
Nov 7 21:52:58 flukso-4d93ce daemon.info fluksod[1261]: processed pulse b4a04e554f01781b518eeae703abebb8:1415397178:504
Nov 7 21:53:00 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397180:1223
Nov 7 21:53:03 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397183:1224
Nov 7 21:53:05 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397185:1225
Nov 7 21:53:08 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397188:1226
Nov 7 21:53:11 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397191:1227
Nov 7 21:53:13 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397193:1228
Nov 7 21:53:15 flukso-4d93ce daemon.info fluksod[1261]: processed pulse b4a04e554f01781b518eeae703abebb8:1415397195:505
Nov 7 21:53:16 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397196:1229
Nov 7 21:53:18 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397198:1230
Nov 7 21:53:21 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397201:1231
Nov 7 21:53:24 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397204:1232
Nov 7 21:53:36 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397216:1237
Nov 7 21:53:38 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397218:1238
Nov 7 21:53:43 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397223:1240
Nov 7 21:54:14 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397254:1252
Nov 7 21:54:27 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397267:1257
Nov 7 21:54:29 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397269:1258
Nov 7 21:54:32 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397272:1259
Nov 7 21:54:34 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397274:1260
Nov 7 21:54:34 flukso-4d93ce daemon.info fluksod[1261]: processed pulse b4a04e554f01781b518eeae703abebb8:1415397274:510
Nov 7 21:54:37 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397277:1261
Nov 7 21:54:39 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397279:1262
Nov 7 21:54:41 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397281:1263
Nov 7 21:54:44 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397284:1264
Nov 7 21:54:46 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397286:1265
Nov 7 21:55:16 flukso-4d93ce daemon.info fluksod[1261]: processed pulse b4a04e554f01781b518eeae703abebb8:1415397316:513
Nov 7 21:55:18 flukso-4d93ce daemon.info fluksod[1261]: POST https://api.flukso.net/sensor/b4a04e554f01781b518eeae703abebb8: 200
Nov 7 21:55:19 flukso-4d93ce daemon.info fluksod[1261]: POST https://api.flukso.net/sensor/8492153f1144dba9fecf777466fdc508: 200
Nov 7 21:55:19 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397317:1278
Nov 7 21:55:23 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397323:1281
Nov 7 21:55:26 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397326:1282
Nov 7 21:55:46 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415397346:1291
Nov 7 22:00:01 flukso-4d93ce cron.info crond[652]: crond: USER root pid 3790 cmd /usr/bin/fcheck
Nov 7 22:05:01 flukso-4d93ce cron.info crond[652]: crond: USER root pid 3811 cmd /usr/bin/heartbeat 0
Nov 7 22:05:04 flukso-4d93ce user.info heartbeat[3812]: POST https://api.flukso.net/device/4d93ceb43bd2b2ef3a262d241f529838: 200
Nov 7 22:15:01 flukso-4d93ce cron.info crond[652]: crond: USER root pid 3830 cmd /usr/bin/fcheck
Nov 7 22:15:14 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415398514:1695
Nov 7 22:15:16 flukso-4d93ce daemon.info fluksod[1261]: POST https://api.flukso.net/sensor/8492153f1144dba9fecf777466fdc508: 200
Nov 7 22:30:01 flukso-4d93ce cron.info crond[652]: crond: USER root pid 3867 cmd /usr/bin/fcheck
Nov 7 22:42:30 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415400150:2456
Nov 7 22:42:32 flukso-4d93ce daemon.info fluksod[1261]: POST https://api.flukso.net/sensor/8492153f1144dba9fecf777466fdc508: 200
Nov 7 22:45:01 flukso-4d93ce cron.info crond[652]: crond: USER root pid 3900 cmd /usr/bin/fcheck
Nov 7 23:00:01 flukso-4d93ce cron.info crond[652]: crond: USER root pid 3937 cmd /usr/bin/fcheck
Nov 7 23:05:01 flukso-4d93ce cron.info crond[652]: crond: USER root pid 3958 cmd /usr/bin/heartbeat 0
Nov 7 23:05:04 flukso-4d93ce user.info heartbeat[3959]: POST https://api.flukso.net/device/4d93ceb43bd2b2ef3a262d241f529838: 200
Nov 7 23:05:07 flukso-4d93ce user.notice root: rshell: wget exit status = 0
Nov 7 23:05:11 flukso-4d93ce user.notice root: rshell: ssh exit status = 0
Nov 7 23:09:35 flukso-4d93ce daemon.info fluksod[1261]: processed pulse 8492153f1144dba9fecf777466fdc508:1415401775:3464
Nov 7 23:09:37 flukso-4d93ce daemon.info fluksod[1261]: POST https://api.flukso.net/sensor/8492153f1144dba9fecf777466fdc508: 200
Nov 7 23:15:01 flukso-4d93ce cron.info crond[652]: crond: USER root pid 3992 cmd /usr/bin/fcheck
Nov 7 23:30:01 flukso-4d93ce cron.info crond[652]: crond: USER root pid 4029 cmd /usr/bin/fcheck
Nov 7 23:45:01 flukso-4d93ce cron.info crond[652]: crond: USER root pid 4062 cmd /usr/bin/fcheck

bazzle's picture
bazzle |

Other issue is
sensor 8492153f1144dba9fecf777466fdc508 is shown on my graph (solar in) but he other sensor b4a04e554f01781b518eeae703abebb8 power used is not on graph. I have put a meter across to check pulses-ok.
They show on log above and were on graph until an hour or so.

icarus75's picture
icarus75 |

This log entry points to an issue with the daughter board:

  1. Nov 7 09:36:20 flukso user.err fsync[2061]: fsync exit status: 3, synchronisation with sensor board failed

I've just checked your FLM and it seems that the communication with the daughter board only works intermittently. Do you think you can replace the red PCB in your FLM if we send you a new one?

bazzle's picture
bazzle |

That will not be an issue.
Please do. Thank you

Baz

bazzle's picture
bazzle |

yes.. same error showing on 'status' page at 192.168.255.1
"syncronisation with sensor board failed"

Please advise went posted :)

Baz

bazzle's picture
bazzle |

Bart

Can you "please" confirm the part has been sent..

Thanks Baz

bazzle's picture
bazzle |

Icarus/Bart

Im asking again if you can you "please" confirm part has been sent?
I have emailed you twice as well but you dont reply there or here?

I need to know where we are at so I can get my data together. My rebate from my supplier requires I get this data to ensure its all going as agreed for my rebate .

Bazzle

icarus75's picture
icarus75 |

Hello Bazzle,

The pcb has been sent out to you by snail mail some time ago. I would expect it to arrive in the next couple of days. Once you've replaced the board, save your sensor configuration once more (no need to start from scratch, just save the existing config) and the FLM should be up-and-running again.

Cheers
/Bart

bazzle's picture
bazzle |

Thank you.

Ill report the progress.

Bazzle

bazzle's picture
bazzle |

OK. Part received thank you.

Plugged in ... some issues.
,
,
,
eventually.... got it going again.
Had to perform FULL reset to make it take the new setup and properly save the wifi etc.
Might be an idea to remember that.
Hopefully when I run a whole day tomorrow data will be OK

Thanks for sending the part.

Baz