Closed IuliiSe closed 7 years ago
sethetter
commented
7 years ago Can you log in as the deploy user to the box and run git clone https://phabricator.opengovfoundation.org/diffusion/1/madison.git?
If that works, go into config/deploy.rb and change the :repo_url setting to https://phabricator.opengovfoundation.org/diffusion/1/madison.git, then try to deploy again.
IuliiSe
commented
7 years ago @sethetter
I can git clone when logged as a user deploy.
BUT
Changing ssh:// to https:// in config/deploy.rb did not help to finish cap deploysuccessfully.
cap aborted!
scp: /tmp/madison/git-ssh.sh: Permission deniedmaybe there is an issue with :branch in deploy.rb ?
Explicitly ask for which branch to deploy from
ask :branch, `git rev-parse --abbrev-ref HEAD`.chomp@IuliiSe in the config/deploy/madison.rb file it should be setting the branch specifically.
Is there perhaps a permissions issue on the /tmp/madison folder?
IuliiSe
commented
7 years ago deploy user can access directory /tmp/madison , can cap and nano
deploy@correctIP:/tmp/madison$ cat git-ssh.sh
#!/bin/sh -e
exec /usr/bin/ssh -o PasswordAuthentication=no -o StrictHostKeyChecking=no "$@"
deploy@correctIP:/tmp/madison$ nano git-ssh.sh@sethetter ? what can i do?
sethetter
commented
7 years ago @IuliiSe it doesn't look like we can switch capistrano to allow https git clones. So you will need to create an ssh key for the deploy user on the box and add it to a user account that you create on https://phabricator.opengovfoundation.org.
IuliiSe
commented
7 years ago Now scripty fails
:~/madison# make watch
cd client && npm run watch
> madison@3.0.0-alpha watch /root/madison/client
> scripty
sh: 1: scripty: not found
npm ERR! Linux 4.4.0-45-generic
npm ERR! argv "/usr/local/nodejs-binary-4.4.5/bin/node" "/usr/local/bin/npm" "run" "watch"
npm ERR! node v4.4.5
npm ERR! npm v2.15.5
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! madison@3.0.0-alpha watch: `scripty`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the madison@3.0.0-alpha watch script 'scripty'.
npm ERR! This is most likely a problem with the madison package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! scripty
npm ERR! Please include the following file with any support request:
npm ERR! /root/madison/client/npm-debug.log
make: *** [watch] Error 1
root@SunLight4am:~/madison# npm -v
2.15.5
:~/madison# npm bugs madison
npm ERR! Linux 4.4.0-45-generic
npm ERR! argv "/usr/local/nodejs-binary-4.4.5/bin/node" "/usr/local/bin/npm" "bugs" "madison"
npm ERR! node v4.4.5
npm ERR! npm v2.15.5
npm ERR! path xdg-open
npm ERR! code ENOENT
npm ERR! errno ENOENT
npm ERR! syscall spawn xdg-open
npm ERR! enoent spawn xdg-open ENOENT
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! Please include the following file with any support request:
npm ERR! /root/madison/npm-debug.lognpm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/nodejs-binary-4.4.5/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'bugs',
1 verbose cli 'madison' ]
2 info using npm@2.15.5
3 info using node@v4.4.5
4 silly mapToRegistry name madison
5 silly mapToRegistry using default registry
6 silly mapToRegistry registry https://registry.npmjs.org/
7 silly mapToRegistry data Result {
7 silly mapToRegistry raw: 'madison',
7 silly mapToRegistry scope: null,
7 silly mapToRegistry name: 'madison',
7 silly mapToRegistry rawSpec: '',
7 silly mapToRegistry spec: 'latest',
7 silly mapToRegistry type: 'tag' }
8 silly mapToRegistry uri https://registry.npmjs.org/madison
9 verbose request uri https://registry.npmjs.org/madison/latest
10 verbose request no auth needed
11 info attempt registry request try #1 at 9:59:10 AM
12 verbose request id 88a54cf35037fb17
13 http request GET https://registry.npmjs.org/madison/latest
14 http 200 https://registry.npmjs.org/madison/latest
15 verbose headers { server: 'CouchDB/1.5.0 (Erlang OTP/R16B03)',
15 verbose headers etag: '"5705HG04ZYXSXHDULJFY1JHWI"',
15 verbose headers 'content-type': 'application/json',
15 verbose headers 'content-encoding': 'gzip',
15 verbose headers 'cache-control': 'max-age=300',
15 verbose headers 'content-length': '571',
15 verbose headers 'accept-ranges': 'bytes',
15 verbose headers date: 'Tue, 22 Nov 2016 09:59:10 GMT',
15 verbose headers via: '1.1 varnish',
15 verbose headers age: '0',
15 verbose headers connection: 'keep-alive',
15 verbose headers 'x-served-by': 'cache-lhr6324-LHR',
15 verbose headers 'x-cache': 'MISS',
15 verbose headers 'x-cache-hits': '0',
15 verbose headers 'x-timer': 'S1479808750.390445,VS0,VE312',
15 verbose headers vary: 'Accept-Encoding' }
16 silly get cb [ 200,
16 silly get { server: 'CouchDB/1.5.0 (Erlang OTP/R16B03)',
16 silly get etag: '"5705HG04ZYXSXHDULJFY1JHWI"',
16 silly get 'content-type': 'application/json',
16 silly get 'content-encoding': 'gzip',
16 silly get 'cache-control': 'max-age=300',
16 silly get 'content-length': '571',
16 silly get 'accept-ranges': 'bytes',
16 silly get date: 'Tue, 22 Nov 2016 09:59:10 GMT',
16 silly get via: '1.1 varnish',
16 silly get age: '0',
16 silly get connection: 'keep-alive',
16 silly get 'x-served-by': 'cache-lhr6324-LHR',
16 silly get 'x-cache': 'MISS',
16 silly get 'x-cache-hits': '0',
16 silly get 'x-timer': 'S1479808750.390445,VS0,VE312',
16 silly get vary: 'Accept-Encoding' } ]
17 verbose get saving madison to /root/.npm/registry.npmjs.org/madison/latest/.cache.json
18 verbose correctMkdir /root/.npm correctMkdir not in flight; initializing
19 silly bugs url https://github.com/mdb/madison/issues
20 verbose stack Error: spawn xdg-open ENOENT
20 verbose stack at exports._errnoException (util.js:870:11)
20 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
20 verbose stack at onErrorNT (internal/child_process.js:344:16)
20 verbose stack at nextTickCallbackWith2Args (node.js:442:9)
20 verbose stack at process._tickCallback (node.js:356:17)
21 verbose cwd /root/madison
22 error Linux 4.4.0-45-generic
23 error argv "/usr/local/nodejs-binary-4.4.5/bin/node" "/usr/local/bin/npm" "bugs" "madison"
24 error node v4.4.5
25 error npm v2.15.5
26 error path xdg-open
27 error code ENOENT
28 error errno ENOENT
29 error syscall spawn xdg-open
30 error enoent spawn xdg-open ENOENT
30 error enoent This is most likely not a problem with npm itself
30 error enoent and is relateIt looks like it's using npm 2, but you'll need to be using npm 3. That could be the issue here.
On Nov 22 2016, at 4:18 am, IuliiSe notifications@github.com wrote:
Now scripty fails
:~/madison# make watch cd client && npm run watch > madison@3.0.0-alpha watch /root/madison/client > scripty sh: 1: scripty: not found npm ERR! Linux 4.4.0-45-generic npm ERR! argv "/usr/local/nodejs-binary-4.4.5/bin/node""/usr/local/bin/npm" "run" "watch"
npm ERR! node v4.4.5 npm ERR! npm v2.15.5 npm ERR! file sh npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn npm ERR! madison@3.0.0-alpha watch: `scripty` npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the madison@3.0.0-alpha watch script 'scripty'. npm ERR! This is most likely a problem with the madison package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! scripty npm ERR! Please include the following file with any support request: npm ERR! /root/madison/client/npm-debug.log make: *** [watch] Error 1 root@SunLight4am:~/madison# npm -v 2.15.5 :~/madison# npm bugs madison npm ERR! Linux 4.4.0-45-generic npm ERR! argv "/usr/local/nodejs-binary-4.4.5/bin/node""/usr/local/bin/npm" "bugs" "madison"
npm ERR! node v4.4.5 npm ERR! npm v2.15.5 npm ERR! path xdg-open npm ERR! code ENOENT npm ERR! errno ENOENT npm ERR! syscall spawn xdg-open npm ERR! enoent spawn xdg-open ENOENT npm ERR! enoent This is most likely not a problem with npm itself npm ERR! enoent and is related to npm not being able to find a file. npm ERR! enoent npm ERR! Please include the following file with any support request: npm ERR! /root/madison/npm-debug.log 0 info it worked if it ends with ok 1 verbose cli [ '/usr/local/nodejs-binary-4.4.5/bin/node', 1 verbose cli '/usr/local/bin/npm', 1 verbose cli 'bugs', 1 verbose cli 'madison' ] 2 info using npm@2.15.5 3 info using node@v4.4.5 4 silly mapToRegistry name madison 5 silly mapToRegistry using default registry 6 silly mapToRegistry registry https://registry.npmjs.org/ 7 silly mapToRegistry data Result { 7 silly mapToRegistry raw: 'madison', 7 silly mapToRegistry scope: null, 7 silly mapToRegistry name: 'madison', 7 silly mapToRegistry rawSpec: '', 7 silly mapToRegistry spec: 'latest', 7 silly mapToRegistry type: 'tag' } 8 silly mapToRegistry uri https://registry.npmjs.org/madison 9 verbose request uri https://registry.npmjs.org/madison/latest 10 verbose request no auth needed 11 info attempt registry request try #1 at 9:59:10 AM 12 verbose request id 88a54cf35037fb17 13 http request GET https://registry.npmjs.org/madison/latest 14 http 200 https://registry.npmjs.org/madison/latest 15 verbose headers { server: 'CouchDB/1.5.0 (Erlang OTP/R16B03)', 15 verbose headers etag: '"5705HG04ZYXSXHDULJFY1JHWI"', 15 verbose headers 'content-type': 'application/json', 15 verbose headers 'content-encoding': 'gzip', 15 verbose headers 'cache-control': 'max-age=300', 15 verbose headers 'content-length': '571', 15 verbose headers 'accept-ranges': 'bytes', 15 verbose headers date: 'Tue, 22 Nov 2016 09:59:10 GMT', 15 verbose headers via: '1.1 varnish', 15 verbose headers age: '0', 15 verbose headers connection: 'keep-alive', 15 verbose headers 'x-served-by': 'cache-lhr6324-LHR', 15 verbose headers 'x-cache': 'MISS', 15 verbose headers 'x-cache-hits': '0', 15 verbose headers 'x-timer': 'S1479808750.390445,VS0,VE312', 15 verbose headers vary: 'Accept-Encoding' } 16 silly get cb [ 200, 16 silly get { server: 'CouchDB/1.5.0 (Erlang OTP/R16B03)', 16 silly get etag: '"5705HG04ZYXSXHDULJFY1JHWI"', 16 silly get 'content-type': 'application/json', 16 silly get 'content-encoding': 'gzip', 16 silly get 'cache-control': 'max-age=300', 16 silly get 'content-length': '571', 16 silly get 'accept-ranges': 'bytes', 16 silly get date: 'Tue, 22 Nov 2016 09:59:10 GMT', 16 silly get via: '1.1 varnish', 16 silly get age: '0', 16 silly get connection: 'keep-alive', 16 silly get 'x-served-by': 'cache-lhr6324-LHR', 16 silly get 'x-cache': 'MISS', 16 silly get 'x-cache-hits': '0', 16 silly get 'x-timer': 'S1479808750.390445,VS0,VE312', 16 silly get vary: 'Accept-Encoding' } ] 17 verbose get saving madison to/root/.npm/registry.npmjs.org/madison/latest/.cache.json
18 verbose correctMkdir /root/.npm correctMkdir not in flight;initializing
19 silly bugs url https://github.com/mdb/madison/issues 20 verbose stack Error: spawn xdg-open ENOENT 20 verbose stack at exports._errnoException (util.js:870:11) 20 verbose stack at Process.ChildProcess._handle.onexit(internal/child_process.js:178:32)
20 verbose stack at onErrorNT (internal/child_process.js:344:16) 20 verbose stack at nextTickCallbackWith2Args (node.js:442:9) 20 verbose stack at process._tickCallback (node.js:356:17) 21 verbose cwd /root/madison 22 error Linux 4.4.0-45-generic 23 error argv "/usr/local/nodejs-binary-4.4.5/bin/node""/usr/local/bin/npm" "bugs" "madison"
24 error node v4.4.5 25 error npm v2.15.5 26 error path xdg-open 27 error code ENOENT 28 error errno ENOENT 29 error syscall spawn xdg-open 30 error enoent spawn xdg-open ENOENT 30 error enoent This is most likely not a problem with npm itself 30 error enoent and is relate—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
IuliiSe
commented
7 years ago I get this after npm install -g npm
/usr/local/nodejs-binary-4.4.5/bin/npm -> /usr/local/nodejs-binary-4.4.5/lib/node_modules/npm/bin/npm-cli.js
/usr/local/nodejs-binary-4.4.5/lib
└── npm@4.0.2
:~/madison# make watch cd client && npm run watch
madison@3.0.0-alpha watch /root/madison/client scripty
sh: 1: scripty: not found
npm ERR! Linux 4.4.0-45-generic
npm ERR! argv "/usr/local/nodejs-binary-4.4.5/bin/node" "/usr/local/bin/npm" "run" "watch"
npm ERR! node v4.4.5
npm ERR! npm v4.0.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! madison@3.0.0-alpha watch: scripty
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the madison@3.0.0-alpha watch script 'scripty'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the madison package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! scripty
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs madison
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls madison
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! Please include the following file with any support request: npm ERR! /root/madison/client/npm-debug.log make: *** [watch] Error 1 root@SunLight4am:~/madison#
Have you run an npm i on the repo yet?
On Nov 22 2016, at 9:29 am, IuliiSe notifications@github.com wrote:
I get this after
npm install -g npm
/usr/local/nodejs-binary-4.4.5/bin/npm -> /usr/local/nodejs- binary-4.4.5/lib/node_modules/npm/bin/npm-cli.js
/usr/local/nodejs-binary-4.4.5/lib
└── npm@4.0.2
:~/madison# make watch
cd client && npm run watch
madison@3.0.0-alpha watch /root/madison/client
scriptysh: 1: scripty: not found
npm ERR! Linux 4.4.0-45-generic
npm ERR! argv "/usr/local/nodejs-binary-4.4.5/bin/node" "/usr/local/bin/npm" "run" "watch"
npm ERR! node v4.4.5
npm ERR! npm v4.0.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! madison@3.0.0-alpha watch:scripty
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the madison@3.0.0-alpha watch script 'scripty'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the madison package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! scripty
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs madison
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls madison
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?npm ERR! Please include the following file with any support request:
npm ERR! /root/madison/client/npm-debug.log
make: *\ [watch] Error 1
root@SunLight4am:~/madison#
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the
thread.
IuliiSe
commented
7 years ago Does anything need to be added? I just followed DEPLOY.md https://github.com/opengovfoundation/madison/blob/master/docs/DEPLOY.md
sethetter
commented
7 years ago I just pushed a commit to master to make scripty a regular npm dependency
instead of a devDependency, see if that helps.
On Nov 22 2016, at 9:37 am, IuliiSe notifications@github.com wrote:
Does anything need to be added?
I just followed DEPLOY.md https://github.com/opengovfoundation/madison/blob/m aster/docs/DEPLOY.md—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
IuliiSe
commented
7 years ago in what directory make watch needs to run?
:/var/www/vhosts/madison/current# make watch
wr: watching 42 files, running 'npm run compile'@IuliiSe you shouldn't need to run make watch. Doing the cap ... deploy from your local machine should take care of everything. make watch is only intended for doing local development work.
IuliiSe
commented
7 years ago why does it look like this then? http://46.101.113.225/
sethetter
commented
7 years ago Looks like the system you're on isn't interpreting that file as utf8. I added the charset annotation to the top of the file in master. Give it another go.
IuliiSe
commented
7 years ago Now deploy failed :(
** DEPLOY FAILED
** Refer to log/capistrano.log for details. Here are the last 20 lines:
DEBUG [da97fcc1] npm
DEBUG [da97fcc1]
DEBUG [da97fcc1] WARN
DEBUG [da97fcc1]
DEBUG [da97fcc1] deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
DEBUG [da97fcc1] npm
DEBUG [da97fcc1]
DEBUG [da97fcc1] WARN
DEBUG [da97fcc1]
DEBUG [da97fcc1] deprecated
DEBUG [da97fcc1] graceful-fs@2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in th…
DEBUG [da97fcc1]
> typechecker@2.0.8 preinstall /var/www/vhosts/madison/releases/20161122165508/client/node_modules/.staging/typechecker-9da3ba81
> node ./cyclic.js
DEBUG [da97fcc1]
DEBUG [da97fcc1]
DEBUG [da97fcc1] make:
DEBUG [da97fcc1] *** [deps-client] Error 1
DEBUG [da97fcc1]@IuliiSe I apologize for all the issues, it's difficult to debug through a GitHub issue.
The above issue doesn't appear to be related to the sass files. There's really no information in that debug output. Is there an npm-debug.log file you can show the contents of?
IuliiSe
commented
7 years ago npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/nodejs-binary-4.4.5/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'run',
1 verbose cli 'watch' ]
2 info using npm@4.0.2
3 info using node@v4.4.5
4 verbose run-script [ 'prewatch', 'watch', 'postwatch' ]
5 info lifecycle madison@3.0.0-alpha~prewatch: madison@3.0.0-alpha
6 silly lifecycle madison@3.0.0-alpha~prewatch: no script for prewatch, continuing
7 info lifecycle madison@3.0.0-alpha~watch: madison@3.0.0-alpha
8 verbose lifecycle madison@3.0.0-alpha~watch: unsafe-perm in lifecycle true
9 verbose lifecycle madison@3.0.0-alpha~watch: PATH: /usr/local/nodejs-binary-4.4.5/lib/node_modules/npm/bin/node-gyp-bin:/root/madison/client/node_modules/.bin:/usr/local/rvm/gems/ruby-2.2.3/bin:/usr/local/rvm/gems/ruby-2.2.3@global/bin:/usr/local/rvm/rubies/ruby-2.2.3/bin:/usr/local/rvm/bin:/root/.rbenv/plugins/ruby-build/bin:/root/.rbenv/shims:/root/.rbenv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
10 verbose lifecycle madison@3.0.0-alpha~watch: CWD: /root/madison/client
11 silly lifecycle madison@3.0.0-alpha~watch: Args: [ '-c', 'scripty' ]
12 info lifecycle madison@3.0.0-alpha~watch: Failed to exec watch script
13 verbose stack Error: madison@3.0.0-alpha watch: `scripty`
13 verbose stack spawn ENOENT
13 verbose stack at ChildProcess.<anonymous> (/usr/local/nodejs-binary-4.4.5/lib/node_modules/npm/lib/utils/spawn.js:33:16)
13 verbose stack at emitTwo (events.js:87:13)
13 verbose stack at ChildProcess.emit (events.js:172:7)
13 verbose stack at maybeClose (internal/child_process.js:827:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
14 verbose pkgid madison@3.0.0-alpha
15 verbose cwd /root/madison/client
16 error Linux 4.4.0-45-generic
17 error argv "/usr/local/nodejs-binary-4.4.5/bin/node" "/usr/local/bin/npm" "run" "watch"
18 error node v4.4.5
19 error npm v4.0.2
20 error file sh
21 error code ELIFECYCLE
22 error errno ENOENT
23 error syscall spawn
24 error madison@3.0.0-alpha watch: `scripty`
24 error spawn ENOENT
25 error Failed at the madison@3.0.0-alpha watch script 'scripty'.
25 error Make sure you have the latest version of node.js and npm installed.
25 error If you do, this is most likely a problem with the madison package,
25 error not with npm itself.
25 error Tell the author that this fails on your system:
25 error scripty
25 error You can get information on how to open an issue for this project with:
25 error npm bugs madison
25 error Or if that isn't available, you can get their info via:
25 error npm owner ls madison
25 error There is likely additional logging output above.
26 verbose exit [ 1, true ]It looks like the error came from trying to run npm run watch, which as I stated previously, isn't needed for deploy.
Are you running the cap .. deploy command from your local machine?
IuliiSe
commented
7 years ago I ran cap deployfrom droplet as root/madison. It switches to user deploy@IP, asks pass, and deploys.
IuliiSe
commented
7 years ago Here is the capistrano.log
DEBUG [b7007ac4] Error reading response length from authentication socket.
DEBUG [97e484f0] Error writing to authentication socket.
> (node-gyp rebuild 2> builderror.log) || (exit 0)
âââ assertion-error@1.0.0
âââ connect@2.30.2 (bytes@2.1.0, cookie@0.1.3, cookie-signature@1.0.6, utils-merge@1.0.0, pause@0.1.0, on-headers@1.0.1, content-type@1.0.2, fresh@0.3.0, vhost@3.0.2, parseurl@1.3.1, basic-auth-connect@1.0.0, cookie-parser@1.3.5, depd@1.0.1, qs@4.0.0, connect-timeout@1.6.2, serve-favicon@2.3.2, debug@2.2.0, http-errors@1.3.1, response-time@2.3.2, type-is@1.6.14, morgan@1.6.1, finalhandler@0.4.0, method-override@2.3.7, express-session@1.11.3, multiparty@3.3.2, serve-static@1.10.3, compression@1.5.2, errorhandler@1.4.3, csurf@1.8.3, body-parser@1.13.3, serve-index@1.7.3)
DEBUG [465340a4] [31m error[0m app/sass/style.scss (Line 169 of app/sass/modules/_global.scss: Invalid US-ASCII character "\xC2")
DEBUG [465340a4] Error: Error: scripty - script "fail" failed by exiting with a non-zero code (1).
DEBUG [465340a4] Error: Error: scripty - script "fail" failed by exiting with a non-zero code (1).
DEBUG [465340a4] Error: Error: scripty - script "fail" failed by exiting with a non-zero code (1).
> (node-gyp rebuild 2> builderror.log) || (exit 0)
â â â â â â ââ⬠error-ex@1.3.0
â âââ assertion-error@1.0.0
â â ââ⬠errorhandler@1.4.3
â â ââ⬠http-errors@1.3.1
â â â â âââ verror@1.3.6
DEBUG [eb0f9a63] [31m error[0m app/sass/style.scss (Line 169 of app/sass/modules/_global.scss: Invalid US-ASCII character "\xC2")
DEBUG [eb0f9a63] Error: Error: scripty - script "fail" failed by exiting with a non-zero code (1).
DEBUG [eb0f9a63] Error: Error: scripty - script "fail" failed by exiting with a non-zero code (1).
DEBUG [eb0f9a63] Error: Error: scripty - script "fail" failed by exiting with a non-zero code (1).
DEBUG [da97fcc1] *** [deps-client] Error 1
DEBUG [fd9694ff] *** [deps-client] Error 1OK. @sethetter Thank you! Big time! Success. Needed to look at chef prepare, chef cook, deploy again.
sethetter
commented
7 years ago @IuliiSe great! It looks like ruby wasn't able to access a UTF-8 encoding for the scss files to compile. Strange. Any idea which fixed it?
IuliiSe
commented
7 years ago nope. if it becomes clear i will notify. what's up with the labels on the interface? Like ''MENU.NAV.HOME''? how to test admin login?
sethetter
commented
7 years ago @IuliiSe Looks like you don't have the APP_URL and/or COOKIE_DOMAIN configured correctly in server/.env. On the server it should be /var/www/vhosts/yourappname/shared/server/.env. So sessions aren't working yet. Make sure to configure everything necessary in there.
The language tags are a known issue. They only show up on first page load then the locale file should be downloaded and cached. A refresh should make them go away.
Default admin login is admin@example.com // password
IuliiSe
commented
7 years ago @sethetter Admin login works. Thanks.
In server/.envAPP_URL should point to domain name or directory root?
like that?
APP_URL=http://correctDomainName.eu
COOKIE_DOMAIN=.correctDomainName.euIs there a need to run make queue-listen ?
sethetter
commented
7 years ago @IuliiSe it should be running already. One of the chef recipes takes care of this. You can create a new user and make sure you receive an email to test. You will need to have the mail settings in .env configured first though.
IuliiSe
commented
7 years ago Thanks for the quick answers today! Have a nice one!
sethetter
commented
7 years ago Absolutely! Glad it all got worked out
On Nov 22, 2016 2:24 PM, "IuliiSe" notifications@github.com wrote:
Thanks for the quick answers today! Have a nice one!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/opengovfoundation/madison/issues/1065#issuecomment-262355312, or mute the thread https://github.com/notifications/unsubscribe-auth/AAoAjBeKsWagchj4dEilZVxd2ck4iop0ks5rA095gaJpZM4K3p5y .
IuliiSe
commented
7 years ago @sethetter Unfortunately, it's not over. More errors on my end.
madison-error.log in /var/log/apache2
[Wed Nov 23] [:error] [pid 23958] PHP Fatal error: Class 'App\\Http\\Controllers\\Hash' not found in /var/www/vhosts/madison/releases/20161122175616/server/app/Http/Controllers/RemindersController.php on line 98, referer: http://sunrise4am.eu/verification/resend
[2016-11-23] production.ERROR: exception 'Symfony\Component\Debug\Exception\FatalErrorException' with message 'Class 'App\Http\Controllers\Hash' not found' in /var/www/vhosts/madison/releases/20161122175616/server/app/Http/Controllers/RemindersController.php:98
Can it be a permission issue?
ls -ld /var/www/vhosts/madison/releases/20161122175616/server/app/Http/Controllers
drwxrwxr-x 3 deploy staff 4096 Nov 22ps aux | egrep '(apache|httpd)'
root 23136 0.0 2.8 350532 29340 ? Ss 17:18 0:00 /usr/sbin/apache2 -k start
www 23948 0.1 4.0 357648 41508 ? S 18:04 0:00 /usr/sbin/apache2 -k start
www 23951 0.0 3.3 356012 34548 ? S 18:04 0:00 /usr/sbin/apache2 -k startThe user www appeared from configure-sites.rb recipes mentioned above.
How can we solve & avoid this issue?
@sethetter what could be a problem?
capistrano.log shows this:
git-ssh.sh looks like this: