Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
litespeed_wiki:lsmcd:user-errors [2019/02/25 19:53]
Robert Perper [Errors Getting Stats]
litespeed_wiki:lsmcd:user-errors [2019/02/25 20:11]
Robert Perper [Other Tools]
Line 21: Line 21:
   /​usr/​local/​lsmcd/​bin/​lsmcdctrl start   /​usr/​local/​lsmcd/​bin/​lsmcdctrl start
  
 +==== Other Tools ====
 +
 +There are other things you can do to validate accessibility to the LSMCD server. ​ All involve running in a console (ssh session) as root:
 +
 +   * Run telnet
 +   * Check the log
 +   * Get stats manually
 +
 +=== Run telnet ===
 +
 +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.
 +
 +=== Check the log ===
 +
 +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.  ​
 +
 +=== Manually perform the stats function ===
 +
 +The stats are obtained by running a script which obtains them.  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.
 +   
 ===== Other Errors (LSMCD related) ===== ===== Other Errors (LSMCD related) =====
  
Line 30: Line 62:
 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]]. 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]].
  
 +It is recommended that you also check the ''​Other Tools''​ in the section above for other troubleshooting ideas.
 ==== ''​node.conf not found in expected location''​ ==== ==== ''​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. 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.
  • Admin
  • Last modified: 2019/02/25 20:59
  • by Lisa Clarke