We assume following configuration:
- FAN installation containing Nagios and Centreon installed on CentOS 5.9
- IP of Nagios: 10.50.100.101
- You are owner of a working machine with linux or macos (windows users will need to use putty for some of the steps or install an ftp server on the centreon machine)
First step, prepare your image
Create an image of 40 by 40 pixels and in PNG format. In order to blend in the image with Nagios, make sure that the parts around the image are transparent. (Alpha layer PGN).
Second step, upload your image
Normally speaking, your server should only support following protocols. HTTPS (or HTTP for local deployments) and SSH. If you have FTP running on your server, things are different, but here we assume we only have HTTP/SSH. We also assume the root account is accessible from the outside. If not (e.g. debian default install) one will have to copy to the user having remote access over SSH.
scp image.png firstname.lastname@example.org:/root
scp image.png email@example.com:/home/user1
Third step, copy the image to the right folder on the server
Please note the second operation is a move operation. Make sure to execute the steps in the correct order.
cp /root/*.png /usr/share/centreon/www/img/media/logos/
mv /root/*.png /usr/share/nagios/images/logos/
Normally, a chown apache:apache to the files would be required in order to make the files readable for Nagios, but this seems to be working without. Just for the sake of correctness, please find following commands.
chown apache:apache /usr/share/centreon/www/img/media/logos/
chown apache:apache /usr/share/nagios/images/logos/
Forth step, refresh the server
Log-in to centreon, go to administration, options, media and select synchronise media. Now you should be able to use the image on any network device.
Installing fresh Observium (18.9.9420) (community version) on Debian 9 does not end up with a working installation. (See Observium documentation)
Only one device is added, that cannot be viewed afterwards.
Possible solution: modify the database structure after installation and before adding your devices.
Start checking if the devices_id field has an auto-increment value set and is the primary key.
One can do so by issuing following commands:
mysql>show columns from devices from observium;
mysql>show create table devices;
If the auto-increment value is missing, please add it:
mysql> use observium;
mysql> alter table devices change column device_id device_id int(11) not null auto_increment;
Easy fix, but takes some time to find out.
Some background information from the logs:
##### Software versions #####
o OS Linux 4.9.0-8-amd64 [amd64] (Debian 9.6)
o Apache 2.4.25
o PHP 7.0.33-0+deb9u1 (OPcache: DISABLED)
o Python 2.7.13
o MySQL 10.1.37-MariaDB-0+deb9u1 (extension: mysqli 5.0.12-dev)
o SNMP NET-SNMP 5.7.3
o RRDtool 1.6.0
o Fping 3.15 (IPv4 and IPv6)
##### Memory Limit #####
o PHP Unlimited
##### MySQL mode #####
o MySQL NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
##### Charset info #####
o PHP UTF-8
o MySQL utf8
##### Timezones info #####
o Date Wednesday, 15-May-19 13:35:30 CAT
o PHP +02:00
o MySQL +02:00
After making the change, please check the auto_increment value is there.
show columns from devices from observium;
Again, the internet saved my VM.
If you move around a CentOS 6.x VM, your network MAC address can change. Here is how to fix it again.
Source: How to solve “Device eth0 does not seem to be present, delaying initialization” error – OSTechNix
Seems netbeans cannot work with OpenJDK 10/11 and stops silently shortly after start.
uninstall 8.1 from software list and/or remove manual installation from /usr/local
Install OpenJDK 1.8
Download latest 8.2 from netbeans.org.
Install Netbeans 8.2 in current user (aka path /home/youruser). Also install Glassfish/Tomcat in current user. For some reason, installation in /usr/local does fail.
During installation, point your java jdk to /usr/lib/jvm/openjdk-1.8.
Please note that editing the /etc/netbeans.conf file as indicated by some sites is not resolving the issue.
After updating from Linux Mint 18.3 to 19, wine stopped working. This is what was required to correct.
sudo all below commands if required
dpkg --add-architecture i386
apt-add-repository 'deb https://dl.winehq.org/wine-builds/ubuntu/ bionic main'
wget -nc https://dl.winehq.org/wine-builds/Release.key
apt-key add Release.key
Check if you do not have duplicate lines from an earlier install.
Then the final step.
apt-get install --install-recommends winehq-stable
Source: Ubuntu – WineHQ Wiki
If Linux Mint 19 (Tara) shows error during update fril 18.3.
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
To fix run following with sudo user:
grep -R all/all *
in kde xml, remove the sections containing:
sudo vi packages/kde.xml
the other files showing these sections can remain untouched.
Then run following, no errors should occur
sudo update-mime-database /usr/share/mime
Source: Unknown media type in type Fix
Why UNIX. Because the way it is designed in Windows is all but design.
File extension madness, Windows Vista / 7 style – virtualdub.org.
Want to get started with a real OS. Here is some guide: http://matt.might.net/articles/basic-unix/
A good guide for windows and powershell users.