Posts by watermelon

Please read about the latest changes and upgrade.
Please note that your newly registered account needs to be manually activated by an admin. Just be patient, you cannot post to any forum before this happens. This is thanks to the unfortunate event of spammers recently. More details here.

    Hey Kevin.Honka ,


    Not sure if you wanted me to create another thread, but I thought I could just add on to this one. In your written guide (thank you for that by the way), there is a part where I am confused:


    Quote

    Some things are important in this Form, we have to set a Notification command, usually there are 2 commands delivered with the standard icinga2 installation. For this template I chose mail-host-notification.


    I have this command defined, but not in Director by default. I had to add in a new Command definition, but I don't think I did it correctly. Here's what it looks like in Director:


    Code
    1. zones.d/director-global/commands.conf
    2. object NotificationCommand "mail-notification-host" {
    3. import "plugin-notification-command"
    4. command = [ "/etc/icinga2/scripts/mail-host-notification.sh" ]
    5. timeout = 1m
    6. }


    I continue through the guide following each step, but in the end, the emails do not send out. If you need more information let me know, but I am almost certain that I have configured the command I pasted above incorrectly.


    Thanks!

    Hey all,


    I've just recently installed Dashing to work with Icinga2. I noticed in the default dashboards/icinga2.erb file that there is a section for iframe. I modified this code to fit my environment, it looks like this:


    HTML
    1. <!-- Icinga Web 2 iFrame -->
    2. <li data-row="4" data-col="1" data-sizex="2" data-sizey="2">
    3. <div data-id="iframe" data-view="Iframe" data-url="https://my.host.address/icingaweb2/monitoring/list/hosts?host_problem=1&sort=host_severity&showFullscreen&showCompact"></div>
    4. </li>
    5. <li data-row="4" data-col="3" data-sizex="2" data-sizey="2">
    6. <div data-id="iframe" data-view="Iframe" data-url="https://my.host.address/icingaweb2/monitoring/list/services?service_problem=1&sort=service_severity&dir=desc&showFullscreen&showCompact"></div>
    7. </li>
    8. </ul>


    However, this widget does not display on the web interface.


    - I inspected the page using development tools and can see that it should be displaying

    - Inspecting the page yields this: Refused to display '(data url from above)' in a frame because it set 'X-Frame-Options' to 'DENY'.

    - I validated that the url in the code works

    - I've loaded in a random url (http://www.cnn.com) to test whether or not the widget works and it was able to load that website

    - I tried to load the interface in Firefox, Chrome, Internet Explorer, and Safari


    Could this be due to https not being compatible with iframe? Or perhaps it is because I'm using a self-signed certificate for https? Or is it a compatibility issue with the web browser?


    Any ideas are welcome. Thanks!



    UPDATE (SOLUTION):


    The problem seemed to be in the X-Frame-Options variable being set in the apache configuration as DENY. This was located at /etc/httpd/conf.d/ssl.conf for my CentOS7 instance. I commented this line out and now the iframes display as wanted.

    Kevin.Honka


    Ah, it was a firewall rule! I allowed port 8005 on firewalld and it worked. Thanks!


    mcktr


    The default port seems to be port 8005, it always listens on that port when I restart dashing. Not sure where 3030 comes from.


    dnsmichi


    I started dashing using ./restart-dashing while in the /usr/share/dashing-icinga2/ directory, and started dashing in the foreground using dashing start



    Thread is now resolved. Thanks all!


    TLDR;

    Allow port 8005 on firewalld if using CentOS7 to access dashing at http://localhost:8005/

    I think you need to specify the command that you're using in the Director template


    You're saying that the check does not execute at all?

    Hi all,


    I'm trying to integrate the Dashing plugin into my Icinga2 instance.


    Here's what I have now:

    - CentOS7

    - I recently upgraded to Icinga v2.6.1 so that I could use this plugin

    - Dashing version: 1.3.7

    - Ruby version: ruby 2.0.0p645 (2015-12-16)

    - Version of the Dashing project: (the current version at 2017-2-10) ...don't know how to check this 

    - I have not made any modifications to the project, besides following the documentation (create API user, download github zip file & install to /usr/share/ using bundle install --system, start dashing)


    Problems:

    I cannot access the Dashing interface at http://localhost:8005. The error according to the browser development console is ERR_CONNECTION_REFUSED.


    I tried running Dashing in the foreground, but that does not seem to be useful. It seems to show the service checks that I've configured via Icinga2. I could put the output in this thread if needed.


    Any ideas? I'm a bit stuck. Thanks!

    Hi all,


    This is more of any information post for anyone wondering about the updating process of Icinga2 and seeing whether some other people run into the same issues.


    I was having some trouble upgrading Icinga2 v2.3.4 to v2.6.x.


    I had some problems with upgrading the IDO-mysql database. Without this upgrade, I couldn't start Icinga2 and the log showed this:


    Code
    1. [2017-02-09 11:34:01 -1000] information/DbConnection: Resuming IDO connection: ido-mysql
    2. [2017-02-09 11:34:01 -1000] critical/IdoMysqlConnection: Schema version '1.13.0' does not match the required version '1.14.2' (or newer)! Please check the upgrade documentation.
    3. Context:
    4. (0) Reconnecting to MySQL IDO database 'ido-mysql'


    I followed this guide. As discussed in the guide, I have the following upgrade files in the /schema/upgrade/ folder:


    2.0.2.sql

    2.1.0.sql

    2.2.0.sql

    2.3.0.sql

    2.4.0.sql

    2.5.0.sql

    2.6.0.sql (this one appeared after running 'yum update')


    When I try to run this command: mysql -u root -p icinga2 < /usr/share/icinga2-ido-mysql/schema/upgrade/2.0.2.sql, I enter my password but get no output.


    I try using the other upgrade files and get mixed results:


    - using 2.1.0.sql, I receive this error: ERROR 1060 (42S21) at line 10: Duplicate column name 'endpoint_name'

    - using 2.2.0.sql, I receive this error: ERROR 1060 (42S21) at line 10: Duplicate column name 'program_version'

    - using 2.3.0 sql, I receive no output.

    - using 2.4.0 sql, I receive this error: ERROR 1060 (42S21) at line 10: Duplicate column name 'zone_object_id'

    - using 2.5.0 sql, I receive this error: ERROR 1060 (42S21) at line 10: Duplicate column name 'idx_comments_object_id'

    - using 2.6.0 sql, I receive a long pause, then no output.


    So, I tried to upgrade the mysql database incrementally, but it didn't seem to work. After running the command using the 2.6.0 sql file, I attempted to restart Icinga2 and it worked.


    My question is why did this work? It showed (in the log above) that my schema version was 1.13.0, and I seemingly jumped to 2.6.0.


    Since this worked, I also am wondering why you would have to run the upgrades incrementally as well.

    Since the check is an .exe, which only runs on Windows, that means the plugin would have to exist on the endpoint anyway which you could then execute remotely. Why not just install the Icinga agent on the Windows endpoint anyway to install a full suite of useful plugins?

    It should also be noted that the configurations are stored by default in C:/ProgramData/icinga2/etc/icinga2/conf.d/ on the monitored system and that after you save the configurations, you must go into your Icinga2 backend and run icinga2 node update-config and service icinga2 reload for the configurations to deploy.

    I'm unsure of what it is defined as in the backend (whether it's a script, php file, etc), but I do know on Icingaweb2 that it is a button with text that you can click to send you to the url specified, "monitoring/list/hosts". This button is located here:




    However, I do not understand your goal here. What exactly are you trying to further understand?

    Did you ever run this command on your backend?


    icinga2 node update-config


    This creates host, service, endpoint, etc. definitions for the agents that you have deployed on your network (and throws the definitions into /etc/icinga2/repository.d). Let me know the output of this command once you run it.

    Interesting!


    After I got off work yesterday and came back today (Icinga wasn't touched until I got in today), the overview now displays and there was a button at the top middle of the screen to deploy 5 pending schema migrations. That button was not there yesterday in the overview or the activity log (as shown by my screenshot).


    All that I did this morning was to acknowledge a few alerts through the web interface and change a host config file in the backend, then reload the icinga2 service to deploy those changes. I assume that the reload "fixed" this, but I did reload the icinga2 service yesterday too when I was having problems not being able to see the overview.


    It seems to be fully functional as of now though, so I guess that's what matters!

    Hey all,


    Just upgraded to version 1.3 of Director, but it seems when I try to access the overview tab (by clicking "Icinga Director"), I get a blank screen. Here's what it looks like:




    All my configurations (services, hosts, etc.) are good though. I am able to see all other tabs except for the overview tab. Also, I noticed that on the left-hand menu, the Activity log says it has 5 pending configurations to be deployed but when I click to it, there are no pending configurations.


    Things I've done already:

    1. Reload Icinga2 service via backend

    2. Reload web browser


    What else can be done?


    Thanks!