Missing glide transformations?

[stephenmeehanuk]

Hi,

I'm noticing when I upload 10 images via drag and drop into the assets section of the control panel, not all the glide transformations are completed?

• The 10 images are taken from unsplash.com, they range from 300KB to 3.8MB
• They're a mixture of portrait, landscape and square formats
• A range of resolutions, 5760 × 3240, 2000 × 3000, 11000 × 6600, 6250 × 6250
• All the images have a resolution of 72DPI
• The combined filesize of all the images is 11MB

I thought they would be a good representation of the kind of images a client may drag and drop in to the assets section of the control panel.

I'm using the Process Source Images option with this preset

'max_upload_size' => ['w' => 2000, 'h' => 2000, 'fit' => 'max'],

and the Intelligently Warm Presets is turned on.

I'm using PHPredis and Horizon.

I've got 26 glide presets, Statamic uses an additional preset based on the format of the image uploaded

cp_thumbnail_small_landscape cp_thumbnail_small_square or cp_thumbnail_small_portrait so each directory in /public/img/containers/assets should have 27 images.

I upload 10 images, in total I expect there to be 270 images generated.

However, when I sFTP into the server and check the images in /public/img/containers/assets only some of the folders have 27 images. Other folders have about 10-20 images, some of the folders only have three images?

When I clear the image cache php please glide:clear I see there's only 102 images

[✔] Glide path cache cleared.
[✔] Found 102 images.

I thought I'd see if anything different happens when I run php please assets:generate-presets --queue from Terminal

[✔] 270 images queued for 10 assets.

I give it plenty of time to process (20 minutes), then run php please glide:clear again

[✔] Glide path cache cleared.
[✔] Found 96 images.

Still not generating the full 270 images required.

This is problem because when I run php please static:warm --queue many images are not pre-generated which causes the site to 500 error. I suspect this is the reason why this is happening.

I'd like to figure out a way to get all the image transformations generated before running static:warm

Failed Jobs are logged in /horizon/failed

Stack trace

Illuminate\Queue\MaxAttemptsExceededException: Statamic\Listeners\GeneratePresetImageManipulations has been attempted too many times. in /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Queue/Worker.php:785
--
Stack trace:
#0 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(519): Illuminate\Queue\Worker->maxAttemptsExceededException()
#1 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(428): Illuminate\Queue\Worker->markJobAsFailedIfAlreadyExceedsMaxAttempts()
#2 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(389): Illuminate\Queue\Worker->process()

laravel.log

#31 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(200): Symfony\\Component\\Console\\Application->run()
#32 /home/ploi/demo.website.co.uk/artisan(35): Illuminate\\Foundation\\Console\\Kernel->handle()
#33 {main}
[previous exception] [object] (PDOException(code: 2002): SQLSTATE[HY000] [2002] Connection refused at /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php:65)
[stacktrace]
#0 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php(65): PDO->__construct()
#1 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php(83): Illuminate\\Database\\Connectors\\Connector->createPdoConnection()
#2 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php(48): Illuminate\\Database\\Connectors\\Connector->tryAgainIfCausedByLostConnection()
#3 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Database/Connectors/MySqlConnector.php(24): Illuminate\\Database\\Connectors\\Connector->createConnection()
#4 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Database/Connectors/ConnectionFactory.php(184): Illuminate\\Database\\Connectors\\MySqlConnector->connect()
#5 [internal function]: Illuminate\\Database\\Connectors\\ConnectionFactory->Illuminate\\Database\\Connectors\\{closure}()
#6 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Database/Connection.php(1275): call_user_func()
#7 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Database/Connection.php(574): Illuminate\\Database\\Connection->getPdo()
#8 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Database/Connection.php(788): Illuminate\\Database\\Connection->Illuminate\\Database\\{closure}()
#9 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Database/Connection.php(934): Illuminate\\Database\\Connection->runQueryCallback()
#10 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Database/Connection.php(913): Illuminate\\Database\\Connection->tryAgainIfCausedByLostConnection()
#11 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Database/Connection.php(757): Illuminate\\Database\\Connection->handleQueryException()
#12 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Database/Connection.php(569): Illuminate\\Database\\Connection->run()
#13 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Database/Connection.php(533): Illuminate\\Database\\Connection->statement()
#14 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(3320): Illuminate\\Database\\Connection->insert()
#15 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Queue/Failed/DatabaseUuidFailedJobProvider.php(58): Illuminate\\Database\\Query\\Builder->insert()
#16 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php(276): Illuminate\\Queue\\Failed\\DatabaseUuidFailedJobProvider->log()
#17 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php(186): Illuminate\\Queue\\Console\\WorkCommand->logFailedJob()
#18 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php(421): Illuminate\\Queue\\Console\\WorkCommand->Illuminate\\Queue\\Console\\{closure}()
#19 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php(249): Illuminate\\Events\\Dispatcher->Illuminate\\Events\\{closure}()
#20 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Queue/Jobs/Job.php(194): Illuminate\\Events\\Dispatcher->dispatch()
#21 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(596): Illuminate\\Queue\\Jobs\\Job->fail()
#22 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(519): Illuminate\\Queue\\Worker->failJob()
#23 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(428): Illuminate\\Queue\\Worker->markJobAsFailedIfAlreadyExceedsMaxAttempts()
#24 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(389): Illuminate\\Queue\\Worker->process()
#25 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(176): Illuminate\\Queue\\Worker->runJob()
#26 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php(137): Illuminate\\Queue\\Worker->daemon()
#27 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php(120): Illuminate\\Queue\\Console\\WorkCommand->runWorker()
#28 /home/ploi/demo.website.co.uk/vendor/laravel/horizon/src/Console/WorkCommand.php(51): Illuminate\\Queue\\Console\\WorkCommand->handle()
#29 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(36): Laravel\\Horizon\\Console\\WorkCommand->handle()
#30 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Container/Util.php(41): Illuminate\\Container\\BoundMethod::Illuminate\\Container\\{closure}()
#31 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(93): Illuminate\\Container\\Util::unwrapIfClosure()
#32 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(35): Illuminate\\Container\\BoundMethod::callBoundMethod()
#33 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Container/Container.php(662): Illuminate\\Container\\BoundMethod::call()
#34 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Console/Command.php(208): Illuminate\\Container\\Container->call()
#35 /home/ploi/demo.website.co.uk/vendor/symfony/console/Command/Command.php(326): Illuminate\\Console\\Command->execute()
#36 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Console/Command.php(177): Symfony\\Component\\Console\\Command\\Command->run()
#37 /home/ploi/demo.website.co.uk/vendor/symfony/console/Application.php(1081): Illuminate\\Console\\Command->run()
#38 /home/ploi/demo.website.co.uk/vendor/symfony/console/Application.php(320): Symfony\\Component\\Console\\Application->doRunCommand()
#39 /home/ploi/demo.website.co.uk/vendor/symfony/console/Application.php(174): Symfony\\Component\\Console\\Application->doRun()
#40 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(200): Symfony\\Component\\Console\\Application->run()
#41 /home/ploi/demo.website.co.uk/artisan(35): Illuminate\\Foundation\\Console\\Kernel->handle()
#42 {main}
"}

• Is this issue related to memory?
• Is there a way to config Statamic/Horizon to process one image at a time? I don't mind if it's slow, I'd rather be sure all images are generated.

PHP settings

• Max upload filesize in MB 500
• Memory limit in MB 128
• Max execution time in seconds 30

I'm using a budget server

• Hetzner CX11
• 2GB Ram
• CPU 1 Core
• Disk 20GB

I've set this particular website up as a demo site, fresh install. All I'm trying to do is get to the bottom of why all the glide images don't get generated.

I'm using these asset settings

These are the presets, my real site (this is just a demo site) has many more presets than this.

            'max_upload_size' => ['w' => 2000, 'h' => 2000, 'fit' => 'max'],
            // Facebook OG - jpg
            'w1200_h630' => ['w' => 1200, 'h' => 630, 'q' => 75, 'fit' => 'crop_focal'],
            // Twitter OG -jpg
            'w1024_h512' => ['w' => 1024, 'h' => 512, 'q' => 75, 'fit' => 'crop_focal'],
            // 4:3 - classic - webp
            'w2000_classic' => ['w' => 2000, 'h' => 1500, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            'w1700_classic' => ['w' => 1700, 'h' => 1275, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            'w1445_classic' => ['w' => 1445, 'h' => 1084, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            'w1228_classic' => ['w' => 1228, 'h' => 921, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            'w1044_classic' => ['w' => 1044, 'h' => 783, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            // 21:9 - ultrawide - webp
            'w2000_ultrawide' => ['w' => 2000, 'h' => 844, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            'w1700_ultrawide' => ['w' => 1700, 'h' => 717, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            'w1445_ultrawide' => ['w' => 1445, 'h' => 610, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            'w1228_ultrawide' => ['w' => 1228, 'h' => 518, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            'w1044_ultrawide' => ['w' => 1044, 'h' => 441, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            // 16:9 - wide - webp
            'w2000_wide' => ['w' => 2000, 'h' => 1125, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            'w1700_wide' => ['w' => 1700, 'h' => 956, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            'w1445_wide' => ['w' => 1445, 'h' => 813, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            'w1228_wide' => ['w' => 1228, 'h' => 691, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            // 1:1 - square - webp
            'w2000_square' => ['w' => 2000, 'h' => 2000, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            'w1700_square' => ['w' => 1700, 'h' => 1700, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            'w1445_square' => ['w' => 1445, 'h' => 1445, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            'w1228_square' => ['w' => 1228, 'h' => 1228, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            'w1044_square' => ['w' => 1044, 'h' => 1044, 'q' => 75, 'fm' => 'webp', 'fit' => 'crop_focal'], 
            // no_crop - no_crop - webp
            'w2000_no_crop' => ['w' => 2000, 'q' => 75, 'fm' => 'webp', 'fit' => 'contain'], 
            'w1700_no_crop' => ['w' => 1700, 'q' => 75, 'fm' => 'webp', 'fit' => 'contain'], 
            'w1445_no_crop' => ['w' => 1445, 'q' => 75, 'fm' => 'webp', 'fit' => 'contain'], 
            'w1228_no_crop' => ['w' => 1228, 'q' => 75, 'fm' => 'webp', 'fit' => 'contain'], 
            'w1044_no_crop' => ['w' => 1044, 'q' => 75, 'fm' => 'webp', 'fit' => 'contain'], 

Environment
Application Name: Statamic
Laravel Version: 10.13.5
PHP Version: 8.2.7
Composer Version: 2.5.8
Environment: local
Debug Mode: OFF
URL: demo.website.co.uk
Maintenance Mode: OFF

Cache
Config: CACHED
Events: NOT CACHED
Routes: CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: statamic
Database: mysql
Logs: stack / single
Mail: smtp
Queue: redis
Session: file

Statamic
Addons: 0
Antlers: runtime
Stache Watcher: Enabled
Static Caching: Disabled
Version: 4.6.0 Solo

[stephenmeehanuk]

As a test I thought I'd try uploading the same batch of 10 images, optimised for the web

• Images are reduced to be 1900px in at least one dimension
• Saved as .jpg
• Further optimised using ImageOptim locally, before uploading

None of my clients would do this.

• I leave it for about 20 minutes
• Check /public/img/containers/assets hoping each folder has 27 images.
• I can see still some folders are missing images?

php please glide:clear shows optimising the images before hand has improved it slightly

[✔] Glide path cache cleared.
[✔] Found 240 images.

It managed to generate 240/270

[stephenmeehanuk]

I thought the reason to use Redis / Horizon was to queue image transformations, to avoid this being an issue? Is that not the case?

Perhaps, is there a way to configure the site to only accept images

• in a certain format (.jpg)
• below a certain filesize
• a fixed resolution (72dpi)
• or configure the maximum number of uploads dragged and dropped in to the control panel at a time?

Is there a way to throttle how many images are dumped in the queue?

[stephenmeehanuk]

Another test

Deleted laravel.log before this test, and deleted all previously uploaded images via control panel

Uploaded three 72dpi images at 19:17

Using the same assets setting as before

• Process Source Images option with 'max_upload_size' preset
• and the Intelligently Warm Presets is turned on.

Images I uploaded via control panel

1. mark-sans-3jj4-HXXa_0-unsplash.jpg. 81KB 3840 × 2160
2. hesam-link--lWW_M2zilE-unsplash.jpg 263KB 2000 × 3000
3. yu-carla-Or3zn5zbgzE-unsplash.jpg 306KB 3840 × 2160

Checked laravel.log at 19:24 there's an error, same as before

#31 /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(200): Symfony\\Component\\Console\\Application->run()
#32 /home/ploi/demo.website.co.uk/artisan(35): Illuminate\\Foundation\\Console\\Kernel->handle()
#33 {main}
[previous exception] [object] (PDOException(code: 2002): SQLSTATE[HY000] [2002] Connection refused at /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php:65)

php please glide:clear shows

[✔] Glide path cache cleared.
[✔] Found 69 images.

Only 69 out of an expected 81 images were generated before it stopped working?

Surely this can't be a memory thing? Three pretty small images can't cause the process to break can it? Have I configured something wrong?

[byron-roots]

The job is failing and then it is trying to add a failed job log to your database. I'm assuming you haven't got a database setup yet which is why the connection is failing. If you setup a database and run the migrations and retry the failed job should be logged and should tell you why it's failing

[stephenmeehanuk]

Thanks for the reply, much appreciated.

You're right, I don't have a database installed. I've installed this add on today: https://statamic.com/addons/jonassiewertsen/jobs

This addon does provide a simple solution for small Statamic setups: A failing job will be saved as flat file in the storage.

Once installed, running this command php artisan queue:failed shows me this error

  2023-06-19 10:37:48 18fabee6-911e-4003-83eb-776d9846c950 ................... redis@default Illuminate\Events\CallQueuedListener  
  2023-06-19 10:37:52 c09c63b9-c2dc-421b-a27f-30e674ac3b89 ................... redis@default Illuminate\Events\CallQueuedListener  

laravel.log now shows this error

[2023-06-19 10:37:48] local.ERROR: Statamic\Listeners\GeneratePresetImageManipulations has been attempted too many times. {"exception":"[object] (Illuminate\\Queue\\MaxAttemptsExceededException(code: 0): Statamic\\Listeners\\GeneratePresetImageManipulations has been attempted too many times. at /home/ploi/demo.website.co.uk/vendor/laravel/framework/src/Illuminate/Queue/Worker.php:785)

Does the errors listed make any sense?

[jackmcdade]

Hey there, there could be other factors at play, but you're definitely going to want to up your memory_limit — you have a 2GB server and are only using 5% of it with 128M. I'd recommend setting it to at least 1536 in your php.ini and seeing how that may help. You could also try using imagemagick instead of gd to manipulate the images, which is much more memory efficient.

[stephenmeehanuk]

Hi, thanks for suggestions.

I bumped the memory to 1536 and I installed Imagick PHP extension. I switched drivers in config/statamic/assets.php to 'driver' => 'imagick',

Unfortunately, still seeing errors.

laravel.log

[2023-06-19 19:36:54] local.ERROR: Statamic\Listeners\GeneratePresetImageManipulations has been attempted too many times. {"exception":"[object] (Illuminate\\Queue\\MaxAttemptsExceededException(code: 0): Statamic\\Listeners\\GeneratePresetImageManipulations has been attempted too many times. at /home/ploi/demo.website.uk/vendor/laravel/framework/src/Illuminate/Queue/Worker.php:785)

php artisan queue:failed shows this:

2023-06-19 19:36:54 0d3f4df2-2b0d-4c57-9369-b668c0a82d05 .......................... redis@default Illuminate\Events\CallQueuedListener  
  2023-06-19 19:37:29 13e9ecc8-a1ff-46dc-b2a8-f56d323a83ee .......................... redis@default Illuminate\Events\CallQueuedListener 

Does the redis part of my env look ok to you?

BROADCAST_DRIVER=log
CACHE_DRIVER=file
FILESYSTEM_DISK=local
QUEUE_CONNECTION=redis
SESSION_DRIVER=file
REDIS_DATABASE=0
REDIS_CLIENT=phpredis
SESSION_LIFETIME=120

php please glide:clear shows

[✔] Glide path cache cleared.
[✔] **Found 249 images.**
[✔] Images deleted.
[✔] Deleted empty directories.

I'm uploading 10 images, with 27 presets. I'm looking for 270 images to be generated.

Is there anything else I can try?

[stephenmeehanuk]

I noticed Horizon behaves differently when I upload images via the Control Panel and the image queue kicks in, versus running php please assets:generate-presets --queue from the command line.

As a test I've paused the daemon in Ploi ploi.io/panel/servers/54379/queues and I've also paused the queue here ploi.io/panel/servers/54379/sites/161651/queues

This is my test

• 10 images already uploaded via control panel, php please glide:clear removes generated images
• 27 presets,
• max_upload_size preset being used

When I run php please assets:generate-presets --queue from command line it works, I've repeated this test multiple times and it always generates 270 images.

• Start time: 15:23:25
• End time: 15:26:16
• Duration: 3 minutes 9 seconds

php please glide:clear shows

[✔] Glide path cache cleared.
[✔] Found 270 images.

config/horizon.php looks like this, I'm using local on my staging site. Any changes I made to this file didn't work unless I used php artisan config:cache first.

 'defaults' => [
        'supervisor-1' => [
            'connection' => 'redis',
            'queue' => ['default'],
            'balance' => 'auto',
            'autoScalingStrategy' => 'time',
            'maxProcesses' => 1,
            'maxTime' => 0,
            'maxJobs' => 0,
            'memory' => 1024,
            'tries' => 1,
            'timeout' => 60,
            'nice' => 0,
        ],
    ],

    'environments' => [
        'production' => [
            'supervisor-1' => [
                'maxProcesses' => 10,
                'balanceMaxShift' => 1,
                'balanceCooldown' => 3,
            ],
        ],

        'local' => [
            'supervisor-1' => [
                'maxProcesses' => 30,
                'balanceMaxShift' => 3,
                'balanceCooldown' => 1,
            ],
        ],
    ],

In Ploi, I've reduced the Memory limit in MB setting to 1024
ploi.io/panel/servers/54379/php

php artisan queue:failed shows no errors and there's no errors on laravel.log.

I think the issue is related to the configuration in Ploi...

I'll ask in the Ploi Discord and post here if I find anything out.

[jackmcdade]

Nice sleuthing! Keep us posted!

[stephenmeehanuk]

Ha ha

[stephenmeehanuk]

Got to the bottom of it.

User error!

All I needed to do was use a queue in Ploi.

I got the mixed up idea I had to use a daemon and Horizon on the server. When this isn't required.

Dennis and Rob in the Ploi Discord put me on the right track.

It's working as expected now. Phew.

Takeaways

• No need to use Horizon
• In Ploi, use site queues
• This is what we need for env

BROADCAST_DRIVER=log
CACHE_DRIVER=redis
FILESYSTEM_DISK=local
QUEUE_CONNECTION=redis
SESSION_DRIVER=redis
REDIS_DATABASE=1
SESSION_LIFETIME=120

• No need to specify REDIS_CLIENT
• Keep a note of what website uses which redis database (if you host more than one site on a server).