Saturday, May 18th 2013, 10:11am UTC+2

You are not logged in.

  • Login
  • Register

[solved] inGraph xmlrpc Port problem

Dear visitor, welcome to Monitoring-Portal.
Although this is a german monitoring forum, please don't hesitate to post in English. Nearly everybody here understands you and will answer in English as well.
If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form to register here or read more information about the registration process. If you are already registered, please login here.

fastschwarz

Beginner

Posts: 4

Number of monitoring servers: 2

Nagios Version: icinga 1.6.1

Distributed monitoring: Nein

Redundant monitoring: Ja

Number of hosts: ~ 20

Number of services: > 100

OS: Linux (SLES11,Debian,Ubuntu)

Plugin Version: 1.4.15

NDO Version: 2

1

Friday, December 9th 2011, 2:18pm

[solved] inGraph xmlrpc Port problem

Moin,

hat hier schon mal jemand inGraph in icinga-web zum Laufen gebracht?
Ich quäle mich da jetzt schon seit 2 Tagen mit rum.
Wenn ich das richtig sehe vergisst icinga-web den xmlrpc Port zu setzen.

Zumindest geht laut Firebug die Anfrage immer an Port 80
In /usr/local/icinga-web/app/modules/inGraph/config/inGraph.xml ist der richtige Port gesetzt.

Icinga Web meldet mir diesen Fehler:
Error 403 Forbidden for Proxy

Kommt aber eindeutig über die Anfrage auf Port 80

Verwendete Software:
inGraph.1.0-Beta
icinga-web-1.6.0
icinga-1.6.1
PHP 5.3.5

Hat da jemand ne Idee dazu?

Gruß
Andreas

This post has been edited 1 times, last edit by "fastschwarz" (Dec 9th 2011, 2:55pm)

lippser

Intermediate

Posts: 184

Gender: male

Occupation: Application Developer

Nagios Version: -

Icinga Version: 1.8.0

Distributed monitoring: Nein

Redundant monitoring: Nein

Number of hosts: -

Number of services: -

OS: Ubuntu 12.04

Plugin Version: 1.4.16

2

Friday, December 9th 2011, 2:27pm

Hi,

welchen Port hast du denn in die inGraph.xml eingetragen? Und welcher Port ist in der /etc/ingraph/ingraph-xmlrpc.conf definiert?
NETWAYS GmbH http://www.netways.de
NETWAYS Blog http://blog.netways.de

fastschwarz

Beginner

Posts: 4

Number of monitoring servers: 2

Nagios Version: icinga 1.6.1

Distributed monitoring: Nein

Redundant monitoring: Ja

Number of hosts: ~ 20

Number of services: > 100

OS: Linux (SLES11,Debian,Ubuntu)

Plugin Version: 1.4.15

NDO Version: 2

3

Friday, December 9th 2011, 2:34pm

Beides mal 4999, 5000 ist bei mir belegt

/usr/local/icinga-web/app/modules/inGraph/config/inGraph.xml

Source code

 
1

<ae:parameter name="port">4999</ae:parameter>


/etc/ingraph/ingraph-xmlrpc.conf

Source code

 
1

xmlrpc_port = 4999


Gruß
Andreas

lippser

Intermediate

Posts: 184

Gender: male

Occupation: Application Developer

Nagios Version: -

Icinga Version: 1.8.0

Distributed monitoring: Nein

Redundant monitoring: Nein

Number of hosts: -

Number of services: -

OS: Ubuntu 12.04

Plugin Version: 1.4.16

4

Friday, December 9th 2011, 2:44pm

Agavi Cache gelöscht nach Änderung der inGraph.xml?

Source code

 
1

/usr/local/icinga-web/bin/clearcache.sh


Quoted

Zumindest geht laut Firebug die Anfrage immer an Port 80

Das Backend ist verantwortlich für die XML-RPC Requests, deshalb passt da port 80.
NETWAYS GmbH http://www.netways.de
NETWAYS Blog http://blog.netways.de

fastschwarz

Beginner

Posts: 4

Number of monitoring servers: 2

Nagios Version: icinga 1.6.1

Distributed monitoring: Nein

Redundant monitoring: Ja

Number of hosts: ~ 20

Number of services: > 100

OS: Linux (SLES11,Debian,Ubuntu)

Plugin Version: 1.4.15

NDO Version: 2

5

Friday, December 9th 2011, 2:54pm

Danke bestens, war der Agavi Cache.

Ich bin begeistert ich seh bunte Grafiken ;-)

lippser

Intermediate

Posts: 184

Gender: male

Occupation: Application Developer

Nagios Version: -

Icinga Version: 1.8.0

Distributed monitoring: Nein

Redundant monitoring: Nein

Number of hosts: -

Number of services: -

OS: Ubuntu 12.04

Plugin Version: 1.4.16

6

Friday, December 9th 2011, 3:10pm

Kein Thema :P
NETWAYS GmbH http://www.netways.de
NETWAYS Blog http://blog.netways.de

Similar threads