If you have experienced an error while using LSMCD Secure User Data in a CloudLinux/cPanel environment, you will probably require administrator intervention. This section assumes that you are either discussing the issue with your administrator now, or are collecting information for later discussion.
There are three types of errors which can occur while getting stats:
RC: 121 Output: Stats server exception:RC: 122 Output: Stats server access error
The message should be examined in detail to attempt to understand the problem. You may need to check the LSMCD log, usually in /tmp/lsmcd.log. If it is not obvious from examination, contact LiteSpeed Technical Support.
Most of the time this is caused by the LSMCD server not being active. Verify the process lsmcd is running. If it is, you should check the LSMCD log, usually found in /tmp/lsmcd.log. If the service is not running, it can be started from a root console with the following command:
/usr/local/lsmcd/bin/lsmcdctrl start
There are other things you can do to validate accessibility to the LSMCD server. All involve running in a console (ssh session) as root:
To run telnet, connect to the server IP and port configured for LSMCD. For example if you are running on the server:
telnet 127.0.0.1 11211
If telnet is not found (and it's not installed by default), you may need to install it:
yum install telnet
Once you have connected, you can run run the stats command to validate that you have proper connectivity. It should report the current stats for the anonymous user.
This should be done for any and all problems. The log is /tmp/lsmcd.log by default. If there is insufficient logging to help you find the problem, you can update node.conf (in /usr/local/lsmcd/conf/node.conf) to set LogLevel=dbg_medium. You will need to restart the LSMCD server.
The stats are obtained by running a script. You can do this manually from the command line. In a default install:
cd /usr/local/cpanel/base/frontend/paper_lantern/lsmcd_usermgr ./lsmcdsasl.py 127.0.0.1:11211 user
Where user is the user you are verifying.
Some other errors which may pop up:
node.conf not found in expected location:cached.addr not found in:cached.addr not given a value in:
If any of these errors occur, you should check the LSMCD log. The log is usually in /tmp/lsmcd.log, as specified in the LogFile parameter of the default node.conf file (usually found in /usr/local/lsmcd/conf/node.conf). The administrator should check the LSMCD configuration as described here.
It is recommended that you also check the Other Tools in the section above for other troubleshooting ideas.
This message will be followed by the expected fully qualified file name location. It is the conf directory in the startup location for LSMCD, usually /usr/local/lsmcd/conf/node.conf. Verify that node.conf is in this location, as this is the configuration file for LSMCD. If the file does exist in that location or the location is something unexpected, contact LiteSpeed Technical Support.
This message indicates that in the node.conf file (which should be displayed fully qualified) the parameter title cached.addr was not found. This parameter, which is not case-sensitive, is the server address used by external applications to get to LSMCD and is required. cached.addr is a title, and all parameters in node.conf are in the form (title)=(value). The form for the line is
cached.addr=(IP address):(port number)
or the Unix Domain Socket file name
cached.addr=UDS:///(file name)
This parameter is required, as it is the way that external applications access the server. The default value in the default file is:
Cached.Addr=127.0.0.1:11211'
If this parameter is in the file and appears correct, or something else unexpected occurs, contact LiteSpeed Technical Support.
This message is followed by the complete line the parameter is found in, and is then followed by the file name. Verify that cached.addr has a value as described above. The default value in the default file is
Cached.Addr=127.0.0.1:11211
If this parameter is in the file and appears correct or something else unexpected occurs, contact LiteSpeed Technical Support.