mitranim / mitranim/epdf

how to solve Error: Command Failed problem

Open
#3 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
2
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Hello, Nice work. When I ran npm install -g epdf and execute epdf command below error is poping up. It is executing fine in local system. My local system has 8gb ram and i5 processor. My server is having 1gb ram and 1 core cpu. I am getting issue in the server. Is this anything related to low server specs?

{ Error: Command failed: /usr/local/lib/node_modules/epdf/node_modules/electron/dist/electron /usr/local/lib/node_modules/epdf/lib/epdf.js  --out="/tmp/epdf/474a04ae-1b27-4994-8881-88ae13682275.pdf"

    at ChildProcess.exithandler (child_process.js:275:12)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:925:16)
    at Socket.stream.socket.on (internal/child_process.js:346:11)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at Pipe._handle.close [as _onclose] (net.js:554:12)
  killed: false,
  code: 1,
  signal: null,
  cmd: '/usr/local/lib/node_modules/epdf/node_modules/electron/dist/electron /usr/local/lib/node_modules/epdf/lib/epdf.js  --out="/tmp/epdf/474a04ae-1b27-4994-8881-88ae13682275.pdf"' }

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure from the global npm installation with the epdf command on a 1GB, single-core server, then inspect lib/epdf.js and the Electron executable shown in the error. Determine why the command exits with code 1 and whether the resource difference is causal; done means recording a confirmed explanation and a reproducible fix or workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, javascript
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.