Cannot build on cPanel/SSH | Laravel + Vue
I have a cPanel server. I have ssh access to the server. Once I have pulled the new changes/files via Git, I ran npm run build. It gave me the following error.
https://i.stack.imgur.com/JaUDG.png
How do I fix this error? I checked the file/directory permissions and they were 644/755 respectively. I searched online and could not found a solution.
How do I fix this error? I checked the file/directory permissions and they were 644/755 respectively. I searched online and could not found a solution.
-
Do you have "Shell Fork Bomb Protection" enabled? I had issues with Laravel development and cPanel support said I *had* to disable fork bomb protection. 0 -
That's a good idea, @bellwood - I'm not sure of anything on the cPanel side that would contribute to that particular error as that is typically caused by a race condition within the application. 0 -
@bellwood and @cPRex - Thanks for responses. I found this article about 'Shell Fork Bomb Protection': Shell Fork Bomb Protection | cPanel & WHM Documentation I don't have WHM access. I asked them to disable it for me. I'll update here if it resolved my issue. 0 -
@bellwood, it is disabled already. See the following screenshot. And, if I try to run `npm run build`, the following error is diplayed. Please help to fix this one. 0 -
Very odd, as, your output for ulimit states that -u is 35, but, vite is saying that you already have 12 and is hitting a limit. On my host that runs Laravel (CentOS 7, Fork Bomb turned off) 'ulimit' on the shell simply states 'unlimited', and 'ulimit -u' is MUCH higher than yours. So, beyond Fork Bomb protection, your host has other limits in place. Are you on a Cloudlinux kernel? If you run 'ps aux' in your shell how many processes do you have running? 0 -
'Fork Bomb' had not been disabled when I tested. After disabling 'ulimit -u' it increased to 4096. Thanks @bellwood for the support. 0 -
Glad you got it working, this one, too, drove me nuts for a while =) 0
Please sign in to leave a comment.
Comments
7 comments