[gpfsug-discuss] pmmonitor - ERROR

Chakravarthy Girda cgirda at wustl.edu
Thu Jul 20 21:03:56 BST 2017


For now I switched the "zimonGrafanaIntf" to port "4262". So far it
didn't crash the pmcollector. Will wait for some more time to ensure its
working.

* Can we start this process in a daemon or service mode?


Thank you
Chakri


On 7/20/17 12:30 PM, Chakravarthy Girda wrote:
> Bob,
>
>  Actually the pmcollector service died in 5min.
>
> 2017-07-20 12:11:29,639 - pmmonitor - WARNING - GPFSCapacityUtil:
> received zero inode/pool total size
> 2017-07-20 12:16:29,470 - pmmonitor - WARNING - GPFSCapacityUtil:
> received zero inode/pool total size
> 2017-07-20 12:16:29,639 - pmmonitor - WARNING - GPFSCapacityUtil:
> received zero inode/pool total size
> 2017-07-20 12:21:29,384 - pmmonitor - ERROR - QueryHandler: Socket
> connection broken, received no data
> 2017-07-20 12:21:29,384 - pmmonitor - ERROR - GPFSCapacityUtil::execute:
> Error sending query in execute, quitting
> 2017-07-20 12:21:29,552 - pmmonitor - ERROR - GPFSCapacityUtil::execute:
> Error sending query in execute, quitting
> 2017-07-20 12:21:30,047 - pmmonitor - ERROR - GPFSCapacityUtil::execute:
> Error sending query in execute, quitting
>
> Thank you
> Chakri
>
>
> On 7/20/17 12:12 PM, Chakravarthy Girda wrote:
>> Bob, 
>>
>>  Your correct. Found the issues with pmcollector services. Fixed issues
>> with pmcollector, resolved the issues.
>>
>>
>> Thank you
>>
>> Chakri
>>
>>
>> On 7/20/17 11:50 AM, Oesterlin, Robert wrote:
>>> You will also see this node when the pmcollector process is still initializing. (reading in the existing database, not ready to service requests)
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss




More information about the gpfsug-discuss mailing list