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/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
- This topic was modified 1 year, 9 months ago by Niklas.
The forum ‘OroCommerce’ is closed to new topics and replies.