Check_MK memory problem



  • Hello!

    The Check_MK package "RC1 0.1.5 platform: 2.2 2.2.999" has RAM problem. As soon the package is installed on a "2.2.4-RELEASE (i386) built on Sat Jul 25 19:56:41 CDT 2015 FreeBSD 10.1-RELEASE-p15" (Alix Hardware with 256 MB RAM), the memory is going to zero and tasks will be killed.

    I had Check_MK installed with IPfire on the same Hardware and it worked.
    Does somebody knows if Check_MK needs so much RAM or is it a bug?

    Tanks you!


  • Banned

    Not exactly sure what memory problem are you seeing, that package is completely broken on 2.2.x in the first place. If you want to test something, use the files from here:
    https://github.com/doktornotor/pfsense-packages/tree/patch-14/config/checkmk-agent


  • Banned

    0.1.6 available now. Good luck. :D



  • With the patch files the memory bug wasn't there any more :-)


  • Banned

    Thanks for testing! My guess would be it was spawning the shell script endlessly due to the totally fucked up inetd handling, but I don't have any setup available to test this thing. Suspect the package has ~2 users altogether.  ;D



  • That could be  :) Check_MK is a really nice tool for monitoring  ;)



  • Hi

    I have just updated the plugin. Finaly it works again. Thx.

    Noticed just one problem, the name of the menu-item changed from "Check_mk Agent" to "check_mk Agent" and the old menu item was not removed when directly upgrading.
    It works when the version 0.1.5 is first removed and then 0.1.6 is installed.

    Now on one system i have both menu items, one not funtional. How can i manually remove that?

    Thanks for your work :)
    Beat


  • Banned

    @Beat:

    Noticed just one problem, the name of the menu-item changed from "Check_mk Agent" to "check_mk Agent" and the old menu item was not removed when directly upgrading.
    It works when the version 0.1.5 is first removed and then 0.1.6 is installed.
    Now on one system i have both menu items, one not funtional. How can i manually remove that?

    Only by manually removing the thing from /cf/conf/config.xml I'm afraid. (Sorry, this install code caching is super retarded.)



  • @doktornotor:

    Only by manually removing the thing from /cf/conf/config.xml I'm afraid. (Sorry, this install code caching is super retarded.)

    That worked. Thx


Log in to reply