Error: Could not find a valid build #1025

throne1986 · 2020-11-26T16:17:58Z

throne1986
Nov 26, 2020

I have followed all instructions in docs about running grouparoo on local machine in Linux system but unfortunatelly when I run npm start i get the following error


2020-11-26T11:35:53.887Z - info: using path "/var/www/intergration/node_modules/@grouparoo/core/api/files/development" for Grouparoo file storage 
modified your next.js environment with /var/www/intergration/.env
2020-11-26T11:35:54.142Z - emerg: Exception occurred in initializer `next` during start 
2020-11-26T11:35:54.142Z - emerg: Error with initializer step: "start" 
2020-11-26T11:35:54.143Z - emerg: Error: Could not find a valid build in the '/var/www/intergration/node_modules/@grouparoo/core/web/.next' directory! Try building your app with 'next build' before starting the server.
    at Server.readBuildId (/var/www/intergration/node_modules/next/dist/next-server/server/next-server.js:137:355)
    at new Server (/var/www/intergration/node_modules/next/dist/next-server/server/next-server.js:3:120)
    at Object.createServer [as default] (/var/www/intergration/node_modules/next/dist/server/next.js:2:638)
    at Next.start (/var/www/intergration/node_modules/ah-next-plugin/dist/initializers/next.js:60:49)
    at async Object.startFunction (/var/www/intergration/node_modules/actionhero/dist/classes/process.js:123:29)
    at async Object.asyncWaterfall (/var/www/intergration/node_modules/actionhero/dist/modules/utils/asyncWaterfall.js:47:23)
    at async Process.start (/var/www/intergration/node_modules/actionhero/dist/classes/process.js:198:13)
    at async main (/var/www/intergration/node_modules/@grouparoo/core/api/dist/grouparoo.js:31:5) 
2020-11-26T11:35:54.143Z - notice: stopping process... 
2020-11-26T11:35:54.151Z - info: actionhero member 192.168.254.128 has joined the cluster 
2020-11-26T11:35:54.247Z - notice: Stopping server: web 
2020-11-26T11:35:54.248Z - notice: Stopping server: websocket 
2020-11-26T11:35:54.257Z - notice: *** Actionhero Stopped *** 
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @grouparoo/app-example@0.0.1 start: `cd node_modules/@grouparoo/core && ./api/bin/start`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @grouparoo/app-example@0.0.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-11-26T11_35_55_435Z-debug.log
root@bonge-virtual-machine:/var/www/intergration

what do I need to do to solve this problem?

Answered by evantahler

Dec 8, 2020

@throne1986 I'm going to convert this to a Discussion because I don't think this is necessarily an Issue with Grouparoo.

View full answer

evantahler · 2020-11-26T17:54:43Z

evantahler
Nov 26, 2020
Maintainer

Hi @throne1986!

Can you let us know if there were any errors that happened when you ran npm install?

As part of npm install, npm run prepare should have also run, would would generate that "valid build" for the web UI. Try running npm run prepare again.

0 replies

throne1986 · 2020-12-08T16:40:05Z

throne1986
Dec 8, 2020
Author

Hi @evantahler I am very sorry for the late reply, I have family problems, tried running npm run prepare but I get the following error

> cd node_modules/@grouparoo/core && npm run prepare


> @grouparoo/core@0.1.25 prepare /var/www/intergration/node_modules/@grouparoo/core
> npm run build-api && npm run build-web && npm run thank-you


> @grouparoo/core@0.1.25 build-api /var/www/intergration/node_modules/@grouparoo/core
> ./api/bin/build

Building @grouparoo/core API...
@grouparoo/core API built in 22s


> @grouparoo/core@0.1.25 build-web /var/www/intergration/node_modules/@grouparoo/core
> cd web && next build

modified your next.js environment with /var/www/intergration/.env
info  - Using external babel configuration from /var/www/intergration/node_modules/@grouparoo/core/web/.babelrc.js
info  - Creating an optimized production build  
Failed to compile.

./scss/grouparoo.scss
Error: Missing binding /var/www/intergration/node_modules/node-sass/vendor/linux-x64-72/binding.node
Node Sass could not find a binding for your current environment: Linux 64-bit with Node.js 12.x

Found bindings for the following environments:
  - Linux 64-bit with Node.js 10.x

This usually happens because your environment has changed since running `npm install`.
Run `npm rebuild node-sass` to download the binding for your current environment.


> Build error occurred
Error: > Build failed because of webpack errors
    at build (/var/www/intergration/node_modules/next/dist/build/index.js:15:918)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @grouparoo/core@0.1.25 build-web: `cd web && next build`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @grouparoo/core@0.1.25 build-web script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-12-08T16_21_58_815Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @grouparoo/core@0.1.25 prepare: `npm run build-api && npm run build-web && npm run thank-you`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @grouparoo/core@0.1.25 prepare script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-12-08T16_21_58_878Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @grouparoo/app-example@0.0.1 prepare: `cd node_modules/@grouparoo/core && npm run prepare`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @grouparoo/app-example@0.0.1 prepare script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-12-08T16_21_58_934Z-debug.log
root@bonge-virtual-machine:/var/www/intergration#

thanks

0 replies

evantahler · 2020-12-08T16:47:06Z

evantahler
Dec 8, 2020
Maintainer

I'm sorry to hear that! I hope everything will be OK soon.

Thank you for sharing the whole error. This confirms that there was a problem with your original run of npm install. Did you follow the instructions about how to rebuild node-sass:

This usually happens because your environment has changed since running npm install.
Run npm rebuild node-sass to download the binding for your current environment.

Alternatively, you could just remove node_modules within your Grouparoo project and nom install again to re-download all the dependencies.

0 replies

evantahler · 2020-12-08T16:49:57Z

evantahler
Dec 8, 2020
Maintainer

@throne1986 I'm going to convert this to a Discussion because I don't think this is necessarily an Issue with Grouparoo.

14 replies

evantahler Dec 9, 2020
Maintainer

Thanks!

It looks like the top of your .env file was cut off. Hopefully yours looks more like mine. This is the file created with npx grouparoo generate without modification:

#############
## GENERAL ##
#############

PORT=3000
WEB_URL=http://localhost:3000

WEB_SERVER=true
SCHEDULER=true
WORKERS=1
SERVER_TOKEN=my-serer-token

#############
## LOGGING ##
#############

# GROUPAROO_LOGS_STDOUT_DISABLE_COLOR=true
# GROUPAROO_LOGS_STDOUT_DISABLE_TIMESTAMP=true
# GROUPAROO_LOGS_PATH="/path/to/logs"

###########
## REDIS ##
###########

# To use an in-memory redis mock (no persistence)
REDIS_URL="redis://mock"

# To use a Redis Server
# REDIS_URL="redis://localhost:6379/0"

##############
## DATABASE ##
##############

# To use sqlite
DATABASE_URL="sqlite://grouparoo_development.sqlite"

# To use Postgres
# DATABASE_URL="postgresql://localhost:5432/grouparoo_development"

# With custom SSL options:
# DATABASE_SSL=true
# DATABASE_SSL_SELF_SIGNED=true

I've tested our install process on new docker container via the steps below, and everything seems to be OK. I've got a few more questions to pin this down:

Which version of Grouparoo are you running (check your package.json). Do the versions of your plugins match the version of @grouparoo/core?
Which version of Node.JS are you running? V12.x and V14.x are supported (run node -v to check)
Did your install process differ significantly from the Docker Test steps below?

It does look like we have a problem where npm prepare is not being run for your as part of the grouparoo generate command. The good news is that we are dropping the need for that in the forthcoming v0.2.0 release.

Docker Test Steps

Run a new Docker Container & expose port 3000 so we can use the web UI + API

docker run -p 3000:3000 -ti ubuntu

Update and Install

apt-get update && apt-get upgrade -y
apt-get install curl htop vim -y

Install NVM / Node

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.2/install.sh | bash
source ~/.bashrc
nvm install v14

Install Grouparoo

mkdir ~/grouparoo && cd ~/grouparoo
npx grouparoo generate (Why didn't this run npm prepare?)
npm run prepare

Run Grouparoo

npm run start

throne1986 Dec 9, 2020
Author

node v12.20.0,
grouparo version "@grouparoo/core": "0.1.25",

I used this instruction from grouparo docs

# Install NVM
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.3/install.sh | bash
nvm install v12 # install v12 of node.js
nvm use v12 # use v12 of node.js

sudo apt install redis-server # Install Redis

sudo apt install postgresql postgresql-contrib # Install Postgres
createdb grouparoo_development # Create a database for Grouparoo

evantahler Dec 11, 2020
Maintainer

I'm at a bit of a loss @throne1986 - it looks like you did everything right, and I'm not able to reproduce this error. Do you have time to jump on a video call together? Email me at help [at] grouparoo.com and we'll set something up!

throne1986 Dec 21, 2020
Author

Hi Now when I run npm run start I get the following error

evantahler Dec 21, 2020
Maintainer

It still looks like you are hitting https://127.0.0.1 rather than http://127.0.0.1 - The grouparoo server does not run an HTTPS port. Do you have another proxy server running (maybe Apache, guessing from the screenshot)?

Usually if you want to use a proxy server, you run the downstream server (Grouparoo) on a port (3000) or local-only socket that isn't exposed to the external world, and then the proxy reads the downstream server and exposes another port (say the normal https port 443). With that sort of configuration you would be trying https://localhost:443 in your browser. But in any case, can you confirm that the Grouparoo server works by itself without the proxy server?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error: Could not find a valid build #1025

{{title}}

Replies: 4 comments 14 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

Error: Could not find a valid build #1025

throne1986 Nov 26, 2020

Replies: 4 comments · 14 replies

evantahler Nov 26, 2020 Maintainer

throne1986 Dec 8, 2020 Author

evantahler Dec 8, 2020 Maintainer

evantahler Dec 8, 2020 Maintainer

evantahler Dec 9, 2020 Maintainer

Docker Test Steps

throne1986 Dec 9, 2020 Author

evantahler Dec 11, 2020 Maintainer

throne1986 Dec 21, 2020 Author

evantahler Dec 21, 2020 Maintainer

throne1986
Nov 26, 2020

Replies: 4 comments 14 replies

evantahler
Nov 26, 2020
Maintainer

throne1986
Dec 8, 2020
Author

evantahler
Dec 8, 2020
Maintainer

evantahler
Dec 8, 2020
Maintainer

evantahler Dec 9, 2020
Maintainer

throne1986 Dec 9, 2020
Author

evantahler Dec 11, 2020
Maintainer

throne1986 Dec 21, 2020
Author

evantahler Dec 21, 2020
Maintainer