Try to monitor seperate IPSEC-VPN-Tunnels on Fortigate

[dns_es]

CMK: v2 p5, raw

Hi,
i try to monitor each IP-Sec-VPN-Tunnel on Fortigate with this MKP.

https://exchange.checkmk.com/p/fortigate-ipsec-p1

• Installation works fine
• service configuration on host showing new services (each vpn ip sec tunnel, so far so good)

If i aply the new services, it throws an error, see pic.

What i can see is, that the installed mkp creates a file (~/var/check_mk/packages) named fortigate_ipsec_p1 not fortigate_ipsec_ph1.

Ideas?

[andreas-doehler (Andreas)]

Rename the file from _p1 to _ph1 and try again.

[dns_es]

did it allready before…
but only rename and then try to reload without doing new service inventory…

i will give it later a new try

[dns_es]

hi @andreas, didn´t work.

1. install
2. rename
3. service config → full scan (see new services)
4. activate changes → failed (same error message)

[dns_es]

Hi @andreas,

now it works. It´s necessary to rename all files…

/var/check_mk/packages/
/var/check_mk/precompiled_checks/local
/tmp/check_mk/check_includes/local
/local/share/check_mk/checks

[andreas-doehler (Andreas)]

@dns_es

/var/check_mk/precompiled_checks/local
/tmp/check_mk/check_includes/local

These two can be deleted any will be recreated after “cmk -R”.
This problem happens some times if the old checks don’t follow the rule - checkname = filename

[_shorty (Uli)]

Hi @dns_es ,

where can I find those files? I’ve tried to search in /omd/sites/mysites/var but the files aren’t there. Where can i find it to rename them?

[dns_es]

hi @_shorty,