DocPad returned a non-zero status code

problem
docpad
Tags: #<Tag:0x00007f10ee2ce0b0> #<Tag:0x00007f10ee2cd688>

#1

When i started the command “docpad run” inside the created project folder and choosed “No Skeleton”, i got a lot of error-messages - here is the full text of the first message:

info: Installing the No Skeleton skeleton into D:\Dat\proj\docpadtest
This can take a moment…
npm ERR! Windows_NT 6.1.7601
npm ERR! argv “C:\Program Files\nodejs\node.exe” “C:\Users\Thomas\AppData
\Roaming\npm\node_modules\npm\bin\npm-cli.js” “install”
npm ERR! node v4.0.0
npm ERR! npm v3.4.1
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read

npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settin
gs.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network ‘proxy’ config is set properly. See: ‘npm help config’


Then some actions were done and the following error occured at least:

npm ERR! Windows_NT 6.1.7601
npm ERR! argv “C:\Program Files\nodejs\node.exe” “C:\Users\Thomas\AppData
\Roaming\npm\node_modules\npm\bin\npm-cli.js” “install”
npm ERR! node v4.0.0
npm ERR! npm v3.4.1

npm ERR! Callback called more than once.
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues

npm ERR! Please include the following file with any support request:
npm ERR! D:\Dat\proj\docpadtest\npm-debug.log
error: The action completed successfully
error: An error occured:

Error: Command exited with a non-zero status code.
at Object.safeps.prepareExecutableResult (C:\Users\Thomas\AppData\Roaming\npm
node_modules\docpad\node_modules\safeps\out\lib\safeps.js:190:24)
at ChildProcess. (C:\Users\Thomas\AppData\Roaming\npm\node_modules
docpad\node_modules\safeps\out\lib\safeps.js:322:29)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:817:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)

To report the above, follow the guide at: http://docpad.org/bug-report
Error: Command exited with a non-zero status code.
at Object.safeps.prepareExecutableResult (C:\Users\Thomas\AppData\Roaming\npm
node_modules\docpad\node_modules\safeps\out\lib\safeps.js:190:24)
at ChildProcess. (C:\Users\Thomas\AppData\Roaming\npm\node_modules
docpad\node_modules\safeps\out\lib\safeps.js:322:29)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:817:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)


The result is: i have two folders

  • node modules (with a lot of subfolders)
  • src (with the subfolders “documents”, “files”, “layouts” which are empty
    The project folder has the files: “docpad.coffee”, “npm-debug”, “package.json” and “readme.md”

I’m not behind a proxy!
What should i do now?


#2

Hey @fritzit :smiley:,

Is your code open anywhere on GitHub for example you may link it with us? :hand: :link:

Looks like you’re using Windows. This shouldn’t be the problem but I use Cloud9 for an on demand Ubuntu IDE myself. :wink:

Best,
Mike
:alien:


#3

That’s quite strange… To proceed further we will need to either see your code as @mikeumus has indicated or see the npm-debug.log file that is generated. Cheers!


#4

As the error occured with safeps, I think this may be resolved in v6.80 due to #1041 being accomplished.