I have a system here that used to have a pip-installed Curator running on it.
Since pip-uninstalling the old version and installing Curator 5.5.4 from the Elastic apt repo, I can't get it to do anything.
Running /usr/bin/curator from the cmdline with no arguments just exits after a second or two. Nothing is logged - in fact it seems to be ignoring curator.yml because it doesn't matter if it's present or not. There is no cmdline output - not even the warning that
action_file is missing, which you'd expect when starting it with no args.
I have a similar machine running the same version of Ubuntu server and has the same version of Curator installed, and that one is fine. I really can't see any difference between the two, but I suspect some version of some library has been left over from the pip installed version.
I've tried to strace both processes and diff the results, but I really can't see anything obvious (although there are differences).
I've spent ages on this and have no idea where to look from here. Help please?