Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:lsmcd:user_errors [2018/08/20 16:37]
Robert Perper created
+++ litespeed_wiki:lsmcd:user_errors [2018/08/21 15:12] (current)
Lisa Clarke Proofreading
@@ Line 1: / Line 1: @@
-====== Errors using LSMCD Secure User Data CloudLinux/cPanel Interface ======
+====== LSMCD Secure User Data Errors ======
+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.
-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.
 ===== Errors Getting Stats =====
 There are three types of errors which can occur while getting stats:
-   - Your user is missing from the SASL database.  You can add yourself by following the link provided and entering a password.
+   * Your user is missing from the SASL database.  You can add yourself by following the link provided and entering a password.
-   - ''RC: 121 Output: Stats server exception:''
+   * ''RC: 121 Output: Stats server exception:''
-   - ''RC: 122 Output: Stats server access error''
+   * ''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.
+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.
 ==== ''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:
+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''
+  /usr/local/lsmcd/bin/lsmcdctrl start
+===== Other Errors (LSMCD related) =====
+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 [[https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:lsmcd:configuration|here]].
+==== ''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 (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.
+==== ''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.