-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lsmcd systemd stops randomly #26
Comments
Hi, Thanks, Bob Perper |
hello @rperper thanks please see partial output from cat /tmp/lsmcd.log
|
Ok, I see what's happening here. When LSMCD sees a problem in its database, it rebuilds it and restarts the application. This is hardly perfect behavior (lots of obnoxious messages), but it is normal and expected. You can ignore them unless you are seeing a failure in availability, and that does not appear to be happening here. Thanks, Bob |
Hello and thanks unfortunately it stops, but I have to manually issue a systemd restart of the service, otherwise it's not restarting itself |
Hi, You can force the condition by sending a USR1 signal to the process. Let me know if that does what I expect or something else. If something else, then we'll need you to open a Litespeed ticket and we'll have to have root access to your system. Reference that you'd like Bob Perper assigned to the problem. Thanks, Bob |
Hi, Bob |
perfect, i'll let you know! |
well it seems that i'm struggling with another problem now, i don't know if it's related to this
but as soon as I turn on memcached, from the Wordpress plugin (LiteSpeed Cache Settings -> Cache -> Object -> Turn on cache settings), almost every page loaded on my website, returns a PHP fatal error. I collected a trace from OpenListeSpeed web server log
|
Hmmm, shouldn't be related to the RemainAfterExit. This may be something
bad left over in the lsmcd cache.
Try deleting the lsmcd by entering (with lsmcd down):
```
sudo rm -rf /dev/shm/lsmcd
```
Then start the lsmcd service and wordpress and see if it works then.
Thanks,
Bob
…On Thu, Mar 10, 2022 at 10:43 AM Dark345 ***@***.***> wrote:
well it seems that i'm struggling with another problem now, i don't know
if it's related to this
RemainAfterExit=yes
but as soon as I turn on memcached, from the Wordpress plugin (LiteSpeed
Cache Settings -> Cache -> Object -> Turn on cache settings), almost every
page loaded on my website, returns a PHP fatal error. I collected a trace
from OpenListeSpeed web server log
[506] [192.168.250.253:3969-1#mydomain:lsapi] [STDERR] PHP Fatal error: Uncaught Error: Cannot use object of type stdClass as array in /usr/local/lsws/sites/mydomain/html/wp-includes/meta.php:657
Stack trace:
#0 /usr/local/lsws/sites/mydomain/html/wp-includes/meta.php(572): get_metadata_raw()
#1 /usr/local/lsws/sites/mydomain/html/wp-includes/post.php(2505): get_metadata()
#2 /usr/local/lsws/sites/mydomain/html/wp-content/plugins/elementor/core/documents-manager.php(210): get_post_meta()
#3 /usr/local/lsws/sites/mydomain/html/wp-content/plugins/elementor/core/files/css/post.php(195): Elementor\Core\Documents_Manager->get()
#4 /usr/local/lsws/sites/mydomain/html/wp-content/plugins/jet-theme-core/includes/locations.php(115): Elementor\Core\Files\CSS\Post->enqueue()
#5 /usr/local/lsws/sites/mydomain/html/wp-includes/class-wp-hook.php(307): Jet_Theme_Core_Locations->enqueue_styles()
#6 /usr/local/lsws/sites/mydomain/html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
#7 /usr/local/lsws/sites/mydomain/html/wp-includes/plugin.php(474): WP_Hook->do_action()
#8 /usr/local/lsws/sites/mydomain/html/wp-includes/script-loader.php(2105): do_action()
#9 /usr/local/lsws/sites/mydomain/html/wp-includes/class-wp-hook.php(307): wp_enqueue_scripts()
#10 /usr/local/lsws/sites/mydomain/html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
#11 /usr/local/lsws/sites/mydomain/html/wp-includes/plugin.php(474): WP_Hook->do_action()
#12 /usr/local/lsws/sites/mydomain/html/wp-includes/general-template.php(3042): do_action()
#13 /usr/local/lsws/sites/mydomain/html/wp-content/themes/monstroid2-child/header.php(19): wp_head()
#14 /usr/local/lsws/sites/mydomain/html/wp-includes/template.php(770): require_once('...')
#15 /usr/local/lsws/sites/mydomain/html/wp-includes/template.php(716): load_template()
#16 /usr/local/lsws/sites/mydomain/html/wp-includes/general-template.php(48): locate_template()
#17 /usr/local/lsws/sites/www.hwlegn
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFSMUB5OQG326BLTT6KHWTTU7IKDZANCNFSM5PYZURMQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Bob Perper
***@***.***
|
hello unfortunately just tried many times, deleting cache and restarting the service |
Can you put in the lsmcd.log so we can see if there are any issues there? Bob |
unfortunately not
it's the only thing logged. Edit: I switched back from PHP 8.1 to PHP 7.4. Same problem |
I'm going to pass this over to Abe who should be able to help you on the PHP, WP Cache side. |
Hi @Dark345 Please refer to this: https://docs.litespeedtech.com/lscache/lscwp/cache/#method Look into the "LSMCD Warning" part. |
hello, perfect. what's the consequence of adding users and user_meta to do not cache group? |
Hello @Dark345 As the option name "Do Not Cache Group" states, once the group is added into this textbox, items/objects under this cache group will not be cached into object cache. About wp cache group, you can refer to this page: https://developer.wordpress.org/reference/classes/wp_object_cache/ |
@Dark345 Have you got the solution? I have the same issue, lsmcd keep on stopping without any error in lsmcd.log. |
Hello yes! solved by applying this suggested parameter. It's indeed as described: When LSMCD sees a problem in its database, it rebuilds it and restarts the application. and It appears that systemd takes down the process if it comes up again in a separate pid |
So are you ok? |
yea, issue lsmcd systemd stops randomly is solved. |
Funny you should mention that. We've been doing some preliminary testing that seems to address the WP Cache problem by installing the libmemcached-awesome library and completely replacing the existing libmemcached library with it. It seems to have fixed the problem. If you don't mind giving something like that a try, we have an early cheat-sheet of instructions for it. We'd love to hear your experiences with it. Check out: https://docs.google.com/document/d/1GNZ3EOcOeBqYS19rl5rnGoh8I9N1BFU3htSn_IPaavg/edit?usp=sharing Bob |
Hey, is this to fix this?
|
Yes it is. |
"RemainAfterExit=yes" is already existed in /etc/systemd/system/lsmcd.service... |
here you have:
|
My file: Latest version of lsmcd `[Unit] [Service] KillMode=none #do not want to be limited in anyway [Install] |
RemainAfterExit=yes should be sufficient. What OS and version are you running? |
My OS is Ubuntu 20.04 LTS. |
Please verify that lsmcd is actually not running any more. The service will show stopped, but there will be a PID running that you can see with |
Ya, I have start it again for a few minutes ago. Now I will wait for the stopped event and update information here. |
So lsmcd is running right? |
If lsmcd's still got a pid running, then the sock file is fine. |
Yes! But the very strange issue is: after 2-3 hours later
|
If lsmcd still has an active pid, then the connection failure is something else. What you should do is open a ticket through LiteSpeed on that and we can better help you that way. |
Yes, thanks so much. I think when the issue happen (after 2-3 hours later), I will update info here first, if can not find solution I will open a tickets in Litespeed Enterprise account. |
hello just trying with the new libmemcached-awesome enabled SASL and multi-user
cleared DB: rm -R /etc/sasllsmcd and re-created users:
upgraded litespeed WP plugin to 5.2 here the log from journal:
and from tail -f /tmp/lsmcd.log: just filled with these lines:
WP plugin status: Memcached Extension: Enabled |
Certainly we'd expect the connection test to fail with SASL not working. First verify that you've put your updated passwords into the WP Cache configuration for your users. When you're sure your configuration is right, please open a ticket with LiteSpeed and reference Bob and we can then send detailed information back and forth. Bob |
okay i'll close this |
That's ok. Put in LSMCD ref Bob in the subject and it will get to me. But it makes it so much easier with a ticket. You can include the lsmcd.log file as well. Thanks, |
Hello
my lsmcd istance stops randomly.
my OS is Debian 11 and I followed this to install LSMCD
https://openlitespeed.org/kb/litespeed-memcached/
Here an extract from
my systemd.service
thanks, any help is appreciated!
The text was updated successfully, but these errors were encountered: