Uninitialized value in split

[jisakiel]

Uninitialized value in split

[derf]

The warnings should be fixed in 08da443, they were probably caused by a contact group which does not contain any contacts.

Regarding acknowledgments: Does it say "Acknowledged localhost/RAID: we know"? If so, is the file returned by config_data --module App::Icli --config command_file writable by the user running icli?

[jisakiel]

I don't get that message when running the command. Icli is running as root (either directly or with sudo) to make sure I can read the status file.

Also, when I run that command I get Can't locate App/Icli/ConfigData.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at (eval 23) line 3.

I have tried bypassing the debian build and directly building from the .tar.gz , in case the debian/rules might be missing something , but it simply installs the man page and the icli binary to /usr/local , resulting in the same error message when calling config_data.

My perl install is the squeeze one, 5.10.1-17squeeze6 . Might this be related to perl versions? Any pointers on how to help you debugging it?

Regarding the warnings, it is more than possible that I get them from empty contact groups, as the icinga config is automatically generated from scripts.

[derf]

Hm... perl 5.10.0 should be sufficient for that. Does it work when using icli -F /path/to/icinga.cmd ...?
(default path for that is /var/lib/icinga/rw/icinga.cmd, but you probably have a different one)

[jisakiel]

Both icli and `icli -F pathwork (as myicinga.cmd``is where you said, in the default path). What doesn't work is the``config_data``line.