I've done an upgrade to 232 and my Flukso has not transmitted data or had a heartbeat in 24 hours. I can see the device is connected to the network via Wi-Fi and I can access it via the wired LAN however the information page showing version number and device s/n is blank. Can anyone please assist in kick starting my device so it works again?
Regards,
Andrew
Really? No one has any advice for me?
Upgrade to 223 worked fine for me; have you heeded Dogbert's tech advice, thus "rebooted" or just power-cycled? No s/n is normal, see https://www.flukso.net/content/serial-number-not-diplayed-webgui
upg to v232, of course (how lovely it would be if one can edit own posts :-/)
Thanks for the reply. I have "Power Cycled" the device by pulling out the power lead. I don't know how to "reboot" other than this. I can see the mac address and allocated IP address on my router so it's connecting wirelessly. I can connect to it via LAN cable and can access it via 192.168.255.1 and I can see everything like normal however the first status box has nothing in it. I normally se the s/n and the firmware version (and other info I think but its raining at the moment so can't take the notebook out to check.
Is there a way to download the v232 firmware and then manually upload it? Settings/devices tab on flukso.net shows 232*** still after days so the upgrade has not taken and now its not responding at all.
Has anyone else had this problem??
Andrew
Can you try to get the FLM online again? I do not think any upgrade was initiated since it's still scheduled on flukso.net (232**). It seems like the FLM lost internet connectivity before the upgrade could even start. What does the syslog say?
Hi again,
I have plugged into the FLM and 100% it has internet connectivity. I can turn the wireless off on my notebook and connect to the net via the FLM. Device also has successful ping to flukso.net.
SYSTEM STATUS screen displays the following: Serial=Blank, Model=Blank, Hostname=Blank, Firmware Version=Blank, Time=Correct time and date displayed, Uptime=Correct uptime displayed.
As for the Syslog it's just repeating the same sequence every hour. (but none today for some reason)
Oct 25 06:00:05 flukso user.err heartbeat[10277]: WWW-Authenticate: No proper provisioning for this device
Oct 25 06:15:01 flukso cron.info crond[549]: crond: USER root pid 10312 cmd /usr/bin/fcheck
Oct 25 06:30:01 flukso cron.info crond[549]: crond: USER root pid 10342 cmd /usr/bin/fcheck
Oct 25 06:45:01 flukso cron.info crond[549]: crond: USER root pid 10372 cmd /usr/bin/fcheck
Oct 25 07:00:01 flukso cron.info crond[549]: crond: USER root pid 10402 cmd /usr/bin/heartbeat 0
Oct 25 07:00:01 flukso cron.info crond[549]: crond: USER root pid 10403 cmd /usr/bin/fcheck
Oct 25 07:00:05 flukso user.err heartbeat[10404]: POST https://api.flukso.net/device/0123456789abcdef0123456789abcdef: 401
I suspect the first line at 06:00:05 is the root of the problem but how can I solve it?
Regards,
Andrew
Mine has the same problem, I applied the update and at some point restarted the flukso. Now it just has the heartbeat error.
Jan 1 00:01:18 flukso user.info sysinit: sh: 1: unknown operand
Jan 1 00:01:18 flukso user.info sysinit: uci: Parse error (invalid command) at line 1, byte 0
Jan 1 00:01:18 flukso user.info sysinit: sh: 1: unknown operand
Jan 1 00:01:25 flukso user.err heartbeat[795]: POST https://api.flukso.net/device/0123456789abcdef0123456789abcdef: 401
Jan 1 00:01:25 flukso user.err heartbeat[795]: WWW-Authenticate: No proper provisioning for this device
Jan 1 00:01:26 flukso daemon.info supd[785]: Received event START for ntp
Yes FURY there seems to be a few people who are having an issue after upgrade. There is another person who has also started a thread with the same issue. It would be good too hear from someone in the know as to a possible solution or perhaps to roll back the firmware. It's frustrating that no one in development making any suggestions or asking for more information.
Is it possible to download the firmware and load it directly to the FLM??
according to your log file your time is off
try to change ntp setting
Same here
Firmware update showing as pending
Serial Version Resets Last heartbeat Uptime Operations
FL020xxxxx 232** 22 30 Oct 2013 12:44:20
0123456789abcdef0123456789abcd is a genetic device code instead of a unuiqe one. So that's where the issue lies....
Yup /etc/config/system has this data I can enter the serial number but I have no ideas what device and key should be. I assume the provisioning mechanism shoudl initialize thsi after the first boot.
config system
option timezone UTC
option model FLM02A
option serial unknown
option hostname flukso
option device 0123456789abcdef0123456789abcdef
option key 00112233445566778899aabbccddeeff
option firstboot 1
option restore 1
option cronloglevel 1
serial number you can normally find on your dashboard on flukso.net
It's probably a dumb question but how do you get into /etc/config/system ?
I've tried putting this in the address line when connected directly to the FLM but it just kept taking me back to the root login.
Andrew
Accessing the FLM's configuration on the level of the operation system requires a SSH client, e.g. PuTTY (see http://www.putty.org/ ) - with such a SSH client you can access the FLM via port 22; this brings you to the OS login (root, password root) and through that to the file system where you may alter nearly everything... (so you should know what you are doing - see OpenWRT documentation and the FLM's source code)
BUT for an upgrade that should not be necessary; so maybe Bart (the wizard behind the FLM) can help remotely; address him via the contact form to get a private conversation.
I don't know if that is very effective, for everyone to contact him. Surely they are already aware of the issue?
Should I be able to SSH the FLM via the wireless network it's connected too or do I need to be connected directly to the network port?
By default SSH is possible only via the cable - see https://www.flukso.net/content/access-flm-wireless-interface
Got it. Thanks Gebhardm.
It seems that an upgrade to r232 was initiated. Then something seems to have gone wrong during first boot of the new firmware due to a UCI parsing error. That's why a.o. the device and key settings are still showing their defaults.
1/ Could you tell me which firmware version you upgraded from?
2/ If you're able to ssh into the FLM after a botched upgrade could you run this command:
I'm expecting the uci command to fail with the following error message:
Please copy/paste the /etc/config/system file into a comment as well.
And don't worry. We'll get these FLMs back online. You might have to reconfigure your FLM though.
Cheers
/Bart
ICARUS75 I had same problems.
Serial number was gone after reboot.
NTP settings were gone too . DNS was not working
root password changed also
@sem If your FLM is still in this state, could you please run the command in the above comment and let me know the result?
No, I fixed it already . But i need to reconfigure everything manually .
I just posting in case you are interested in improving upgrade process in the future.
If you need uci show system i can post it by mail to you
This issue seems to have popped up on a subset of the migrations. I haven't been able to reproduce the problem at my side. Investigating a broken upgrade can be very helpful to find the root cause.
Contents of /etc/config/system
(weird extra lines at start and end)
And removing those first and last lines from /etc/system/config solves it
So:
Connect the flukso with a direct ethernet cable to your computer
Use putty (http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe) or ssh to connect
Login with username root password root
You can use vi to edit the file
Remove the first line by pressing the letter d twice
Go to the end of the file with the arrow keys
Remove the last line by pressing the letter d twice
Save the file by typing wq!
Reboot the router by typing reboot
Please note do the above at your own risk maybe Bart has a better method
Only delete these lines if they show something similar to
system 0% | | 0 --:--:-- ETA
Allright! The migration script will download two files that will end up as /etc/config/system and /etc/config/firewall. I forgot the wget -q switch to silence the output of the wget command. The lines you're seeing is wget printing download progress. This has now been fixed in the script. For affected systems, the procedure given by jaap is correct, just make sure to scan both system and firewall, so:
If this seems too much trouble, then the alternative is to start the FLM, wait for the heartbeat LED to start blinking and then pressing the recessed toggle button between 60 and 120 secs. This will cause the FLM to delete the overlay file system containing the corrupted file(s) and to boot with a fresh r232 firmware. The downside is that your FLM will have lost all of its wifi and sensor settings. So you'll have to configure the FLM from scratch again.
@jaap Thanks for the help in finding the root cause. I've slightly edited two lines in your comment to fix typos.
Thanks JAPP and ICARUS75. removing the odd lines and reboot made the FLM bounce straight back into life. Still shows that the upgrade to 232 is pending so I'll see if it's successful this time. I'll report back in with my result.
Andrew