Cpanel composer update kill

The "Killed" message usually means your process consumed too much memory, so you may simply need to add more memory to your system if possible. At the time of writing this answer, I've had to increase my virtual machine's memory to at least 768MB in order to get composer update to work in some situations.

However, if you're doing this on a live server, you shouldn't be using composer update at all. What you should instead do is:

Run composer update in a local environment (such as directly on your physical laptop/desktop, or a docker container/VM running on your laptop/desktop) where memory limitations shouldn't be as severe.
Upload or git push the composer.lock file.
Run composer install on the live server.
composer install will then read from the .lock file, fetching the exact same versions every time rather than finding the latest versions of every package. This makes your app less likely to break, and composer uses less memory.

Source: stackoverflow.com

Similar codes

5 votes212 views2 answers
Cmd download file
PHP
0 vote274 views1 answer
User input in oop php
PHP
0 vote228 views1 answer
Factorial in php
PHP
2 votes281 views2 answers
File exist check in laravel blade
PHP Laravel
0 vote288 views1 answer
Pusher
PHP
2 votes343 views1 answer
Laravel get list of columns in a table
PHP
0 vote250 views1 answer
Doctrine querybuilder print sql
PHP
0 vote275 views1 answer
Laravel disable config cache
PHP Laravel
0 vote244 views2 answers
How to get current location latitude and longitude in php
PHP
0 vote295 views1 answer
Newrelic apache virtual hosts
PHP