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
