-
Notifications
You must be signed in to change notification settings - Fork 673
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
Error to start ntopng #2111
Comments
Hi, please remove the --daemon option from the config. The ntopng service will automatically read /etc/ntopng/ntopng.conf on startup. Can you try to manually start ntopng from command line and get a backtrace of the crash as described here? https://github.com/ntop/ntopng/blob/dev/doc/README.crash |
Hi, thanks for your asnwer. I removed --daemon option from the config, but error message still on console. gdb --args ntopng /etc/ntopng/ntopng.conf Program received signal SIGSEGV, Segmentation fault. |
This is the same issue as #2021 . The fix has not been backported to stable |
Now backported with 12f6373 . A new package will be available in one hour. Thank you for reporting. |
Hi! It´s working!! |
Hi, when i try run ntopng with file config path, console inform the follow error:
"ntopng /etc/ntopng/ntopng.conf
Segmentation fault"
However, on the reeset/start machine, ntopng take config, but i dont know from wich file config.
Data SO:
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
Nntopng version:
ntopng Enterprise Edition v.3.6.181017
ntopng.conf:
-G=/var/run/ntopng.pid
--online-license-check
--local-networks="10.0.0.0/16,10.1.0.0/16,10.2.0.0/16,10.1.1.0/24,10.3.0.0/16,10.4.0.0/16, 10.7.0.0/16,10.8.0.0/20,10.16.0.0/20,172.17.0.0/16"
--interface="tcp://10.1.0.26:5555"
--interface="tcp://10.1.0.26:5556"
--interface="tcp://10.1.0.26:5557"
--interface="tcp://10.1.0.26:5558"
--interface="tcp://10.1.0.26:5559"
--daemon
--enable-aggregations
--max-num-flows=200000
--max-num-hosts=250000
--sticky-hosts
Thanks for you attention.
The text was updated successfully, but these errors were encountered: