I'm deploying a HELM chart using:
helm upgrade -i -f < RELEASE PARAMETERS >
When I run this locally in a custom docker image, the release works fine.
When I try to run the same release using the GilabRunner (self-hosted runners) I'm getting this error:
ERROR: Job failed: exit code 1
More details:
HELM Version:
version.BuildInfo Version:"v3.5.0"
Kubectl Version:
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-16T11:56:40Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Gitlab Runner Version:
Version: 13.2.2
Add more information
The output from --debug from gitlab-runner
Executing "step_script" stage of the job script job=job_id project=project_id runner=runner_id
Looking for image index.docker.io/repository... job=job_id project=project_id runner=runner_id
Removing container runner-runner_id-project-project_id-concurrent-0-e6d1019ef7fea87c-build-2 job=job_id project=project_id runner=runner_id
Disconnecting container runner-runner_id-project-project_id-concurrent-0-e6d1019ef7fea87c-build-2 from networks job=job_id project=project_id runner=runner_id
Removing container runner-runner_id-project-project_id-concurrent-0-e6d1019ef7fea87c-build-2 finished with error Error: No such container: runner-runner_id-project-project_id-concurrent-0-e6d1019ef7fea87c-build-2 (docker.go:845:0s) job=job_id project=project_id runner=runner_id
Creating container runner-runner_id-pro
job=job_id project=project_id runner=runner_id
Attaching to container container_id ... job=job_id project=project_id runner=runner_id
Starting container container_id ... job=job_id project=project_id runner=runner_id
Appending trace to coordinator... ok code=202 job=job_id job-log=0-2763 job-status=running runner=runner_id sent-log=894-2762 status=202 Accepted update-interval=3s
Executing build stage build_stage=after_script job=job_id project=project_id runner=runner_id
Skipping stage (nothing to do) build_stage=after_script job=job_id project=project_id runner=runner_id
Executing build stage build_stage=upload_artifacts_on_failure job=job_id project=project_id runner=runner_id
Skipping stage (nothing to do) build_stage=upload_artifacts_on_failure job=job_id project=project_id runner=runner_id
Skipping referees execution job=job_id project=project_id runner=runner_id
WARNING: Job failed: exit code 1 duration=7.163806778s job=job_id project=project_id runner=runner_id
Appending trace to coordinator... ok code=202 job=job_id job-log=0-3369 job-status=running runner=runner_id sent-log=2763-3368 status=202 Accepted update-interval=3s
Submitting job to coordinator... ok code=200 job=job_id job-status= runner=runner_id
Removing container container_id job=job_id project=project_id runner=runner_id
Disconnecting container container_id from networks job=job_id project=project_id runner=runner_id
Removing container container_id_2 job=job_id project=project_id runner=runner_id
Disconnecting container container_id_2 from networks job=job_id project=project_id runner=runner_id
Removing container container_id_3 job=job_id project=project_id runner=runner_id
Disconnecting container container_id_3 from networks job=job_id project=project_id runner=runner_id
Removed container container_id_3 job=job_id project=project_id runner=runner_id
Removed container container_id job=job_id project=project_id runner=runner_id
Removed container container_id_2 job=job_id project=project_id runner=runner_id
WARNING: Failed to process runner builds=0 error=exit code 1 executor=docker runner=runner_id
The main issue for this error is related to a previous step is creating a file under /root/.config
When I identify it, I set the --registry-config=~/.helm_config/helm/registry.json in the helm command and the issue was solved.
Related
MBP:~ Tim$ yarn create react-app my-app --template typescript
yarn create v1.22.19
[1/4] 🔍 Resolving packages...
[2/4] 🚚 Fetching packages...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
error An unexpected error occurred: "http://nexus.qcpaws.qantas.com.au/nexus/repository/npm-repo/fstream/-/fstream-1.0.11.tgz: getaddrinfo ENOTFOUND nexus.qcpaws.qantas.com.au".
info If you think this is a bug, please open a bug report with the information provided in "/Users/benli/.config/yarn/global/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/create for documentation about this command.
So when I use yarn to create React App, it will try to install a package from qantas.com.au
I worked at Qantas before, so I must have set the registry somewhere.
So far, I've tried:
run yarn cache clearn to clean the cache, not working
uninstall yarn globally and re-install again, not working
check yarn config list to list the config, but cannot find qantas.com related information
checked .npmrc and .yarnrc, but cannot find any clues
Can someone help me how to remove the nexus registry?
thanks
This is my first time using a Mac for react native dev so I installed
everything and made a project but when I try to run (npm run start) it gives
me an error. Thanks for the help if you can :)
jest-haste-map: Watchman crawl failed. Retrying once with node crawler.
Usually this happens when watchman isn't running. Create an empty .watchmanconfig file in your project's root folder or initialize a git or hg repository in your project.
Error: Watchman error: std::__1::system_error: open: /Users/struanmclean/Documents/Dovekie/App: Operation not permitted. Make sure watchman is running for this project. See https://facebook.github.io/watchman/docs/troubleshooting.
/Users/struanmclean/Documents/Dovekie/App/node_modules/metro-hermes-compiler/src/emhermesc.js:77
throw ex;
^
Error: std::__1::system_error: open: /Users/struanmclean/Documents/Dovekie/App: Operation not permitted
at BunserBuf. (/Users/struanmclean/Documents/Dovekie/App/node_modules/fb-watchman/index.js:95:23)
at BunserBuf.emit (node:events:527:28)
at BunserBuf.process (/Users/struanmclean/Documents/Dovekie/App/node_modules/bser/index.js:292:10)
at /Users/struanmclean/Documents/Dovekie/App/node_modules/bser/index.js:247:12
at processTicksAndRejections (node:internal/process/task_queues:78:11)
Emitted 'error' event on WatchmanWatcher instance at:
at Client. (/Users/struanmclean/Documents/Dovekie/App/node_modules/metro/node_modules/jest-haste-map/build/watchers/WatchmanWatcher.js:150:10)
at Client.emit (node:events:527:28)
at BunserBuf. (/Users/struanmclean/Documents/Dovekie/App/node_modules/fb-watchman/index.js:107:12)
at BunserBuf.emit (node:events:527:28)
at /Users/struanmclean/Documents/Dovekie/App/node_modules/bser/index.js:249:12
at processTicksAndRejections (node:internal/process/task_queues:78:11) {
watchmanResponse: {
error: 'std::__1::system_error: open: /Users/struanmclean/Documents/Dovekie/App: Operation not permitted',
version: '2022.06.13.00'
}
}
When I build mediasoup environment, come into dir "server". I use the command node server.js which results in the following error:
mediasoup:ERROR:Worker worker process failed [pid:undefined]: spawn /root/mediasoup-demo/server/node_modules/mediasoup/worker/out/Release/mediasoup-worker ENOENT
screenshot of the error
make sure you have all the requirements for the installation process https://mediasoup.org/documentation/v3/mediasoup/installation/
watchman warning:
opendir(/Users/mahamadouniakate/Library/Caches/CloudKit/com.apple.Safari) -> Operation not permitted. Marking this portion of the tree deleted
To clear this warning, run:
`watchman watch-del /Users/mahamadouniakate ; watchman watch-project /Users/mahamadouniakate`
INFO
03:35
Opening exp://127.0.0.1:19000 in iOS simulator
ERROR
03:35
opendir(/Users/mahamadouniakate/Library/Caches/CloudKit/com.apple.Safari) -> Operation not permitted. Marking this portion of the tree deleted
To clear this warning, run:
`watchman watch-del /Users/mahamadouniakate ; watchman watch-project /Users/mahamadouniakate`
ERROR
03:35
opendir(/Users/mahamadouniakate/Library/Caches/CloudKit/com.apple.Safari) -> Operation not permitted. Marking this portion of the tree deleted
To clear this warning, run:
`watchman watch-del /Users/mahamadouniakate ; watchman watch-project /Users/mahamadouniakate`
INFO
03:35
Tunnel ready.
ERROR
04:42
We noticed your tunnel is having issues. This may be due to intermittent problems with our tunnel provider. If you have trouble connecting to your app, try to Restart the project, or switch Host to LAN.
INFO
In my case it was because I had two directories called 'watchman', I don't know why this happened, just uncheck the repeated boxes in
Mac-> System Preferences -> Security and privacy -> Privacy
For me this solution works:
Run these commands one by one -
$ watchman watch-del-all
$ watchman shutdown-server
I am using a Macbook and when I try to create a React Native app, it throws ESOCKETTIMEDOUT error.
I have tried to clean the npm and yarn cache however it doesn't help.
react-native init AwesomeProject
This will walk you through creating a new React Native project in /Users/gaurang.shah/Documents/personal/code/mobile/AwesomeProject
Using yarn v1.13.0
Installing react-native...
yarn add v1.13.0
info No lockfile found.
[1/4] 🔍 Resolving packages...
[2/4] 🚚 Fetching packages...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
error An unexpected error occurred: "https://registry.yarnpkg.com/lodash/-/lodash-4.17.11.tgz: ESOCKETTIMEDOUT".
info If you think this is a bug, please open a bug report with the information provided in "/Users/gaurang.shah/Documents/personal/code/mobile/AwesomeProject/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
I am able to download the https://registry.yarnpkg.com/lodash/-/lodash-4.17.11.tgz file through my browser, so it can't be networking issue.
Stacktrace
Yarn version:
1.13.0
Node version:
11.10.0
Platform:
darwin x64
Trace:
Error: https://registry.yarnpkg.com/lodash/-/lodash-4.17.11.tgz: ESOCKETTIMEDOUT
at ClientRequest.<anonymous> (/usr/local/Cellar/yarn/1.13.0/libexec/lib/cli.js:130024:19)
at Object.onceWrapper (events.js:285:13)
at ClientRequest.emit (events.js:197:13)
at TLSSocket.emitRequestTimeout (_http_client.js:669:40)
at Object.onceWrapper (events.js:285:13)
at TLSSocket.emit (events.js:197:13)
at TLSSocket.Socket._onTimeout (net.js:447:8)
at listOnTimeout (timers.js:327:15)
at processTimers (timers.js:271:5)
npm manifest:
{"name":"AwesomeProject","version":"0.0.1","private":true,"scripts":{"start":"node node_modules/react-native/local-cli/cli.js start"}}
yarn manifest:
No manifest
Lockfile:
No lockfile
Had the same issue when retrieving big packages on a slow network. As suggested on this comment, increasing the network timeout for installing the packages worked for me.
Firstly, have your project directory created beforehand and then create a .yarnrc file inside of it having the following content:
network-timeout 600000
Now, just run the react-native init <project_name> command from the parent directory of your project as you did.
It is equivalent to running yarn like so:
yarn install --network-timeout 600000
If npm can be used, please use 'npm install' & it generates package-lock.json or 'yarn install --network-timeout <time in ms>' - generates yarn.lock. Both works for me.