We are using a script on the router where we read the eventslog and create additional events.
Up to Version 06.xx everything works perfect, in Version 07.xx eventslog isn’t available anymore.
Why ?
We read and transfer the events to our database, to archive them for our customers.
In Version 06 i can use the command:
Reading
/usr/bin/eventslog -p -t EVENTS -o ID -q “WHERE ID > xyz”
Add own event
/usr/bin/eventslog -i -t EVENTS -n “MYNAME” -e “This is my own event text”
The transition from version 06.xx to 07.xx marked a major firmware upgrade, with 06.xx now considered legacy. This update brought about significant changes in file structure and overall functionality.
Currently, log files can be located in the /log/log.db file.
I’m sorry to say that we don’t have any examples of using log.db in that way because it’s not the intended use of log.db. Generally, tampering with log databases is not advised because it can corrupt the log data.
If you really need to edit it, you can access it using scripting, for example, Python with the sqlite3 library.
Regarding the “No space left on the device” issue, could you please specify which device you are using and what files you are storing? If you’re using the same device where you write to the log file, it’s inevitable that memory would fill up, as only selected important logs are written in event logs. Depending on the device, you can expand its memory via USB or, in some cases, an SD card.
The customer installed this router 1 month ago, yesterday I’ve tried to setup OpenVPN but the router didn’t save the files (OpenVPN Cert files: ta.key, ca.crt, user.crt, user.key). After using the solution from https://community.teltonika-networks.com/55449/rut-950-flash-full I was able to free up a few kBytes to safe the files.
BUT after a reboot of the router the files appears again with the same result: no space left on the device.
My company and our customers having more than 2000 RUT 9xx / RUT 240 installed in the last 10 years (if you like I can provide more details in a private message) and we had never such big problems as in Version 07.xx…
If you’re using the same device where you write to the log file, it’s inevitable that memory would fill up, as only selected important logs are written in event logs
→ we don’t because up to now I don’t know how to do this without /usr/bin/eventlogs.
Could you please provide information on the number of devices that were affected? Were these devices just reinstalled with the 07.xx firmware or had they been running for a while? Additionally, did they have any additional logging or other implementations where data was being saved?
actually we simply keep the devices running with latest Version 06 (approx. 65% of 1300 pcs) and testing migration to 07 step by step (25%) because I’m afraid of migrating untested to 07. Lot of them installed far away from us. If we loose VPN / mobile access we have to send a someone with a laptop to the router.
This Router we talk about has no changes from our side, latest FOTA 07 firmware. Customer contact us, because he wasn’t able to setup OpenVPN tunnel, message “no space left on device”. So we start to check why and the only way to upload the certs was to remove the profiles files. What is needed to check why /overlay is fully used?
When you install something or delete files on your device, they take up space in the “/overlay” directory, except for temporary files stored in RAM. Most of the space on your client’s system is occupied by files like “1.5M /overlay/upper/etc/profiles” and “1.9M /overlay/upper/etc”. These are likely files related to client packages or configurations, as system-generated files are usually not stored in long-term memory but in “/tmp”.
It’s important to note that RUT9xx and RUT2xx series devices have limited flash space, with only a few spare MB available. Therefore, every MB counts. It’s worth checking for any unnecessary packages or profiles on the system.
Version 00.07 has been around for a while and has received numerous updates. It is recommended when upgrading from version 00.06 to 00.07 to do it without keeping settings, and with a few firmware jumps instead of going straight to the newest firmware. Upgrading with keep settings on might have resulted in some leftover packages or other information.