• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Latest Update #17 killed the Redis Server in Docker or Docker itself

19patrick

New Pleskian
EDIT: Plesk in running in Debian 8.7

The latest update on saturday #17 killed my redis server in docker. This was shown in the logfile:

"1:M 25 Feb 07:32:09.174 * Background saving terminated with success
1:signal-handler (1488023745) Received SIGTERM scheduling shutdown...
1:M 25 Feb 11:55:45.716 # User requested shutdown...
1:M 25 Feb 11:55:45.716 * Saving the final RDB snapshot before exiting.
1:M 25 Feb 11:55:45.801 * DB saved on disk
1:M 25 Feb 11:55:45.801 # Redis is now ready to exit, bye bye...
.
.
.
1:M 25 Feb 11:55:46.819 # Server started, Redis version 3.2.7
1:M 25 Feb 11:55:46.819 * DB loaded from disk: 0.000 seconds
1:M 25 Feb 11:55:46.819 * The server is now ready to accept connections on port 6379
"

The service didn't restartet after it was stopped so that a shop on the server had an error and nobody could reach the shop for a very long time. I restartet the redis server manually at 11:55. In plesk the redis server was shown as startet.

Due to that problem I had to deactivate the automatic update routine from plesk.

Here is the error from my JTL Shop:

"Fatal error: Uncaught RedisException: Failed to AUTH connection in /var/www/vhosts/xyz.com/httpdocs/classes/CachingMethods/class.cachingMethod.redis.php:73 Stack trace: #0 /var/www/vhosts/xyz.com/httpdocs/classes/CachingMethods/class.cachingMethod.redis.php(73): Redis->select(0) #1 /var/www/vhosts/xyz.com/httpdocs/classes/CachingMethods/class.cachingMethod.redis.php(34): cache_redis->setRedis('localhost', 6379, NULL, 0, false) #2 /var/www/vhosts/xyz.com/httpdocs/classes/CachingMethods/class.cachingMethod.redis.php(52): cache_redis->__construct(Array) #3 /var/www/vhosts/xyz.com/httpdocs/classes/class.JTL-Shop.JTLCache.php(387): cache_redis::getInstance(Array) #4 /var/www/vhosts/xyz.com/httpdocs/classes/class.JTL-Shop.JTLCache.php(478): JTLCache->setCache('redis') #5 /var/www/vhosts/xyz.com/httpdocs/classes/class.JTL-Shop.JTLCache.php(464): JTLCache->init() #6 /var/www/vhosts/xyz.com/httpdocs/admin/includes/admininclude.php(34): JTLCache->setJtlCacheConfig() #7 /var/www/vhosts/xyz in /var/www/vhosts/xyz.com/httpdocs/classes/CachingMethods/class.cachingMethod.redis.php on line 73"

So what went wrong?
 
Last edited:
Redis failed again with the same error in the shop.

EDIT: Redis Log: 1:signal-handler (1488463509) Received SIGTERM scheduling shutdown...
 
Back
Top