The message:
ERROR: ProcessContext::initialise Unable to get group info : Success(0)It can appear in the Netprobe when it is started up or restarted.
Example:
2023-03-31 10:34:35.096+0000 *****************************************************************************************************************************
2023-03-31 10:34:35.096+0000 Geneos EMF2 Netprobe GA6.2.1-230214 (with support for CORE,ORACLE,SQL_TOOLKIT,IXWATCH_RTT,RMC,MQ,RV) (c) 1995-2023 ITRS Group
2023-03-31 10:34:35.096+0000 *****************************************************************************************************************************
2023-03-31 10:34:35.097+0000 INFO: Build type: linux_64:Release
2023-03-31 10:34:35.097+0000 INFO: Running from: /itrs/netprobe
2023-03-31 10:34:35.097+0000 INFO: User/uid/gid: root/0/0
2023-03-31 10:34:35.097+0000 INFO: Current path: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
2023-03-31 10:34:35.097+0000 INFO: LD_LIBRARY_PATH has not been set
2023-03-31 10:34:35.098+0000 ERROR: ProcessContext::initialise Unable to get group info : Success(0)The error means the running user of netprobe has no rights to query the AD/LDAP for the group info they belong. In that case, it should be related to a local account rather than a domain account. Even so, "Success(0)" means no error was returned for the query request, but the query was successful, but no response was obtained.
By default, Linux is designed to only have root as admin (userid 0 and group id 0) and the other users to be sudoers (elevated rights), If more than one user is assigned to group 0, then Linux Process Context will return no group info can be extracted. Security enhancement software normally modifies the groups so that only specific users or groups can obtain information.
The error in the grand scheme of things is harmless, it will not impact monitoring.
Further Reading
If you need further help:
-
Please contact our support team via the chat service box on any of our websites or raise a support request.
-
Make sure you provide us with:
- Background of the issue or request.
- Use cases, requirements, business impact, etc.
- Encountered error messages.
- Log files or diagnostic files.
- Screenshots.
- And other important information relevant to your inquiry.
Comments
0 comments
Please sign in to leave a comment.