Release Log 2022-11-14 18:12:08 LiteSpeed Memcached release log is frequently updated with new features and bug fixes. Join the "LiteSpeed Edge Users" Google Group for cutting-edge build notifications.

LiteSpeed Memcached
Release Log

Join the "LiteSpeed Edge Users" Google Group for cutting-edge build notifications.

LiteSpeed Memcached is frequently updated with new features and bug fixes.

LS Memcached 1.4.33(11-14-2022) Update & Bugfix

  • UPDATE cPanel interface uses the newest lsmcd icon.
  • BUG FIX Detect when the SHM reports file size: 0 and rebuilds the database.

LS Memcached 1.4.31(03-07-2022) Bugfix

  • BUG FIX Fix bug where systemd will take down LSMCD when it tries to recover after a crash. This will make systemd's status misleading - use `ps -ef|grep lsmcd` as the method to determine if lsmcd is running.

LS Memcached 1.4.30(09-01-2021) Bugfix

  • BUG FIX Address crashes caused by incorrect file size in hash table shared memory.

LS Memcached 1.4.29(09-01-2021) New Features & Bugfixes

  • NEW FEATURE Report PID rather than user in log.
  • NEW FEATURE A debug validation option has been added (DBG.VALIDATE=TRUE) - only usable in -d mode.
  • NEW FEATURE can now specify the server IP:PORT with the --r parameter.
  • NEW FEATURE You can specify a single worker by setting CachedProcCnt=0.
  • BUG FIX During rehash, turn assertion into rebuilds avoiding crashes.
  • BUG FIX Fixed single worker bugs in listening.

LS Memcached 1.4.28(08-09-2021) Bugfixes

  • BUG FIX Fixed a few small bugs with NULL pointer references.
  • BUG FIX Added additional code to detect data corruption.

LS Memcached 1.4.27(08-02-2021) Bugfix

  • BUG FIX Ignore a SIGPIPE rather than process it.

LS Memcached 1.4.26(07-08-2021) Improvement & Bugfixes

  • IMPROVEMENT On the detection of a corrupt database size, it is rebuilt.
  • BUG FIX A response is generated for a GETKQ.
  • BUG FIX Response avoids timeouts for SET.

LS Memcached 1.4.25(06-29-2021) Improvements & Bugfixes

  • IMPROVEMENT USR1 signal can be used to restart the service.
  • IMPROVEMENT On the detection of corrupt shared memory, it is rebuilt.
  • BUG FIX Several unnecessary assertions removed.
  • BUG FIX Detect NULL in chkMemSz.
  • BUG FIX Removed assertion in ls_atomic_spin_pidwait.
  • BUG FIX Fixed a regression introduced in 1.4.24 where the database size will not be increased correctly.

LS Memcached 1.4.24(06-23-2021) Improvement & Bugfix

  • IMPROVEMENT Add address sanitizer to the debug build. Doc has been updated for this.
  • BUG FIX A number of significant fixes which should reduce crashes.

LS Memcached 1.4.23(06-17-2021) Bugfix

  • BUG FIX No longer report incorrect messages "Received length < header minimum".

LS Memcached 1.4.22(06-01-2021) Bugfixes

  • BUG FIX Binary 0 terminate SASL mechanism which addresses an issue with PHP unable to authenticate.
  • BUG FIX Fix a crash if there's a memory shortage in the hash map.
  • BUG FIX Reduce the opportunity for a crash in LsShmPool.
  • BUG FIX Reduce the opportunity for crashes in LsShmTidMgr.
  • BUG FIX Reduce the opportunity for crashes in LsShmHash.

LS Memcached 1.4.21(05-25-2021) Improvement

  • IMPROVEMENT Add a log entry when the program crashes.

LS Memcached 1.4.20(04-13-2021) Bugfixes

  • BUG FIX Only the oldest core dump will be preserved if you have cores written by pid enabled.
  • BUG FIX NULL ptr in find should no longer crash.
  • BUG FIX Exceeding the buffer size should not cause a crash in tracing.
  • BUG FIX Avoid using NULL freelist bot size.
  • BUG FIX Handle NULL pointer in an iterator allocation.
  • BUG FIX Avoid additional NULL compares during hash check.
  • BUG FIX Address NULL pointer in TidMgr.
  • BUG FIX Change a number of assertions to tests.

LS Memcached 1.4.19(03-26-2021) Improvement and Bugfix

  • IMPROVEMENT Core dumps will not write to the /tmp/lsmcd directory.
  • BUG FIX Reverted incorrect bug fix in single receive.

LS Memcached 1.4.17(03-16-2021) Improvement and Bugfix

  • IMPROVEMENT Log messages closer to the time they occur.
  • BUG FIX Get rid of 'FATAL ERROR alloc2 cross large page boundary' messages.

LS Memcached 1.4.16(03-03-2021) Improvements

  • IMPROVEMENT Improve the text on a few error messages.
  • IMPROVEMENT Remove unnecessary code in the SASL module.
  • IMPROVEMENT Support python3 in as bmemcached no longer supports python2.

LS Memcached 1.4.15(02-08-2021) Improvements and Bugfixes

  • IMPROVEMENT Reduced the severity of a number of messages from INFO to DEBUG cleaning up the log as well as adding additional debugging messages to aid in future issues.
  • BUG FIX Missing response for binary GETQ and GETKQ can cause long delays in LSCACHE_WP, fixed.
  • BUG FIX Correctly switch from binary to text mode and back in persistent connections.

LS Memcached 1.4.14(11-12-2020) Bugfixes

  • BUG FIX Correctly support 0 to disable Cached.ValMaxSz for maximum data size validation.
  • BUG FIX Correctly fold machine name to lower case to match SASL machine name storage.

LS Memcached 1.4.13(09-14-2020) Bug Fix

  • BUG FIX Cleaned up lsmcdctrl so it does not run the program usleep and works correctly

LiteSpeed Memcached 1.4.12(08-25-2019) Bug Fix

  • BUG FIX Fixed hash table bug.

LS Memcached 1.4.11(11-26-2019) Bug Fix

  • BUG FIX `make install` leaves your existing installation and does not step on your configuration.

LS Memcached 1.4.10(11-26-2019) Improvements and Note

  • IMPROVEMENT Support ASCII accesses using the anonymous user if the Cached.Anonymous=True
  • IMPROVEMENT Cleaned up code to compile without warnings with the newer gcc compilers.
  • NOTE This version is compiled in a newer development environment. If you have problems recompiling the software, run `autoreconf --install --force` to rebuild the environment.

LS Memcached 1.4.9(11-07-2019) Improvements

  • IMPROVEMENT Added new configuration option: Cached.SaslDB. You can set it to an independent SASL database which you can control with the regular SASL programs (saslpasswd2 and sasldblistusers2) with the -f option to specify the database name. You can then set the owner to be the LSMCD user and give this user the sole permission to access the file. Lets /etc/sasldb2 be available for other program's use.
  • IMPROVEMENT with no parameters will set one value and finish rather than fail attempting to perform a full stress test with SASL.

LS Memcached 1.4.8(11-05-2019) Tuning

  • TUNING Turned off SASL in the default user configuration file.

LS Memcached 1.4.7(10-22-2019) Bug Fix

  • BUG FIX Fixed a leakage between users when SASL user separation is enabled.

LS Memcached 1.4.6(10-10-2019) Improvement and Bug Fix

  • IMPROVEMENT Added a python stress test program (
  • BUG FIX Don't put a bad command line into the system list.

LS Memcached 1.4.5(08-06-2019) Bugfix

  • BUG FIX Fixed default node.conf file (from v1.4.4) which was broken by incomplete merge.

LS Memcached 1.4.4(07-10-2019) Bugfix

  • BUG FIX Updated github to the correct SASL updated version.

LS Memcached 1.4.3(07-08-2019) Bugfix

  • BUG FIX Report correct version number when lsmcd is run with -v

LS Memcached 1.4.2(07-03-2019) Improvement

  • IMPROVEMENT Better error messages when there are config file problems.

LS Memcached 1.4.1(05-07-2019) Improvement

  • IMPROVEMENT Log entry with version number and include VERSION.txt file.

LS Memcached 1.4.0(03-01-2019) Improvement and Bug Fix

  • IMPROVEMENT Better logging.
  • BUG FIX Tolerate incorrect command line parameters to lsmcd.

LS Memcached 1.3.0(01-21-2019) Improvement

  • IMPROVEMENT Support for systemd services.

LS Memcached 1.0.0(02-10-2016) Initial Release

Privacy Policy

Privacy Policy

LiteSpeed Technologies, Inc. (aka “LiteSpeed”) is committed to protecting your privacy. This policy ("Privacy Policy" or "Policy") explains our practices for our site, ("Site"). You can visit most pages of the Site without giving us any information about yourself, but sometimes we do need information to provide services that you request. By using this Site or any products or services provided through the Site, you expressly consent to the use and disclosure of information as described in this Privacy Policy.

LiteSpeed reserves the right to revise, modify, add, or remove provisions to this Privacy Policy at any time. If we make changes to this Privacy Policy, we will update the Effective Date to note the date of such changes. LiteSpeed encourages you to review this Privacy Policy periodically for any changes. IF YOU DO NOT AGREE WITH ANY OF THE TERMS BELOW, YOU SHOULD NOT USE THIS SITE OR THE PRODUCTS OR SERVICES OFFERED BY LITESPEED TECHNOLOGIES AT THIS SITE.

Collection of Information

Personal Information.

LiteSpeed will ask you for certain “Personal Information” when you complete registration or product information request forms on the Site, including but not limited to your name, address, telephone number, email address, and credit card information. You can always choose not to provide us with the requested information, however, you may not be able to complete the transaction or use our products or services if you do not provide the information requested.

Non-Personal Information.

LiteSpeed may collect non-personally identifiable information from you such as the type of browser you use, your operating system, the screen resolution of your browser, your ISP, your IP address, which pages you view on the Site and the time and duration of your visits to the Site (collectively, “Non-Personal Information”). LiteSpeed may associate Non-Personal Information with Personal Information if you register with the Site.

User Communications.

If you communicate with us, we may collect information relating to that communication whether it takes the form of email, fax, letter, forum posting, blog comments, testimonials or any other form of communication between you and LiteSpeed or Submitted by you to the Site (collectively, “User Communications”).

Server Information.

If you use one of our software products such as LiteSpeed Web Server or LiteSpeed Web ADC, we may collect certain information concerning such software and concerning the server upon which the software operates. This information includes: (a) the licensed or unlicensed status of the software; (b) the source from which the license for the software was obtained (i.e., LiteSpeed or a LiteSpeed affiliate); or (c) information about the server upon which the software is installed including (i) the public IP address, (ii) the operating system and (iii) the use of any virtualization technologies on such server ((a) through (c) collectively, “Server Information”). Additionally, “Server Information” may also include information collected from you by LiteSpeed in the event that you request technical support services including without limitation, IP addresses, usernames, and passwords necessary to login to SSH, the root directory of the server upon which you installed the LiteSpeed software and any affected accounts including email accounts, control panel accounts, MySQL accounts, CMS accounts and other accounts.

Use and Storage of Collected Information

LiteSpeed may use Personal Information to create and authenticate your account, to respond to your requests, to provide you with customer and technical support, or to provide you with information regarding our products, services, partners, and company. You may update your Personal Information with us at any time, but we may maintain records of any Personal Information you disclose to us indefinitely, unless otherwise requested as outlined below.

We may use User Communications in the same ways we use Personal Information. If you communicate with us for a particular purpose, we may use your User Communications for that purpose. For example, if you contact us for technical support, we may use your communications to provide technical support to you. We may maintain records of User Communications you transmit to us indefinitely, unless otherwise requested as outlined below.

LiteSpeed may use Non-Personal Information to maintain, evaluate, improve and provide our Site, the Services and any other LiteSpeed products and services. We may retain Non-Personal Information indefinitely.

We may use Server Information to provide you with technical support services and to maintain, evaluate, improve and provide LiteSpeed products and services. We may also use such information to investigate unlicensed (and therefore unauthorized) uses of our software. LiteSpeed may maintain Server Information indefinitely, with the exception of usernames, passwords, and other login information given in connection with support service requests. Such login information will be purged when the ticket is closed.

Disclosure of Collected Information

LiteSpeed will only disclose Personal Information to third parties if acting under a good faith belief that such action is necessary, including but not limited to: (a) to resolve disputes, investigate problems, or comply with laws or regulations; (b) to enforce our Terms of Service; (c) to protect and defend the rights, property, or safety of our company or our users; or (d) in the event of a merger, acquisition or sale of all or substantially all LiteSpeed assets. Other than this limited activity, we do not share, sell, or rent any personal information to third parties.

You will receive notice in the form of modifications to this Policy when information about you might go to third parties other than as described in this Policy, and you always have the opportunity to contact us as set forth below if you do not wish your information to go to third parties.

LiteSpeed cannot be responsible for protecting your information if you share such information in publicly available sections of the Site such as the user forums, blog comments, or testimonials section. You should use your own judgment in disclosing this information on the Site.

Use of Cookies

“Cookies” are small pieces of information that your browser stores on your computer on behalf of a website that you have visited. Cookies may be used in order to complete transactions on our site. You can always choose not to accept cookies with the settings of your web browser, however, you may not be able to complete these transactions if you do not accept cookies.

Security of Personal Information

We use reasonable security methods to protect your personal information from unauthorized access, use or disclosure. No data transmission over the Internet or any wireless network can be guaranteed to be perfectly secure. While we try to protect your personal information, we cannot guarantee the security of any information you transmit to us, and you do so at your own risk.

LiteSpeed uses industry-standard SSL-encryption to protect sensitive data.

In the event that LiteSpeed becomes aware of a security breach, unauthorized disclosure or inadvertent disclosure concerning your information, you agree that LiteSpeed may notify you of such an event using the Personal Information previously provided.

You are responsible for maintaining your account’s security.

GDPR Statement

LiteSpeed Technologies values your users’ privacy. Although our software does not directly collect any personally identifiable information from visitors to your site, LiteSpeed may still be considered a data processor, as user information may be temporarily cached and/or logged, as outlined in this document.


LiteSpeed Web Server, OpenLiteSpeed, LiteSpeed Web ADC, and related software may record IP addresses as a part of normal logging. An access log and an error log may record visitor IP addresses and URL visited. The logs are stored locally on the system where LiteSpeed server software is installed and are not transferred to or accessed by LiteSpeed employees in any way, except as necessary in providing routine technical support if you request it. This logging may be turned off through configuration. It is up to individual server administrators to come up with their own schedule for removing such logs from the file system.

Cache Solutions

Our cache plugins potentially store a duplicate copy of every web page on display on your site. The pages are stored locally on the system where LiteSpeed server software is installed and are not transferred to or accessed by LiteSpeed employees in any way, except as necessary in providing routine technical support if you request it. All cache files are temporary, and may easily be purged before their natural expiration, if necessary, via a Purge All command. It is up to individual site administrators to come up with their own cache expiration rules.

LSCache for WordPress

In addition to caching, our WordPress plugin has an Image Optimization feature. When optimization is requested, images are transmitted to a remote LiteSpeed server, processed, and then transmitted back for use on your site. LiteSpeed keeps copies of optimized images for 7 days (in case of network stability issues) and then permanently deletes them.

Similarly, the WordPress plugin has a Reporting feature whereby a site owner can transmit an environment report to our server so that we may better provide technical support.

Neither of these features collects any visitor data. Only server and site data is involved.

Support Services

Sometimes, when you request technical support, LiteSpeed may ask for login credentials to various areas of your site. You may refuse to share such credentials, however refusal may impact LiteSpeed’s ability to provide the requested support services.

Upon completion of a support ticket, LiteSpeed immediately deletes all login credentials you may have shared.

Any user data encountered by LiteSpeed is kept strictly confidential. We never provide your support ticket information to any third party without your explicit consent.

Contact Us

If you would like to update information that you have voluntarily provided to us, stop receiving information from us, or exercise any of the rights granted to you under Privacy Laws, including the EU’s General Data Protection Regulation, please e-mail