Config Change Report says "No Configs to Compare"

I recently moved Cirrus from one server to another, while simultaneously upgrading to version 4. I created new scheduled jobs identical to my old ones and had the problem I'm about to describe. I then copied the old job files to the new server, deactivated the newly created ones and activated the copied ones. This yielded the same results. Here's what happens.

I have a nightly job that downloads running and startup configs from all devices and keeps a copy if there has been a change. This job takes a few minutes to run

Roughly 9 hours later, I have another job that runs a Config Change Report and emails it to me. The problem is that most of the lines say either "No Configs" or "No configs to Compare".

I have checked the job logs for both jobs and both appear to be working normally, except that the Config Change Report only takes about 6 seconds to run - presumably because it doesn't see any configs to compare.

Find more posts tagged with

config

ncm

Accepted answers

All comments

Clickster

Forgot a piece of useful information. My Config change report is supposed to report on any changes made in the last 2 days - though again, how it compares doesn't matter if it doesn't have anything to compare.

bleearg13

This is quite possibly a problem with the aggravating permissions settings on Scheduled Tasks in your Windows Control Panel. The permissions settings are way too numerous and annoyingly (did I mention aggravating?) system/install-specific to list out here. I would start by going to your Scheduled Tasks control panel item and select Advanced/View log. See if the command completed without errors. If it did, there could still be a frustrating (did I mention aggravating and annoying yet?) permissions issue to deal with. Does the task run from within Cirrus and complete? If so, you can try resetting the username/password that your scheduled job runs as within Cirrus. Failing that, you can go directly to the Scheduled Tasks panel, right-click, and set permissions that way. You may also need to set permissions on cmd.exe as well, if you are running the scheduled jobs as a different user than Administrator (which is a necessity if you don't want to reset the password for all your jobs whenever the admin password changes).

That said, none of this may be helpful, as Windows Scheduled Tasks is such a poorly documented and terrible task scheduling service, that every server I've tried to configure it on acts differently with regard to what is necessary to get tasks working via a non-Administrator account.

Clickster

UPDATED:

I've had a ticket open with Solarwinds for a while on this, but was told that this is a known issue they are working on. Cirrus has been effectively useless to me since I upgraded to 4.0. Frankly it's a little frustrating to have it down with no end in sight.

chris.lapoint

v4.0.1 is now available, which fixes an issue where the 'Changes over the Last XX Days' config change report would report inaccurate data.

Please see release notes for more data:

http://www.solarwinds.com/support/cirrus/docs/ReleaseNotes/releaseNotes.htm