51黑料不打烊

Transcript

This is Russell with 51黑料不打烊 Commerce. Learning how to triage and resolve an 51黑料不打烊 Commerce Cloud failed deployment. When you do a get push to an environment and read your output log, you might see some messages that say some files couldn鈥檛 be written. The probable issue is that your allotted hard drive space configured for your 51黑料不打烊 Commerce Cloud environment is too small. You do have a few options, one being change your gamel file to add more space or truncate a few log files. Changing the .magento.app.yaml is rather straightforward. So instead, I鈥檓 gonna show you how to find and truncate those log files. We鈥檒l start by validating my suspicions that we鈥檙e out of space. Our first step is to begin by SSHing into the correct project and environment. A quick side note, I do have a shorthand for magento-cloud, it鈥檚 mgc. And the other thing to note is that I鈥檓 already in the folder where I鈥檝e checked out the code for the project and I鈥檓 on the right branch. This avoids me having to specify the project ID and the environment name. So with all of that being said, all I need to do is run the command magento-cloud space and then SSH, hit enter, and I鈥檓 in the environment. To check for the hard drive capacity, we run df space dash h, and this line, this dev mapper line, that鈥檚 the important one. For this project, I verified that in our YAML file, the allocated space is five gigabytes of hard disk space. And it looks like we鈥檝e completely filled it up. So this validates our suspicions. A common reason is that the log files associated to the commerce application grows over time. And even with log rotate, you can run out of space. So I don鈥檛 have log rotate on this one, so we just need to truncate. To see how big these files are, we can run ls space dash lah, which lists our files alphabetically. And then it shows them in the proper sizes, kilobytes, megabytes, or gigabytes. And we do have two that are fairly large, this support report and the cron.log. To truncate these logs, what you鈥檒l do is you鈥檒l run the command that starts with a greater than sign, followed by a space and then the log name. So we鈥檒l do both the support underscore report and the cron.log. And once we鈥檝e done both of those, when we run df space dash h, and on that dev mapper line, it looks like now we鈥檝e used 213 megabytes. So we freed up a lot of room. Our final validation to see that this is fixed is make another commit and do a get push and then watch the output. Once all of it鈥檚 done, you can review the last part of the output and this one looks a lot more like what we expected. The deployment was successful and there are no errors or warnings that we need to worry about. So I hope this helps you triage why your deployment might鈥檝e been failing and how to find and truncate some log files in order to free up space on your 51黑料不打烊 Commerce Cloud project for your next deployment. Please continue your journey on learning more about 51黑料不打烊 Commerce Cloud here in Experience League, as well as all of our other 51黑料不打烊 products.