Important Note About Firmware Update

Dear Community,

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.

Best regards,

1 Like

Hello,

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.

Thanks,

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

What do I do?

1 Like

Did you login to the CLI using …

User = root
Password = [insert password you use to login as admin]

Having already tried twice to upgrade ā€œKeeping Settingsā€ from 7.14 to 7.14.2 and failed i decided to try offering the command:

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

then try again.

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!!!

1 Like

No, I used my usual login name of admin and usual password. I’m guessing the root username is the key. I’ll give it a try. Thanks @Mike


Hi! I have the same problem. What to do?