/*
|--------------------------------------------------------------------------
| Default Queue Driver
|--------------------------------------------------------------------------
|
| Laravel's queue API supports an assortment of back-ends via a single
| API, giving you convenient access to each back-end using the same
| syntax for each one. Here you may set the default queue driver.
|
| Supported: "sync", "database", "beanstalkd", "sqs", "redis", "null"
|
*/// envメソッドの第二引数をデフォルトの`sync`から指定したいドライバーに変更'default'=>env('QUEUE_DRIVER','database'),
下記のようにActive: active (running)…と表示され、/etc/supervisord.d/laravel-worker.confのcommand項目で設定したコマンドがnumprocs項目で設定した回数分表示されていれば問題ありません（下記では301829〜301836のプロセス）。
ターミナル
● supervisord.service - Process Monitoring and Control Daemon
Loaded: loaded (/usr/lib/systemd/system/supervisord.service;enabled; vendor preset: disabled) Active: active (running) since Sun 2021-01-10 xx:xx:xx JST;xs ago
Process: 301824 ExecStart=/usr/bin/supervisord -c /etc/supervisord.conf (code=exited, status=0/SUCCESS)
Main PID: 301828 (supervisord)
Tasks: 9 (limit: 5049)
Memory: 144.6M
CGroup: /system.slice/supervisord.service
├─301828 /usr/bin/python3.6 /usr/bin/supervisord -c /etc/supervisord.conf
├─301829 php /var/www/html/laravel/artisan queue:work --sleep=3 --tries=10
├─301830 php /var/www/html/laravel/artisan queue:work --sleep=3 --tries=10
├─301831 php /var/www/html/laravel/artisan queue:work --sleep=3 --tries=10
├─301832 php /var/www/html/laravel/artisan queue:work --sleep=3 --tries=10
├─301833 php /var/www/html/laravel/artisan queue:work --sleep=3 --tries=10
├─301834 php /var/www/html/laravel/artisan queue:work --sleep=3 --tries=10
├─301835 php /var/www/html/laravel/artisan queue:work --sleep=3 --tries=10
└─301836 php /var/www/html/laravel/artisan queue:work --sleep=3 --tries=10
1月 10 xx:xx:xx 160-251-23-222 systemd[1]: Starting Process Monitoring and Control Daemon...
1月 10 xx:xx:xx 160-251-23-222 systemd[1]: Started Process Monitoring and Control Daemon.
UpdateElasticsearchDomainConfig: {"message":"You can’t attach an IP-based policy to a domain that has a VPC endpoint. Instead, use a security group to control IP-based access."}
