I've just noticed that most of the images that should be visible within posts appear as broken links! All the images are on the server, there seems to be something wrong within WordPress, or mySQL.
At first I thought no problem, that's an easy fix… No its not! as this will require me to edit every post and relink the files. Now having just on two and s half years of blog posts, that would be rather time consuming!
So for the moment, broken image links it is until I either find a semi/fully automated way of fixing the problem it's going to remain. 😐
Well as the last week & a half have been pretty hectic, I've not had much time to even look at my blog, little lone write something worth while. There has been lots happening with Clare, but I'm not going to discuss/talk about that in this post, only to day what I just said!
On my Android front, there has been two updates released for the custom ROM that I'm currently using (T-Mod) these have really only been minor fixes (ROM based off LeeDrOid) some of the fixes were for applications I've not even used!
On the 6th of October, Icinga unified release 1.2 was let loose at the OSMC in Nürnberg, so far the response has been very positive for both companies & users of Icinga! So a big thanks goes out to the Icinga Team for their hard work & dedication towards the open source community. Oh yes, the surprise release of a mobile Web UI at the OSMC was a show stopper! Loss of "ohh & ahh" I've yet to set it up on my Icinga service, but when I get the time I certainly will be.
On the amateur radio front there isn't much to mention either! But version 0.67 of the Alpha Code was released from Byon, this addressed some issues that crept into release 0.66 Again I've yet to update my two TinyTrak4 units to the latest firmware.
Now as I've not really had that much to say, here's an image of Maisie …
Well today marks a special day in the development of the Icinga project, its first birthday! Now for me this all started out as a twitter post I happen to see and then investigated further. For me, I wasn't familiar with the structure of the Nagios project nor was I even aware/interested in any political issues that had been brewing, so from that stand point the Icinga project was ideal for me as it was a new direction on a well known monitoring solution. Again I must stress that until I heard of the Icinga fork I was aware of Nagois, but never really had a use for it with my small home set up… This changed when I first downloaded the initial release of Icinga and well the rest is history (as they say!)
I became an official team member in October 2009 (during the OSMC in Nürnberg) to assist with marketing and publicity although in that latter few months I've been focussed on testing and QA.
So a very special thanks goes out to all members of the Icinga team for their dedication to ensure that this fork wasn't going to just be a one week wonder! and with translations for the new Web-UI being worked on by many, this ensures that Icinga will continue to grow and develop into another option for system administrators to consider… 😀
I've been part of the Icinga team now since October 2009. The Icinga project is a fork from the well known network monitoring suite Nagios. Now I have to admit that I'm not up with all the politics of the reason for the fork and why there is so much dislike for the Icinga project (mainly by Nagios developers that are loyal to Ethan?) but the name Nagios & Nagios Enterprises are causing a divide within the Nagios community too.
So what's in a name?
Nagios Enterprises is a new "commercial" venture from the Nagios project. So for developers that had contributed many hours of time to assist with coding their work is now being sold without any renumeration. This has clearly got many off side within the Nagios community.
So regardless, the fork that has become Icinga, should be allowed to grow and develop further. This is what drives FOSS, the ability to adapt/alter code to suite. You only have to do a search and you will find many discussions around this (both positive and negative)
Where's the problem in that?
A commercial interest will never work within a FOSS community, it's a conflict that will only result in failure…
I've been part of the Icinga team now since October 2009. The Icinga project is a fork from the well known network monitoring suite Nagios. Now I have to admit that I'm not up with all the politics of the reason for the fork and why there is so much dislike for the Icinga project (mainly by Nagios developers that are loyal to Ethan?) but the name Nagios & Nagios Enterprises are causing a divide within the Nagios community too.
So what's in a name?
Nagios Enterprises is a new "commercial" venture from the Nagios project. So for developers that had contributed many hours of time to assist with coding their work is now being sold without any renumeration. This has clearly got many off side within the Nagios community.
So regardless, the fork that has become Icinga, should be allowed to grow and develop further. This is what drives FOSS, the ability to adapt/alter code to suite. You only have to do a search and you will find many discussions around this (both positive and negative)
Where's the problem in that?
A commercial interest will never work within a FOSS community, it's a conflict that will only result in failure…
December 16 2009: Today the Icinga Team releases the Icinga Core 1.0. This is a milestone for both the team and the project as a whole. After many months of hard work we are proud to bring you a stable, alternative monitoring solution. This release includes many changes as suggested by the community and in particular the inclusion of Oracle in IDOUtils.
With just as many new improvements, Icinga Web UI has hit release 0.9.1 alpha. We have added a makefile for easier installation and fixed installation permission and cache problems. More changes are still to come, including an ExtJS update to 3.0.3. See below for the full list of new developments across Icinga Core, API, Docs and Web.
As we are always eager to keep the momentum going, we have decided to release the stable Icinga Core alongside the Icinga Web 0.9.1 alpha. These two will converge again in the coming months to a uniform release status. Till then, we hope you like the latest improvements.
Core:
Improved IDOUtils with Oracle
Added prepared statements for most called queries
Split code into ocilib OR libdbi, to allow oracle to decide which rdbm lib will be used during configuration
idoutils: fixed duplicate rows in table system commands, timed events, timed event queue (missing unique keys)
idoutils: added upgrade path/sql queries for unique key failure – check docs for more information
idoutils: changed default data_processing_options in idomod.cfg
idoutils: fixed this version and perl path generation in db install scripts
idoutils: fixed save custom variables segfault
Docs:
Updates and fixes for quickstart guides
New section on upgrading Icinga & IDOUtils
Revised section for Icinga Web
API:
Restructured DB access for upcoming RDBM support
Made several fixes for table prefix, exception handling
Started a ‘how-to’ guide for upcoming documentation
Web:
Added makefile for easier installation
Fixed installation permission and cache problems
Modified .htaccess
Removed yui
Removed php notice warnings (isset, undef vars)
In the process of changing API result keys to uppercase
In the process of updating ExtJS to 3.0.3
Introducing commands through the web
Should you find any issues, please report them to the following links:
Report Issue API
Report issue Core
Report Issue Docs
Report Issue Web
As always we look forward to your feedback, so feel free to drop us a comment.
rewrite prepared statement queries to use SELECT unixts2date(unixtimestamp) FROM DUAL
allow rebinding of params in prepared statement for multi execution
prepared statement at db init
bind params the correct way
execute binded statement query instead of plain MERGE statement
code is now the same as NDOUtils Oracle, but with
– better code base (actual NDOUtils code)
– long_output
– SSL support
– better library: ocilib instead of own driver
– more prepared statements/bind param queries
split code into ocilib OR libdbi
–enable-oracle during configure decides which rdbm lib will be used
So as you can see there has been a lot of refinement in the Core. This of course goes with much thanks to Icinga team!
So if you can't wait until the official release of these two additions to the Icinga project, then you can always get a copy of the current Git repository and experiment a little!
rewrite prepared statement queries to use SELECT unixts2date(unixtimestamp) FROM DUAL
allow rebinding of params in prepared statement for multi execution
prepared statement at db init
bind params the correct way
execute binded statement query instead of plain MERGE statement
code is now the same as NDOUtils Oracle, but with
– better code base (actual NDOUtils code)
– long_output
– SSL support
– better library: ocilib instead of own driver
– more prepared statements/bind param queries
split code into ocilib OR libdbi
–enable-oracle during configure decides which rdbm lib will be used
So as you can see there has been a lot of refinement in the Core. This of course goes with much thanks to Icinga team!
So if you can't wait until the official release of these two additions to the Icinga project, then you can always get a copy of the current Git repository and experiment a little!
I've been working on my Icinga Monitoring service, to date I now have it successfully monitoring 7 hosts and 50 services!
So what am I monitoring ??? OK well, I only have a small home network, however I want to know just what is down at any stage! as I run my own Email/Web server its obvious that I want to know if there is a problem with this. I'm also monitoring the services required by the web-server , as in MySQL to ensure that the database is in good health, My sever also has a small UPS that uses NUT, So again just ensuring that all is OK there. I'm also ensuring the services that I make use of from my ISP (POP3, SMTP, HTTP & PING… are they there!) are accessible too, along with two other PC's (My Desktop & Amateur Radio I-Gate)
If you are interested in how I have achieved this, then here is a link to the relevant files… Icinga-files Please feel free to add any suggestions or advice on these configuration files, as I'm still learning the basics about how they all do the magic that they do! 😉
