Closed rreiner closed 10 months ago
Please update ntopng and report
Updated to v.5.7.231010 No change in the problem.
Oct 10 17:00:48 pinkeye systemd[1]: ntopng.service: Main process exited, code=killed, status=7/BUS
Oct 10 17:05:48 pinkeye systemd[1]: ntopng.service: Main process exited, code=killed, status=7/BUS
Oct 10 17:10:48 pinkeye systemd[1]: ntopng.service: Main process exited, code=killed, status=7/BUS
Oct 10 17:15:48 pinkeye systemd[1]: ntopng.service: Main process exited, code=killed, status=7/BUS
Oct 10 17:20:46 pinkeye systemd[1]: ntopng.service: Main process exited, code=killed, status=7/BUS
Oct 10 17:25:47 pinkeye systemd[1]: ntopng.service: Main process exited, code=killed, status=7/BUS
Oct 10 17:30:49 pinkeye systemd[1]: ntopng.service: Main process exited, code=killed, status=7/BUS
Oct 10 17:35:49 pinkeye systemd[1]: ntopng.service: Main process exited, code=killed, status=7/BUS
Oct 10 17:40:48 pinkeye systemd[1]: ntopng.service: Main process exited, code=killed, status=7/BUS
Oct 10 17:45:49 pinkeye systemd[1]: ntopng.service: Main process exited, code=killed, status=7/BUS
@rreiner Can you please download https://www.dropbox.com/scl/fi/gsygutkjt3y0w4rexipy7/ntopng-rpi-arm64-debug.tgz?rlkey=csjut57lau1jhoh0sjhe1m29f&dl=0 and run it (instead of the binary you are using) then paste here the crash report? Thanks
@lucaderi That's a 64-bit binary; but I'm running a 32-bit version of the OS Sorry if my "architecture" tag misled you in the OP; that's the hardware architecture, but it's running an older install with the 32-bit version of Raspbian
can you please update the package from packages.ntop.org first and report if it still crashing (we have fixed a bug yesterday) ? If so I will create a debug for 32 bit
Now running v.5.7.231012 No change in the crashes -- they continue to occur almost exactly 5 minutes after each restart.
Oct 12 17:35:46 pinkeye systemd[1]: ntopng.service: Main process exited, code=killed, status=7/BUS
Oct 12 17:40:46 pinkeye systemd[1]: ntopng.service: Main process exited, code=killed, status=7/BUS
Oct 12 17:45:48 pinkeye systemd[1]: ntopng.service: Main process exited, code=killed, status=7/BUS
Oct 12 17:50:47 pinkeye systemd[1]: ntopng.service: Main process exited, code=killed, status=7/BUS
Oct 12 17:55:48 pinkeye systemd[1]: ntopng.service: Main process exited, code=killed, status=7/BUS
Received the update to v5.7.231015.
Crashes continue every 5 minutes.
Can you please try to crash https://www.dropbox.com/s/gey08a37qgn294l/ntopng-debug.tgz?dl=0 and report? Thank you
@rreiner Do you have an update perhaps?
Sorry, I'm traveling this weekend, can get to this Sunday evening or Monday
-- Sent from my phone
On Sat, Oct 21, 2023, 11:14 Luca Deri @.***> wrote:
@rreiner https://github.com/rreiner Do you have an update perhaps?
— Reply to this email directly, view it on GitHub https://github.com/ntop/ntopng/issues/7887#issuecomment-1773826208, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6TFYNKDUJ4YABSJUTQ5WTYAPRFHAVCNFSM6AAAAAA5ZDK46CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZTHAZDMMRQHA . You are receiving this because you were mentioned.Message ID: @.***>
It's still crashing in the same way with the debug binary.
Is it writing some log data somewhere that I can retrieve and send to you?
You should use the debug binary I have sent you to generate a coredump and share it with me for inspection. Is this possible?
Are you sure this core was generated with the debug binary I have sent you? It says
$ file core-ntopng-S-upload-7-997-993-2336-1698012647 core-ntopng-S-upload-7-997-993-2336-1698012647: ELF 32-bit LSB core file, ARM, version 1 (SYSV), SVR4-style, from '/usr/bin/ntopng /etc/ntopng/ntopng.conf', real uid: 0, effective uid: 0, real gid: 0, effective gid: 0, execfn: '/usr/bin/ntopng', platform: 'v7l'
I have sent you ntopng-debug and I expected to see this binary used in the core.
Yes, it was generated with the debug binary. I renamed it to ntopng. Conf file attached (renamed to ntopng.conf.txt so that Github allows the file type)
Can you please also attach /var/lib/ntopng/protos.txt ?
@rreiner I haven't managed to crash it nor to understand the culprit with you core dump. Can you please mail me (deri@ntop.org) so that we can arrange an interactive session? Thanks
@lucaderi Looks like the corrupted rrd file explanation is correct -- after deleting two more rrd files, I am seeing no more crashes. Thanks for the assistance!
Thanks for reporting
Environment:
What happened: ntopng's main process dies on signal 7 (bus error ).
The installation was previously stable.
Each time the system log shows a sequence like this:
This is happening approximately every 5 minutes, even when there is no user interaction with ntopng.
How did you reproduce it? Wait 5 minutes and check the logs:
Debug Information: Longer continuous extract from the journal, for context: