I recently subscribed to hostinger vps with 1GB ram. But i cannot run composer update.
[ErrorException]
proc_open(): fork failed - Cannot allocate memory
The problem is i cannot run composer update because of the RAM limitation. I tried setting the ram limit to 512m to 768m to -1 but it still doesnt work. I still get the RAM error Issue.
php -d memory_limit=512M /usr/local/bin/composer update
php -d memory_limit=768M /usr/local/bin/composer update
php -d memory_limit=-1 /usr/local/bin/composer update
I also tried the swap file but unfortunately, hostinger doesn't allow swap files. i cannot use the swapon command.
swapon: /swapfile: swapon failed: Operation not permitted
I am looking for help on the options so that I can run a laravel project on the vps with 1GB ram.
I tried all the suggestions on the docs but none helped.
https://getcomposer.org/doc/articles/troubleshooting.md#proc-open-fork-failed-errors
I am really in a bind here. Any help is greatly appreciated.
As pointed out by #apokryfos , running
composer update
on the development machine then committing the updated composer.lock file and then running
composer install
on the live server resolved the problem.
Thanks to all who answered.
We have setup running Phabricator in one of our servers. Today I upgrade it by following the standard steps given in "https://secure.phabricator.com/book/phabricator/article/upgrading/" upgrade note.
When I try to start pdh using systemctl start phabricator-phd it get fails.
Error is
ERROR: Unable to load libphutil. Update your PHP 'include_path' to include the parent directory of libphutil/.
I tried other different way to start it but all of the giving this same error.
Hope someone can help me to solve this issue.
in the folder where arcanist/ is
git clone https://github.com/phacility/libphutil.git
This solved my problem.
Using git clone https://github.com/phacility/libphutil.git like #Youngjae Ji recommends doesn't work anymore. Take a look at that repo now. There's nothing in it! https://github.com/phacility/libphutil. A work-around seems to be the following, however:
sudo apt install libphutil then dpkg -L libphutil to see where it's located on your system. Once you find out where it is (ex: /usr/share/libphutil), symbolically link to it in arcanist as follows: ln -s /usr/share/libphutil path_to_arcanist/externals/includes. Now it should work.
Typically phd is restarted via bin/phd restart. Does this work? If yes, then the issue is your startup script. If no, then Phabricator likely wasn't installed correctly.
Fixed.
It was a permission issue. below fixed it.
chmod g+rX,o+rX libphutil/ -Rc
chmod g+rX,o+rX arcanist/ -Rc
chmod g+rX,o+rX phabricator/ -Rc
I have met the same problem.One way to solve: just put libphutil, arcanist, phabricator(the websever started) on same path
when I input hhvm command. Terminal deoesn't response.
[environment]
Ubuntu 15.10
HipHop VM 3.11.0
Composer 1.0-dev
vagrant#vagrant-ubuntu-trusty:/var/www/html$ cat test2.hh
<?hh
require_once 'vender/facebook/xhp-lib/init.php';
echo <p>test</p>;
vagrant#vagrant-ubuntu-trusty:/var/www/html$ sudo hhvm test2.hh
Why??
If I remove .hhconfig file and input "touch .hhconfig" command, "hhvm test.hh" success one time.
But, I re-try "hhvm test.hh" and no-response....
vagrant#vagrant-ubuntu-trusty:/var/www/html/project$ sudo rm .hhconfig
vagrant#vagrant-ubuntu-trusty:/var/www/html/project$ sudo touch .hhconfig
vagrant#vagrant-ubuntu-trusty:/var/www/html/project$ sudo hhvm test.hh
<p>test</p>vagrant#vagrant-ubuntu-trusty:/var/www/html/project$
vagrant#vagrant-ubuntu-trusty:/var/www/html/project$ sudo hhvm test.hh
^Cvagrant#vagrant-ubuntu-trusty:/var/www/html/project$
I guess some service got lock of .hhconfig file...
Does someone give me hint??
I strongly suspect you are running into this issue with hh_client, which affects hhvm since the latter calls into the former. We are investigating it now, and will release 3.11.1 to fix it when we pin down the problem.
In the meantime, you can use the 3.9 LTS, or you can try passing -d hhvm.hack.lang.auto_typecheck=0 when invoking hhvm. (Though if you do the latter, make sure to stop doing that when 3.11.1 is out, since it removes protection against Hack type errors sneaking into your code!)
This is going to be easy one I guess. On my OS X - Yosemite I have copied composer.phar to my /usr/bin directory. I have been using it for a while but today I needed to run "composer update". It didnt work of course so I ran "sudo composer update". Then I got the message "command composer not found". Chmm
I copied composer to /usr/local/bin according to the documentation and now "sudo composer" works like charm. BUT when I run "composer" without sudo, it still uses the old one in "/usr/bin" directory. So I deleted it.
Now composer works only with sudo command. I get "Could not open input file: /usr/bin/composer.phar" otherwise. What should I do to point command "composer" to the new location in /usr/local/bin?
Another alternative to get a nice composer command instead of composer.phar:
$ curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin
$ ln -s /usr/local/bin/composer.phar /usr/local/bin/composer
Edit:
/etc/bashrc
Add this to that file:
alias composer="php /usr/local/bin/composer"
run:
source /etc/bashrc
Composer should now run without sudo.
Okay, I encountered issues of having to run composer commands with sudo as well, but in order to get it working without throwing this kind of error (in Ubuntu 15.10):
[ErrorException]
copy(/home/randomuser/.composer/cache/files/barryvdh/laravel-cors/056068736ff8f002514178e1416c7665732eaddc.zip): failed to open stream: Permission denied
What simply solved the issue for me is:
Navigating to my home directory $ cd
Changing the ownership of .composer with: sudo chown -R $USER:$USER .composer/
Then composer install works smoothly.
PS: this might be different for other situation.
Hope this helps :)
i will answer you how i solve it in my Ubuntu 16.10 and you can compare yours
my composer folder set in
/home/abdallah/.composer/
i only give this file the 777 permission so can be reached by any user group
sudo chmod -R 777 /home/abdallah/.composer/
and that is it
i hope this helpful for you
Judging from other answers it seems the solution can vary depending on your system. This is how I fixed the problem on Mac 10.12.
My composer executable in /usr/local/bin/composer had a different group than ~/.composer/ config and cache files.
/usr/local/bin/composer myusr admin
~/.composer/ myusr staff
The primary group for myusr is staff so I changed the group for /usr/local/bin/composer to staff.
/usr/local/bin myusr$ chgrp staff composer
Cache files that had been created when running composer as sudo in the past were still causing problems so I deleted those. Composer cache files are located here: ~/.composer/cache/
If updating hangs during composer update for a project check/empty cache files in the .composer directory for the project.
I got a problem, I tried to install a new package to my Laravel 4 project.
But when I run php composer.phar update I get this:
Loading composer repositories with package information
Updating dependencies (including require-dev)
Killed
I have looked for the problem in the Internet and saw that the memory is the problem, I think I don't have enough RAM available, I've checked this I have about 411mb free.
Does composer really need more RAM?
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.
Read more here: https://getcomposer.org/doc/01-basic-usage.md#installing-with-composer-lock
Alternatively, you can upload the entire vendor directory to the server, bypassing the need to run composer install at all, but then you should run composer dump-autoload --optimize.
If like me, you are using some micro VM lacking of memory, creating a swap file does the trick:
#Check free memory before
free -m
mkdir -p /var/_swap_
cd /var/_swap_
#Here, 2G ~ 2GB of swap memory. Feel free to add MORE
sudo fallocate -l 2G swapfile
chmod 600 swapfile
mkswap swapfile
swapon swapfile
#Automatically mount this swap partition at startup
echo "/var/_swap_/swapfile none swap sw 0 0" >> /etc/fstab
#Check free memory after
free -m
As several comments pointed out, don't forget to add sudo if you don't work as root.
btw, feel free to select another location/filename/size for the file.
/var is probably not the best place, but I don't know which place would be, and rarely care since tiny servers are mostly used for testing purposes.
Unfortuantely composer requires a lot of RAM & processing power. Here are a few things that I did, which combined, made the process bearable. This was on my cloud playpen env.
You may be simply running out of RAM. Enable swap: https://www.digitalocean.com/community/search?q=add+swap (note: I think best practice is to add a seperate partition. Digitalocean's guide is appropriate for their environment)
service mysql stop (kill your DB/mem-hog services to free some RAM - don't forget to start it again!)
use a secondary terminal session running top to watch memory/swap consumption until process is complete.
composer.phar update --prefer-dist -vvv (verbose output [still hangs at some points when working] and use distro zip files). Maybe try a --dry-run too?
Composer is apparently know to run slower in older versions of PHP (e.g. 5.3x). It was still slow in 5.5.9 for me...
DigitalOcean fix that does not require extra memory - activating swap, here is an example for 1gb:
in terminal run below
/bin/dd if=/dev/zero of=/var/swap.1 bs=1M count=1024
/sbin/mkswap /var/swap.1
sudo /sbin/swapon /var/swap.1
The above solution will work until the next reboot, after that the swap would have to be reactivated. To persist it between the reboots add the swap file to fstab:
sudo nano /etc/fstab
open the above file add add below line to the file
/var/swap.1 swap swap sw 0 0
now restart the server. Composer require works fine.
I've got this error when I ran composer install inside my PHP DOCKER container,
It's a memory issue.
Solved by increasing SWAP memory in DOCKER PREFERENCES from 512MB to 1.5GB
To do that:
Docker -> Preferences -> Rousources
Increase the memory limit for composer
php -d memory_limit=4G /usr/local/bin/composer update
Run composer self-update and composer clearcache
remove vendor and composer.lock
restart your local environment and then run
php -d memory_limit=-1 /usr/local/bin/composer install
If you're using docker you can use COMPOSER_PROCESS_TIMEOUT
environment:
COMPOSER_MEMORY_LIMIT: -1
COMPOSER_PROCESS_TIMEOUT: 2000 #seconds
Also in big projects composer needs more RAM than 2GB, you can check that with ps -aux while it is running.
You will have to add it manually inside docker options, nothing else will help.
Here's how I succeeded in installing maatwebsite\excel package from composer in Laravel Framework:
I download composer.json file and composer.lock file from my remote server.
I run composer update from local command prompt (then wait until all the install process finished).
Upload composer.lock file to remote server.
run composer install on remote server (then wait until all process finished).
DONE
composer 2 update have reduced the memory usage
composer self-update
composer update
composer require xxx
Fix for AWS ec2 Ubuntu Server Php Memory Value Upgrade For Magento 2.3.X
Php 7.2 / 7.3
nginx
ubuntu
composer 1.X
mariaDB
magento 2.3.X
Error : Updating dependencies (including require-dev)
Killed
for
Ram Must at least 4GB
Change instance type to suitable or Upgrade Ram
Php Memory Value change
Server Restart
Try to install the same package again
PHP value update
may locate under '/etc/php/7.2/fpm/php.ini'
depend on your server and PHP fpm X.XX version
Using Seed command 'change as your server requires'
on my case >> /etc/php/7.2/fpm/php.ini
memory limit type as "3.5G" or "3500MB"
Php 7.2.X
sudo sed -i "s/memory_limit = .*/memory_limit = 3.5G/" /etc/php/7.2/fpm/php.ini
Php 7.3.X
sudo sed -i "s/memory_limit = .*/memory_limit = 3.5G/" /etc/php/7.3/fpm/php.ini
Test if applied on 'free -h' command
free -h
Install-Package Again#
Install extension via Composer
go to your Magento 2 installation directory
cd /var/www/html/
with 'superuser' privileges
sudo su
Start installation
composer require XXXXXX/XXXXXXX
Enable Module s
php bin/magento module:enable XXXXXX/XXXXXXX
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
Restart
sudo reboot
Enjioy
I was facing this same issue on my ec2 instance, following steps worked for me :
Copied composer.lock file from my local environment to ec2.
then run sudo composer install and its simply installed all the dependencies for my project.
I solved it maintaining the below steps in my ubuntu server. Hope it will works for you.
Stop my apache server
sudo service apache2 stop
Run composer update
sudo composer update
Start my apache server
sudo service apache2 start
php -d memory_limit=5G composer.phar update
I get this problem caused for a package that don't update correctly with wildcards, I use directly the last version and it works finally.
"l3/cas-bundle": "~1.0" -------> "l3/cas-bundle": "1.1.13"
Solved on Laravel/Homestead (Vagrant Windows)
Edit Homestead.yaml and increase memory from 2048 to 4096
vagrant up
vagrant ssh
Install Symfony with this line on the folder you choose (must be without files)
COMPOSER_MEMORY_LIMIT=-1 composer create-project symfony/website-skeleton . -s dev
I was using:
Virtualbox
4096 Gb RAM
2 CPU
10 GB HDD (500 MB swap)
Ubuntu 20.04
Running:
composer update in a laravel 8 project folder
I didn't set the swap for the virtual machine, so Virtualbox created a 500Mb swap space, which was NOT enough.
So composer was using 4Gb of RAM plus swap.
I gave more swap space to the VM and then it worked.
As the picture below, composer used all my RAM + 2GB of swap
System Monitor
You can try setting preferred-install to "dist" in Composer config.
I was getting this error in a local Docker environment. I solved it by simply restarting Docker.