Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Luaengine script error every minute spams the hostlog with 10´s of thousands of lines a day. #9011

Open
DerRealKeyser opened this issue Mar 1, 2025 · 0 comments

Comments

@DerRealKeyser
Copy link

Environment:

  • OS name: [e.g. Ubuntu]: Raspbian OS (Debian)
  • OS version: [e.g. 18.04]: 12 / Bookworm
  • Architecture: [e.g. amd64]: ARM64
  • ntopng version/revision: [e.g. 5.1.211223]: 6.3.250213 and 6.3.250222

What happened:
Every minute the logs on my NtopNG embedded installs on Raspberry PI 4 and 5 hardware gets spammed with the following sequence:

ntopng[5785]: 17/Feb/2025 12:06:19 [LuaEngine.cpp:702] WARNING: /usr/share/ntopng/scripts/lua/modules/asset_utils.lua:21: bad argument #1 to 'for iterator' (table expected, got string) [/usr/share/ntopng/scripts/callbacks/minute-delayed/interface/inactive_assets.lua]
ntopng[5785]: ERROR: table expected, got string
ntopng[5785]: stack traceback:
ntopng[5785]: /usr/share/ntopng/scripts/lua/modules/ntop_utils.lua:181: in function 'table.len'
ntopng[5785]: /usr/share/ntopng/scripts/lua/modules/asset_utils.lua:278: in function 'asset_utils.getLastVersion'
ntopng[5785]: ...s/callbacks/minute-delayed/interface/inactive_assets.lua:27: in main chunk
ntopng[5785]: 17/Feb/2025 12:06:19 [LuaEngine.cpp:702] WARNING: /usr/share/ntopng/scripts/lua/modules/asset_utils.lua:21: bad argument #1 to 'for iterator' (table expected, got string) [/usr/share/ntopng/scripts/callbacks/minute-delayed/interface/inactive_assets.lua]

How did you reproduce it?
It always present after updating to 6.3.xxx daily builds

Debug Information:

There is no point in pasting the journalctl log for ntopng here. It's justs hundreds of thousands of repeats of the reported lines above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant