Error exited with error code 128

I tried ‘RNVectorIcons’ package in my react native project using the following link react-native-vector-icons.I used pod install command in my terminal.But I got the following error in my terminal window.

Analyzing dependencies
Fetching podspec for `RNVectorIcons` from `../node_modules/react-native-vector-icons`
Downloading dependencies
Installing RNVectorIcons (4.6.0)
Installing React (0.11.0)
[!] /bin/bash -c 
set -e
npm install --production

npm WARN deprecated connect@2.8.3: connect 2.x series is deprecated
npm WARN deprecated babel-core@5.8.21: Babel 5 is no longer being maintained. Upgrade to Babel 6.
npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated line-numbers@0.2.0: Copy its ~20 LOC directly into your code instead.
npm WARN deprecated tough-cookie@1.2.0: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated coffee-script@1.6.3: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated formatio@1.1.1: This package is unmaintained. Use @sinonjs/formatio instead
npm WARN deprecated gulp-util@3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm ERR! Error while executing:
npm ERR! /usr/bin/git ls-remote -h -t git://github.com/facebook/react.git
npm ERR! 
npm ERR! undefined
npm ERR! exited with error code: 128

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/macmini1/.npm/_logs/2018-06-21T12_59_11_182Z-debug.log

my package.json file look like the following:

{
  "name": "sample",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "gulp": "gulp"
  },
  "dependencies": {
    "eslint": "4.19.1",
    "eslint-config-airbnb": "16.1.0",
    "eslint-config-airbnb-base": "12.1.0",
    "eslint-config-rallycoding": "3.2.0",
    "eslint-import-resolver-webpack": "0.10.0",
    "eslint-plugin-import": "2.12.0",
    "eslint-plugin-jsx-a11y": "6.0.3",
    "eslint-plugin-react": "7.8.2",
    "react": "16.3.1",
    "react-native": "0.55.4",
    "react-native-vector-icons": "4.6.0",
    "react-navigation": "2.3.1"
  },
  "devDependencies": {
    "babel-jest": "23.0.1",
    "babel-preset-react-native": "4.0.0",
    "jest": "23.1.0",
    "react-test-renderer": "16.3.1"
  },
  "jest": {
    "preset": "react-native"
  }

debug.log file is

1609 verbose stack Error: exited with error code: 128
1609 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/util/finished.js:12:19)
1609 verbose stack     at ChildProcess.emit (events.js:182:13)
1609 verbose stack     at maybeClose (internal/child_process.js:961:16)
1609 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:5)
1610 verbose cwd /Users/macmini1/Library/Caches/CocoaPods/Pods/Release/React/0.11.0-ab1a2
1611 verbose Darwin 17.0.0
1612 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "--production"
1613 verbose node v10.4.1
1614 verbose npm  v6.1.0
1615 error Error while executing:
1615 error /usr/bin/git ls-remote -h -t git://github.com/facebook/react.git
1615 error
1615 error undefined
1615 error exited with error code: 128
1616 verbose exit [ 1, true ]

How to solve this issue?

Doesn’t work in 5.5.1 with Node 8.9.1:

C:tools>npm install --verbose
npm install --verbose
npm info it worked if it ends with ok
npm verb cli [ 'C:\Program Files\nodejs\node.exe',
npm verb cli   'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
npm verb cli   'install',
npm verb cli   '--verbose' ]
npm info using npm@5.5.1
npm info using node@v8.9.1
npm verb npm-session feac14d5fa993067
npm info lifecycle tools@1.0.0~preinstall: tools@1.0.0
npm http fetch GET 200 https://registry.npmjs.org/babel-cli 160ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/babel-preset-react 161ms (from cache)
[...]
npm http fetch GET 200 https://registry.npmjs.org/longest 55ms (from cache)
npm http fetch GET 304 https://registry.npmjs.org/p-limit 138ms (from cache)
npm verb stack Error: exited with error code: 128
npm verb stack     at ChildProcess.onexit (C:Program Filesnodejsnode_modulesnpmnode_modulesmississippinode_modulesend-of-streamindex.js:39:36)
npm verb stack     at emitTwo (events.js:126:13)
npm verb stack     at ChildProcess.emit (events.js:214:7)
npm verb stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
npm verb cwd C:tools
npm verb Windows_NT 10.0.14393
npm verb argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "--verbose"
npm verb node v8.9.1
npm verb npm  v5.5.1
npm ERR! Error while executing:
npm ERR! C:Program FilesGitcmdgit.EXE ls-remote -h -t https://github.com/gulpjs/gulp.git
npm ERR!
npm ERR! fatal: Not a git repository: C:/tools/../../.git/modules/C/tools
npm ERR!
npm ERR! exited with error code: 128
npm verb exit [ 1, true ]

npm ERR! A complete log of this run can be found in:
npm ERR!     C:UsersContainerAdministratorAppDataRoamingnpm-cache_logs2017-11-17T20_36_20_543Z-debug.log

{
  "name": "tools",
  "version": "1.0.0",
  "babel": {
    "presets": [
      "env",
      "react",
      "stage-2"
    ]
  },
  "engines": {
    "node": "^8 || ^9",
    "npm": "^5"
  },
  "dependencies": {
    "autoprefixer": "^7.1.4",
    "babel-cli": "^6 <7",
    "babel-preset-env": "^1 <2",
    "babel-preset-react": "^6 <7",
    "babel-preset-stage-2": "^6 <7",
    "bower": "^1 <2",
    "coffee-script": "^1 <2",
    "csslint": "^1 <2",
    "gulp": "https://github.com/gulpjs/gulp.git#4.0",
    "gulp-babel": "^7.0.0",
    "gulp-coffee": "^2.3.4",
    "gulp-csslint": "^1.0.0",
    "gulp-if": "^2.0.2",
    "gulp-less": "^3.3.2",
    "gulp-postcss": "^7.0.0",
    "gulp-print": "^2.0.1",
    "gulp-rename": "^1.2.2",
    "gulp-sass": "^3.1.0",
    "gulp-sass-lint": "^1.3.4",
    "gulp-sourcemaps": "^2.6.1",
    "less": "^2.7.3",
    "mime": "^1 <2",
    "minimist": "^1.2.0",
    "node-sass": "^4 <5",
    "postcss-cli": "^4.1.1",
    "sass-lint": "^1 <2",
    "uglify-js": "^3 <4"
  }
}

Please don’t force me to use yarn

exited with an unexpected code: 128. Host key verification failed. fatal: Could not read from remote repository. #4479

Description

Just installed GitHub Desktop fresh. I opened a local cloned repo, commited a change and tried to push.

I suspect the issue is in the git binary that GH desktop is using.

Version

• GitHub Desktop:
  1.1.1
• Operating system:
  Microsoft Windows [Version 10.0.16299.371]

Steps to Reproduce

Install GitHub Desktop fresh. I opened a local cloned repo, commited a change and tried to push.

Expected Behavior

Actual Behavior

Authentication error modal

Additional Information

Have installed git for windows, git in cygwin and gitkraken. All these work in their own respective environments.

Relevant excerpt provided above

The text was updated successfully, but these errors were encountered:

Thanks for opening this @deed02392. The Host key verification failed error usually indicates an issue with SSH — did you clone this repository in GitHub Desktop, or did you clone it from another client using SSH?

I think I cloned it using GitKraken. I hope this helps.

@deed02392 thanks for the update. You can check the remote URL the repository is using from GitHub Desktop by going to the file menu and selecting Repository > Repository Settings > Remote . Let me know what that shows.

@deed02392 that’s all the information I needed, and it does indicate that this repository is using SSH.

There are two solutions for this:

1. Switch the remote URL to use HTTPS instead of SSH (you should not have any authentication issues as long as you are logged in with your GitHub Enterprise account in GitHub Desktop).
2. Get SSH working. The host key verification failed error means that the host key from GitHub Enterprise isn’t in your known_hosts file. You should be able to fix this by running the following command from Git Bash:

Replace with the URL of the GitHub Enterprise server you are connecting to.

Hope that helps. Let me know if that doesn’t get things working.

Thanks. Switching to HTTPS works, but I believe there are advantages to using SSH instead.

SSH cloning worked for this repository in the first place (from a cygwin environment). Adding the host key within the Git Bash environment succeeded, however this has not fixed the issue for GitHub Desktop. I think we need to review how GitHub Desktop uses SSH to determine why it isn’t working. E.g., does it use ‘ssh.exe’ from its processes PATH?

I believe there are advantages to using SSH instead.

Would you mind sharing these advantages and how using HTTPS does not fit into your workflow?

@iAmWillShepherd I did not say that HTTPS does not fit into my workflow.

I was just of the understanding that SSH was more secure than HTTPS because it used keys instead of authenticating with my username and password on every connect. I also perhaps mistakenly have the impression that SSH generally performs git operations faster than HTTPS.

Using HTTPS will be merely a workaround anyway.

I think this is a similar issue as #2085 so I’m going to close this. HTTPS should be a completely valid way to clone without any issues (I don’t think there’s a speed difference between the two but I could be mistaken), but we recognize that many people still prefer to use SSH so we’re tracking that as something to provide better support for in the future. Thanks!

Источник

npm5: git+ssh:// urls started to return error 128 #16830

I’m opening this issue because:

• npm is crashing.
• npm is producing an incorrect install.
• npm is doing something I don’t understand.
• Other (see below for feature requests):

What’s going wrong?

npm install git+ssh://git@github.mycompany.com:example/example.git url is producing npm ERR! exited with error code: 128 . It works like a charm with previous NPM versions.

How can the CLI team reproduce the problem?

I cannot provide our URL to you, but I guess every kind of git+ssh setup can produce this error.

supporting information:

• npm -v prints: 5.0.0
• node -v prints: v7.4.0
• npm config get registry prints: https://registry.npmjs.org/
• Windows, OS X/macOS, or Linux?: OSX
• Network issues:
  • Geographic location where npm was run:
  • I use a proxy to connect to the npm registry.
  • I use a proxy to connect to the web.
  • I use a proxy when downloading Git repos.
  • I access the npm registry via a VPN
  • I don’t use a proxy, but have limited or unreliable internet access.
• Container:
  • I develop using Vagrant on Windows.
  • I develop using Vagrant on OS X or Linux.
  • I develop / deploy using Docker.
  • I deploy to a PaaS (Triton, Heroku).

The text was updated successfully, but these errors were encountered:

The same error here as well for gitlab url.

782 silly fetchPackageMetaData error for git+ssh://git@gitlab.mycompany.com:group/package.git exited with error code: 128
783 verbose stack Error: exited with error code: 128
783 verbose stack at ChildProcess.onexit (/usr/lib/node_modules/npm/node_modules/mississippi/node_modules/end-of-stream/index.js:39:36)
783 verbose stack at emitTwo (events.js:125:13)
783 verbose stack at ChildProcess.emit (events.js:213:7)
783 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:197:12)
784 verbose cwd /home/risa/projects/msp/openimp-oauth2-server
785 verbose Linux 4.10.0-21-generic
786 verbose argv «/usr/bin/nodejs» «/usr/bin/npm» «update»
787 verbose node v8.0.0
788 verbose npm v5.0.0
789 error exited with error code: 128
790 verbose exit [ 1, true ]

I am getting the same error as those above, also for a self-hosted gitlab url.
It seems from multiple issues reported against npm5 relating specifically to git+ssh URLs.

Similar npm5 Issues with git+ssh URLs:
#16841
#16789
#16726

Источник

Git fetch failed with exit code: 128 #2116

Having issue with software on Hosted Agent?

Hi Team, I have problem with Hosted Agent. When I tried to build solution I got error on Get Sources Job
2019-02-20T05:56:43.5708405Z fatal: The remote end hung up unexpectedly
2019-02-20T05:56:43.5726175Z error: RPC failed; curl 52 Empty reply from server
2019-02-20T05:56:43.7161877Z ##[error]Git fetch failed with exit code: 128
2019-02-20T05:56:43.7174861Z ##[section]Finishing: Get Sources

On other project build works as Excepted, with only one I have problem.

Have you tried troubleshooting?

I have added git config —global http.postBuffer 157286400 sslVerify=false and nothing happend.

Agent Version and Platform

Agent: 2.120.2
VSTS: 16.131.27701.1

OS of the machine running the agent? Windows 10

If on-premises, which release?
TFS 2018.2

What’s not working?

Please include error messages and screenshots.[
_

Agent and Worker’s Diagnostic Logs

The text was updated successfully, but these errors were encountered:

@markofranjic i don’t think this is a problem about the agent, the agent invoke git.exe and it returns 128.
check your TFS AT’s event log, see whether there is any exceptions on server side.

@markofranjic i don’t think this is a problem about the agent, the agent invoke git.exe and it returns 128.
check your TFS AT’s event log, see whether there is any exceptions on server side.

I don’t see any error logs about TFS. I see only informations logs like this
TF200030: Team Foundation Server completed group synchronization for the following group: Sync Tree.

Incremental sync (current cycle start time (UTC) 20.2.2019. 16:00:11, cycle duration 1.00:00:00, number of syncs per cycle 24).

Application Domain: TfsJobAgent.exe
Service Host: f3a91bc8-f499-4f1f-a93a-be4146db3794 (TEAM FOUNDATION)

I can’t understand why Get Source works on other repository but on one repository I got 128 code error.

@markofranjic have you retry the build? are you getting 128 all the time for this repository?

@markofranjic have you retry the build? are you getting 128 all the time for this repository?

Yes I have retry build many times but not success. When I change repository, other project build works as excepted.

Only one project have that problem

@markofranjic make sure you check the TFS event log.

I think there must be some server problems, as the agent just use git.exe to fetch the repository.
if you can’t find any useful error in the TFS event log, you might want to open issue at https://developercommunity.visualstudio.com/spaces/22/index.html or ask for TFS customer support.

Unfortunately I see only logs from 2015, I will open issues to developer community

@markofranjic not that folder, 3 lines below on the left tree.

Microsoft-Team Foundations ServerDebug

I have checked that logs and I can see any logs which I can reference with exists problem wit build
Debug.zip

@markofranjic the event log has info after 2019-02-20T08:23:45 , the build log you shared is 2019-02-20T05:55:45 , have you tried another build after 2019-02-20T08:23:45 UTC ? i need some timestamp so i can link the event log and the agent log. 🙂

I have found error log. I have started build and I got this`

i am not sure that the right error, i would expect there are some message around git area.
do you might send me the log (build and event log)?

Time From: 20.02.2019 18:32.51
Time To: 20.02.2019 18:35.00

the event log has everything 2019-02-20T17:13:28.391762000Z , the build log shows the problem happened at 2019-02-20T17:28:54.5037277Z , you might want to re-save the log. 🙂

Huang Thank you,
You thing that

Authentication
FrameworkBasicAuthenticationModule.OnEndRequest
-1
1
2019-02-20T17:13:24.329285800Z
9454
JGit/3.7.0.201502260915-r
UnauthorizedRequestException
<00000000-0000-0000-0000-000000000000>
9454
1
false
Identity
4

Unauthorized is problem?

How I can authorize agent, because I have installed agent by standard procedure.
Why other project can build?

this is not the right error either, the error is coming form JGit/3.7.0.201502260915-r which is not the agent.

Sorry, above record is form jGit.
Did you think of beyond error?

If yes? What can I do that resolve this problem. I’m new in TFS and every help I appreciate

JGit/3.7.0.201502260915-r
UnauthorizedRequestException
TF400813: Resource not available for anonymous access. Client authentication required.

@markofranjic can you send me a new copy of your event log?

I have enclosed logs
—-new logs provided——
I have run build at 20.05:31 UTC+1
And failed at 20:05:53 UTC+1.

Many thanks for your help

Sorry, enclosed updated logs
Debug.zip

I find the error, but not sure what’s that means.
I will find someone to help me take a look, if i can find an answer to you, you might need to post the question to developer community.

Thank you very much for your help. I have posted question to developer community.

We’ll handle it there.

I have added git config —global http.postBuffer 157286400 sslVerify=false and nothing happend.

Please don’t forget to unset both of those settings ASAP.
sslVerify=false leaves you vulnerable to MITM attacks.
http.postBuffer is almost always useless nowadays. See https://docs.microsoft.com/en-us/azure/devops/repos/git/rpc-failures-http-postbuffer?view=azure-devops

i am going to close this issue here since it’s not scope to a problem within the agent.

Источник

Failed to execute git command: exit status 128 #3294

I recently upgraded to the most recent docker build. Now when I clone and push to a new repository I get this when running git push :

This is only when using the git protocol. If I use the http protocol I can clone and push, but when pushing I have to specify origin master like this git push origin master . I can’t just write git push , which I think used to work before.

The text was updated successfully, but these errors were encountered:

I figured out the origin master part. My package manager updated git, and it wanted me to run this to get the old behavior back:
git config —global push.default matching

Please show gogs log as required.

I created another test in order to provide the full sequence along with the corresponding log statements:

I then ran git push origin master it it worked OK:

Here’s the part of the log that corresponds to the transaction:

Please dump logs in log/serv.log file.

This is the serv.log

And just in case . this is the gogs.log :

I’m assuming that’s the version. I got it from running docker logs gogs and this printed (See last line):

Your Gogs version is far too old, please upgrade.

Yup — I just realized that it did not pull the upgrade the first time I attempted it. I just did a fresh image pull and I still get this error:

You can only go git push/pull after web UI is available to visit, from the log does not seem so, the migration is not finished.

Yes it did finish. I created the repository ole after the server was back up.

I guess it might be problem with volumed directory. cc @0rax

It seems like it’s a protocol issue. If I do git push origin master it works. I just repeated both tests to make sure. This is the git push origin master test.

Hi there, I have multiple question for you as I am not able to reproduce even the clone via ‘git@realm:orax/repo’.

Using just this url will ask me for a password, using ssh://git@realm:orax/repo will work as expected (incuding git push ).

Via https everything is also working as expected.

What is your local git version as well as your gogs version. What url are you given by Gogs when running it ? In the current version you only have an HTTP / HTTPS one and a SSH one (no old school git@. without any prefix).

I am really wondering how it is registered in your side via git / why you are able to clone without specifying the ssh:// protocol by default.

Can you give us the output of git remote show origin [with any url redacted if you wish] ?

Also can you check your

/.gitconfig for any weird option ?

Gogs version from logs:

So now I’ll visit my gogs URL (203.0.113.1:3000) and create a repo:

Then clone it, etc:

FAILURE:

SUCCESS:

Thanks that’s perfect, I will try to reproduce this with those exact version & git configuration !

Will keep you informed here !

Cool thanks — let me know if you need anything else 👍 I am using an SSH key which I’m sure you already guessed.

Just run this test in a ubuntu:14.04 container and on my Mac. Which contains the same version of git as you.

Note that I have my ssh port set to 2222 on my instance of Gogs, thus requiring me to create an ssh_config telling git & ssh to use port 2222 by default as the syntax you are using to clone does not accept a port.

Источник

Bug: Yarn fails to install (Exit code: 128) #3303

Comments

andrewhavens commented May 2, 2017

Do you want to request a feature or report a bug?

What is the current behavior?

Yarn fails to install and does not provide any helpful error message for debugging. I have already done this:

..but it has not made any difference.

If the current behavior is a bug, please provide the steps to reproduce.

Yarn seems to install in other projects. Inspecting the directory that is mentioned in the output:

What is the expected behavior?

I expect install to succeed or at least provide an actionable error message.

Please mention your node.js, yarn and operating system version.

• Node: 7.9.0
• Yarn: 0.23.3
• macOS Sierra 10.12.4

The text was updated successfully, but these errors were encountered:

EugeneHlushko commented May 3, 2017 •

Same thing, happened after yarn cache clean i run yarn

• node: 7.4.0
• yarn 0.23.2
• CentOS release 6.8 (Final)

EugeneHlushko commented May 3, 2017

Oh yes, if you fail to proceed with yarn install because of this error, just delete your lockfile ( yarn.lock ) and run yarn install again

xiankai commented May 18, 2017

I think this can result from trying to install a deleted git branch as well — I was using a custom fork over here apollographql/graphql-tag#52, but when it got merged/deleted, I started encountering a similar error:

Where on the last line, was the commit hash of the deleted branch. I switched to the main branch since the pull request had been merged, for my fix.

andrewhavens commented May 18, 2017

I think I found the reason for my original error. I think one of the packages that was linked to a branch had a commit deleted, or force-pushed updates. Unfortunately, I don’t know for sure and the yarn error message does not make it clear if that was the case or not.

bestander commented May 23, 2017

I think there are several issues discussed here.
We have fixed a git related issue in 0.25.
Feel free to open a new issue with steps to reproduce if it still remains.

jppellerin commented May 31, 2017

I was getting the same error when trying to yarn add our common library from bitbucket. After reading this and trying a few things without success I thought I’d try npm to see how it would behave. Also erroring out but I got a better error message :

ENOTEMPTY: directory not empty, rmdir ‘/mnt/c/Users/[user]/Documents/workspace/[project]/node_modules/common-js/dist’

Using WSL. Seems like it cannot remove the old directory properly.

I know this is probably unrelated to yarn, but thought I’d post anyways for information purposes.

juanca commented Jun 2, 2017

I got this same error. I was able to reproduce and fix the issue (it was direct mistake from me).

Basically, I have a git dependency (and it’s pointing a branch) that is tracked in the yarn lockfile. At some point during the day, I force pushed my git branch which clobbered the tracked sha. I verified that the clobbered sha was the git archive CLOBBERED_SHA presented in the error message.

The fix was to yarn upgrade (if you’re on latest). Otherwise, you can yarn add —force .

rally25rs commented Jul 24, 2018

I tend to get this error when using a github dependency and switching between branches.
For those that run into this issue, you can usually fix it by deleting the cace folder from the output.

Fix it by deleting: /Users/andrew/Library/Caches/Yarn/v1/.tmp/f1b469ac943bb80864be5dfa2512836d then rerun yarn.

I think yarn is reusing the cache directory, but git doesn’t like overwriting one branch with another in that directory.

Источник

npm5: git+ssh:// urls started to return error 128 #16830

Comments

matenadasdi commented May 31, 2017

I’m opening this issue because:

• npm is crashing.
• npm is producing an incorrect install.
• npm is doing something I don’t understand.
• Other (see below for feature requests):

What’s going wrong?

npm install git+ssh://git@github.mycompany.com:example/example.git url is producing npm ERR! exited with error code: 128 . It works like a charm with previous NPM versions.

How can the CLI team reproduce the problem?

I cannot provide our URL to you, but I guess every kind of git+ssh setup can produce this error.

supporting information:

• npm -v prints: 5.0.0
• node -v prints: v7.4.0
• npm config get registry prints: https://registry.npmjs.org/
• Windows, OS X/macOS, or Linux?: OSX
• Network issues:
  • Geographic location where npm was run:
  • I use a proxy to connect to the npm registry.
  • I use a proxy to connect to the web.
  • I use a proxy when downloading Git repos.
  • I access the npm registry via a VPN
  • I don’t use a proxy, but have limited or unreliable internet access.
• Container:
  • I develop using Vagrant on Windows.
  • I develop using Vagrant on OS X or Linux.
  • I develop / deploy using Docker.
  • I deploy to a PaaS (Triton, Heroku).

The text was updated successfully, but these errors were encountered:

risa commented May 31, 2017

The same error here as well for gitlab url.

782 silly fetchPackageMetaData error for git+ssh://git@gitlab.mycompany.com:group/package.git exited with error code: 128
783 verbose stack Error: exited with error code: 128
783 verbose stack at ChildProcess.onexit (/usr/lib/node_modules/npm/node_modules/mississippi/node_modules/end-of-stream/index.js:39:36)
783 verbose stack at emitTwo (events.js:125:13)
783 verbose stack at ChildProcess.emit (events.js:213:7)
783 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:197:12)
784 verbose cwd /home/risa/projects/msp/openimp-oauth2-server
785 verbose Linux 4.10.0-21-generic
786 verbose argv «/usr/bin/nodejs» «/usr/bin/npm» «update»
787 verbose node v8.0.0
788 verbose npm v5.0.0
789 error exited with error code: 128
790 verbose exit [ 1, true ]

nicmyers commented May 31, 2017 •

I am getting the same error as those above, also for a self-hosted gitlab url.
It seems from multiple issues reported against npm5 relating specifically to git+ssh URLs.

Similar npm5 Issues with git+ssh URLs:
#16841
#16789
#16726

Источник

npm install zeppelin-solidity exited with error code: 128 #17425

Comments

ilyadruzh commented Jun 25, 2017 •

I’m opening this issue because:

• npm is crashing.
• npm is producing an incorrect install.
• npm is doing something I don’t understand.
• Other (see below for feature requests):

What’s going wrong?

npm install npm install zeppelin-solidity is producing npm ERR! exited with error code: 128.

How can the CLI team reproduce the problem?

Command: npm install zeppelin-solidity

Excerpt from npm-debug.log:

307 silly resolveWithNewModule crypto-js@3.1.8 checking installable status
308 silly pacote range manifest for xhr2@* fetched in 30ms
309 silly resolveWithNewModule xhr2@0.1.4 checking installable status
310 silly pacote range manifest for xmlhttprequest@* fetched in 31ms
311 silly resolveWithNewModule xmlhttprequest@1.8.0 checking installable status
312 silly fetchPackageMetaData error for bignumber.js@git+https://github.com/debris/bignumber.js.git#94d7146671b9719e00a09c29b01a691bc85048c2 exited with error code: 128
313 verbose stack Error: exited with error code: 128
313 verbose stack at ChildProcess.onexit (/usr/lib/node_modules/npm/node_modules/mississippi/node_modules/end-of-stream/index.js:39:36)
313 verbose stack at emitTwo (events.js:125:13)
313 verbose stack at ChildProcess.emit (events.js:213:7)
313 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:197:12)
314 verbose cwd /home/ilyadruzhinin/myproject
315 verbose Linux 4.8.0-36-generic
316 verbose argv «/usr/bin/nodejs» «/usr/bin/npm» «install» «zeppelin-solidity»
317 verbose node v8.1.2
318 verbose npm v5.0.3
319 error exited with error code: 128
320 verbose exit [ 1, true ]

supporting information:

• npm -v prints: 5.0.3
• node -v prints: 8.1.2
• npm config get registry prints: https://registry.npmjs.org/
• Windows, OS X/macOS, or Linux?: Ubuntu

The text was updated successfully, but these errors were encountered:

Источник

npm5: git+ssh:// urls started to return error 128 #16830

Comments

matenadasdi commented May 31, 2017

I’m opening this issue because:

• npm is crashing.
• npm is producing an incorrect install.
• npm is doing something I don’t understand.
• Other (see below for feature requests):

What’s going wrong?

npm install git+ssh://git@github.mycompany.com:example/example.git url is producing npm ERR! exited with error code: 128 . It works like a charm with previous NPM versions.

How can the CLI team reproduce the problem?

I cannot provide our URL to you, but I guess every kind of git+ssh setup can produce this error.

supporting information:

• npm -v prints: 5.0.0
• node -v prints: v7.4.0
• npm config get registry prints: https://registry.npmjs.org/
• Windows, OS X/macOS, or Linux?: OSX
• Network issues:
  • Geographic location where npm was run:
  • I use a proxy to connect to the npm registry.
  • I use a proxy to connect to the web.
  • I use a proxy when downloading Git repos.
  • I access the npm registry via a VPN
  • I don’t use a proxy, but have limited or unreliable internet access.
• Container:
  • I develop using Vagrant on Windows.
  • I develop using Vagrant on OS X or Linux.
  • I develop / deploy using Docker.
  • I deploy to a PaaS (Triton, Heroku).

The text was updated successfully, but these errors were encountered:

risa commented May 31, 2017

The same error here as well for gitlab url.

782 silly fetchPackageMetaData error for git+ssh://git@gitlab.mycompany.com:group/package.git exited with error code: 128
783 verbose stack Error: exited with error code: 128
783 verbose stack at ChildProcess.onexit (/usr/lib/node_modules/npm/node_modules/mississippi/node_modules/end-of-stream/index.js:39:36)
783 verbose stack at emitTwo (events.js:125:13)
783 verbose stack at ChildProcess.emit (events.js:213:7)
783 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:197:12)
784 verbose cwd /home/risa/projects/msp/openimp-oauth2-server
785 verbose Linux 4.10.0-21-generic
786 verbose argv «/usr/bin/nodejs» «/usr/bin/npm» «update»
787 verbose node v8.0.0
788 verbose npm v5.0.0
789 error exited with error code: 128
790 verbose exit [ 1, true ]

nicmyers commented May 31, 2017 •

I am getting the same error as those above, also for a self-hosted gitlab url.
It seems from multiple issues reported against npm5 relating specifically to git+ssh URLs.

Similar npm5 Issues with git+ssh URLs:
#16841
#16789
#16726

Источник

frontend_1 | npm ERR! exited with error code: 128 #796

Comments

kartikpshah commented May 26, 2020

docker-compose -f docker-compose.dev.yml up
I am getting below error.
error
backend_1 | Watching for file changes with StatReloader

frontend_1 | npm ERR! Error while executing:
frontend_1 | npm ERR! /usr/bin/git ls-remote -h -t git://github.com/adobe-webplatform/eve.git
frontend_1 | npm ERR!
frontend_1 | npm ERR! fatal: unable to connect to github.com:
frontend_1 | npm ERR! github.com[0: 140.82.118.3]: errno=Connection timed out
frontend_1 | npm ERR!
frontend_1 | npm ERR!
frontend_1 | npm ERR! exited with error code: 128

frontend_1 |
frontend_1 | npm ERR! A complete log of this run can be found in:
frontend_1 | npm ERR! /root/.npm/_logs/2020-05-26T20_26_04_942Z-debug.log
doccano_frontend_1 exited with code 1

Your Environment

• Operating System:
• Python Version Used:
• When you install doccano:
• How did you install doccano (Heroku button etc):

How to reproduce the problem

$ /usr/bin/git ls-remote -h -t git://github.com/adobe-webplatform/eve.git
fatal: unable to connect to github.com:
github.com[0: 140.82.118.4]: errno=Connection timed out

S46981@vc163: $
S46981@vc163: $ sudo /usr/bin/git ls-remote -h -t git://github.com/adobe-webplatform/eve.git
fatal: unable to connect to github.com:
github.com[0: 140.82.118.4]: errno=Connection timed out

The text was updated successfully, but these errors were encountered:

Источник

We have several Windows 2003 servers that we run utilities on using psexec. Recently, it stopped working on one of them. For those unfamiliar with it, here’s how the process normally works:

Psexec:

1. copies PSEXESVC.exe to \targetadmin$ (Typically C:WINDOWS)
2. installs it as a service and starts it
3. communicates with the service to have the service start the requested program
4. has the service wait for the exit status of the process
5. displays the exit status to the user
6. stops and deletes the service
7. removes PSEXESVC.exe

On the affected server, I have verified everything happens except something in step 3. No matter what program I ask psexec to run (cmd, ping, ipconfig, etc.), it gives the message «command exited on target with error code 128.»

This has been seen a few times on the sysinternals forums:

• PSEXEC returns 128
• error code 128
• psexec error 128 one way only

Some claim that the error is returned by the called command, but I think this is just an artifact of the way it’s trying to get the exit code. net helpmsg 128 gives «There are no child processes to wait for.», so this makes me think it’s failing to wait for the child because there isn’t one.

I’ve verified that the service is in fact starting correctly, that the permissions to the requested program are identical between the working servers and the non-working server, and that psexec works if running from the affected server as local (e.g. with psexec cmd instead of psexec \target cmd).

The only confirmed solution I’ve seen to this is rebooting the machine. While this is a production server, rebooting during the day is an option since its primary workload is batch style processing at night. However, I am hesitant to reboot, since I would really like to determine the cause of the psexec trouble, and right now the psexec process is being used for development purposes, so there’s no production impact to holding off on the reboot.