Thanks
Niranjan
On Fri, May 23, 2014 at 5:10 PM, <icinga-users-requ...@lists.icinga.org
<mailto:icinga-users-requ...@lists.icinga.org>> wrote:
Send icinga-users mailing list submissions to
icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org>
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.icinga.org/mailman/listinfo/icinga-users
or, via email, send a message with subject or body 'help' to
icinga-users-requ...@lists.icinga.org
<mailto:icinga-users-requ...@lists.icinga.org>
You can reach the person managing the list at
icinga-users-ow...@lists.icinga.org
<mailto:icinga-users-ow...@lists.icinga.org>
When replying, please edit your Subject line so it is more specific
than "Re: Contents of icinga-users digest..."
Today's Topics:
1. Re: icinga-users Digest, Vol 5, Issue 13 (Michael Friedrich)
----------------------------------------------------------------------
Message: 1
Date: Fri, 23 May 2014 23:10:44 +0200
From: Michael Friedrich <michael.friedr...@gmail.com
<mailto:michael.friedr...@gmail.com>>
To: "Icinga User's Corner" <icinga-users@lists.icinga.org
<mailto:icinga-users@lists.icinga.org>>
Subject: Re: [icinga-users] icinga-users Digest, Vol 5, Issue 13
Message-ID:
<cao443j+icbqvtnkutuj5covtnryoc8g379kjq37f7gxhqsb...@mail.gmail.com
<mailto:cao443j%2bicbqvtnkutuj5covtnryoc8g379kjq37f7gxhqsb...@mail.gmail.com>>
Content-Type: text/plain; charset="utf-8"
Your env variables are not the same as from my example. Why?
Am 23.05.2014 21:17 schrieb "Niranjan Babu Bommu"
<niranjan.bo...@gmail.com <mailto:niranjan.bo...@gmail.com>
>:
> Hi,
>
> I made the change and tested, still I'm seeing pagerduty is rejecting
> messages.
>
> Error in the logs:
>
> Icinga event in file /tmp/pagerduty_icinga/pd_1400871969_22062.txt
> REJECTED by the PagerDuty server. Server says: The
NOTIFICATIONTYPE field
> must be present and must be one of: PROBLEM, ACKNOWLEDGEMENT,
RECOVERY,
> NOP.#012The following fields must be present when pd_nagios_object =
> service: HOSTNAME, SERVICEDESC, SERVICESTATE
>
> Exiting config files:
>
> object NotificationCommand "notify-service-by-pagerduty" {
> import "plugin-notification-command"
> command = "/usr/local/bin/pagerduty_icinga.pl
<http://pagerduty_icinga.pl> enqueue -f
> pd_nagios_object=service"
>
> env = {
> "NOTIFICATIONTYPE" = "$notification.type$"
> "SERVICEDESC" = "$service.name <http://service.name>$"
> "HOSTALIAS" = "$host.display_name$",
> "HOSTADDRESS" = "$address$",
> "SERVICESTATE" = "$service.state$",
> "LONGDATETIME" = "$icinga.long_date_time$",
> "SERVICEOUTPUT" = "$service.output$",
> "NOTIFICATIONAUTHORNAME" = "$notification.author$",
> "NOTIFICATIONCOMMENT" = "$notification.comment$",
> "HOSTDISPLAYNAME" = "$host.display_name$",
> "SERVICEDISPLAYNAME" = "$service.display_name$",
> "CONTACTPAGER" = "$user.pager$"
> }
> }
> object NotificationCommand "notify-host-by-pagerduty" {
> import "plugin-notification-command"
> command = "/usr/local/bin/pagerduty_icinga.pl
<http://pagerduty_icinga.pl> enqueue -f
> pd_nagios_object=host"
>
> env = {
> "NOTIFICATIONTYPE" = "$notification.type$"
> "SERVICEDESC" = "$service.name <http://service.name>$"
> "HOSTALIAS" = "$host.display_name$",
> "HOSTADDRESS" = "$address$",
> "SERVICESTATE" = "$service.state$",
> "LONGDATETIME" = "$icinga.long_date_time$",
> "SERVICEOUTPUT" = "$service.output$",
> "NOTIFICATIONAUTHORNAME" = "$notification.author$",
> "NOTIFICATIONCOMMENT" = "$notification.comment$",
> "HOSTDISPLAYNAME" = "$host.display_name$",
> "SERVICEDISPLAYNAME" = "$service.display_name$",
> "CONTACTPAGER" = "$user.pager$"
> }
> }
>
> template Notification "pagerduty-service" {
>
> command = "notify-service-by-pagerduty"
> states = [ OK, Warning, Critical, Unknown ]
> types = [ Problem, Acknowledgement, Recovery ]
>
> period = "24x7"
> }
>
> template Notification "pagerduty-host" {
>
> command = "notify-host-by-pagerduty"
> states = [ OK, Warning, Critical, Unknown ]
> types = [ Problem, Acknowledgement, Recovery ]
>
> period = "24x7"
> }
>
>
>
> On Wed, May 21, 2014 at 4:14 PM,
<icinga-users-requ...@lists.icinga.org
<mailto:icinga-users-requ...@lists.icinga.org>>wrote:
>
>> Send icinga-users mailing list submissions to
>> icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org>
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://lists.icinga.org/mailman/listinfo/icinga-users
>> or, via email, send a message with subject or body 'help' to
>> icinga-users-requ...@lists.icinga.org
<mailto:icinga-users-requ...@lists.icinga.org>
>>
>> You can reach the person managing the list at
>> icinga-users-ow...@lists.icinga.org
<mailto:icinga-users-ow...@lists.icinga.org>
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of icinga-users digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Re: Errors upgrading idoutils to versions 1.12.0
(Alexander Wirt)
>> 2. Pagerduty in icinga2 (Niranjan Babu Bommu)
>> 3. Re: Pagerduty in icinga2 (Michael Friedrich)
>> 4. Re: Pagerduty in icinga2 (Michael Friedrich)
>> 5. Re: Errors upgrading idoutils to versions 1.12.0
>> (Michael Friedrich)
>> 6. Re: unable to pass http basic authentication with icinga2go
>> (Michael Friedrich)
>> 7. Re: Icinga web: ajax calls 'statusOverall' and
>> 'monitorPerformance' fail (Michael Friedrich)
>>
>>
>>
----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Wed, 21 May 2014 15:19:24 +0200
>> From: Alexander Wirt <formo...@formorer.de
<mailto:formo...@formorer.de>>
>> To: Icinga User's Corner <icinga-users@lists.icinga.org
<mailto:icinga-users@lists.icinga.org>>
>> Subject: Re: [icinga-users] Errors upgrading idoutils to versions
>> 1.12.0
>> Message-ID: <20140521131923.gb12...@lisa.snow-crash.org
<mailto:20140521131923.gb12...@lisa.snow-crash.org>>
>> Content-Type: text/plain; charset=iso-8859-1
>>
>> On Wed, 21 May 2014, Andr? Freitas wrote:
>>
>> > How do i do that?
>> >
>> > On Wed, 2014-05-21 at 11:31 +0200, Alexander Wirt wrote:
>> > > On Wed, 21 May 2014, Andr? Freitas wrote:
>> > >
>> > > > Hi,
>> > > >
>> > > > i was upgrading my icinga core from version 1.10.0 to
1.11.3 and
>> one of
>> > > > the recommend steps is to upgrade the idoutils to the last
version.
>> From
>> > > > what i understand from documentation regarding idoutils
upgrade, i
>> had
>> > > > to make all incremetal steps from 1.10 -> 1.11 -> 1.11.3 ->
>> 1.12.0.sql
>> > > > but in the various steps i have a few errors. What should
i do to
>> > > > resolve this?
>> > > wait. there is a bug in the package.
>> > >
>> > > Or apply the update by hand and say dbconfig that you don't
want it
>> to apply
>> > > the update.
>> I uploaded fixed packages to debian unstable, the ubuntu ppa and
debmon a
>> few
>> minutes ago. It may take a few hours until they are available on all
>> platforms.
>>
>> Alex
>>
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Wed, 21 May 2014 12:06:25 -0400
>> From: Niranjan Babu Bommu <niranjan.bo...@gmail.com
<mailto:niranjan.bo...@gmail.com>>
>> To: icinga-users@lists.icinga.org
<mailto:icinga-users@lists.icinga.org>
>> Subject: [icinga-users] Pagerduty in icinga2
>> Message-ID:
>> <
>>
ca+7hzvnzeerjmq4gfjtnofcxj23z-rkdds7sb0hmv07iu1z...@mail.gmail.com
<mailto:ca%2b7hzvnzeerjmq4gfjtnofcxj23z-rkdds7sb0hmv07iu1z...@mail.gmail.com>>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hi,
>>
>> I'm having difficult time to setup pagerduty in incinga2, can
any one
>> please help me out on this.
>>
>> I followed these instructions.
>>
>> http://www.pagerduty.com/docs/guides/icinga-integration-guide/
>> --
>> *Thanks*
>> *Niranjan*
>> *+1 781.956.6900 <tel:%2B1%20781.956.6900>*
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <
>>
http://lists.icinga.org/pipermail/icinga-users/attachments/20140521/d69f4b0b/attachment-0001.html
>> >
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Wed, 21 May 2014 18:52:05 +0200
>> From: Michael Friedrich <michael.friedr...@gmail.com
<mailto:michael.friedr...@gmail.com>>
>> To: icinga-users@lists.icinga.org
<mailto:icinga-users@lists.icinga.org>
>> Subject: Re: [icinga-users] Pagerduty in icinga2
>> Message-ID: <537cd9b5.7030...@gmail.com
<mailto:537cd9b5.7030...@gmail.com>>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>> On 21.05.2014 18 <tel:21.05.2014%2018>:06, Niranjan Babu Bommu
wrote:
>> >
>> > Hi,
>> >
>> > I'm having difficult time to setup pagerduty in incinga2, can
any one
>> > please help me out on this.
>> >
>> > I followed these instructions.
>> >
>> > http://www.pagerduty.com/docs/guides/icinga-integration-guide/
>>
>> That's written for Icinga 1.x as there is no official final
release of
>> Icinga 2 yet. But soon, Beta is up for next.
>>
>> Creating a notification, a user (and group) as well as notification
>> commands is presumingly easy following the Icinga 2 documentation.
>>
>> The pagerduty script uses environment variables, but does not
tell which
>> ones are required and which are not. You should ask them about
it and
>> modify your notification command setting the required environment
>> variables.
>>
>> Icinga 2 does not export everything into the environment unlike
Icinga
>> 1.x does. But rather allows you to define which variable is
exported and
>> which macro value should be fetched.
>>
>>
>> best regards,
>> Michael
>>
>>
>>
>> --
>> DI (FH) Michael Friedrich
>>
>> michael.friedr...@gmail.com <mailto:michael.friedr...@gmail.com>
|| icinga open source monitoring
>> https://twitter.com/dnsmichi || lead core developer
>> dnsmi...@jabber.ccc.de <mailto:dnsmi...@jabber.ccc.de> ||
https://www.icinga.org/team
>> irc.freenode.net/icinga <http://irc.freenode.net/icinga> ||
dnsmichi
>>
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Wed, 21 May 2014 20:29:23 +0200
>> From: Michael Friedrich <michael.friedr...@gmail.com
<mailto:michael.friedr...@gmail.com>>
>> To: icinga-users@lists.icinga.org
<mailto:icinga-users@lists.icinga.org>
>> Subject: Re: [icinga-users] Pagerduty in icinga2
>> Message-ID: <537cf083.8060...@gmail.com
<mailto:537cf083.8060...@gmail.com>>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>> On 21.05.2014 18 <tel:21.05.2014%2018>:52, Michael Friedrich
wrote:> On 21.05.2014 18 <tel:21.05.2014%2018>:06,
>> Niranjan Babu Bommu wrote:
>> >>
>> >> Hi,
>> >>
>> >> I'm having difficult time to setup pagerduty in incinga2,
can any one
>> >> please help me out on this.
>> >>
>> >> I followed these instructions.
>> >>
>> >> http://www.pagerduty.com/docs/guides/icinga-integration-guide/
>> >
>> > That's written for Icinga 1.x as there is no official final
release of
>> > Icinga 2 yet. But soon, Beta is up for next.
>> >
>> > Creating a notification, a user (and group) as well as
notification
>> > commands is presumingly easy following the Icinga 2
documentation.
>> >
>> > The pagerduty script uses environment variables, but does not
tell
>> which
>> > ones are required and which are not. You should ask them
about it and
>> > modify your notification command setting the required environment
>> > variables.
>> >
>> > Icinga 2 does not export everything into the environment
unlike Icinga
>> > 1.x does. But rather allows you to define which variable is
exported
>> and
>> > which macro value should be fetched.
>>
>> I've sent them a mail asking which macros are required. In the
meantime
>> you can try the untested on-the-fly configuration I've sent them too
>> after getting insights which environment macros are used:
>>
>> [--QUOTE--]
>> Generally, the four required environment variables are noted int the
>> following cURL-call example:
>>
>> curl -d "pd_nagios_object=host" -d
>> "CONTACTPAGER=13a49387497498987497849784914" -d
>> "NOTIFICATIONTYPE=PROBLEM" -d "HOSTSTATE=down"
>> http://events.pagerduty.com/nagios/2010-04-15/create_event
>>
>> However, we also recommend that users also include the additional
>> variables noted here:
>>
>>
https://support.pagerduty.com/entries/23579473-Customizing-Phone-SMS-Messages-in-Nagios.
>>
[--QUOTE--<https://support.pagerduty.com/entries/23579473-Customizing-Phone-SMS-Messages-in-Nagios.%5B--QUOTE-->
>> ]
>>
>> [--SNIP--]
>> object NotificationCommand "notify-service-by-pagerduty" {
>> import "plugin-notification-command"
>> command = "/usr/local/bin/pagerduty_icinga.pl
<http://pagerduty_icinga.pl> enqueue -f
>> pd_nagios_object=service"
>>
>> env = {
>> "CONTACTPAGER" = "$user.pager$"
>> "NOTIFICATIONTYPE" = "$notification.type$"
>> "SERVICEDESC" = "$service.name <http://service.name>$"
>> "HOSTNAME" = "$host.name <http://host.name>$"
>> "HOSTALIAS" = "$host.display_name$"
>> "SERVICESTATE" = "$service.state$"
>> "SERVICEOUTPUT" = "$service.output$"
>> }
>> }
>>
>> object NotificationCommand "notify-host-by-pagerduty" {
>> import "plugin-notification-command"
>> command = "/usr/local/bin/pagerduty_icinga.pl
<http://pagerduty_icinga.pl> enqueue -f
>> pd_nagios_object=host"
>>
>> env = {
>> "CONTACTPAGER" = "$user.pager$"
>> "NOTIFICATIONTYPE" = "$notification.type$"
>> "HOSTNAME" = "$host.name <http://host.name>$"
>> "HOSTALIAS" = "$host.display_name$"
>> "HOSTSTATE" = "$host.state$"
>> "HOSTOUTPUT" = "$host.output$"
>> }
>> }
>>
>> object User "pagerduty" {
>> display_name = "PagerDuty Notification User"
>> pager = "<YOURPAGERDUTYSERVICEKEY>"
>> }
>>
>> apply Notification "pagerduty-service" to Service {
>> command = "notify-service-by-pagerduty"
>> states = [ OK, Warning, Critical, Unknown ]
>> types = [ Problem, Acknowledgement, Recovery, Custom ]
>> period = "24x7"
>> users = [ "pagerduty" ]
>>
>> assign where service.vars.enable_pagerduty == true
>> }
>>
>> apply Notification "pagerduty-host" to Host {
>> command = "notify-host-by-pagerduty"
>> states = [ Up, Down ]
>> types = [ Problem, Acknowledgement, Recovery, Custom ]
>> period = "24x7"
>> users = [ "pagerduty" ]
>>
>> assign where host.vars.enable_pagerduty == true
>> }
>>
>> object Service "pagerduty-test-service" {
>> import "generic-service"
>> check_command = "ping4"
>> host_name = "pagerduty-test-host"
>>
>> vars.enable_pagerduty = true
>> }
>>
>> object Host "pagerduty-test-host" {
>> import "generic-host"
>> address = "127.0.0.1"
>>
>> vars.enable_pagerduty = true
>> }
>> [--SNIP--]
>>
>>
>> Remember, I did not test that configuration not having an pagerduty
>> around - it may contain validation errors, so verify it working,
and if
>> not, please fix it and post feedback here.
>>
>> best regards,
>> Michael
>>
>>
>> --
>> DI (FH) Michael Friedrich
>>
>> michael.friedr...@gmail.com <mailto:michael.friedr...@gmail.com>
|| icinga open source monitoring
>> https://twitter.com/dnsmichi || lead core developer
>> dnsmi...@jabber.ccc.de <mailto:dnsmi...@jabber.ccc.de> ||
https://www.icinga.org/team
>> irc.freenode.net/icinga <http://irc.freenode.net/icinga> ||
dnsmichi
>>
>>
>> ------------------------------
>>
>> Message: 5
>> Date: Wed, 21 May 2014 21:47:21 +0200
>> From: Michael Friedrich <michael.friedr...@gmail.com
<mailto:michael.friedr...@gmail.com>>
>> To: icinga-users@lists.icinga.org
<mailto:icinga-users@lists.icinga.org>
>> Subject: Re: [icinga-users] Errors upgrading idoutils to versions
>> 1.12.0
>> Message-ID: <537d02c9.5050...@gmail.com
<mailto:537d02c9.5050...@gmail.com>>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>> On 21.05.2014 11 <tel:21.05.2014%2011>:23, Andr? Freitas wrote:
>> > Hi,
>> >
>> > i was upgrading my icinga core from version 1.10.0 to 1.11.3
and one of
>> > the recommend steps is to upgrade the idoutils to the last
version. From
>> > what i understand from documentation regarding idoutils
upgrade, i had
>> > to make all incremetal steps from 1.10 -> 1.11 -> 1.11.3 ->
1.12.0.sql
>>
>> The 1.12.0.sql shouldn't exist. That one slipped into the
tarball from a
>> local git checkout, but does not exist in the support/1.11 git
branch.
>> I've uploaded a new tarball to github without those files not in
git.
>>
>>
>> >
>> > $ psql -U icinga -d icinga <
>> > module/idoutils/db/pgsql/upgrade/pgsql-upgrade-1.11.3.sql
>> > ALTER TABLE
>> > ALTER TABLE
>> > ALTER TABLE
>> > ALTER TABLE
>> > ALTER TABLE
>> > ALTER TABLE
>> > ERROR: syntax error at or near "("
>> > LINE 1: ...icinga_hoststatus ADD COLUMN is_reachable smallint(6)
>> > DEFAUL...
>> > ^
>> > ERROR: syntax error at or near "("
>> > LINE 1: ...nga_servicestatus ADD COLUMN is_reachable smallint(6)
>> > DEFAUL...
>> > ^
>> https://dev.icinga.org/issues/6193
>>
>>
>> > updatedbversion
>> > -----------------
>> >
>> > (1 row)
>> > $ psql -U icinga -d icinga <
>> > module/idoutils/db/pgsql/upgrade/pgsql-upgrade-1.12.0.sql
>> > ALTER TABLE
>> > updatedbversion
>> > -----------------
>> >
>> > (1 row)
>> >
>> > $ psql -U icinga -d icinga -c "SELECT * FROM icinga_dbversion;"
>> > dbversion_id | name | version | create_time
|
>> > modify_time
>> >
>>
--------------+----------+---------+-------------------------------+-------------------------------
>> > 1 | idoutils | 1.12.0 | 2013-11-15
12:50:27.416588+00 |
>> > 2014-05-13 18:01:46.812382+01
>> > (1 row)
>>
>> Do a rollback of that one.
>>
>>
>> --
>> DI (FH) Michael Friedrich
>>
>> michael.friedr...@gmail.com <mailto:michael.friedr...@gmail.com>
|| icinga open source monitoring
>> https://twitter.com/dnsmichi || lead core developer
>> dnsmi...@jabber.ccc.de <mailto:dnsmi...@jabber.ccc.de> ||
https://www.icinga.org/team
>> irc.freenode.net/icinga <http://irc.freenode.net/icinga> ||
dnsmichi
>>
>>
>>
>> ------------------------------
>>
>> Message: 6
>> Date: Wed, 21 May 2014 22:12:13 +0200
>> From: Michael Friedrich <michael.friedr...@gmail.com
<mailto:michael.friedr...@gmail.com>>
>> To: icinga-users@lists.icinga.org
<mailto:icinga-users@lists.icinga.org>
>> Subject: Re: [icinga-users] unable to pass http basic authentication
>> with icinga2go
>> Message-ID: <537d089d.8040...@gmail.com
<mailto:537d089d.8040...@gmail.com>>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>> On 16.05.2014 16:04, Christian Gruen wrote:
>> >
>> >
>> > Has anyone an idea what i am missing here? I would deeply
grateful if
>> > someone could post a working Apache config here. Or could give
hint
>> > that points me into he right direction.
>>
>> I'd say that's more of an application problem not sending basic
auth if
>> configured. The sencha methods used could do that, though it's
kind of a
>> hackery making these options available as configurable items.
>>
>> Looking at
>>
>>
https://git.icinga.org/?p=icinga-mobile.git;a=blob;f=lib/Model/IcingaApiStore.js;h=0bf6638af011c15da5f339fecaef718d089e13f3;hb=HEAD#l116
>> unveils that the headers are not modified when sending a request.
>>
>> Similar to sending a command here
>>
>>
https://git.icinga.org/?p=icinga-mobile.git;a=blob;f=lib/Model/IcingaCommandSender.js;h=0d2383e5fe116967138edcb0b611f132bf848712;hb=HEAD#l17
>> and the general file
>>
>>
https://git.icinga.org/?p=icinga-mobile.git;a=blob;f=deploy/IcingaMobile-debug.js;h=49e1af369e8797366be83e3f3e37b673c89751ce;hb=HEAD#l432
>>
>> By sending a base64 encoded authorization string of user/pass, this
>> could work (REST is similar to SOAP here).
>>
>>
http://stackoverflow.com/questions/3298891/using-authentication-with-ajax-request
>>
>> Tbh that's just a blind guess, and requires one patching it into,
>> testing it and creating an upstream compatible patch. If it even
works,
>> and the apache config thingy isn't solvable.
>>
>> Jannis should know more here being the original author.
>>
>> Regarding the apache foo - you must handle the exclusion
directly in the
>> /icinga-web location. Similar to
>>
>>
http://stackoverflow.com/questions/13950207/how-to-make-basic-auth-exclude-a-rewritten-url
>> (only a quick google, untested)
>>
>> kind regards,
>> Michael
>>
>>
>> --
>> DI (FH) Michael Friedrich
>>
>> michael.friedr...@gmail.com <mailto:michael.friedr...@gmail.com>
|| icinga open source monitoring
>> https://twitter.com/dnsmichi || lead core developer
>> dnsmi...@jabber.ccc.de <mailto:dnsmi...@jabber.ccc.de> ||
https://www.icinga.org/team
>> irc.freenode.net/icinga <http://irc.freenode.net/icinga> ||
dnsmichi
>>
>>
>>
>> ------------------------------
>>
>> Message: 7
>> Date: Wed, 21 May 2014 22:14:28 +0200
>> From: Michael Friedrich <michael.friedr...@gmail.com
<mailto:michael.friedr...@gmail.com>>
>> To: icinga-users@lists.icinga.org
<mailto:icinga-users@lists.icinga.org>
>> Subject: Re: [icinga-users] Icinga web: ajax calls
'statusOverall' and
>> 'monitorPerformance' fail
>> Message-ID: <537d0924.9010...@gmail.com
<mailto:537d0924.9010...@gmail.com>>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>> On 16.05.2014 11:20, FDGSDF SDGFDGF wrote:
>> > Hi,
>> >
>> > I've recently discovered Icinga and I've installed it on my
private
>> > server following the steps described here:
>> > http://docs.icinga.org/latest/en/quickstart-idoutils.html
>> > http://docs.icinga.org/latest/en/icinga-web-scratch.html
>> >
>> > I have an Ubuntu 12.04 server with apache running on ports
8080 and
>> > 4430 because I use Tomcat as default web server (80/443) for
my web. I
>> > use MySQL community server 5.6.16, not only for Icinga storage but
>> > also as DB for my web.
>> > I'm able to log into both icinga classic interface
>> > (myserverHostName:8080/icinga) and icinga-web
>> > (myserverHostName:8080/icinga-web).
>> >
>> > The problem happens when I log into Icinga-web: no information is
>> > shown no matter the section I browse. On the other hand, the web
>> > interface is shown correctly and seems to work fine. Upon checking
>> > ajax calls to icinga-web, I've found the following messages in
firebug:
>> >
>> > GET
>> >
>>
http://myserverHostName:8080/icinga-web/modules/cronks/monitorPerformance/json?_dc=1400229486354
>> > ------------------
>> > Response:
>> > A critical exception occured!
>> > Uncaught AppKitPHPError thrown:
>> > PHP Error Argument 1 passed to
AppKitExtJsonDocument::hasFieldBulk()
>> > must be of the type array, null given, called in
>> >
>>
/usr/local/icinga-web/app/modules/Cronks/models/Provider/SystemPerformanceModel.class.php
>> > on line 131 and defined
>> >
>>
(/usr/local/icinga-web/app/modules/AppKit/lib/json/AppKitExtJsonDocument.class.php:180)
>> > Stacktrace:
>> > #0
>> >
>>
/usr/local/icinga-web/app/modules/AppKit/lib/json/AppKitExtJsonDocument.class.php(180):
>> > AppKitExceptionHandler::exceptionOnError(4096, 'Argument 1
pass...',
>> > '/usr/local/icin...', 180, Array)
>> > #1
>> >
>>
/usr/local/icinga-web/app/modules/Cronks/models/Provider/SystemPerformanceModel.class.php(131):
>> > AppKitExtJsonDocument->hasFieldBulk(NULL)
>> > #2
>> >
>>
/usr/local/icinga-web/app/modules/Cronks/views/System/MonitorPerformanceSuccessView.class.php(37):
>> > Cronks_Provider_SystemPerformanceModel->getJson()
>> > #3
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1672):
>> >
>>
Cronks_System_MonitorPerformanceSuccessView->executeJson(Object(AgaviWebRequestDataHolder))
>> > #4
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1533):
>> > AgaviExecutionFilter->executeView(Object(AgaviExecutionContainer))
>> > #5
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1255):
>> > AgaviExecutionFilter->execute(Object(AgaviFilterChain),
>> > Object(AgaviExecutionContainer))
>> > #6
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1700):
>> > AgaviFilter->executeOnce(Object(AgaviFilterChain),
>> > Object(AgaviExecutionContainer))
>> > #7
>> >
>>
/usr/local/icinga-web/lib/agavi/src/filter/AgaviSecurityFilter.class.php(73):
>> > AgaviFilterChain->execute(Object(AgaviExecutionContainer))
>> > #8
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1255):
>> > AgaviSecurityFilter->execute(Object(AgaviFilterChain),
>> > Object(AgaviExecutionContainer))
>> > #9
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1700):
>> > AgaviFilter->executeOnce(Object(AgaviFilterChain),
>> > Object(AgaviExecutionContainer))
>> > #10
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(870):
>> > AgaviFilterChain->execute(Object(AgaviExecutionContainer))
>> > #11
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1266):
>> > AgaviExecutionContainer->execute()
>> > #12
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1255):
>> > AgaviDispatchFilter->execute(Object(AgaviFilterChain),
>> > Object(AgaviExecutionContainer))
>> > #13
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1700):
>> > AgaviFilter->executeOnce(Object(AgaviFilterChain),
>> > Object(AgaviExecutionContainer))
>> > #14
>> >
>>
/usr/local/icinga-web/lib/agavi/src/filter/AgaviFormPopulationFilter.class.php(78):
>> > AgaviFilterChain->execute(Object(AgaviExecutionContainer))
>> > #15
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1700):
>> > AgaviFormPopulationFilter->executeOnce(Object(AgaviFilterChain),
>> > Object(AgaviExecutionContainer))
>> > #16
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(579):
>> > AgaviFilterChain->execute(Object(AgaviExecutionContainer))
>> > #17 /usr/local/icinga-web/pub/index.php(49):
AgaviController->dispatch()
>> > #18 {main}
>> >
>> > GET
>> >
>>
http://myserverHostName:8080/icinga-web/modules/cronks/statusOverall/json?_dc=1400229486462
>> > ------------------
>> > Response:
>> > A critical exception occured!
>> > Uncaught AppKitPHPError thrown:
>> > PHP Error array_keys() expects parameter 1 to be array, null given
>> >
>>
(/usr/local/icinga-web/app/modules/Cronks/models/Provider/StatusSummaryModel.class.php:257)
>> > Stacktrace:
>> > #0 [internal function]:
AppKitExceptionHandler::exceptionOnError(2,
>> > 'array_keys() ex...', '/usr/local/icin...', 257, Array)
>> > #1
>> >
>>
/usr/local/icinga-web/app/modules/Cronks/models/Provider/StatusSummaryModel.class.php(257):
>> > array_keys(NULL)
>> > #2
>> >
>>
/usr/local/icinga-web/app/modules/Cronks/views/System/StatusOverallSuccessView.class.php(33):
>> > Cronks_Provider_StatusSummaryModel->getJson()
>> > #3
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1672):
>> >
>>
Cronks_System_StatusOverallSuccessView->executeJson(Object(AgaviWebRequestDataHolder))
>> > #4
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1533):
>> > AgaviExecutionFilter->executeView(Object(AgaviExecutionContainer))
>> > #5
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1255):
>> > AgaviExecutionFilter->execute(Object(AgaviFilterChain),
>> > Object(AgaviExecutionContainer))
>> > #6
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1700):
>> > AgaviFilter->executeOnce(Object(AgaviFilterChain),
>> > Object(AgaviExecutionContainer))
>> > #7
>> >
>>
/usr/local/icinga-web/lib/agavi/src/filter/AgaviSecurityFilter.class.php(73):
>> > AgaviFilterChain->execute(Object(AgaviExecutionContainer))
>> > #8
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1255):
>> > AgaviSecurityFilter->execute(Object(AgaviFilterChain),
>> > Object(AgaviExecutionContainer))
>> > #9
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1700):
>> > AgaviFilter->executeOnce(Object(AgaviFilterChain),
>> > Object(AgaviExecutionContainer))
>> > #10
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(870):
>> > AgaviFilterChain->execute(Object(AgaviExecutionContainer))
>> > #11
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1266):
>> > AgaviExecutionContainer->execute()
>> > #12
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1255):
>> > AgaviDispatchFilter->execute(Object(AgaviFilterChain),
>> > Object(AgaviExecutionContainer))
>> > #13
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1700):
>> > AgaviFilter->executeOnce(Object(AgaviFilterChain),
>> > Object(AgaviExecutionContainer))
>> > #14
>> >
>>
/usr/local/icinga-web/lib/agavi/src/filter/AgaviFormPopulationFilter.class.php(78):
>> > AgaviFilterChain->execute(Object(AgaviExecutionContainer))
>> > #15
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(1700):
>> > AgaviFormPopulationFilter->executeOnce(Object(AgaviFilterChain),
>> > Object(AgaviExecutionContainer))
>> > #16
>> >
>>
/usr/local/icinga-web/app/cache/config/compile.xml_production__119920113a175a2dcea22e33a36de83ba298e663.php(579):
>> > AgaviFilterChain->execute(Object(AgaviExecutionContainer))
>> > #17 /usr/local/icinga-web/pub/index.php(49):
AgaviController->dispatch()
>> > #18 {main}
>>
>> Sounds a bit like https://dev.icinga.org/issues/6126
>>
>> >
>> >
>> > When I run 'service ido2db start' i get the following response:
>> > Ido2db PID not running. Removing lockfile.
>> > Starting Ido2db: done.
>> >
>> > Wnen I run the command 'service ido2db status' after executing
the one
>> > above I get:
>> > Ido2db is not running but subsystem locked
>> >
>> > Maybe are these problems related to an ido2db's
>> > fault/misconfiguration? I just followed the instructions I
mentioned.
>>
>> There's something wrong with your idoutils installation. Verify
that by
>> following the wiki guide on testing idoutils/web.
>>
>>
>>
https://wiki.icinga.org/display/testing/Icinga+Web+Testing#IcingaWebTesting-NoData
>>
>> --
>> DI (FH) Michael Friedrich
>>
>> michael.friedr...@gmail.com <mailto:michael.friedr...@gmail.com>
|| icinga open source monitoring
>> https://twitter.com/dnsmichi || lead core developer
>> dnsmi...@jabber.ccc.de <mailto:dnsmi...@jabber.ccc.de> ||
https://www.icinga.org/team
>> irc.freenode.net/icinga <http://irc.freenode.net/icinga> ||
dnsmichi
>>
>>
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> _______________________________________________
>> icinga-users mailing list
>> icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org>
>> https://lists.icinga.org/mailman/listinfo/icinga-users
>>
>>
>> ------------------------------
>>
>> End of icinga-users Digest, Vol 5, Issue 13
>> *******************************************
>>
>
>
>
> --
> *Thanks*
> *Niranjan*
> *+1 781.956.6900 <tel:%2B1%20781.956.6900> <%2B1%20781.956.6900>*
>
> _______________________________________________
> icinga-users mailing list
> icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org>
> https://lists.icinga.org/mailman/listinfo/icinga-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.icinga.org/pipermail/icinga-users/attachments/20140523/be5a1145/attachment.html>
------------------------------
Subject: Digest Footer
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org>
https://lists.icinga.org/mailman/listinfo/icinga-users
------------------------------
End of icinga-users Digest, Vol 5, Issue 22
*******************************************
--
/*Thanks*/
/*Niranjan*/
/*+1 781.956.6900*/
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
