-
Notifications
You must be signed in to change notification settings - Fork 31
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
Minimal owampd server configuration #76
Comments
The daemon forks and detaches:
|
@mfeit-internet2 What version do you use? Because
If I use the
|
The example was in a fresh CentOS 7 container with the latest from the perfSONAR repository, which would be 4.4.4. Owampd hasn't changed much in the last 5-7 years. Are you starting owampd as root so it can bind to the (privileged) control port? |
You're right. When I run it as root the forked process successfully runs (btw, does it write its However, it still does require a config file in Although the server is running, the client still cannot connect to it with the following error:
Importantly,
|
Sorry, this got buried. You'd need to have a look at the network and firewall configuration on your system. Running The owamp family of tools isn't very good about writing the specific error to the console. I've opened #77 to improve that. This is bone-stock CentOS 7 with irrelevant text removed for clarity:
|
A newbie here. :)
I have two LXC containers and want to run
owping
between them. One must runowampd
. I'm trying to find the minimal configuration that will allow me to tryowping
.In the installation, I found
installation/root/config/owampd.conf
and copied it over toinstallation/root/etc/owampd-server.conf
. Then I tried:I only get this warning:
But it actually seems fatal. An
owamp-server.pid
is created but the process seems to exit immediately after it prints the warning.Where can I find the minimal config file from which to start?
The text was updated successfully, but these errors were encountered: