本篇内容主要讲解“如何解决composer执行命令提示已杀死问题”，感兴趣的朋友不妨来看看。本文介绍的方法操作简单快捷，实用性强。下面就让小编来带大家学习“如何解决composer执行命令提示已杀死问题”吧!

十年的武宁网站建设经验，针对设计、前端、开发、售后、文案、推广等六对一服务，响应快，48小时及时工作处理。成都全网营销的优势是能够根据用户设备显示端的尺寸不同，自动调整武宁建站的显示方式，使网站能够适用不同显示终端，在浏览器中调整网站的宽度，无论在任何一种浏览器上浏览网站，都能展现优雅布局与设计，从而大程度地提升浏览体验。创新互联从事“武宁网站设计”,“武宁网站推广”以来，每个客户项目都认真落实执行。

本文由composer教程栏目给大家介绍关于执行composer require 一会儿就提示“已杀死”问题，希望对需要的朋友有所帮助！

具体问题：

执行composer require 一会儿就提示“已杀死”

composer require voku/simple_html_dom -vvv
Reading ./composer.json
Loading config file ./composer.json
Checked CA file /etc/pki/tls/certs/ca-bundle.crt: valid
Failed to initialize global composer: Composer could not find the config file: /home/admin/.composer/composer.json
To initialize a project, please create a composer.json file as described in the https://getcomposer.org/ "Getting Started" section
Reading /home/wwwroot/vendor/composer/installed.json
Loading plugin EasyWeChatComposer\Plugin
Loading plugin think\composer\Plugin
Running 1.7.2 (2018-08-16 16:57:12) with PHP 7.1.18 on Linux / 2.6.32-696.16.1.el6.x86_64
Downloading https://repo.packagist.org/packages.json
Writing /home/admin/.composer/cache/repo/https---repo.packagist.org/packages.json into cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2013.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2014.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2015.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2016.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2017.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2018.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2019-01.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2019-04.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2019-07.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2019-10.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-archived.json from cache
Downloading http://repo.packagist.org/p/provider-latest%24502b160e3dcbe13f8c125df618d18632ebbad2402f1e07d96e00bf46c3da14ac.json
Writing /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-latest.json into cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/provider-voku$simple-html-dom.json from cache
Using version ^4.7 for voku/simple_html_dom
./composer.json has been updated
Reading ./composer.json
Loading config file ./composer.json
Failed to initialize global composer: Composer could not find the config file: /home/admin/.composer/composer.json
To initialize a project, please create a composer.json file as described in the https://getcomposer.org/ "Getting Started" section
Reading /home/wwwroot/vendor/composer/installed.json
Loading plugin EasyWeChatComposer\Plugin_composer_tmp0
Loading plugin think\composer\Plugin_composer_tmp1
Reading ./composer.lock
Loading composer repositories with package information
Downloading https://repo.packagist.org/packages.json
Writing /home/admin/.composer/cache/repo/https---repo.packagist.org/packages.json into cache
Updating dependencies (including require-dev)
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2013.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2014.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2015.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2016.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2017.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2018.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2019-01.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2019-04.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2019-07.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-2019-10.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-archived.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/p-provider-latest.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/provider-adbario$php-dot-notation.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/provider-clagiordano$weblibs-configmanager.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/provider-danielstjules$stringy.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/provider-guzzlehttp$guzzle.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/provider-mtdowling$jmespath.php.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/provider-alibabacloud$client.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/provider-symfony$polyfill-mbstring.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/provider-guzzlehttp$psr7.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/provider-guzzlehttp$promises.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/provider-psr$http-message.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/provider-ralouphie$getallheaders.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/provider-aliyuncs$oss-sdk-php.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/provider-doctrine$cache.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/provider-easywechat-composer$easywechat-composer.json from cache
Reading /home/admin/.composer/cache/repo/https---repo.packagist.org/provider-symfony$options-resolver.json from cache

解决办法：

一般是内存不足导致进程被杀死。

没办法增大物理内存的话可以考虑扩容 swap 分区。

参考如下：

composer 安装或者更新时报错killed ，因为当前内存不足。

free -m
mkdir -p /var/_swap_
cd /var/_swap_
#Here, 1M * 2000 ~= 2GB of swap memory
dd if=/dev/zero of=swapfile bs=1M count=2000
mkswap swapfile
swapon swapfile
echo “/var/_swap_/swapfile none swap sw 0 0” >> /etc/fstab
#cat /proc/meminfo
free -m

到此，相信大家对“如何解决composer执行命令提示已杀死问题”有了更深的了解，不妨来实际操作一番吧！这里是创新互联网站，更多相关内容可以进入相关频道进行查询，关注我们，继续学习！

当前题目：如何解决composer执行命令提示已杀死问题
网页URL：http://pwwzsj.com/article/gscses.html