Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
litespeed_wiki:lsmcd:user_errors [2018/08/20 20:16] Robert Perper [''RC: 121 Output: Stats server exception: (message)''] |
litespeed_wiki:lsmcd:user_errors [2018/08/20 20:18] Robert Perper [''RC: 122 Output: Stats server access error''] |
||
|---|---|---|---|
| Line 12: | Line 12: | ||
| ==== ''RC: 121 Output: Stats server exception: (message)'' ==== | ==== ''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'' | + | 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'' ==== | ==== ''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 and 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'' | ||