Closed jkaitschuck closed 2 years ago
with GPFS -> gpfs.base-5.1.1-4.x86_64 CNS and <>
python/3.6.10 CherryPy 18.6.1
log displays ....
port=4242 protocol=http server=localhost serverPort=9980 apiKeyName=scale_grafana includeDiskData=False logPath=/var/log/ibm_bridge_for_grafana logLevel=5 logFile=zserver.log 2022-10-30 13:13:11,449 - bridgeLogger - DEBUG - readSensorsConfigFromMMSDRFS attempt to read /var/mmfs/gen/mmsdrfs 2022-10-30 13:13:11,450 - bridgeLogger - DEBUG - __do_RESTcall invoke params: perfmon/topo GET None 2022-10-30 13:13:11,450 - bridgeLogger - DEBUG - createRequestDataObj created request 2022-10-30 13:13:11,452 - bridgeLogger - MOREINFO - Server internal error occurred. Reason: can't set attribute 2022-10-30 13:13:11,452 - bridgeLogger - ERROR - Metadata could not be retrieved. Check log file for more details, quitting
===
?
pmcollector is running and mmperfmon from the node queries just fine.
on the pmcollector node please execute the following commands and paste the output here.
I discovered the issue late Sunday. There was a typo in the config file,. V6 of the code didn’t return the metadata collection error until the program was killed, V7 returned the metadata collection error in the log.
We are a bit behind the curve version wise on this particular system.
Thanks.
On Nov 1, 2022, at 11:49 AM, Helene Wassmann @.**@.>> wrote:
on the pmcollector node please execute the following commands and paste the output here.
— Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIBM%2Fibm-spectrum-scale-bridge-for-grafana%2Fissues%2F74%23issuecomment-1298962046&data=05%7C01%7Cjkaitschuck%40nvidia.com%7Ca41b423f37244408f16908dabc39c77e%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638029253598839635%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=MM85suNWEMIc8qJCD3YZYgZYaQum0%2BKaAquX1m%2BPiBY%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA346VJ6ZXMHNQGXURHDZOCDWGFQ2ZANCNFSM6AAAAAARSO65ZM&data=05%7C01%7Cjkaitschuck%40nvidia.com%7Ca41b423f37244408f16908dabc39c77e%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638029253598839635%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=sK6NT%2FuNF3sbUgI95P3zrWkqY4gS6BVAGRuWWUqNKaA%3D&reserved=0. You are receiving this because you authored the thread.Message ID: @.***>
Can we close this ticket?
yes … and thank you.
On Nov 1, 2022, at 11:56 AM, Helene Wassmann @.**@.>> wrote:
Can we close this ticket?
— Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIBM%2Fibm-spectrum-scale-bridge-for-grafana%2Fissues%2F74%23issuecomment-1298970566&data=05%7C01%7Cjkaitschuck%40nvidia.com%7C50c4cf710e774989e0c708dabc3accf8%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638029257988055996%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=aDjq0yuO4FIrPW%2FidU0azTuTF8GxvrVrciJq1euM5%2Fg%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA346VJ2CZPR5D5G5NN4DMVLWGFRWFANCNFSM6AAAAAARSO65ZM&data=05%7C01%7Cjkaitschuck%40nvidia.com%7C50c4cf710e774989e0c708dabc3accf8%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638029257988055996%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7MN0pFYfGRPrWzea3ncl4%2BlZfMfg7YEM254Y8IGGDfM%3D&reserved=0. You are receiving this because you authored the thread.Message ID: @.***>
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context Add any other context about the problem here.