lscache_prestashop Cache for desktop and mobile

Hi everyone,

cache for desktop/tablet/mobile is the same. For any device - Crawler always chooses desktop version to cache.

Prestashop 1.7.8.0, PHP 7.4

Oct 27 '21 21:10 Matysek666

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]

Oct 31 '19 12:10 rperper

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 [email protected] Sent: Thursday, October 31, 2019 2:53 PM To: litespeedtech/lsmcd‏ [email protected] Cc: drorzeno‏ [email protected]; Author‏ [email protected] 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 [email protected] mailto:[email protected]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/litespeedtech/lsmcd/issues/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

Oct 31 '19 13:10 drorzeno

Another thing, Because the lsmcd not started there no lsmcd.log file.

From: [email protected] [email protected] Sent: Thursday, October 31, 2019 3:06 PM To: 'litespeedtech/lsmcd'‏ [email protected]; 'litespeedtech/lsmcd'‏ [email protected] Cc: 'Author'‏ [email protected] 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 <[email protected] mailto:[email protected] > Sent: Thursday, October 31, 2019 2:53 PM To: litespeedtech/lsmcd‏ <[email protected] mailto:[email protected] > Cc: drorzeno‏ <[email protected] mailto:[email protected] >; Author‏ <[email protected] mailto:[email protected] > 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 [email protected] mailto:[email protected]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/litespeedtech/lsmcd/issues/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

Oct 31 '19 13:10 drorzeno

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]

Oct 31 '19 13:10 rperper

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] 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