dz00te
November 26, 2020, 3:51pm
1
tested installation after latest updates of webproxy,openvpn and bandwidth: install with no error
but ntopng seems to fail when enabled:
ov 26 16:45:14 ns79rc1b systemd: Failed at step EXEC spawning /usr/local/bin/ntopng: No such file or directory
Nov 26 16:45:14 ns79rc1b systemd: Unit ntopng.service entered failed state.
Nov 26 16:45:14 ns79rc1b systemd: ntopng.service failed.
1 Like
giacomo
(Giacomo Sanchietti)
November 26, 2020, 4:02pm
2
I know, but it should be fixed with: Access web applications from port 980 · Issue #6344 · NethServer/dev · GitHub
Could you please verify to have the versions listed in that comment?
dz00te
November 26, 2020, 4:27pm
3
sorry, yes i had already checked, same versions
n2n-2.8.0-539.x86_64
ndpi-3.4.0-2929.x86_64
ntopng-data-4.0.200525-9255.noarch
ntopng-4.2.201125-11566.x86_64
pfring-7.8.0-3283.x86_64
giacomo
(Giacomo Sanchietti)
November 26, 2020, 5:04pm
4
Thank you! Is there anything relevant inside /var/log/messages
or journalctl -u ntopng
?
dz00te
November 26, 2020, 5:26pm
5
not so much:
var/log/messages
Nov 26 18:07:30 ns79rc1b systemd: ntopng.service holdoff time over, scheduling restart.
Nov 26 18:07:30 ns79rc1b systemd: Stopped ntopng high-speed web-based traffic monitoring and analysis tool.
Nov 26 18:07:30 ns79rc1b systemd: Starting ntopng high-speed web-based traffic monitoring and analysis tool...
Nov 26 18:07:30 ns79rc1b systemd: Started ntopng high-speed web-based traffic monitoring and analysis tool.
Nov 26 18:07:30 ns79rc1b systemd: Failed at step EXEC spawning /usr/local/bin/ntopng: No such file or directory
Nov 26 18:07:30 ns79rc1b systemd: ntopng.service: main process exited, code=exited, status=203/EXEC
Nov 26 18:07:30 ns79rc1b systemd: Unit ntopng.service entered failed state.
Nov 26 18:07:30 ns79rc1b systemd: ntopng.service failed.
journal
Nov 26 18:08:07 ns79rc1b.framassa.local systemd[1]: ntopng.service holdoff time over, scheduling restart.
Nov 26 18:08:07 ns79rc1b.framassa.local systemd[1]: Stopped ntopng high-speed web-based traffic monitoring and analysis tool.
Nov 26 18:08:07 ns79rc1b.framassa.local systemd[1]: Starting ntopng high-speed web-based traffic monitoring and analysis tool...
Nov 26 18:08:07 ns79rc1b.framassa.local systemd[1]: Started ntopng high-speed web-based traffic monitoring and analysis tool.
Nov 26 18:08:07 ns79rc1b.framassa.local systemd[1]: ntopng.service: main process exited, code=exited, status=203/EXEC
Nov 26 18:08:07 ns79rc1b.framassa.local systemd[1]: Unit ntopng.service entered failed state.
Nov 26 18:08:07 ns79rc1b.framassa.local systemd[1]: ntopng.service failed.
and
# systemctl status ntopng
● ntopng.service - ntopng high-speed web-based traffic monitoring and analysis tool
Loaded: loaded (/etc/systemd/system/ntopng.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2020-11-26 18:11:37 CET; 3s ago
Process: 31223 ExecStopPost=/bin/rm -rf /run/ntopng.conf (code=exited, status=0/SUCCESS)
Process: 31221 ExecStart=/usr/local/bin/ntopng /run/ntopng.conf (code=exited, status=203/EXEC)
Process: 31217 ExecStartPre=/bin/sh -c /bin/sed "/^[ ]*-e.*$\|^[ ]*-G.*\|^[ ]*--daemon.*\|^[ ]*--pid.*/s/^/#/" /etc/ntopng/ntopng.conf > /run/ntopng.conf (code=exited, status=0/SUCCESS)
Process: 31196 ExecStartPre=/bin/sh -c /usr/bin/ntopng-utils-manage-config -a check-restore && /usr/bin/ntopng-utils-manage-config -a restore || true (code=exited, status=0/SUCCESS)
Main PID: 31221 (code=exited, status=203/EXEC)
but ntopng seems to be in /usr/bin/ntopng , so i changed the ExecStart in ntopng.service, and it seems to work, or at least it starts
giacomo
(Giacomo Sanchietti)
November 30, 2020, 8:25am
6
Sorry for the late response, I took a day off
This indeed a bug: https://github.com/NethServer/dev/issues/6350
It was a changed asked by me to upstream, but I didn’t expect that it could land so soon inside the release.
I’m going to fix it, thanks for reporting!
Also I would like to ask: did you notice an increased CPU usage from the new ntopng page?
3 Likes
giacomo
(Giacomo Sanchietti)
November 30, 2020, 4:47pm
7
The original issue has been fixed and verified
Thanks to @francio87 !
1 Like