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

Upgraded to ntopng 2.0 and get the error HTTPserver.cpp:486] ERROR: Unable to start HTTP server (IPv4) on ports 3000 #55

Closed
EdSchmidt opened this issue Jun 16, 2015 · 9 comments

Comments

@EdSchmidt
Copy link

We were running stable on version 1.99. Everything was working fine until the update. I performed the update to hopefully get historical data to work when coming from nprobe. The server is running CentOS 6.6 with the ntop.repo enabled. The ntopng service did not start, so I ran ntopng at the command line. Whether I use my ntopng.conf file or not, I get the same error.

16/Jun/2015 10:25:54 [src/HTTPserver.cpp:486] ERROR: Unable to start HTTP server (IPv4) on ports 3000,3001s Success

port 3000 is not in use

I do see 'User changed to nobody' before the error occurs.

ntopng version is

ntopng-data-2.0.150616-203.noarch
ntopng-2.0.150616-203.x86_64

@lucaderi
Copy link
Member

@EdSchmidt Is the SSL certificate present in httpdocs/ssl?

@EdSchmidt
Copy link
Author

In /usr/share/ntpng/httpdocs/ there is a ntopng-cert.pem file.

From: Luca Deri [mailto:notifications@github.com]
Sent: Tuesday, June 16, 2015 10:56 AM
To: ntop/ntopng
Cc: Schmidt, Edward A.
Subject: Re: [ntopng] Upgraded to ntopng 2.0 and get the error HTTPserver.cpp:486] ERROR: Unable to start HTTP server (IPv4) on ports 3000 (#55)

@EdSchmidthttps://github.com/EdSchmidt Is the SSL certificate present in httpdocs/ssl?


Reply to this email directly or view it on GitHubhttps://github.com//issues/55#issuecomment-112461062.

@lucaderi
Copy link
Member

@EdSchmidt Please provide the complete command line you have used to start ntopng

@EdSchmidt
Copy link
Author

I just moved the .pem file out of the ssl directory and everything works.

@lucaderi
Copy link
Member

Well SSL won't work for sure.

@EdSchmidt
Copy link
Author

-G=/var/tmp/ntopng.pid
-i tcp://127.0.0.1:5556
-n=2
-F=db
-d /var/tmp/ntopng
-w 3000
-m 10.72.0.0/16,10.70.0.0/16,10.1.0.0/16,10.3.7.0/24,10.32.84.0/24,10.11.84.0/24,10.3.22.0/24,10.3.5.0/24,10.3.36.0/24,10.3.30.0/24,74.116.228.0/24,10.75.184.0/22,10.75.0.0/21,10.75.232.0/22,172.25.0.0/16,10.75.176.0/22,10.75.8.0/22,10.75.24.0/24,10.3.18.0/22,10.75.168.0/22,10.75.152.0/22,10.75.168.0/22
-e
-H
-v

@ariava ariava added the Bug label Jun 16, 2015
@ariava ariava added this to the ntopng 2.1 milestone Jun 16, 2015
@ariava ariava self-assigned this Jun 16, 2015
@ariava
Copy link
Contributor

ariava commented Jun 16, 2015

@EdSchmidt how did you generate the pem file? Is it the same one you used with ntopng 1.99?

@ariava ariava closed this as completed Jun 19, 2015
@grinapo
Copy link

grinapo commented Mar 16, 2016

Apart from that being closed this problem is extremely hard to solve since the error messages are probably completely unrelated to the problem: there is error output without the matching syscall, so probably the output is bogus.

("[HTTPserver.cpp:495] ERROR: Unable to start HTTP server (IPv4) on ports 127.0.0.1;3301,127.0.0.1;3302s: Success" - no syscall to give "Success" or "Bad file descriptor" or other random nonsense.)

My PEM was the same as under v1.2.1 and it fails under v2.2. This is Debian/sid, and judging by the strace/ltrace everything is fine except SSL server doesn't work. Probably PEM file isn't what ntopng expects but the only solution is trial-and-error... (It's cat server.key server.crt > ntopng.pem right now.)

@lucaderi
Copy link
Member

Can you please move to version 2.3 and open a bug if the problem is still present?

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

No branches or pull requests

4 participants