lscmd not started

[collie-script]

Hello,
When I tried to start lscmd I get this error:

I install before:
yum groupinstall "Development Tools"
yum install autoconf automake zlib-devel openssl-devel expat-devel pcre-devel libmemcached-devel cyrus-sasl*

Please help me.

[rperper]

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
rperper@litespeedtech.com

[collie-script]

Hi bob! Thank you for your response. I don't know if I use SASL for other things. I think I don't use and the SASL SQL was installed for the lsmcd via this command: I don't have the file /etc/sasl2/smtpd.conf but the folder /etc/sasl2 is exists and empty. I don't know how to use the commands saslpasswd2 and sasldblistusers2. Its VPS with cloudlinux and DirectAdmin and litespeed web enterprise. My /usr/local/lsmcd/conf/node.conf: Repl.HeartBeatReq=30 Repl.HeartBeatRetry=3000 Repl.MaxTidPacket=2048000 Repl.GzipStream=YES Repl.LbAddrs=127.0.0.1:12340 Repl.ListenSvrAddr=127.0.0.1:12340 REPL.DispatchAddr=127.0.0.1:5501 RepldSockPath=/tmp/repld.usock CACHED.PRIADDR=127.0.0.1:11000 CACHED.ADDR=127.0.0.1:11211 #CACHED.ADDR=UDS:///tmp/lsmcd.sock #default is 8, it can be bigger depending on cache data amount Cached.Slices=8 Cached.Slice.Priority.0=100 Cached.Slice.Priority.1=100 Cached.Slice.Priority.2=100 Cached.Slice.Priority.3=100 Cached.Slice.Priority.4=100 Cached.Slice.Priority.5=100 Cached.Slice.Priority.6=100 Cached.Slice.Priority.7=100 Cached.ShmDir=/dev/shm/lsmcd Cached.UseSasl=true Cached.DataByUser=true Cached.Anonymous=false ##this is the global setting, no need to have per slice configuration. User=nobody Group=nobody #depends CPU core CachedProcCnt=4 CachedSockPath=/tmp/cached.usock. TmpDir=/tmp/lsmcd LogLevel=notice #LogLevel=dbg_medium LogFile=/tmp/lsmcd.log Thanks! From: Bob Perper <notifications@github.com> Sent: Thursday, October 31, 2019 2:53 PM To: litespeedtech/lsmcd‏ <lsmcd@noreply.github.com> Cc: drorzeno‏ <drorzeno@gmail.com>; Author‏ <author@noreply.github.com> Subject: Re: [litespeedtech/lsmcd] lscmd not started (#10) 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 rperper@litespeedtech.com <mailto:rperper@litespeedtech.com> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#10?email_source=notifications&email_token=AIP5HPHS3FCSOZXU6N4NFUDQRLIKTA5CNFSM4JHFS75KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECXUY3Y#issuecomment-548359279> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIP5HPBKEFMM7FGQPSC6R5DQRLIKTANCNFSM4JHFS75A> . <https://github.com/notifications/beacon/AIP5HPEF2UIKOW3QDTBIFTDQRLIKTA5CNFSM4JHFS75KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECXUY3Y.gif>

[collie-script]

Another thing, Because the lsmcd not started there no lsmcd.log file. From: drorzeno@gmail.com <drorzeno@gmail.com> Sent: Thursday, October 31, 2019 3:06 PM To: 'litespeedtech/lsmcd'‏ <reply@reply.github.com>; 'litespeedtech/lsmcd'‏ <lsmcd@noreply.github.com> Cc: 'Author'‏ <author@noreply.github.com> Subject: RE: [litespeedtech/lsmcd] lscmd not started (#10) Hi bob! Thank you for your response. I don't know if I use SASL for other things. I think I don't use and the SASL SQL was installed for the lsmcd via this command: I don't have the file /etc/sasl2/smtpd.conf but the folder /etc/sasl2 is exists and empty. I don't know how to use the commands saslpasswd2 and sasldblistusers2. Its VPS with cloudlinux and DirectAdmin and litespeed web enterprise. My /usr/local/lsmcd/conf/node.conf: Repl.HeartBeatReq=30 Repl.HeartBeatRetry=3000 Repl.MaxTidPacket=2048000 Repl.GzipStream=YES Repl.LbAddrs=127.0.0.1:12340 Repl.ListenSvrAddr=127.0.0.1:12340 REPL.DispatchAddr=127.0.0.1:5501 RepldSockPath=/tmp/repld.usock CACHED.PRIADDR=127.0.0.1:11000 CACHED.ADDR=127.0.0.1:11211 #CACHED.ADDR=UDS:///tmp/lsmcd.sock #default is 8, it can be bigger depending on cache data amount Cached.Slices=8 Cached.Slice.Priority.0=100 Cached.Slice.Priority.1=100 Cached.Slice.Priority.2=100 Cached.Slice.Priority.3=100 Cached.Slice.Priority.4=100 Cached.Slice.Priority.5=100 Cached.Slice.Priority.6=100 Cached.Slice.Priority.7=100 Cached.ShmDir=/dev/shm/lsmcd Cached.UseSasl=true Cached.DataByUser=true Cached.Anonymous=false ##this is the global setting, no need to have per slice configuration. User=nobody Group=nobody #depends CPU core CachedProcCnt=4 CachedSockPath=/tmp/cached.usock. TmpDir=/tmp/lsmcd LogLevel=notice #LogLevel=dbg_medium LogFile=/tmp/lsmcd.log Thanks! From: Bob Perper <notifications@github.com <mailto:notifications@github.com> > Sent: Thursday, October 31, 2019 2:53 PM To: litespeedtech/lsmcd‏ <lsmcd@noreply.github.com <mailto:lsmcd@noreply.github.com> > Cc: drorzeno‏ <drorzeno@gmail.com <mailto:drorzeno@gmail.com> >; Author‏ <author@noreply.github.com <mailto:author@noreply.github.com> > Subject: Re: [litespeedtech/lsmcd] lscmd not started (#10) 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 rperper@litespeedtech.com <mailto:rperper@litespeedtech.com> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#10?email_source=notifications&email_token=AIP5HPHS3FCSOZXU6N4NFUDQRLIKTA5CNFSM4JHFS75KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECXUY3Y#issuecomment-548359279> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIP5HPBKEFMM7FGQPSC6R5DQRLIKTANCNFSM4JHFS75A> . <https://github.com/notifications/beacon/AIP5HPEF2UIKOW3QDTBIFTDQRLIKTA5CNFSM4JHFS75KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECXUY3Y.gif>

[rperper]

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
rperper@litespeedtech.com

[collie-script]

Oh, So I don't need SASL. I disable this via change Cached.UseSasl to false but It's don't work. My log file: 2019-10-31 15:27:46.630 [DEBUG] [__root] About to test USESASL 2019-10-31 15:27:46.630 [DEBUG] [__root] CACHED.USESASL = false 2019-10-31 15:27:46.630 [DEBUG] [__root] CACHED.SLICE.PRIORITY.0=100 2019-10-31 15:27:46.630 [DEBUG] [__root] CACHED.SHMFILEPATH.0=/dev/shm/lsmcd/data0 2019-10-31 15:27:46.630 [DEBUG] [__root] CACHED.SLICE.PRIORITY.1=100 2019-10-31 15:27:46.630 [DEBUG] [__root] CACHED.SHMFILEPATH.1=/dev/shm/lsmcd/data1 2019-10-31 15:27:46.630 [DEBUG] [__root] CACHED.SLICE.PRIORITY.2=100 2019-10-31 15:27:46.630 [DEBUG] [__root] CACHED.SHMFILEPATH.2=/dev/shm/lsmcd/data2 2019-10-31 15:27:46.630 [DEBUG] [__root] CACHED.SLICE.PRIORITY.3=100 2019-10-31 15:27:46.630 [DEBUG] [__root] CACHED.SHMFILEPATH.3=/dev/shm/lsmcd/data3 2019-10-31 15:27:46.630 [DEBUG] [__root] CACHED.SLICE.PRIORITY.4=100 2019-10-31 15:27:46.630 [DEBUG] [__root] CACHED.SHMFILEPATH.4=/dev/shm/lsmcd/data4 2019-10-31 15:27:46.630 [DEBUG] [__root] CACHED.SLICE.PRIORITY.5=100 2019-10-31 15:27:46.630 [DEBUG] [__root] CACHED.SHMFILEPATH.5=/dev/shm/lsmcd/data5 2019-10-31 15:27:46.630 [DEBUG] [__root] CACHED.SLICE.PRIORITY.6=100 2019-10-31 15:27:46.630 [DEBUG] [__root] CACHED.SHMFILEPATH.6=/dev/shm/lsmcd/data6 2019-10-31 15:27:46.630 [DEBUG] [__root] CACHED.SLICE.PRIORITY.7=100 2019-10-31 15:27:46.630 [DEBUG] [__root] CACHED.SHMFILEPATH.7=/dev/shm/lsmcd/data7 2019-10-31 15:27:46.630 [NOTICE] [__root] LSMCD/1.4.7 LiteSpeed Memcached Replacement 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser contructor 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser contructor 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser contructor 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser contructor 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser contructor 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser contructor 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser contructor 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser contructor 2019-10-31 15:27:46.637 [DEBUG] [__root] McHashMulti init, ShmName: data0, HashName: SHMMCHASH, slice: 0 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser Allocate default hash, size: 500000 2019-10-31 15:27:46.637 [DEBUG] [__root] LsMcHashMulti::init m_idx:0 2019-10-31 15:27:46.637 [DEBUG] [__root] McHashMulti init, ShmName: data1, HashName: SHMMCHASH, slice: 1 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser Allocate default hash, size: 500000 2019-10-31 15:27:46.637 [DEBUG] [__root] LsMcHashMulti::init m_idx:1 2019-10-31 15:27:46.637 [DEBUG] [__root] McHashMulti init, ShmName: data2, HashName: SHMMCHASH, slice: 2 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser Allocate default hash, size: 500000 2019-10-31 15:27:46.637 [DEBUG] [__root] LsMcHashMulti::init m_idx:2 2019-10-31 15:27:46.637 [DEBUG] [__root] McHashMulti init, ShmName: data3, HashName: SHMMCHASH, slice: 3 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser Allocate default hash, size: 500000 2019-10-31 15:27:46.637 [DEBUG] [__root] LsMcHashMulti::init m_idx:3 2019-10-31 15:27:46.637 [DEBUG] [__root] McHashMulti init, ShmName: data4, HashName: SHMMCHASH, slice: 4 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser Allocate default hash, size: 500000 2019-10-31 15:27:46.637 [DEBUG] [__root] LsMcHashMulti::init m_idx:4 2019-10-31 15:27:46.637 [DEBUG] [__root] McHashMulti init, ShmName: data5, HashName: SHMMCHASH, slice: 5 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser Allocate default hash, size: 500000 2019-10-31 15:27:46.637 [DEBUG] [__root] LsMcHashMulti::init m_idx:5 2019-10-31 15:27:46.637 [DEBUG] [__root] McHashMulti init, ShmName: data6, HashName: SHMMCHASH, slice: 6 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser Allocate default hash, size: 500000 2019-10-31 15:27:46.637 [DEBUG] [__root] LsMcHashMulti::init m_idx:6 2019-10-31 15:27:46.637 [DEBUG] [__root] McHashMulti init, ShmName: data7, HashName: SHMMCHASH, slice: 7 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser Allocate default hash, size: 500000 2019-10-31 15:27:46.637 [DEBUG] [__root] LsMcHashMulti::init m_idx:7 2019-10-31 15:27:46.637 [DEBUG] [__root] SASL defined: NO 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] Conn 0x8c23d0 set pHash: 0x8ba310 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] Conn 0x8c3590 set pHash: 0x8ba990 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] Conn 0x8c4750 set pHash: 0x8bb010 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] Conn 0x8c5910 set pHash: 0x8bb690 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] Conn 0x8c6ad0 set pHash: 0x8bbd10 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] Conn 0x8c7c90 set pHash: 0x8bc390 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] Conn 0x8c8e50 set pHash: 0x8bca10 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] Conn 0x8ca010 set pHash: 0x8bd090 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] Conn 0x8c23d0 set pHash: 0x8ba310 2019-10-31 15:27:46.637 [DEBUG] [__root] ShmSlice: [/dev/shm/lsmcd/data0.shm]. 2019-10-31 15:27:46.637 [DEBUG] [__root] SetHdrOff: 4480 for pConn: 0x8c23d0 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] Conn 0x8c3590 set pHash: 0x8ba990 2019-10-31 15:27:46.637 [DEBUG] [__root] ShmSlice: [/dev/shm/lsmcd/data1.shm]. 2019-10-31 15:27:46.637 [DEBUG] [__root] SetHdrOff: 4480 for pConn: 0x8c3590 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] Conn 0x8c4750 set pHash: 0x8bb010 2019-10-31 15:27:46.637 [DEBUG] [__root] ShmSlice: [/dev/shm/lsmcd/data2.shm]. 2019-10-31 15:27:46.637 [DEBUG] [__root] SetHdrOff: 4480 for pConn: 0x8c4750 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] Conn 0x8c5910 set pHash: 0x8bb690 2019-10-31 15:27:46.637 [DEBUG] [__root] ShmSlice: [/dev/shm/lsmcd/data3.shm]. 2019-10-31 15:27:46.637 [DEBUG] [__root] SetHdrOff: 4480 for pConn: 0x8c5910 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] Conn 0x8c6ad0 set pHash: 0x8bbd10 2019-10-31 15:27:46.637 [DEBUG] [__root] ShmSlice: [/dev/shm/lsmcd/data4.shm]. 2019-10-31 15:27:46.637 [DEBUG] [__root] SetHdrOff: 4480 for pConn: 0x8c6ad0 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] Conn 0x8c7c90 set pHash: 0x8bc390 2019-10-31 15:27:46.637 [DEBUG] [__root] ShmSlice: [/dev/shm/lsmcd/data5.shm]. 2019-10-31 15:27:46.637 [DEBUG] [__root] SetHdrOff: 4480 for pConn: 0x8c7c90 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] Conn 0x8c8e50 set pHash: 0x8bca10 2019-10-31 15:27:46.637 [DEBUG] [__root] ShmSlice: [/dev/shm/lsmcd/data6.shm]. 2019-10-31 15:27:46.637 [DEBUG] [__root] SetHdrOff: 4480 for pConn: 0x8c8e50 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] HashByUser: getHash default 2019-10-31 15:27:46.637 [DEBUG] [__root] Conn 0x8ca010 set pHash: 0x8bd090 2019-10-31 15:27:46.637 [DEBUG] [__root] ShmSlice: [/dev/shm/lsmcd/data7.shm]. 2019-10-31 15:27:46.637 [DEBUG] [__root] SetHdrOff: 4480 for pConn: 0x8ca010 2019-10-31 15:27:46.637 [ERROR] [__root] Memcache Listener failed to start Thanks! From: Bob Perper <notifications@github.com> Sent: Thursday, October 31, 2019 3:18 PM To: litespeedtech/lsmcd‏ <lsmcd@noreply.github.com> Cc: drorzeno‏ <drorzeno@gmail.com>; Author‏ <author@noreply.github.com> Subject: Re: [litespeedtech/lsmcd] lscmd not started (#10) 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 rperper@litespeedtech.com <mailto:rperper@litespeedtech.com> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#10?email_source=notifications&email_token=AIP5HPEC5MHCIMF552OF4M3QRLLILA5CNFSM4JHFS75KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECXXMFY#issuecomment-548369943> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIP5HPAQAJJLHHCKTHIOPATQRLLILANCNFSM4JHFS75A> . <https://github.com/notifications/beacon/AIP5HPE47PZYU3TDLB6P2PTQRLLILA5CNFSM4JHFS75KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECXXMFY.gif>

[rperper]

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
rperper@litespeedtech.com

[collie-script]

Thanks. I set the Cached.DataByUser to false. I tried to kill the process lsmcd but Its always start again and the service is failed, see picture - You have any idea? From: Bob Perper <notifications@github.com> Sent: Thursday, October 31, 2019 4:00 PM To: litespeedtech/lsmcd‏ <lsmcd@noreply.github.com> Cc: drorzeno‏ <drorzeno@gmail.com>; Author‏ <author@noreply.github.com> Subject: Re: [litespeedtech/lsmcd] lscmd not started (#10) 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 rperper@litespeedtech.com <mailto:rperper@litespeedtech.com> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#10?email_source=notifications&email_token=AIP5HPHAAX7XZTAIDNUKBSTQRLQFZA5CNFSM4JHFS75KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECX37RI#issuecomment-548388805> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIP5HPDMSQ6AGYF6TXL3CALQRLQFZANCNFSM4JHFS75A> . <https://github.com/notifications/beacon/AIP5HPHB5EI6CSJNU637W5LQRLQFZA5CNFSM4JHFS75KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECX37RI.gif>

[rperper]

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
rperper@litespeedtech.com

[rperper]

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

Thanks,
Bob Perper
rperper@litespeedtech.com

[collie-script]

Thanks. It's not working I can't stop the process. I think I need to do restart for the VPS so I will do it in the night and let you know. Thank you very much! From: Bob Perper <notifications@github.com> Sent: Thursday, October 31, 2019 4:21 PM To: litespeedtech/lsmcd‏ <lsmcd@noreply.github.com> Cc: drorzeno‏ <drorzeno@gmail.com>; Author‏ <author@noreply.github.com> Subject: Re: [litespeedtech/lsmcd] lscmd not started (#10) Another thought might be to stop it using systemctl: systemctl stop lsmcd. Thanks, Bob Perper rperper@litespeedtech.com <mailto:rperper@litespeedtech.com> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#10?email_source=notifications&email_token=AIP5HPEML4UUMWUTX5ON7JLQRLSUJA5CNFSM4JHFS75KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECX6LPY#issuecomment-548398527> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIP5HPBVRCR24CHQHP44O3LQRLSUJANCNFSM4JHFS75A> . <https://github.com/notifications/beacon/AIP5HPEPBLTML2X327OQ3TTQRLSUJA5CNFSM4JHFS75KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECX6LPY.gif>

[rperper]

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
rperper@litespeedtech.com

[collie-script]

Thank you very much! You help me and I solved the problem with the command "systemctl kill lsmcd" And all working. Thanks! From: Bob Perper <notifications@github.com> Sent: Thursday, October 31, 2019 5:40 PM To: litespeedtech/lsmcd‏ <lsmcd@noreply.github.com> Cc: drorzeno‏ <drorzeno@gmail.com>; Author‏ <author@noreply.github.com> Subject: Re: [litespeedtech/lsmcd] lscmd not started (#10) 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 rperper@litespeedtech.com <mailto:rperper@litespeedtech.com> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#10?email_source=notifications&email_token=AIP5HPHUMSAVABHI7RFG6Q3QRL35PA5CNFSM4JHFS75KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECYHSNI#issuecomment-548436277> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIP5HPD6W2DDMKVHHANSGNDQRL35PANCNFSM4JHFS75A> . <https://github.com/notifications/beacon/AIP5HPBXFIHA6FWSNOH4HFTQRL35PA5CNFSM4JHFS75KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECYHSNI.gif>