Closed Taralas closed 3 years ago
@Taralas I remember you had a bunch of failures, some of them were due to the inability to find lua modules (we pushed a fix for this some time ago), could you confirm you are no longer experiencing those failures? Is this the only message you get now, or you have more logs? Thank you.
That is the only message that I am receiving at this time.
Please drop an email to cardigliano at ntop.org, I will send a debug binary
ntopng binaries were crashing upon application startup until yesterday's release. Today's version seems to be running and it is executing (with debug symbols) at the user premises. We will wait for updates.
Sorry on the lack of updates. Work has been a bit difficult. I was able to get some time this morning, and ran the last debug build, and had two crashes, both with no stack traces:
14/Oct/2021 11:45:01 [LuaEngine.cpp:560] WARNING: Script failure {/usr/local/share/ntopng/scripts/callbacks/system/discover.lua][attempt to index a string value] PANIC: unprotected error in call to Lua API (attempt to index a function value) Abort trap During startup program exited with code 134. (gdb) bt No stack.
14/Oct/2021 12:15:01 [LuaEngine.cpp:560] WARNING: Script failure [/usr/local/share/ntopng/scripts/callbacks/system/discover.lua][attempt to index a string value] Segmentation fault During startup program exited with code 139. (gdb) bt No stack.
Shawn Hurst (262) 497-7787
From: Alfredo @.> Sent: Thursday, October 7, 2021 11:59 AM To: @.> Cc: Shawn @.>; @.> Subject: Re: [ntop/ntopng] Segfault on pfSense related to LuaEngine (#5929)
ntopng binaries were crashing upon application startup until yesterday's release. Today's version seems to be running and it is executing (with debug symbols) at the user premises. We will wait for updates.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/ntop/ntopng/issues/5929#issuecomment-937982032, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AABKN6GFOA7MLEDGE2VR4ILUFXGVRANCNFSM5E5TJWNA.
From last night:
14/Oct/2021 20:45:00 [LuaEngine.cpp:560] WARNING: Script failure [/usr/local/share/ntopng/scripts/callbacks/system/discover.lua][attempt to index a string value] PANIC: unprotected error in call to Lua API (attempt to index a function value) Abort trap During startup program exited with code 134. (gdb) bt No stack.
From: Shawn @.> Sent: Thursday, October 14, 2021 12:18 PM To: @.> Cc: Shawn @.>; Your @.> Subject: Re: [ntop/ntopng] Segfault on pfSense related to LuaEngine (#5929)
Sorry on the lack of updates. Work has been a bit difficult. I was able to get some time this morning, and ran the last debug build, and had two crashes, both with no stack traces:
14/Oct/2021 11:45:01 [LuaEngine.cpp:560] WARNING: Script failure {/usr/local/share/ntopng/scripts/callbacks/system/discover.lua][attempt to index a string value] PANIC: unprotected error in call to Lua API (attempt to index a function value) Abort trap During startup program exited with code 134. (gdb) bt No stack.
14/Oct/2021 12:15:01 [LuaEngine.cpp:560] WARNING: Script failure [/usr/local/share/ntopng/scripts/callbacks/system/discover.lua][attempt to index a string value] Segmentation fault During startup program exited with code 139. (gdb) bt No stack.
Shawn Hurst (262) 497-7787
From: Alfredo @.> Sent: Thursday, October 7, 2021 11:59 AM To: @.> Cc: Shawn @.>; @.> Subject: Re: [ntop/ntopng] Segfault on pfSense related to LuaEngine (#5929)
ntopng binaries were crashing upon application startup until yesterday's release. Today's version seems to be running and it is executing (with debug symbols) at the user premises. We will wait for updates.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/ntop/ntopng/issues/5929#issuecomment-937982032, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AABKN6GFOA7MLEDGE2VR4ILUFXGVRANCNFSM5E5TJWNA.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/ntop/ntopng/issues/5929#issuecomment-943560710, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AABKN6ERBLT7KFLZYM2LLA3UG4GFJANCNFSM5E5TJWNA.
@Taralas please be patient a bit more as we are testing new fixes that could also fix your issue. Sorry for the inconvenience.
Not a problem. Real troubleshooting takes time 😉
From: Alfredo @.> Sent: Friday, October 15, 2021 9:27 AM To: @.> Cc: Shawn @.>; @.> Subject: Re: [ntop/ntopng] Segfault on pfSense related to LuaEngine (#5929)
@Taralashttps://github.com/Taralas please be patient a bit more as we are testing new fixes that could also fix your issue. Sorry for the inconvenience.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/ntop/ntopng/issues/5929#issuecomment-944346242, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AABKN6FAR7ILC3NEMBVXZJLUHA223ANCNFSM5E5TJWNA.
@Taralas Can you please update and report: we believe we have fixed the issues
Other users have reported that the issue has been fixed on pfSense. So I'm closing for now, asking @Taralas to check and reopen if necessary.
Sadly, I am still getting nightly crashes, but I do not believe they are related to the lua issues.
From: Simone @.> Sent: Thursday, October 28, 2021 3:03 AM To: @.> Cc: Shawn @.>; @.> Subject: Re: [ntop/ntopng] Segfault on pfSense related to LuaEngine (#5929)
Other users have reported that the issue has been fixed on pfSense. So I'm closing for now, asking @Taralashttps://github.com/Taralas to check and reopen if necessary.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/ntop/ntopng/issues/5929#issuecomment-953598461, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AABKN6CE4FJ5VVF5YIBBHCDUJEGXJANCNFSM5E5TJWNA.
Using pfSense 21.05.1-RELEASE (amd64) on a Netgate SG-4860, with v.5.1.210927 from the ntop pkg repo, I am receiving the following error approximately 15-45 minutes after starting:
I was originally working with alfredo.cardigliano via the Discord on this issue. I have a coredump from a previous version that was also exhibiting the same behavior, which I would love to attach, but GitHub is choking on after being compressed