search

eirslett / frontend-maven-plugin

"Maven-node-grunt-gulp-npm-node-plugin to end all maven-node-grunt-gulp-npm-plugins." A Maven plugin that downloads/installs Node and NPM locally, runs NPM install, Grunt, Gulp and/or Karma.
Apache License 2.0
4.2k stars 868 forks source link

[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.10.0:npm #1148

Closed quoctri1 closed 4 weeks ago

quoctri1 commented 1 month ago

Suddenly 3 days ago I faced to this issue: [ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.10.0:npm (npm install) on project system-manager-ui: Failed to run task: 'npm install' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1]. IDK why it's weird cause it's just happened sometimes, now I use mvn version 3.6.3, java 11, frontend-maven-plugin: 1.10.0 image A little confuse, is it require resources or something else in node config? Thank you so much!!!

eirslett commented 1 month ago

If npm install failed, then there's probably a problem with npm? You'll see it somewhere in the logs.

quoctri1 commented 1 month ago

I added verbose option in mvn that show releate to CPU thread image

eirslett commented 1 month ago

You're looking at the wrong part of the build log - try scrolling up a bit! Or send the entire build log...

quoctri1 commented 4 weeks ago

not really relate to plugin @eirslett or pom config, cause I built by jenkins so multiple agent pods running on the same node in k8s, so when I move it to another node the same resource it will be fine. any recommends if happend in the future?

eirslett commented 4 weeks ago

Maybe a firewall issue on that node?

quoctri1 commented 4 weeks ago

Absolutely not, cause all nodes in the same subnet, not different anything in network. Just the resources issue or containerd service cause multiple pods in the same node so hit some default litmit. BTW so hard to debug, I didn't see anything.

eirslett commented 4 weeks ago

Could you just nuke the node and set it up from scratch maybe?

Or less invasive, nuke the ~/.npm folder which is the npm cache, similar to the ~/.m2 folder.

quoctri1 commented 4 weeks ago

thank you @eirslett, I'll try with that