Nagios Support Forum

ssax wrote: Are you able to see the changes after saving in the CCM?

Yes, changes made within CCM are still visible within CCM after they are "Saved".

Actually yea, cron jobs are used in various places in XI. Let's see what the log timestamps look like:

ls -lhtr /usr/local/nagiosxi/var/

root@c4 var]# ls -lhtr /usr/local/nagiosxi/var/
total 260K
drwxr-xr-x 2 nagios nagios 6 Oct 28 12:24 upgrades
drwsrwsr-x. 2 apache nagios 47 Oct 28 12:28 components
-rw-r--r-- 1 nagios nagios 1.1K Dec 2 03:16 load_url.log-20151202
-rw-r--r-- 1 nagios nagios 1.1K Dec 6 03:27 load_url.log-20151206
-rw-r--r-- 1 nagios nagios 273 Dec 14 03:01 recurringdowntime.log-20151214
-rw-r--r-- 1 nagios nagios 11K Dec 14 03:40 dbmaint.log-20151214
-rw-r--r-- 1 nagios nagios 75 Dec 14 03:40 deadpool.log-20151214
-rw-r--r-- 1 nagios nagios 1.1K Dec 14 03:43 load_url.log-20151214
-rw-r--r-- 1 nagios nagios 303 Dec 14 03:43 cleaner.log-20151214
-rw-r--r-- 1 nagios nagios 81 Dec 14 03:44 perfdataproc.log-20151214
-rw-r--r-- 1 nagios nagios 82 Dec 14 03:44 cmdsubsys.log-20151214
-rw-r--r-- 1 nagios nagios 40 Dec 14 03:44 eventman.log-20151214
-rw-r--r-- 1 nagios nagios 25 Dec 14 03:44 feedproc.log-20151214
-rw-r--r-- 1 nagios nagios 7.4K Dec 14 03:44 sysstat.log-20151214
-rw-r--r-- 1 nagios nagios 1002 Dec 15 14:14 load_url.log-20151220
-rw-r--r--. 1 nagios nagios 195 Dec 18 16:50 xiversion
-rw-r--r--. 1 nagios nagios 6.5K Dec 18 16:50 xi-sys.cfg
-rw-r--r-- 1 nagios nagios 273 Dec 20 03:01 recurringdowntime.log-20151220
-rw-r--r-- 1 nagios nagios 2.7K Dec 20 03:35 dbmaint.log-20151220
-rw-r--r-- 1 nagios nagios 75 Dec 20 03:35 deadpool.log-20151220
-rw-r--r-- 1 nagios nagios 303 Dec 20 03:37 cleaner.log-20151220
-rw-r--r-- 1 nagios nagios 0 Dec 20 03:37 load_url.log
-rw-r--r-- 1 nagios nagios 81 Dec 20 03:38 cmdsubsys.log-20151220
-rw-r--r-- 1 nagios nagios 81 Dec 20 03:38 perfdataproc.log-20151220
-rw-r--r-- 1 nagios nagios 40 Dec 20 03:38 eventman.log-20151220
-rw-r--r-- 1 nagios nagios 25 Dec 20 03:38 feedproc.log-20151220
-rw-r--r-- 1 nagios nagios 8.0K Dec 20 03:38 sysstat.log-20151220
-rwxrwxr-x 1 nagios nagios 513 Dec 22 13:04 corelog.newobjects
-rw-r--r--. 1 nagios nagios 1.2K Dec 25 03:29 nom.log-20151225
-rw-r--r-- 1 nagios nagios 1.2K Dec 27 03:24 nom.log-20151227
-rw-r--r-- 1 nagios nagios 273 Dec 28 03:01 recurringdowntime.log-20151228
-rw-r--r-- 1 nagios nagios 2.7K Dec 28 03:10 dbmaint.log-20151228
-rw-r--r-- 1 nagios nagios 75 Dec 28 03:10 deadpool.log-20151228
-rw-r--r-- 1 nagios nagios 303 Dec 28 03:14 cleaner.log-20151228
-rw-r--r-- 1 nagios nagios 81 Dec 28 03:15 perfdataproc.log-20151228
-rw-r--r-- 1 nagios nagios 40 Dec 28 03:15 eventman.log-20151228
-rw-r--r-- 1 nagios nagios 82 Dec 28 03:15 cmdsubsys.log-20151228
-rw-r--r-- 1 nagios nagios 25 Dec 28 03:15 feedproc.log-20151228
-rw-r--r-- 1 nagios nagios 8.0K Dec 28 03:15 sysstat.log-20151228
-rw-r--r-- 1 nagios nagios 273 Jan 3 03:01 recurringdowntime.log-20160103
-rw-r--r-- 1 nagios nagios 2.7K Jan 3 03:05 dbmaint.log-20160103
-rw-r--r-- 1 nagios nagios 75 Jan 3 03:05 deadpool.log-20160103
-rw-r--r-- 1 nagios nagios 303 Jan 3 03:07 cleaner.log-20160103
-rw-r--r-- 1 nagios nagios 82 Jan 3 03:08 cmdsubsys.log-20160103
-rw-r--r-- 1 nagios nagios 81 Jan 3 03:08 perfdataproc.log-20160103
-rw-r--r-- 1 nagios nagios 40 Jan 3 03:08 eventman.log-20160103
-rw-r--r-- 1 nagios nagios 25 Jan 3 03:08 feedproc.log-20160103
-rw-r--r-- 1 nagios nagios 8.0K Jan 3 03:08 sysstat.log-20160103
-rw-r--r-- 1 nagios nagios 1.2K Jan 4 03:28 nom.log-20160104
-rw-r--r-- 1 nagios nagios 273 Jan 7 15:01 recurringdowntime.log
-rw-r--r-- 1 nagios nagios 2.7K Jan 7 15:30 dbmaint.log
-rw-r--r-- 1 nagios nagios 75 Jan 7 15:30 deadpool.log
drwxr-xr-x. 2 nagios nagios 47 Jan 7 15:33 subsys
-rw-r--r-- 1 nagios nagios 0 Jan 7 15:34 nom.log
-rw-r--r--. 1 nagios nagios 0 Jan 7 15:34 reportengine.log
-rw-r--r-- 1 nagios nagios 81 Jan 7 15:34 perfdataproc.log
-rw-r--r--. 1 nagios nagios 0 Jan 7 15:34 corelog.diff
-rw-r--r--. 1 nagios nagios 7 Jan 7 15:34 corelog.data
-rw-r--r-- 1 nagios nagios 1.2K Jan 7 15:34 cleaner.log
-rw-r--r-- 1 nagios nagios 25 Jan 7 15:34 feedproc.log
-rw-r--r-- 1 nagios nagios 8.0K Jan 7 15:34 sysstat.log
-rw-r--r-- 1 nagios nagios 40 Jan 7 15:34 eventman.log
-rw-r--r-- 1 nagios nagios 5.4K Jan 7 15:34 cmdsubsys.log

In the Nagios XI GUI, can you go to Admin > System Profile and click on the Show Profile Button, copy the data and post the sanitized output here?

tgriep wrote:In the Nagios XI GUI, can you go to Admin > System Profile and click on the Show Profile Button, copy the data and post the sanitized output here?

Please find attached.

Now that we've paid for licensing it's a bigger priority for us to get past this so we can start using the system. Do you think it would be prudent to reset the database and start that from scratch? If so, what would be the best way to go about that? I'd prefer not have to redeploy the entire VM. Thanks.

Is this the same server you are talking about in the customer forum? I don't want to split the information between two threads.

hsmith wrote:Is this the same server you are talking about in the customer forum? I don't want to split the information between two threads.

Yes, this is the same system.

Is submitting a ticket about this an option for you?

I believe these two issues you are having could be related.

Thanks for the profile. It looks like your system time doesn't match the PHP time and that could be causing the issue.
Open this link the describes how to setup the XI servers time.
https://assets.nagios.com/downloads/nag ... m_Time.pdf