This is an old revision of the document!


Errors using LSMCD Secure User Data CloudLinux/cPanel Interface

Most problems that will occur during a CPanel session 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:

  1. Your user is missing from the SASL database. You can add yourself by following the link provided and entering a password.
  2. RC: 121 Output: Stats server exception:
  3. RC: 122 Output: Stats server access error

''RC: 121 Output: Stats server exception: (message)''

The message should be examined in detail to attempt to understand the problem. If it is not obvious from examination, contact LiteSpeed Technical Support. You may need to check the LSMCD log, usually in /tmp/lsmcd.log

''RC: 122 Output: Stats server access error''

Most of the time this is caused by the lsmcd server not being active. It can be started from a root console with the following command: /usr/local/lsmcd/bin/lsmcdctrl start

Some other errors which may pop up:

  1. node.conf not found in expected location:
  2. cached.addr not found in:
  3. cached.addr not given a value in:

If any of these errors occur, you should check the lsmcd log: usually in /tmp/lsmcd.log as specified in the LogFile parameter in the default node.conf file usually in /usr/local/lsmcd/conf/node.conf. The administrator should check LSMCD configuration as described in: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:lsmcd:configuration

''node.conf not found in expected location''

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.

''cached.addr not found in (node.conf file name)

This message indicates that in the node.conf file (should be displayed fully qualified) the parameter title cached.addr (case should not matter for this parameter) was not found. This parameter 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.

''cached.addr not given a value in:''

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.

  • Admin
  • Last modified: 2018/08/20 20:16
  • by Robert Perper