| Newsgroups |
gmane.comp.monitoring.monit.general |
| Message-ID |
<[email protected]> |
Please upgrade monit, you need version >= 5.12.0
> On 11 Dec 2018, at 06:53, rahul ramani <[email protected]> wrote:
>
> Hi,
>
> Monit version is 5.2.5
>
> monit -V
> This is Monit version 5.2.5
> Copyright (C) 2000-2011 Tildeslash Ltd. All Rights Reserved.
>
>
> Thanks
> Rahul
>
>
>
> On Tuesday, 11 December, 2018, 12:48:19 AM IST, [email protected] <[email protected]> wrote:
>
>
> 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
>
>
>> On 10 Dec 2018, at 14:42, rahul ramani <[email protected] <mailto:[email protected]>> wrote:
>>
>> Hi Martin,
>>
>> Is there any way we can get this working by setting some limit in the configs ?
>>
>> Thanks
>> Rahul
>>
>>
>>
>> On Wednesday, 5 December, 2018, 7:10:48 AM IST, rahul ramani <[email protected] <mailto:[email protected]>> 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
>>
>> Thanks
>> Rahul
>>
>>
>>
>> On Wednesday, 5 December, 2018, 12:21:12 AM IST, [email protected] <mailto:[email protected]> <[email protected] <mailto:[email protected]>> wrote:
>>
>>
>> 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
>>
>>
>>
>>> On 4 Dec 2018, at 09:17, [email protected] <mailto:[email protected]> wrote:
>>>
>>> The attached message has been automatically discarded.
>>> From: rahul ramani <[email protected] <mailto:[email protected]>>
>>> Subject: Need help with monit procmatch
>>> Date: 4 December 2018 at 09:17:18 CET
>>> To: "[email protected] <mailto:[email protected]>" <[email protected] <mailto:[email protected]>>
>>> Reply-To: rahul ramani <[email protected] <mailto:[email protected]>>
>>>
>>>
>>> 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.
>>>
>>>
>>>
>>> Thanks
>>> Rahul
>>>
>>>
>>>
>>
>
--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general