Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Server not processing agent data
#1
Hi there.

I'm a complete newbie to Pandora. I'm using Pandora for a degree, but I'm having some troubles with it.

I previously thought that the agent (running in local mode in the server machine), wasn't copying data into the var/spool/pandora/data_in directory, but in fact, it IS copying the data. The server just doesn't process that data.

The agent is well configured, it seems. On the server side, however, I tried putting both 127.0.0.1 and the machine address as the agent address, but it refuses to do anything.

On the tactical view, it shows Monitor not init: 2 and Data not init: 1. Clicking on agent details, it still shows agent down.

Does anyone have any clue of where I should look at?

Thanks in advance
 Reply
#2
I suppose you're running fine the Pandora FMS data server, isn't ?

What version and environments are you using ?
 Reply
#3
I'm using Pandora FMS data server, version 1.3.1 on a centos machine. The database is ok, the servers (all 4 of them) are up, and working, but still, there is no way of reading what the agent sends. The idea was to run a local agent (already configured the agent for that), in the very same machine.
 Reply
#4
Quote:[cite]Posted By: decece[/cite][p]I'm using Pandora FMS data server, version 1.3.1 on a centos machine. The database is ok, the servers (all 4 of them) are up, and working, but still, there is no way of reading what the agent sends. The idea was to run a local agent (already configured the agent for that), in the very same machine.[/p]

Check that agent name (or host name) of the agent host, is defined in the console. You need to define first the agent. Pandora 2.0 autocreate agents, but 1.3.x dont.
 Reply
#5
Yes, that's what I did, following the user manual step by step. But no luck so far.

The host (and agent) use a rather long name, could that be the cause?
 Reply
#6
Mmm, i don't know. Try to setup server log verbosity to max (10) and take a look to pandora_server.log and pandora_server.log.err

Sorry but sometimes could be something very simple, but it's hard to find the problem...
 Reply
#7
I know, sometimes the smallest detail can generate great headaches.

I had a few more issues, but this is the last (I hope) remaining problem.
 Reply
#8
Pandora_server.log.err is empty, and pandora_server.log contains some old errors (had problems with mysql server going down, but it's fixed already).

Maybe I should use "localhost" as agent IP address?
 Reply
#9
Let's go....I assume that:

1. XML data file xxxx.data is present on incoming dir of Pandora server.
2. Pandora FMS Server have permissions to delete and read this file.
3. This XML data file is correct (try to rename it and open with firefox).
4. This agent is defined (with the same name that have in the XML header.
5. This agent is defined as learning mode.
6. This agent is not disabled.

Try to put your pandora_server.conf here.
 Reply
#10
Ok, let's see:

1. XML data file xxxx.data is present on incoming dir of Pandora server.

Check. There are several xx.data files, with the 5 minutes (300) interval (in /var/spool/pandora/data_in)

2. Pandora FMS Server have permissions to delete and read this file.

Uncertain. I'm afraid to ask, how do I check?

3. This XML data file is correct (try to rename it and open with firefox).

Check, the files are correct.

4. This agent is defined (with the same name that have in the XML header.

Check.

5. This agent is defined as learning mode.

Check.

6. This agent is not disabled.

Check.

I asume that probably the problem comes from the server side. In the very beggining I thought it was the agent not sending any data, but I already checked that the agent is working fine. The server just leaves the data files without proccessing (thus giving the agent down error).

Pandora_server.conf:

###################################################################################
# Pandora Server Parameters, please change it for your setup needs
###################################################################################

# Servername: Name of this server
# if not given, it takes localhost. It's preferable to setup one
# because machine name could change by some reason.

servername IbercomPandora

# incomingdir: Defines directory where incoming data packets are stored
# You could set directory relative to base path or absolute, starting with /

incomingdir /var/spool/pandora/data_in

# log_file: Main logfile for pandora_server
# You could set file relative to base path or absolute, starting with /

log_file /var/log/pandora/pandora_server.log

# Log file for Pandora FMS SNMP console. Its generated by NetSNMP Trap daemon

snmp_logfile /var/log/pandora/pandora_snmptrap.log

# Error logfile: aux logfile for pandora_server errors (in Daemon mode)
# You could set file relative to base path or absolute, starting with /

errorlog_file /var/log/pandora/pandora_server.error

# dbname: Database name (pandora by default

dbname pandora

# dbuser: Database user name (pandora by default)

dbuser pandora

# daemon: Runs in daemon mode (background) if 1, if 0 runs in foreground
# this could be setup on command line with -D option

# daemon 1

# dbpass: Database password

dbpass ************

# dbhost: Database hostname or IP address

dbhost localhost

# verbosity: level of detail on errors/messages (0 default, 1 verbose, 2 debug.... 10 noisy)
# -v in command line (verbose) or -d (debug)

verbosity 1

# Alert threshold

alert_threshold 45

# Master Server, 1 if master server (normal mode), 0 for slave mode (slave in multi-server setup)

master 1

# Check datafiles using a MD5 hash, 1 to check (default), 0 to ignore .checksum

checksum 0

# Activate Pandora SNMP console (depending on snmptrapd)
# only available on Pandora Network server

snmpconsole 1

# Activate (1) Pandora Network Server

networkserver 1

# Activate (1) Pandora Data Server

dataserver 1

# Activate (1) Pandora FMS Recon server

reconserver 1

# Network timeout (in seconds) for timeout in network connections for Network agents

network_timeout 5

# Server keepalive (in seconds)

server_keepalive 50

# Server Threshold: defines number of seconds of main loop (in sec)

server_threshold 15

network_threads 5

# icmp_checks x : defines number of pings for each icmp_proc module type. at least one of that ping should be 1 to report 1
icmp_checks 2
 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