Bobcares

Installation failed deleting ./composer.json – How we fix it?

by | Feb 14, 2020

Are you looking to fix the “Composer installation failed deleting ./composer.json file” error?

Lack of enough server resources, missing package links, etc. are the common reasons for Composer installation failures.

At Bobcares, we often get requests to fix Composer errors, as a part of our Server Management Services.

Today, let’s see a brief guide on how our Support Engineers fixed the Composer error.

 

What is Composer?

Before getting into the error details, let’s have a quick look at the Composer.

The Composer is an application-level package manager. Installing PHP based applications like the Laravel framework, Doctrine, etc. requires some dependency installation and updates.

Composer makes the task of dependency management easier by checking and installing the required packages with appropriate versions.

 

Reasons for Installation failed deleting ./composer.json error

To use a Composer for any project, it needs a composer.json file. This file tells the Composer to download the needed dependencies. This file is usually auto-generated while adding any dependency using the require command.

But sometimes while executing the command composer require <package name> the installation fails. Then it shows the error message as “Installation failed deleting ./composer.json”. It displays the exact reason for the error along with it. It can be due to incorrect package links, memory constraints and many more.

Recently, a customer approached us to fix an error he got while installing the Composer. The customer was trying to install the Laravel framework. And the error message appeared as,

Installation failed deleting ./composer.json

Here the error message specifies that there is no enough space, hence it checked for the swap. As there was no memory space and swap, the Composer installation failed.

Now let’s see how our Support Engineers fixed this error.

 

How we fix the error “Installation failed deleting ./composer.json”?

So far we have seen the reason for the error. Here, the error clearly says that the server is lacking memory for the installation. And one way to resolve this error is to allocate more memory.

Initially, when we get such an error our Support Engineers check the available resources in the server. We check this using the free -m command. This gives a complete picture of both memory and the swap space in the server.

If the server lacks memory space, we ask the customer to add more RAM space.

However, adding more RAM may not be possible in all scenarios. Alternatively, by checking the server space we can also allocate swap space. Usually, this can complete the Composer installation.

Allocating swap space can be recommended when the memory requirement is only for initialization. But this has a downside of slowing down the server.

Here, in this case, our Support Engineers analyzed the server space, memory usage, and performance of the server. Later, we suggested the customer add more RAM to the server. This solved the error and Composer started working fine.

In many error scenarios, the exact reason will be PHP version or missing modules, non-existing package URLs, etc. Therefore, the fix involves installing the missing modules, using valid package URLs in Composer.

 

[Still, having trouble in fixing Composer errors? – We can help you.]

 

Conclusion

In short, Composer installation failed deleting ./composer.json error happens due to lack of enough server memory, incorrect package links, etc. Today, we saw how our Support Engineers troubleshoot and fix this error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF