Dave Close

Is there any known ability to make bulk changes to the NagiosQL data base? I have more than 1000 hosts defined and want to change the host group for many of them. Using the GUI works but wears me out.

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.

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...

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.

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...

Is there any way to change the name of a host without losing all the Nagios history for that host?

Thanks for that explanation. My difficulty is that I didn't create these entries, at least not deliberately. They appeared after NagiosQL crashed while I was working on a normal entry. Most of them match legitimate hosts but one has a name which does not appear in the normal list. That one gets written to the services file but nowhere else leading to a complaint when Nagios checks the files. BTW, when I said I could not delete the (common) entries, that is because there are no buttons to the right...

Thanks for that explanation. My difficulty is that I didn't create these entries, at least not deliberately. They appeared after NagiosQL crashed while I was working on a normal entry. Most of them match legitimate hosts but one has a name which does not appear in the normal list. That one gets written to the services file but nowhere else leading to a complaint when Nagios checks the files. BTW, when I said I could not delete the (common) entries, that is because there are no buttons to the right...