"NOSCRIPT No matching script. Please use EVAL" error while trying to acquire lock in redis #2350

urbaman · 2025-01-31T00:12:30Z

urbaman
Jan 31, 2025

Shlink version

shlinkio/shlink:latest

PHP version

provided

How do you serve Shlink

Docker image

Database engine

PostgreSQL

Database version

16.8

Summary

Getting Redis errors after a crash:

  ERR    [Predis\Response\ServerException]
  ERR    at /etc/shlink/vendor/predis/predis/src/Client.php:416
  ERR   Predis\Client->onErrorResponse() at /etc/shlink/vendor/predis/predis/src/Client.php:385
  ERR   Predis\Client->executeCommand() at /etc/shlink/vendor/predis/predis/src/Client.php:335
  ERR   Predis\Client->__call() at /etc/shlink/vendor/symfony/lock/Store/RedisStore.php:287
  ERR    [Predis\Response\ServerException]
  ERR    at /etc/shlink/vendor/predis/predis/src/Client.php:416
  ERR   Predis\Client->onErrorResponse() at /etc/shlink/vendor/predis/predis/src/Client.php:385
  ERR   Predis\Client->executeCommand() at /etc/shlink/vendor/predis/predis/src/Client.php:335
  ERR   Predis\Client->__call() at /etc/shlink/vendor/symfony/lock/Store/RedisStore.php:287

Redis is not showing any problems:

1:C 30 Jan 2025 22:55:14.862 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 30 Jan 2025 22:55:14.862 * Redis version=7.4.2, bits=64, commit=00000000, modified=1, pid=1, just started
1:C 30 Jan 2025 22:55:14.862 * Configuration loaded
1:M 30 Jan 2025 22:55:14.863 * monotonic clock: POSIX clock_gettime
1:M 30 Jan 2025 22:55:14.865 * Running mode=standalone, port=6379.
1:M 30 Jan 2025 22:55:14.866 * Server initialized
1:M 30 Jan 2025 22:55:14.931 * Reading RDB base file on AOF loading...
1:M 30 Jan 2025 22:55:14.931 * Loading RDB produced by version 7.4.2
1:M 30 Jan 2025 22:55:14.931 * RDB age 9730 seconds
1:M 30 Jan 2025 22:55:14.931 * RDB memory usage when created 23.81 Mb
1:M 30 Jan 2025 22:55:14.931 * RDB is base AOF
1:M 30 Jan 2025 22:55:15.436 * Done loading RDB, keys loaded: 18508, keys expired: 0.
1:M 30 Jan 2025 22:55:15.437 * DB loaded from base file appendonly.aof.955.base.rdb: 0.506 seconds
1:M 30 Jan 2025 22:55:17.433 * DB loaded from incr file appendonly.aof.955.incr.aof: 1.996 seconds
1:M 30 Jan 2025 22:55:17.433 * DB loaded from append only file: 2.565 seconds
1:M 30 Jan 2025 22:55:17.434 * Opening AOF incr file appendonly.aof.955.incr.aof on server start
1:M 30 Jan 2025 22:55:17.434 * Ready to accept connections tcp
1:M 30 Jan 2025 23:10:07.544 * Starting automatic rewriting of AOF on 505% growth
1:M 30 Jan 2025 23:10:07.548 * Creating AOF incr file appendonly.aof.956.incr.aof on background rewrite
1:M 30 Jan 2025 23:10:07.549 * Background append only file rewriting started by pid 3294
3294:C 30 Jan 2025 23:10:08.331 * Successfully created the temporary AOF base file temp-rewriteaof-bg-3294.aof
3294:C 30 Jan 2025 23:10:08.331 * Fork CoW for AOF rewrite: current 3 MB, peak 3 MB, average 2 MB
1:M 30 Jan 2025 23:10:08.335 * Background AOF rewrite terminated with success
1:M 30 Jan 2025 23:10:08.336 * Successfully renamed the temporary AOF base file temp-rewriteaof-bg-3294.aof into appendonly.aof.956.base.rdb
1:M 30 Jan 2025 23:10:08.340 * Removing the history file appendonly.aof.955.incr.aof in the background
1:M 30 Jan 2025 23:10:08.342 * Removing the history file appendonly.aof.955.base.rdb in the background
1:M 30 Jan 2025 23:10:08.398 * Background AOF rewrite finished successfully

How to properly debug/solve? Already SHELL_VERBOSITY=3

Answered by acelaya

Feb 4, 2025

Issue reported to upstream project with minimal reproduction steps symfony/symfony#59686

Issue to track it here #2354

View full answer

acelaya · 2025-01-31T07:04:32Z

acelaya
Jan 31, 2025
Maintainer

Where do you get the error? While doing what exactly? Is it causing a disruption in the service? What redis version are you using?

Also, that seems like an incomplete exception trace, but it's lacking the actual error message.

0 replies

urbaman · 2025-01-31T07:40:59Z

urbaman
Jan 31, 2025
Author

Hi,

I had a self-hosted shlink container on a kubernetes cluster, working perfectly.
After a crash, the pod does not come up anymore. Here the full log:

Initializing database if needed... [Running "/usr/local/bin/php bin/cli db:create"]   RUN  '/usr/local/bin/php' 'bin/cli' 'db:create'
  ERR  [2025-01-31T07:32:27.398150+00:00] [-] Shlink.NOTICE - Failed to acquire the "Shlink:db:create" lock.
  ERR
  ERR  In Lock.php line 116:
  ERR
  ERR    [Symfony\Component\Lock\Exception\LockAcquiringException]
  ERR    Failed to acquire the "Shlink:db:create" lock.
  ERR
  ERR
  ERR  Exception trace:
  ERR    at /etc/shlink/vendor/symfony/lock/Lock.php:116
  ERR   Symfony\Component\Lock\Lock->acquire() at /etc/shlink/module/CLI/src/Command/Util/AbstractLockedCommand.php:27
  ERR   Shlinkio\Shlink\CLI\Command\Util\AbstractLockedCommand->execute() at /etc/shlink/vendor/symfony/console/Command/Command.php:279
  ERR   Symfony\Component\Console\Command\Command->run() at /etc/shlink/vendor/symfony/console/Application.php:1076
  ERR   Symfony\Component\Console\Application->doRunCommand() at /etc/shlink/vendor/symfony/console/Application.php:342
  ERR   Symfony\Component\Console\Application->doRun() at /etc/shlink/vendor/symfony/console/Application.php:193
  ERR   Symfony\Component\Console\Application->run() at /etc/shlink/bin/cli:10
  ERR
  ERR  In Client.php line 416:
  ERR
  ERR    [Predis\Response\ServerException]
  ERR    NOSCRIPT No matching script. Please use EVAL.
  ERR
  ERR
  ERR  Exception trace:
  ERR    at /etc/shlink/vendor/predis/predis/src/Client.php:416
  ERR   Predis\Client->onErrorResponse() at /etc/shlink/vendor/predis/predis/src/Client.php:385
  ERR   Predis\Client->executeCommand() at /etc/shlink/vendor/predis/predis/src/Client.php:335
  ERR   Predis\Client->__call() at /etc/shlink/vendor/symfony/lock/Store/RedisStore.php:287
  ERR   Symfony\Component\Lock\Store\RedisStore->evaluate() at /etc/shlink/vendor/symfony/lock/Store/RedisStore.php:327
  ERR   Symfony\Component\Lock\Store\RedisStore->getNowCode() at /etc/shlink/vendor/symfony/lock/Store/RedisStore.php:60
  ERR   Symfony\Component\Lock\Store\RedisStore->save() at /etc/shlink/vendor/shlinkio/shlink-common/src/Lock/NamespacedStore.php:29
  ERR   Shlinkio\Shlink\Common\Lock\NamespacedStore->save() at /etc/shlink/vendor/symfony/lock/Lock.php:75
  ERR   Symfony\Component\Lock\Lock->acquire() at /etc/shlink/module/CLI/src/Command/Util/AbstractLockedCommand.php:27
  ERR   Shlinkio\Shlink\CLI\Command\Util\AbstractLockedCommand->execute() at /etc/shlink/vendor/symfony/console/Command/Command.php:279
  ERR   Symfony\Component\Console\Command\Command->run() at /etc/shlink/vendor/symfony/console/Application.php:1076
  ERR   Symfony\Component\Console\Application->doRunCommand() at /etc/shlink/vendor/symfony/console/Application.php:342
  ERR   Symfony\Component\Console\Application->doRun() at /etc/shlink/vendor/symfony/console/Application.php:193
  ERR   Symfony\Component\Console\Application->run() at /etc/shlink/bin/cli:10
  ERR
  ERR  db:create
  ERR
  ERR
  RES  1 Command did not run successfully
Updating database... [Running "/usr/local/bin/php bin/cli db:migrate"]   RUN  '/usr/local/bin/php' 'bin/cli' 'db:migrate'
  ERR  [2025-01-31T07:32:27.497457+00:00] [-] Shlink.NOTICE - Failed to acquire the "Shlink:db:migrate" lock.
  ERR
  ERR  In Lock.php line 116:
  ERR
  ERR    [Symfony\Component\Lock\Exception\LockAcquiringException]
  ERR    Failed to acquire the "Shlink:db:migrate" lock.
  ERR
  ERR
  ERR  Exception trace:
  ERR    at /etc/shlink/vendor/symfony/lock/Lock.php:116
  ERR   Symfony\Component\Lock\Lock->acquire() at /etc/shlink/module/CLI/src/Command/Util/AbstractLockedCommand.php:27
  ERR   Shlinkio\Shlink\CLI\Command\Util\AbstractLockedCommand->execute() at /etc/shlink/vendor/symfony/console/Command/Command.php:279
  ERR   Symfony\Component\Console\Command\Command->run() at /etc/shlink/vendor/symfony/console/Application.php:1076
  ERR   Symfony\Component\Console\Application->doRunCommand() at /etc/shlink/vendor/symfony/console/Application.php:342
  ERR   Symfony\Component\Console\Application->doRun() at /etc/shlink/vendor/symfony/console/Application.php:193
  ERR   Symfony\Component\Console\Application->run() at /etc/shlink/bin/cli:10
  ERR
  ERR  In Client.php line 416:
  ERR
  ERR    [Predis\Response\ServerException]
  ERR    NOSCRIPT No matching script. Please use EVAL.
  ERR
  ERR
  ERR  Exception trace:
  ERR    at /etc/shlink/vendor/predis/predis/src/Client.php:416
  ERR   Predis\Client->onErrorResponse() at /etc/shlink/vendor/predis/predis/src/Client.php:385
  ERR   Predis\Client->executeCommand() at /etc/shlink/vendor/predis/predis/src/Client.php:335
  ERR   Predis\Client->__call() at /etc/shlink/vendor/symfony/lock/Store/RedisStore.php:287
  ERR   Symfony\Component\Lock\Store\RedisStore->evaluate() at /etc/shlink/vendor/symfony/lock/Store/RedisStore.php:327
  ERR   Symfony\Component\Lock\Store\RedisStore->getNowCode() at /etc/shlink/vendor/symfony/lock/Store/RedisStore.php:60
  ERR   Symfony\Component\Lock\Store\RedisStore->save() at /etc/shlink/vendor/shlinkio/shlink-common/src/Lock/NamespacedStore.php:29
  ERR   Shlinkio\Shlink\Common\Lock\NamespacedStore->save() at /etc/shlink/vendor/symfony/lock/Lock.php:75
  ERR   Symfony\Component\Lock\Lock->acquire() at /etc/shlink/module/CLI/src/Command/Util/AbstractLockedCommand.php:27
  ERR   Shlinkio\Shlink\CLI\Command\Util\AbstractLockedCommand->execute() at /etc/shlink/vendor/symfony/console/Command/Command.php:279
  ERR   Symfony\Component\Console\Command\Command->run() at /etc/shlink/vendor/symfony/console/Application.php:1076
  ERR   Symfony\Component\Console\Application->doRunCommand() at /etc/shlink/vendor/symfony/console/Application.php:342
  ERR   Symfony\Component\Console\Application->doRun() at /etc/shlink/vendor/symfony/console/Application.php:193
  ERR   Symfony\Component\Console\Application->run() at /etc/shlink/bin/cli:10
  ERR
  ERR  db:migrate
  ERR
  ERR
  RES  1 Command did not run successfully
Generating proxies... [Running "/usr/local/bin/php bin/doctrine orm:generate-proxies"]   RUN  '/usr/local/bin/php' 'bin/doctrine' 'orm:generate-proxies'
  ERR   Processing entity "Shlinkio\Shlink\Core\Visit\Entity\ShortUrlVisitsCount"
  ERR   Processing entity "Shlinkio\Shlink\Core\Visit\Entity\OrphanVisitsCount"
  ERR   Processing entity "Shlinkio\Shlink\Core\Visit\Entity\VisitLocation"
  ERR   Processing entity "Shlinkio\Shlink\Core\ShortUrl\Entity\ShortUrl"
  ERR   Processing entity "Shlinkio\Shlink\Core\RedirectRule\Entity\ShortUrlRedirectRule"
  ERR   Processing entity "Shlinkio\Shlink\Core\Tag\Entity\Tag"
  ERR   Processing entity "Shlinkio\Shlink\Core\Domain\Entity\Domain"
  ERR   Processing entity "Shlinkio\Shlink\Core\RedirectRule\Entity\RedirectCondition"
  ERR   Processing entity "Shlinkio\Shlink\Core\Visit\Entity\Visit"
  ERR   Processing entity "Shlinkio\Shlink\Core\Geolocation\Entity\GeolocationDbUpdate"
  ERR   Processing entity "Shlinkio\Shlink\Rest\Entity\ApiKey"
  ERR   Processing entity "Shlinkio\Shlink\Rest\Entity\ApiKeyRole"
  ERR
  ERR   Proxy classes generated to "/etc/shlink/data/proxies"
  ERR
  RES  Command ran successfully
 Success!
Clearing entities cache... [Running "/usr/local/bin/php bin/doctrine orm:clear-cache:metadata"]   RUN  '/usr/local/bin/php' 'bin/doctrine' 'orm:clear-cache:metadata'
  ERR
  ERR   // Clearing all Metadata cache entries
  ERR
  ERR   [OK] Successfully deleted cache entries.
  ERR
  ERR
  RES  Command ran successfully
 Success!
Downloading GeoLite2 db file... [Running "/usr/local/bin/php bin/cli visit:download-db"]   RUN  '/usr/local/bin/php' 'bin/cli' 'visit:download-db'
  OUT
  OUT   [WARNING] Max consecutive errors reached. Cannot retry for a couple of days.
  OUT
  OUT
  RES  1 Command did not run successfully
 Warning!

And here's the Redis log (it's working for other apps), version 7.4.2:

1:C 30 Jan 2025 22:55:14.862 * Redis version=7.4.2, bits=64, commit=00000000, modified=1, pid=1, just started
1:C 30 Jan 2025 22:55:14.862 * Configuration loaded
1:M 30 Jan 2025 22:55:14.863 * monotonic clock: POSIX clock_gettime
1:M 30 Jan 2025 22:55:14.865 * Running mode=standalone, port=6379.
1:M 30 Jan 2025 22:55:14.866 * Server initialized
1:M 30 Jan 2025 22:55:14.931 * Reading RDB base file on AOF loading...
1:M 30 Jan 2025 22:55:14.931 * Loading RDB produced by version 7.4.2
1:M 30 Jan 2025 22:55:14.931 * RDB age 9730 seconds
1:M 30 Jan 2025 22:55:14.931 * RDB memory usage when created 23.81 Mb
1:M 30 Jan 2025 22:55:14.931 * RDB is base AOF
1:M 30 Jan 2025 22:55:15.436 * Done loading RDB, keys loaded: 18508, keys expired: 0.
1:M 30 Jan 2025 22:55:15.437 * DB loaded from base file appendonly.aof.955.base.rdb: 0.506 seconds
1:M 30 Jan 2025 22:55:17.433 * DB loaded from incr file appendonly.aof.955.incr.aof: 1.996 seconds
1:M 30 Jan 2025 22:55:17.433 * DB loaded from append only file: 2.565 seconds
1:M 30 Jan 2025 22:55:17.434 * Opening AOF incr file appendonly.aof.955.incr.aof on server start
1:M 30 Jan 2025 22:55:17.434 * Ready to accept connections tcp
1:M 30 Jan 2025 23:10:07.544 * Starting automatic rewriting of AOF on 505% growth
1:M 30 Jan 2025 23:10:07.548 * Creating AOF incr file appendonly.aof.956.incr.aof on background rewrite
1:M 30 Jan 2025 23:10:07.549 * Background append only file rewriting started by pid 3294
3294:C 30 Jan 2025 23:10:08.331 * Successfully created the temporary AOF base file temp-rewriteaof-bg-3294.aof
3294:C 30 Jan 2025 23:10:08.331 * Fork CoW for AOF rewrite: current 3 MB, peak 3 MB, average 2 MB
1:M 30 Jan 2025 23:10:08.335 * Background AOF rewrite terminated with success
1:M 30 Jan 2025 23:10:08.336 * Successfully renamed the temporary AOF base file temp-rewriteaof-bg-3294.aof into appendonly.aof.956.base.rdb
1:M 30 Jan 2025 23:10:08.340 * Removing the history file appendonly.aof.955.incr.aof in the background
1:M 30 Jan 2025 23:10:08.342 * Removing the history file appendonly.aof.955.base.rdb in the background
1:M 30 Jan 2025 23:10:08.398 * Background AOF rewrite finished successfully
1:M 31 Jan 2025 01:21:02.635 * Starting automatic rewriting of AOF on 514% growth
1:M 31 Jan 2025 01:21:02.639 * Creating AOF incr file appendonly.aof.957.incr.aof on background rewrite
1:M 31 Jan 2025 01:21:02.639 * Background append only file rewriting started by pid 37870
37870:C 31 Jan 2025 01:21:03.282 * Successfully created the temporary AOF base file temp-rewriteaof-bg-37870.aof
37870:C 31 Jan 2025 01:21:03.283 * Fork CoW for AOF rewrite: current 3 MB, peak 3 MB, average 2 MB
1:M 31 Jan 2025 01:21:03.334 * Background AOF rewrite terminated with success
1:M 31 Jan 2025 01:21:03.335 * Successfully renamed the temporary AOF base file temp-rewriteaof-bg-37870.aof into appendonly.aof.957.base.rdb
1:M 31 Jan 2025 01:21:03.340 * Removing the history file appendonly.aof.956.incr.aof in the background
1:M 31 Jan 2025 01:21:03.342 * Removing the history file appendonly.aof.956.base.rdb in the background
1:M 31 Jan 2025 01:21:03.346 * Background AOF rewrite finished successfully
1:M 31 Jan 2025 03:34:17.190 * Starting automatic rewriting of AOF on 508% growth
1:M 31 Jan 2025 03:34:17.193 * Creating AOF incr file appendonly.aof.958.incr.aof on background rewrite
1:M 31 Jan 2025 03:34:17.194 * Background append only file rewriting started by pid 73052
73052:C 31 Jan 2025 03:34:17.631 * Successfully created the temporary AOF base file temp-rewriteaof-bg-73052.aof
73052:C 31 Jan 2025 03:34:17.632 * Fork CoW for AOF rewrite: current 2 MB, peak 2 MB, average 1 MB
1:M 31 Jan 2025 03:34:17.732 * Background AOF rewrite terminated with success
1:M 31 Jan 2025 03:34:17.733 * Successfully renamed the temporary AOF base file temp-rewriteaof-bg-73052.aof into appendonly.aof.958.base.rdb
1:M 31 Jan 2025 03:34:17.739 * Removing the history file appendonly.aof.957.incr.aof in the background
1:M 31 Jan 2025 03:34:17.741 * Removing the history file appendonly.aof.957.base.rdb in the background
1:M 31 Jan 2025 03:34:17.792 * Background AOF rewrite finished successfully
1:M 31 Jan 2025 05:48:43.535 * Starting automatic rewriting of AOF on 510% growth
1:M 31 Jan 2025 05:48:43.539 * Creating AOF incr file appendonly.aof.959.incr.aof on background rewrite
1:M 31 Jan 2025 05:48:43.540 * Background append only file rewriting started by pid 108549
108549:C 31 Jan 2025 05:48:43.891 * Successfully created the temporary AOF base file temp-rewriteaof-bg-108549.aof
108549:C 31 Jan 2025 05:48:43.891 * Fork CoW for AOF rewrite: current 2 MB, peak 2 MB, average 1 MB
1:M 31 Jan 2025 05:48:43.943 * Background AOF rewrite terminated with success
1:M 31 Jan 2025 05:48:43.944 * Successfully renamed the temporary AOF base file temp-rewriteaof-bg-108549.aof into appendonly.aof.959.base.rdb
1:M 31 Jan 2025 05:48:43.950 * Removing the history file appendonly.aof.958.incr.aof in the background
1:M 31 Jan 2025 05:48:43.952 * Removing the history file appendonly.aof.958.base.rdb in the background
1:M 31 Jan 2025 05:48:43.957 * Background AOF rewrite finished successfully
1:M 31 Jan 2025 08:03:03.198 * Starting automatic rewriting of AOF on 510% growth
1:M 31 Jan 2025 08:03:03.201 * Creating AOF incr file appendonly.aof.960.incr.aof on background rewrite
1:M 31 Jan 2025 08:03:03.203 * Background append only file rewriting started by pid 144035
144035:C 31 Jan 2025 08:03:03.662 * Successfully created the temporary AOF base file temp-rewriteaof-bg-144035.aof
144035:C 31 Jan 2025 08:03:03.662 * Fork CoW for AOF rewrite: current 3 MB, peak 3 MB, average 2 MB
1:M 31 Jan 2025 08:03:03.734 * Background AOF rewrite terminated with success
1:M 31 Jan 2025 08:03:03.735 * Successfully renamed the temporary AOF base file temp-rewriteaof-bg-144035.aof into appendonly.aof.960.base.rdb
1:M 31 Jan 2025 08:03:03.739 * Removing the history file appendonly.aof.959.incr.aof in the background
1:M 31 Jan 2025 08:03:03.741 * Removing the history file appendonly.aof.959.base.rdb in the background
1:M 31 Jan 2025 08:03:03.745 * Background AOF rewrite finished successfully

1 reply

acelaya Jan 31, 2025
Maintainer

Have you googled for the error NOSCRIPT No matching script. Please use EVAL? It seems to be related with a redis instance that gets restarted, but I'm not so sure.

I checked for the error in the library used to connect to Redis, and there's no mention of this, at least in recent issues.

Also in this other abstraction the project also uses https://github.com/symfony/symfony. No mentions to the error (even partially) in recent issues.

acelaya · 2025-01-31T08:41:06Z

acelaya
Jan 31, 2025
Maintainer

Shlink version

shlinkio/shlink:latest

What exact version are you using? If you run shlink -V inside the container, what version do you get?

If you can't do that, can you make sure your local latest tag is actually up to date by pulling from the registry?

0 replies

urbaman · 2025-01-31T11:13:28Z

urbaman
Jan 31, 2025
Author

Hi,

I can only see that each time I delete the pod, and the deployment recreates it, it pulls the latest:

Successfully pulled image "shlinkio/shlink:latest"

The container is too much unstable to let me in and throw commands

0 replies

urbaman · 2025-01-31T11:16:56Z

urbaman
Jan 31, 2025
Author

Also, the Redis pod seems to be almost stable (6 restarts in the last 2+ days), but not really, I'll monitor it.
Thing is: all of the other apps using redis do not have the same problem shlink has.

0 replies

urbaman · 2025-01-31T11:24:07Z

urbaman
Jan 31, 2025
Author

Hi,

I restarted the Redis deployment, and now while it does not restart (not yet), shlink still has the same error while the other apps using redis work.

ubuntu@mk8s1:~$ kubectl get pods -n redis
NAME             READY   STATUS    RESTARTS   AGE
redis-master-0   2/2     Running   0          2m18s
ubuntu@mk8s1:~$ kubectl logs -n redis redis-master-0
Defaulted container "redis" out of: redis, metrics, k8tz (init)
1:C 31 Jan 2025 12:19:51.237 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 31 Jan 2025 12:19:51.237 * Redis version=7.4.2, bits=64, commit=00000000, modified=1, pid=1, just started
1:C 31 Jan 2025 12:19:51.237 * Configuration loaded
1:M 31 Jan 2025 12:19:51.237 * monotonic clock: POSIX clock_gettime
1:M 31 Jan 2025 12:19:51.238 * Running mode=standalone, port=6379.
1:M 31 Jan 2025 12:19:51.239 * Server initialized
1:M 31 Jan 2025 12:19:51.240 * Reading RDB base file on AOF loading...
1:M 31 Jan 2025 12:19:51.240 * Loading RDB produced by version 7.4.2
1:M 31 Jan 2025 12:19:51.240 * RDB age 7249 seconds
1:M 31 Jan 2025 12:19:51.240 * RDB memory usage when created 23.83 Mb
1:M 31 Jan 2025 12:19:51.240 * RDB is base AOF
1:M 31 Jan 2025 12:19:51.303 * Done loading RDB, keys loaded: 18849, keys expired: 0.
1:M 31 Jan 2025 12:19:51.303 * DB loaded from base file appendonly.aof.961.base.rdb: 0.063 seconds
1:M 31 Jan 2025 12:19:51.541 * DB loaded from incr file appendonly.aof.961.incr.aof: 0.238 seconds
1:M 31 Jan 2025 12:19:51.541 * DB loaded from append only file: 0.302 seconds
1:M 31 Jan 2025 12:19:51.542 * Opening AOF incr file appendonly.aof.961.incr.aof on server start
1:M 31 Jan 2025 12:19:51.542 * Ready to accept connections tcp

7 replies

acelaya Feb 4, 2025
Maintainer

@urbaman we have found the root cause. See #2350 (reply in thread)

I'm going to create an issue here to track it, and I'm also reporting it to the symfony repository.

acelaya Feb 4, 2025
Maintainer

Feel free to subscribe to #2354

urbaman Feb 4, 2025
Author

Thank you very much!

acelaya Feb 4, 2025
Maintainer

@urbaman FYI, I just discovered only Shlink 4.4.2 is affected by this, 4.4.1 was built before symfony/lock 7.2.3 was released, so it ships with a version that works.

The only thing Shlink 4.4.2 introduced was ARM docker images that had to be disabled for v4.4.1 due to an unrelated issue, so unless you are precisely using the ARM variant, it's safe for you to downgrade to 4.4.1 until Shlink 4.4.3 has been released.

urbaman Feb 4, 2025
Author

Can confirm 4.4.1 working flawlessly for my k8s deployment with external DBs.

Thank you.

ymage · 2025-02-03T16:40:57Z

ymage
Feb 3, 2025

I used the provided docker-compose.yml from the repo and I followed https://github.com/shlinkio/shlink/blob/develop/CONTRIBUTING.md and I get the same error with ./indocker bin/cli db:create command

7 replies

acelaya Feb 4, 2025
Maintainer

Thanks! I was able to reproduce it now.

acelaya Feb 4, 2025
Maintainer

I was able to reproduce it once in my usual dev environment, after updating dependencies (it was the only thing I could think of that was different). Then I downgraded symfony/lock, as it is where this error is originating, and the error was gone. However, I updated the dependencies again and I can't reproduce it anymore 🤦🏼‍♂️

I can still consistently reproduce it on the new dev env created from scratch though.

acelaya Feb 4, 2025
Maintainer

Ok, by comparing symfony/lock 7.2.0 and 7.2.3 I can see there are changes in the code related to precisely this error: symfony/lock@v7.2.0...v7.2.3

They seem to have changed how this error is handled and apparently broke it.

acelaya Feb 4, 2025
Maintainer

@ymage to work around that for the dev env, apply this diff in the composer.json file:

diff --git a/composer.json b/composer.json
index d18802a2..7f0382cc 100644
--- a/composer.json
+++ b/composer.json
@@ -56,7 +56,7 @@
         "spiral/roadrunner-jobs": "^4.6",
         "symfony/console": "^7.2",
         "symfony/filesystem": "^7.2",
-        "symfony/lock": "^7.2",
+        "symfony/lock": "7.2.0",
         "symfony/process": "^7.2",
         "symfony/string": "^7.2"
     },

Then run ./indocker compose update, and then ./indocker bin/cli db:create should work as expected.

ymage Feb 4, 2025

It works. Thank you

acelaya · 2025-02-04T08:30:28Z

acelaya
Feb 4, 2025
Maintainer

Issue reported to upstream project with minimal reproduction steps symfony/symfony#59686

Issue to track it here #2354

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

"NOSCRIPT No matching script. Please use EVAL" error while trying to acquire lock in redis #2350

{{title}}

Replies: 8 comments 15 replies

{{title}}

{{title}}

{{title}}

{{title}}

Shlink version

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

"NOSCRIPT No matching script. Please use EVAL" error while trying to acquire lock in redis #2350

urbaman Jan 31, 2025

Shlink version

PHP version

How do you serve Shlink

Database engine

Database version

Summary

Replies: 8 comments · 15 replies

acelaya Jan 31, 2025 Maintainer

urbaman Jan 31, 2025 Author

acelaya Jan 31, 2025 Maintainer

acelaya Jan 31, 2025 Maintainer

Shlink version

urbaman Jan 31, 2025 Author

urbaman Jan 31, 2025 Author

urbaman Jan 31, 2025 Author

acelaya Feb 4, 2025 Maintainer

acelaya Feb 4, 2025 Maintainer

urbaman Feb 4, 2025 Author

acelaya Feb 4, 2025 Maintainer

urbaman Feb 4, 2025 Author

ymage Feb 3, 2025

acelaya Feb 4, 2025 Maintainer

acelaya Feb 4, 2025 Maintainer

acelaya Feb 4, 2025 Maintainer

acelaya Feb 4, 2025 Maintainer

ymage Feb 4, 2025

acelaya Feb 4, 2025 Maintainer

urbaman
Jan 31, 2025

Replies: 8 comments 15 replies

acelaya
Jan 31, 2025
Maintainer

urbaman
Jan 31, 2025
Author

acelaya Jan 31, 2025
Maintainer

acelaya
Jan 31, 2025
Maintainer

urbaman
Jan 31, 2025
Author

urbaman
Jan 31, 2025
Author

urbaman
Jan 31, 2025
Author

acelaya Feb 4, 2025
Maintainer

acelaya Feb 4, 2025
Maintainer

urbaman Feb 4, 2025
Author

acelaya Feb 4, 2025
Maintainer

urbaman Feb 4, 2025
Author

ymage
Feb 3, 2025

acelaya Feb 4, 2025
Maintainer

acelaya Feb 4, 2025
Maintainer

acelaya Feb 4, 2025
Maintainer

acelaya Feb 4, 2025
Maintainer

acelaya
Feb 4, 2025
Maintainer