I have installed 3.4 and much of it appears to be working. However, two problems:
1. The support page reports that the Nagios process, command, and binary files are missing. But without some indication of what file names are expected, I don't know what to fix. I didn't have this issue with 3.3.
2. The import function does not import anything. I suppose this could be a result of #1. Initially, it crashed due to exceeding PHP's memory limit but that has been fixed. It doesn't crash but it also doesn't import anything.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Go to 'Tools' -> 'Config targets, select your configuration domain and press the edit button. There all red fields should be filled in. With the help funktion behind each text field you find out what file is meant.
Normally the memory limit should not be touched when using the import function. You should not select all file of your configuration, import file per file using the recommended way:
Re #1, it was the blue fields that were incorrect. All the red ones were ok.
Re #2, I do not reach the point of specifying what to import. After a 20s pause, the screen returns to where it was. This is still true after correcting the files in #1. Administration/Support shows no errors.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
How many millions of files do you have in your nagiosql and nagios base path? :)
Actually, it is not possible for me to reproduce a wait time bigger than 0.5s when opening the Import page.
I need much more detailed informations about your configuration:
1. Complete directory structure of NagiosQL Base path (/etc/nagiosql or similar)
2. Complete directory structure of Nagios Base path (/etc/nagios or similar)
3. Complete directory structure of Import directory
4. How many files are in each of this directories (ls -Rtl /etc/nagiosql | wc -l)
5. Are there any links (soft / hard links) inside this directories to directories outside or inside (loops)?
6. Is this a localhost, an ssh or an ftp domain
7. Screenshot of your domain configuration
Possibly more after that.
Last edit: Martin 2018-05-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Some ideas:
1. Can you use the pages "Delete Backup files" and "Delete config files" or did you have the same issue there? (They use the same function like import)
2. Are there some messages in apache log after opening the import page? Can you post them?
3. Move away all backup files (not the directories) from /etc/nagiosql and try again.
4. Change Import directory to /etc/nagiosql/objects
Last edit: Martin 2018-05-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have installed 3.4 and much of it appears to be working. However, two problems:
1. The support page reports that the Nagios process, command, and binary files are missing. But without some indication of what file names are expected, I don't know what to fix. I didn't have this issue with 3.3.
2. The import function does not import anything. I suppose this could be a result of #1. Initially, it crashed due to exceeding PHP's memory limit but that has been fixed. It doesn't crash but it also doesn't import anything.
commands -> timeperiods -> contacttemplates -> contacts -> contactgroups -> hosttemplates -> hosts -> hostgroups -> servicetemplates -> services -> servicegroups
After an upgrade it is normally not nesecary to import the configurtion - the update does not touch the configuration items inside the database.
The import functionality was deeply tested wit 3.4.0 and there was no issue.
Last edit: Martin 2018-05-03
Thanks for the quick response.
Re #1, it was the blue fields that were incorrect. All the red ones were ok.
Re #2, I do not reach the point of specifying what to import. After a 20s pause, the screen returns to where it was. This is still true after correcting the files in #1. Administration/Support shows no errors.
How many millions of files do you have in your nagiosql and nagios base path? :)
Actually, it is not possible for me to reproduce a wait time bigger than 0.5s when opening the Import page.
I need much more detailed informations about your configuration:
1. Complete directory structure of NagiosQL Base path (/etc/nagiosql or similar)
2. Complete directory structure of Nagios Base path (/etc/nagios or similar)
3. Complete directory structure of Import directory
4. How many files are in each of this directories (ls -Rtl /etc/nagiosql | wc -l)
5. Are there any links (soft / hard links) inside this directories to directories outside or inside (loops)?
6. Is this a localhost, an ssh or an ftp domain
7. Screenshot of your domain configuration
Possibly more after that.
Last edit: Martin 2018-05-03
Directory structure:
/etc/nagios
├── backup -> ../nagiosql/backup
├── conf.d -> ../nagiosql/conf.d
├── hosts -> ../nagiosql/hosts
├── objects -> ../nagiosql/objects
├── old-backup
│ ├── hosts
│ └── services
├── old-conf.d
├── old-hosts
├── old-objects
├── old-private
├── old-services
├── private -> ../nagiosql/private
└── services -> ../nagiosql/services
/etc/nagiosql
├── backup
│ ├── hosts
│ └── services
├── conf.d
├── hosts
├── objects
├── private
└── services
I don't find any directory called Import or import.
[~]# ls -Rtl /etc/nagios | wc -l
1307
[~]# ls -Rtl /etc/nagiosql | wc -l
8635
The domain is localhost. Screenshots attached.
Some ideas:
1. Can you use the pages "Delete Backup files" and "Delete config files" or did you have the same issue there? (They use the same function like import)
2. Are there some messages in apache log after opening the import page? Can you post them?
3. Move away all backup files (not the directories) from /etc/nagiosql and try again.
4. Change Import directory to /etc/nagiosql/objects
Last edit: Martin 2018-05-04
The delete functions worked. After I tried them, I tried import again, and it also worked! I swear I didn't change anything in the interim.
The only messages in the Apache log were the memory messages I saw initially. They no longer appear.
Please consider this issue resolved. Thanks for holding my hands.