-
Notifications
You must be signed in to change notification settings - Fork 1
FAQ (v4)
You can check the version of your ldmsd with:
> ldmsd -V LDMSD Version: 4.1.1 LDMS Protocol Version: 4.1.0.0 LDMSD Interface Version: 3.2.2.0 git-SHA: e9afd5d888330d68d1627373758eca60315c2d1f-dirty
where:
- LDMSD Version - LDMS package version. This reflects code advancement.
- LDMS Protocol Version - Version of the transport protocol. Transports must have version compatibility.
- LDMSD Interface Versions - Version of the ldmsd interface. Communications between ldmsds must have version compatibility.
- git-SHA - git checkout SHA
> ldms_ls -V LDMS_LS Version: 4.1.1 LDMS Protocol Version: 4.1.0.0
where:
- LDMS_LS Version - LDMS package version.
For configuration best practices and example scripts, see the Configuration section under the main wiki menu
> ldmsd -u meminfo LDMSD plugins in XXX/lib64/ovis-ldms : ======= SAMPLER meminfo: config name=meminfoproducer=<name> instance=<name> [component_id=<int>] [schema=<name>] [job_set=<name>] [job_id=<name>] [app_id=<name>] [job_start=<name>] [job_end=<name>] [uid=<user-id>] [gid=<group-id>] [perm=<mode_t permission bits>] producer A unique name for the host providing the data instance A unique name for the metric set component_id A unique number for the component being monitored, Defaults to zero. schema The name of the metric set schema, Defaults to the sampler name job_set The instance name of the set containing the job data, default is 'job_info' job_id The name of the metric containing the Job Id, default is 'job_id' app_id The name of the metric containing the Application Id, default is 'app_id' job_start The name of the metric containing the Job start time, default is 'job_start' job_end The name of the metric containing the Job end time, default is 'job_end' uid The user-id of the set's owner (defaults to geteuid()) gid The group id of the set's owner (defaults to getegid()) perm The set's access permissions (defaults to 0777) =========================
If you have a small number of components and/or infrequent write intervals your system may be buffering the writes. Try setting the buffering to write out more frequently (in lines or bytes) or turn off buffering.
Check your authentication settings
If you are using sock, there can be a delay in the ability to do an immediate rebind to the same port. You will see an error message about the port being in use in the ldms logs. One can reconnect after a short (10s of seconds) wait.
- Home
- Search
- Feature Overview
- LDMS Data Facilitates Analysis
- Contributing patches
- User Group Meeting Notes - BiWeekly!
- Publications
- News - now in Discussions
- Mailing Lists
- Help
Tutorials are available at the conference websites
- Coming soon!
- Testing Overview
- Test Plans & Documentation: ldms-test
- Man pages currently not posted, but they are available in the source and build
V3 has been deprecated and will be removed soon
- Configuring
- Configuration Considerations
- Running