Welcome to Pandora FMS Community › Forums › Community support › 3.0rc2, Ubuntu 9.10 Windows agent/server communication not working
-
3.0rc2, Ubuntu 9.10 Windows agent/server communication not working
Posted by guillaume on December 8, 2009 at 23:44Hello, I installed 3.0RC2 on Ubuntu 9.10, then installed some 3.0rc1 agents on Windows 2003 servers. They simply don’t communicate, the server does not discover them and when manually added, in the next contact section it always says out of limits.
When I test the tentacle_client on the windows machine a get an error connect 10061.
Tentacle_server is installed but when I try to start it I get unknown user pandora.Thank you.
Sancho replied 15 years, 2 months ago 3 Members · 9 Replies -
9 Replies
-
-
-
-
-
-
::
sudo service tentacle_serverd start ??, what’s this raul ?, avoid use of untested “shortcuts” in ubuntu please, if “service” is not properly installed probably this doesnt work and installer doesnt use this, at least if I dont remember well.
Just use the standard way:
1. Make sure your pandora user is working
2. Make sure /etc/init.d/tentacle_serverd is present and have the correct attributes.
3. Make yourself root and execute/etc/init.d/tentacle_serverd start
Should work on a standard ubuntu server with “pandora” user created.
-
::
😐 The service command is not proprietary, is installed with the sysvinit-utils package, and it’s available in ubuntu since, at least, 2007, it’s also known to be in other distros (Red Hat, Fedora, and CentOS, for example)
If the service command wasn’t installed, the error will be sudo: service: command not found.
-
-
::
😐 The service command is not proprietary, is installed with the sysvinit-utils package, and it’s available in ubuntu since, at least, 2007, it’s also known to be in other distros (Red Hat, Fedora, and CentOS, for example)
If the service command wasn’t installed, the error will be sudo: service: command not found.
You’re right, I’ve compared two versions of service command (Suse and Ubuntu) and it’s different code but the same mechanism, just “search” for the script in /etc/rcX.D directory and pass the status. stop or start parameter. As everyday, I have the oportunity to learn something new 😎