oro:asset:install fails (timeout)

We have some problems when we try to install our assets.
Everytime we use the command “sudo php ./bin/console oro:assets:install –no-debug” (with or without sudo or debug) we get the following timeout error:

[OK] All assets were successfully installed.

Move “XXX/public/js/bowerassets” to “XXX/public/bundles/bowerassets”
Move “XXX/public/js/npmassets” to “XXX/public/bundles/npmassets”
Move “XXX/public/js/components” to “XXX/public/bundles/components”
Installing npm dependencies.
/usr/local/bin/npm
–no-audit
install
Done.
Building assets.
‘/usr/local/bin/node’ ‘vendor/oro/platform/build/node_modules/webpack/bin/webpack.js’ ‘–mode=production’ ‘–env.symfony=dev’ ‘–colors’

In Process.php line 1330:

The process “‘/usr/local/bin/node’ ‘vendor/oro/platform/build/node_modules/webpack/bin/webpack.js’ ‘–mode=production’ ‘–env.symfony=de
v’ ‘–colors'” exceeded the timeout of 300 seconds.

oro:assets:build [-w|–watch] [-i|–npm-install] [-h|–help] [-q|–quiet] [-v|vv|vvv|–verbose] [-V|–version] [–ansi] [–no-ansi] [-n|–no-interaction] [-e|–env ENV] [–no-debug] [–disabled-listeners DISABLED-LISTENERS] [–current-user CURRENT-USER] [–current-organization CURRENT-ORGANIZATION] [–] <command> [<theme>]

In CommandExecutor.php line 214:

The command terminated with an exit code: 1.

Is there any way to increase the timeout limit? Somehow the install command succeed from time to time… so we were able to load our styles.scss changes. But now even with an empty styles.scss file we get the timeout. We even tried to disable all custom bundles!
We would be grateful for any help!

we are using OroCommerce 3.1.17

best regards,
Niklas

• This topic was modified 2 years, 5 months ago by  Niklas.

Topic

[HulThParticipant]

+1

We have the same issue.

• This reply was modified 2 years, 5 months ago by  HulTh.

[Andrey YatsenkoModerator]

You can increase timeouts for npm install and webpack build commands with the configuration in config/config.yml file:
https://github.com/oroinc/platform/blob/master/src/Oro/Bundle/AssetBundle/Resources/doc/index.md#build_timeout

[HulThParticipant]

Thanks for reply. The increase works.

Now i get this errors:

Shell

ERROR in ./css/layout/custom/styles.css.scss Module build failed (from ../vendor/oro/platform/build/node_modules/mini-css-extract-plugin/dist/loader.js): ModuleNotFoundError: Module not found: Error: Can't resolve './bundles/orocustomtheme/FrontendBundle/fonts/asap-condensed/AsapCondensed-Bold.svg' in '/xxx/xxx/xxx/public/css/layout/custom' ERROR in ./css/layout/default/styles.css.scss Module build failed (from ../vendor/oro/platform/build/node_modules/mini-css-extract-plugin/dist/loader.js): ModuleNotFoundError: Module not found: Error: Can't resolve './bundles/oroform/default/images/icons/arrow-down--gray.svg' in '/xxx/xxx/xxx/public/css/layout/default'

1 2 3 4 5 6 7

ERROR in ./css/layout/custom/styles.css.scss Module build failed (from ../vendor/oro/platform/build/node_modules/mini-css-extract-plugin/dist/loader.js): ModuleNotFoundError: Module not found: Error: Can't resolve './bundles/orocustomtheme/FrontendBundle/fonts/asap-condensed/AsapCondensed-Bold.svg' in '/xxx/xxx/xxx/public/css/layout/custom'   ERROR in ./css/layout/default/styles.css.scss Module build failed (from ../vendor/oro/platform/build/node_modules/mini-css-extract-plugin/dist/loader.js): ModuleNotFoundError: Module not found: Error: Can't resolve './bundles/oroform/default/images/icons/arrow-down--gray.svg' in '/xxx/xxx/xxx/public/css/layout/default'

• This reply was modified 2 years, 5 months ago by  HulTh.

[Andrey YatsenkoModerator]

Do you have this error during the upgrade or after some changes in your application code?

[HulThParticipant]

After the Upgrade.

[Andrey YatsenkoModerator]

Please clarify, from what version do you upgrade an application?

[NiklasParticipant]

We did an upgrade from orocommerce 3.1.6 to 3.1.17

[NiklasParticipant]

Okay we have found our Problem.. we mistakenly included the default oro settings and variables like ‘bundles/orofrontend/default/scss/settings/global-settings.scss’ & – ‘bundles/orofrontend/default/scss/variables/page-content-config.scss’ in our assets.yml!

That’s why it took so long to execute the oro:asset:install command and why apparently the correct paths to fonts and images were not found.

[Author]

Replies