Maintenance doesn't seem to run

[cmerchant]

After the upgrade to 1.3 of NLS, are you still getting errors when you issue the following:

Code: Select all

curator

In version 1.3 of NLS, there is an added panel to display scheduled jobs - under Administration --> System --> Command Subsystem.

I found the job ID not meaningful, but you can edit the Job to get the description of the System Job. I found this panel helpful to find when the next time a maintenance job will run. You can change the frequency, and the scheduled time for the next run (change it to time before current time to run immediate).

[ljorg]

After the upgrade to 1.3 of NLS, are you still getting errors when you issue the following:

Code: Select all

curator

Yes, it's still there:

Code: Select all

Traceback (most recent call last):
  File "/usr/bin/curator", line 5, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python2.6/site-packages/pkg_resources.py", line 2655, in <module>
    working_set.require(__requires__)
  File "/usr/lib/python2.6/site-packages/pkg_resources.py", line 648, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python2.6/site-packages/pkg_resources.py", line 546, in resolve
    raise DistributionNotFound(req)
pkg_resources.DistributionNotFound: elasticsearch>=1.0.0,<2.0.0

However, my maintenance seems to be running fine after the 1.3 upgrade. The post earlier in the thread stating is was not working was some other guy hijacking the thread


Lars

[teirekos]

I am very sorry. My intention was to avoid open another thread with the same subject because my backup schedule does not seem to work. I am sorry for this ljorg.

[ljorg]

I am very sorry. My intention was to avoid open another thread with the same subject because my backup schedule does not seem to work. I am sorry for this ljorg.

Not at all, there's no problem other than the confusion of the Nagios support team


Lars

[scottwilkerson]

We have a fix in 1.3 that does fix the exact error you received when calling curator directly, now we call it with the full path

Glad it is now working.