What happens when composer executes the command prompt 'Killed'?
This article is written by the tutorial column of composer to introduce to you the problem of "Killed" when executing composer require after a while. I hope it will be helpful to friends in need!
Specific problem:
When executing composer require, it prompts "Killed" after a while
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
Solution:
Generally, insufficient memory causes the process to be killed.
If you cannot increase the physical memory, you can consider expanding the swap partition.
Reference is as follows:
composer error is killed when installing or updating because the current memory is insufficient.
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
The above is the detailed content of What happens when composer executes the command prompt 'Killed'?. For more information, please follow other related articles on the PHP Chinese website!
Hot AI Tools
Undresser.AI Undress
AI-powered app for creating realistic nude photos
AI Clothes Remover
Online AI tool for removing clothes from photos.
Undress AI Tool
Undress images for free
Clothoff.io
AI clothes remover
AI Hentai Generator
Generate AI Hentai for free.
Hot Article
Hot Tools
Notepad++7.3.1
Easy-to-use and free code editor
SublimeText3 Chinese version
Chinese version, very easy to use
Zend Studio 13.0.1
Powerful PHP integrated development environment
Dreamweaver CS6
Visual web development tools
SublimeText3 Mac version
God-level code editing software (SublimeText3)
Hot Topics
Composer's advanced features: aliases, scripts, and conflict resolution
Jun 03, 2024 pm 12:37 PM
Composer provides advanced features, including: 1. Aliases: define convenient names for packages for repeated reference; 2. Scripts: execute custom commands when installing/updating packages, used to create database tables or compile resources; 3. Conflict resolution: use priorities Rules, satisfaction constraints, and package aliases resolve the different requirements of multiple packages for the same dependency version to avoid installation conflicts.
Agile development and operation of PHP microservice containerization
May 08, 2024 pm 02:21 PM
Answer: PHP microservices are deployed with HelmCharts for agile development and containerized with DockerContainer for isolation and scalability. Detailed description: Use HelmCharts to automatically deploy PHP microservices to achieve agile development. Docker images allow for rapid iteration and version control of microservices. The DockerContainer standard isolates microservices, and Kubernetes manages the availability and scalability of the containers. Use Prometheus and Grafana to monitor microservice performance and health, and create alarms and automatic repair mechanisms.
What are the common ways to convert arrays to objects in PHP?
Apr 28, 2024 pm 10:54 PM
How to convert PHP array to object: use stdClass class, use json_decode() function, use third-party library (such as ArrayObject class, Hydrator library)
PHP code version control and collaboration
May 07, 2024 am 08:54 AM
PHP code version control: There are two version control systems (VCS) commonly used in PHP development: Git: distributed VCS, where developers store copies of the code base locally to facilitate collaboration and offline work. Subversion: Centralized VCS, a unique copy of the code base is stored on a central server, providing more control. VCS helps teams track changes, collaborate and roll back to earlier versions.
How to use Redis cache in PHP array pagination?
May 01, 2024 am 10:48 AM
Using Redis cache can greatly optimize the performance of PHP array paging. This can be achieved through the following steps: Install the Redis client. Connect to the Redis server. Create cache data and store each page of data into a Redis hash with the key "page:{page_number}". Get data from cache and avoid expensive operations on large arrays.
The role of PHP CI/CD in DevOps projects
May 08, 2024 pm 09:09 PM
PHPCI/CD is a key practice in DevOps projects that automates the build, test, and deployment processes to improve development efficiency and software quality. A typical PHPCI/CD pipeline consists of the following stages: 1) Continuous Integration: Whenever the code changes, the code is automatically built and tested. 2) Continuous deployment: Speed up delivery by automatically deploying tested and integrated code to the production environment. By implementing the PHPCI/CD pipeline, you can increase development efficiency, improve software quality, shorten time to market, and improve reliability.
How to use PHP CI/CD to iterate quickly?
May 08, 2024 pm 10:15 PM
Answer: Use PHPCI/CD to achieve rapid iteration, including setting up CI/CD pipelines, automated testing and deployment processes. Set up a CI/CD pipeline: Select a CI/CD tool, configure the code repository, and define the build pipeline. Automated testing: Write unit and integration tests and use testing frameworks to simplify testing. Practical case: Using TravisCI: install TravisCI, define the pipeline, enable the pipeline, and view the results. Implement continuous delivery: select deployment tools, define deployment pipelines, and automate deployment. Benefits: Improve development efficiency, reduce errors, and shorten delivery time.
Visualization technology of PHP data structure
May 07, 2024 pm 06:06 PM
There are three main technologies for visualizing data structures in PHP: Graphviz: an open source tool that can create graphical representations such as charts, directed acyclic graphs, and decision trees. D3.js: JavaScript library for creating interactive, data-driven visualizations, generating HTML and data from PHP, and then visualizing it on the client side using D3.js. ASCIIFlow: A library for creating textual representation of data flow diagrams, suitable for visualization of processes and algorithms.
