We would like to inform you that if a system upgrade with keep settings is performed from firmware version 7.14 or 7.14.1 to 7.14.2, the following command must be executed via CLI before the upgrade to avoid issues with Data Limit and Traffic Monitoring: mkdir -p /usr/local/lib/upgrade/keep.d && echo /usr/local/usr/lib/mdcollectd/mdcollectd.db_new.gz > /usr/local/lib/upgrade/keep.d/mdcollect
Note: If an upgrade with keep settings was already performed from 7.14 to 7.14.1, Data Limit and Traffic Monitoring issues cannot be resolved manually. In this case, a firmware upgrade without keep settings is required.
We apologize for any inconvenience this issue may have caused and appreciate your understanding.
What are the consequences to upgrade 7.14.x â 7.14.2 without doing this command and keep settings ? Is it feasible via SSH ?
Also in TRB140 Firmware Downloads - Teltonika Networks Wiki page TRB1_R_00.07.14.2_WEBUI is announced with â50 MB MBâ size (download real size is a more common 17 736 795 bytes). MD5 and SHA256 also doesnât match. SDK seems to have same trouble.
Iâm not good on command line things, but Iâve logged in to the CLI, pasted the command provided and it says: mkdir: canât create directory â/usr/local/lib/upgrade/â: Permission denied
The command appeared to complete successfully insofar as the process didnât return an error. I then tried to upgrade from 7.14 to 7.14.2 keeping settings again and after a very worrying 18 minutes and what appeared to be a couple of reboots âpossiblyâ the router became responsive again and i could log in.
Upgrade was successful this time.
However i think itâs important to say that you should wait a lot longer than normall for this upgrade to complete⌠Go put the kettle on and make yourself some toast!!!
Using your PassWord you have logged in using the UserName âadminâ.
Try using your PassWord but instead use the UserName ârootâ.
Using the UserName âadminâ gives you admin level access to the system, using the UserName ârootâ gives you an elevated or a higher level of access, a much more powerful level of access to the system.
Careful though, ârootâ access to the system gives you much more power to do stuff but used incorrectly or make mistakes and you can also do a lot of damage too!!
It was necessary to log in directly to the command line interface (I use the PuTTY) as the ROOT user; using ADMIN and SU was not sufficient. Once logged in as ROOT, the command executed without issues, and the subsequent firmware upgrade from version 14 to 14.2 completed within the standard timeframe of until 5 minutes.
Excellent question. I would very much like an official answer from Teltonika on what is the best procedure to get out of this mess, what to do when you are already upgraded to 7.14 and do want to keep settings. And/or a more detailed explanation what is the issue.
It looks like the database storing traffic has gone read only on update to 7.14 but thatâs guessing.
Note to self: never ever upgrade again tt remote systems until very sure. But when, only to mass production release?
Hi,
I have already updated to the 7.14.1 version when it came and therefore need to upgrade again but without âKeep all settingâ.
Does any body know if the sim pin code is saved when updating without Keep seeting? I was hoping so since it is saved when doing a factory reset. Otherwise it´s going to be a lot of travel for me since the router are far away in rural locations.
Re-reading the Teltonika answer, the âwithout keep settingâ update is only needed for 7.14.1 â 7.14.2 if I understand it correctly. 7.14 â 7.14.2 can be done issuing a cmd first.
But I wait a bit till the dust settless.
Good luck with restoring your systems, le us know how you fare!
Hi Michal, thank you for your reply, I have read the link you sent.
Maybe I can do a factory reset and then upgrade to 7.14.2 but do the CLI thing first. Then I dont have to go the router.
I think this is so strange, I´m a noob at this IT stuff and just want it to work as smooth as possable. Have Teletonika not tested the new version before they relise it? Just extra unnecessary work for all custemers. I will also be very careful with updating in the future. Hackers will be unemployed soon, teletonika is perfectly capable of destroing there stuff them selves.
root@RUTX09:~# opkg install coreutils-nohup
Package coreutils-nohup (8.32-6) installed in root is up to date.
root@RUTX09:~# nohup
-ash: nohup: not found
is it related ? Everything worked well with previous versionâŚ
Im 100% with you, our company has 500+ active routers that the 7.14 firmware has screwed up all previous configs, reverted back to mass production FW 7.13.4 and now trying to create tasks to basically set the Setup_wizard configs but guess what, now RMS servers arenât working and our call center is literally on fire now. It doesnât seem like Teltonika is responsive at all here so not sure if this is even worth posting but I will anyways to let everyone know you arenât alone if youâre being inconvenienced from this. Any response would be nice. Thanks
