Troubleshooting
Problem
After the upgrade for Guardium appliance to version 11, error seen on cli:
"Failed to create bus connection: No such file or directory"
Symptom
After running any command on cli will result in the error, for example:
In the messages files inside the must_gather you will see the following snippet:
Cause
This is a Redhat Linux (rhel7) issue as described here (requires Redhat login to see full document): https://access.redhat.com/solutions/3550072
RHEL7 (since 7.0) expects that /var/run should be a symbolic link to /run. This issue happens whenever a symbolic link is not found. The error only appears if internal package 'dbus' was updated to dbus-1.10.24 or later.
Detailed explanation of the error messages seen :
which may fail depending on the state of the system i.e. when /var/run is not a symbolic link to /run.
In dbus-1.6.12, /var/run/dbus/system_bus_socket socket still exists but dbus daemon is not listening on that socket so Connection refused is returned to the service trying to connect to the socket.
If /var/run was changed from a symbolic link to /run to some real directory during system's life time,
/var/run/dbus/system_bus_socket socket doesn't exist, causing No such file or directory to be returned to the service trying to connect to the socket.
Diagnosing The Problem
Please check for the below error on the cli:-
Resolving The Problem
IBM Guardium Technical Support will need root access to the appliance.
Guardium support engineer can follow the internal steps in this document to resolve.
Related Information
Document Location
Worldwide
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Component":"","Platform":[{"code":"PF004","label":"Appliance"}],"Version":"11","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Was this topic helpful?
Document Information
Modified date:
17 March 2020
UID
ibm11073518