Forums

Logs not saving 24 hours

• Author
  Posts
• June 29, 2024 at 4:27 pm #6319
  Rocket

  Participant

  Is there a limit to the number of log entries? I have about 13 devices connected and the logs usually only go back 10 to 14 hours consistently. They used to be the full 24 hours. I have a script to save them nightly and now I am missing some of the hours. TIA.

  June 29, 2024 at 4:32 pm #6324
  support

  Keymaster

  The logs are stored in memory so there is an upper limit to the amount of memory used to store logs. The router admin page allows you to go back 24 hours but the logs may be cut off if you have a lot of Internet activities. Please consider increasing the frequency of backup for your script.

  July 2, 2024 at 1:05 pm #6327
  Rocket

  Participant

  Is there a way to expand the memory?

  Related, the script I created is a Rube Goldberb kludge of cron jobs and xdotool commands. It often fails to complete the desired task. Is there a better way to pull the logs on a frequent basis? Could that be added to a future firmware release?

  July 7, 2024 at 3:31 pm #6332
  support

  Keymaster

  @rocket Can you share more info about your script?

  July 16, 2024 at 6:12 pm #6342
  Rocket

  Participant

  I’m using Linux Mint as my OS for this. In case you (or other forum members) are not familar with xdotools, it is a command-line tool used to automate GUI tasks such as window manipulation, cursor movement, key presses, mouse clicks, etc. Since I couldn’t find a way to directly download the logs, I developed this xdotool script that logs onto the router home page, ‘clicks’ to the Apps > Access Control, etc… when it gets to the logs page, it ‘clicks’ the Raw option, moves the cursor to the window with logs and does a right click “Save As …”. It then repeats that 11 times by clicking the left arrow and moving back in time to get all 24 hours. It is essentially automating what the human would do to download the logs. I just learned of this tool a few months ago so I am really a neophyte with it. I can send you the actual code if that’s helpful.

  It is inconsistent because sometimes the cursor ends up slightly off where it needs to be make the correct click, the window doesn’t resize properly, etc. and therefore it fails to save the log correctly. Also, there can be NO other GUI interaction happening on the computer concurrently or the cursor gets all confused and ‘clicks’ in wrong locations. Therefore, I set it up to run very early in the morning hours via cron job.

  A more direct way to download the logs, e.g., simply pull a CSV file, would be more consistent, easier to run in the background, and greatly appreciated.

  • This reply was modified 9 months, 2 weeks ago by Rocket.
• Author
  Posts