GithubHelp home page GithubHelp logo

lscmd not started about lsmcd HOT 12 OPEN

litespeedtech avatar litespeedtech commented on July 19, 2024
lscmd not started

from lsmcd.

Comments (12)

rperper avatar rperper commented on July 19, 2024

Hi,
My name is Bob Perper and I'm a developer here at Litespeed technologies and I work with the lsmcd program. This is an interesting error, while as lsmcd does use Sasl, it does not use any SQL, so it must be the SASL configuration that is attempting to load SQL. Do you know if you use SASL for other things? If not, check your /etc/sasl2/smtpd.conf file and make sure that the mech_list: only has the values of plain and login.

Also verify that you can add users with saslpasswd2 and list users with sasldblistusers2.

If you're still confused, please send me your /usr/local/lsmcd/conf/node.conf file and /tmp/lsmcd.log file.

Thanks,

Bob Perper
[email protected]

from lsmcd.

drorzeno avatar drorzeno commented on July 19, 2024

from lsmcd.

drorzeno avatar drorzeno commented on July 19, 2024

from lsmcd.

rperper avatar rperper commented on July 19, 2024

Hi,
The instructions for using saslpasswd2 and sasldblistusers2 are here: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:lsmcd:new_sasl#option_1_recommendedsasldb_managed_database
You need to create SASL managed users with saslpasswd2 before using lsmcd with SASL anyway, so it's best to do it first.

In your node.conf file, put a '#' in front of the line LogLevel=notice and take out the '#' in front of the line: #LogLevel=dbg_medium. This will turn on debug logging. After you add a couple of SASL users, try starting lsmcd again: systemctl start lsmcd and then please send me the resulting /tmp/lsmcd.log file. Note that after everything is working you'll want to uncomment out the LogLevel=notice and comment out the LogLevel=dbg_medium (reversing what you did above) to avoid filling the log with extra junk.

Thanks,

Bob Perper
[email protected]

from lsmcd.

drorzeno avatar drorzeno commented on July 19, 2024

from lsmcd.

rperper avatar rperper commented on July 19, 2024

Typically the message [ERROR] [__root] Memcache Listener failed to start indicates that the IP port 11211 is in use. You can validate that using netstat: netstat -lntp which will also show you the process that owns the listener.

If you're turning off SASL, you should also set Cached.DataByUser=false as DataByUser requires SASL.

Thanks,

Bob Perper
[email protected]

from lsmcd.

drorzeno avatar drorzeno commented on July 19, 2024

from lsmcd.

rperper avatar rperper commented on July 19, 2024

Kill the process with the -9 option. If that doesn't work, see if the lscpd program is running: ps-ef|grep lscpd, if so that may be restarting lsmcd so kill that as well.

Thanks,
Bob Perper
[email protected]

from lsmcd.

rperper avatar rperper commented on July 19, 2024

Another thought might be to stop it using systemctl: systemctl stop lsmcd.

Thanks,
Bob Perper
[email protected]

from lsmcd.

drorzeno avatar drorzeno commented on July 19, 2024

from lsmcd.

rperper avatar rperper commented on July 19, 2024

That should not be necessary.

The first thing you should try is to end it the normally supported way: /usr/local/lsmcd/bin/lsmcdctrl stop. Note that you have to be root to do any of these things (or sudo the command).

One of the nice things about ps is that it gives us the parent process. Do a ps -ef|grep lsmcd. The first column is the owner, the second column is the process PID and the third column is the parent process.

If the parent process is 1, then we know that it's being restarted by something which is part of the system startup, most likely systemd. In that case you should be able to use systemctl to stop and disable the process: systemctl stop lsmcd, systemctl kill lsmcd, systemctl disable lsmcd. You can disable the service and then try manually killing the processes, with -9 if necessary.

If the parent process is not 1, then use ps -ef|grep <parent pid> and then you can kill that process ID and then should be able to kill lsmcd.

If lsmcd is not getting a new process ID each time you kill it with -9, then most likely there's something wrong with your OS.

No matter what, I'd disable the lsmcd service if you're going to restart your system so that it doesn't end up like this again. You can manually restart lsmcd by running /usr/local/lsmcd/bin/lsmcd

Thanks,

Bob Perper
[email protected]

from lsmcd.

drorzeno avatar drorzeno commented on July 19, 2024

from lsmcd.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.