| Hi,
which monit version it is?:
monit -V
As mentioned, monit >= 5.12.0 should work fine with up to 4096 bytes long commands.
Best regards, Martin
Hi Martin,
Is there any way we can get this working by setting some limit in the configs ?
On Wednesday, 5 December, 2018, 7:10:48 AM IST, rahul ramani < address@hidden> wrote:
Hi Martin,
There are 2069 characters in the process. copied the process in a test file
cat test | wc -c
2069
size of test file
4.0K test
Hello,
the limit for the command-line pattern is 4kB since monit 5.12.0 (was 1kB for monit <= 5.11.0)
Please can you provide the length of your command line? We can refactor the limit out or add a new option to "set limits" statement.
Best regards, Martin
The attached message has been automatically discarded. Subject: Need help with monit procmatch
Date: 4 December 2018 at 09:17:18 CET
HI Monit Users,
I recently started using monit in infrastructure and came across a scenario while using monit procmatch feature. Application which is being monitored is a java application and the string that need to be matched exist at the very end of the process string, now it seems procmatch is able to match the string till a specific length there might be a limit to that and since the string to be match exist at the end it is not able to catch it.
example: this is the process, and the STRINGTOMATCH exist at the end of the process
"/apps/java1.8/jre/bin/java -d64 -server -noverify -Xms4g -Xmx4g -XX:MaxMetaspaceSize=256m
-XX:InitialCodeCacheSize=128m -XX:ReservedCodeCacheSize=256m
-XX:CodeCacheMinimumFreeSpace=16m -XX:+UseG1GC
-XX:MaxGCPauseMillis=500 <many parameters here> <STRINGTOMATCH>"
Monit version used is 5.2.5 , so is there any way i can increase the limit or any config parameter which can be updated.
|