Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Server does not use "group" specified by agent
#1
Hi All,

I'm trying out the latest version of PandoraFMS server:
. pandorafms_server-5.0SP4-1.noarch
. pandorafms_console-5.0SP4-1.noarch

And agent:
. pandorafms_agent_unix-5.0SP4-1

The agent sends the proper info to the server, including the group which is "sample":
=====
2014/06/09 19:18:20 - [setup] - server_ip is <hidden from forum>
2014/06/09 19:18:20 - [setup] - server_path is /var/spool/pandora/data_in
2014/06/09 19:18:20 - [setup] - temporal is /tmp
2014/06/09 19:18:20 - [setup] - logfile is /var/log/pandora/pandora_agent.log
2014/06/09 19:18:20 - [setup] - interval is 300
2014/06/09 19:18:20 - [setup] - debug is 0
2014/06/09 19:18:20 - [setup] - udp_server is 0
2014/06/09 19:18:20 - [setup] - udp_server_port is 41122
2014/06/09 19:18:20 - [setup] - udp_server_auth_address is 0.0.0.0
2014/06/09 19:18:20 - [setup] - server_port is 41121
2014/06/09 19:18:20 - [setup] - transfer_mode is tentacle
2014/06/09 19:18:20 - [setup] - group is sample
2014/06/09 19:18:20 - [setup] - include is /etc/pandora/pandora_agent.common.inc
2014/06/09 19:18:20 - [setup] - include is /etc/pandora/pandora_agent_cpu_8col.inc
2014/06/09 19:18:20 - [setup] - reading /etc/pandora/pandora_agent.common.inc
2014/06/09 19:18:20 - [setup] - reading /etc/pandora/pandora_agent_cpu_8col.inc
2014/06/09 19:18:20 - [log] - Thread is disabled.
=====

But when I go to the pandora_console, this agent is included under the group "Servers".
How can this be fixed?

Thanks,
-eric
 Reply
#2
Hello

Go to agent detail from where you can see this agent and then click on its name. Click on the manage icon and then just change the group and click on update.

Regards
Ivo
 Reply
#3
Thank you very much for your reply.
We are aware that the group may be changed through the web admin GUI.

Is there a bug in the latest version 5.0SP4 of pandora_console (or tentacle?) which prevents it from using the group name which was specified by the agent?
This used to work in version 4.x

Thanks.
 Reply
#4
Upon further testing, we found that you have to create a group first before agents can add themselves to it.

In the past, a new group would be automatically created on the server when an agent specified a non-existent group.
 Reply
#5
Hello

We will check and inform you on it.

Regards
Ivo
 Reply
#6
I am seeing this in 5.1 as well. I've just set up the appliance, a week or so ago, and have been testing various scenarios (all local agents on Windows) and every agent install has been added to group "servers" instead of the custom group specified in the config file, which was already added to the console before deploying any agents. Not a big deal now, in the lab, but would definitely be a bother if/when we go live.
 Reply
#7
Yes, it was a bug, it will be solve in 5.1 SP1.

Thanks for your contribution
 Reply


Users browsing this thread: 1 Guest(s)


(c) 2006-2018 Artica Soluciones Tecnol├│gicas. Contents of this wiki are under Create Common Attribution v3 licence. | pandorafms.com | pandorafms.org

Theme © MyBB Themes