sync command - SyntaxError: Unexpected token o in JSON at position 1

Question

sync command - SyntaxError: Unexpected token o in JSON at position 1

lovasoa opened this issue 4 years ago · comments

Hello,
I recently got the following error on CI, so I thought I would report it :

> openode sync && openode restart

[Sat Mar 21 2020 19:04:09 GMT+0000 (Coordinated Universal Time)] -  [+] Authentication valid.

- 

Processing for canada

SyntaxError: Unexpected token o in JSON at position 1

    at JSON.parse (<anonymous>)

    at execSyncFiles (/home/travis/build/lovasoa/whitebophir/node_modules/openode/modules/deploy.js:276:24)

    at process._tickCallback (internal/process/next_tick.js:68:7)

[ { SyntaxError: Unexpected token o in JSON at position 1

      at JSON.parse (<anonymous>)

      at execSyncFiles (/home/travis/build/lovasoa/whitebophir/node_modules/openode/modules/deploy.js:276:24)

      at process._tickCallback (internal/process/next_tick.js:68:7) location: 'canada' } ]

[Sat Mar 21 2020 19:04:42 GMT+0000 (Coordinated Universal Time)] -  [+] Authentication valid.

- 

Processing for canada

[ { result: 'success', deploymentId: 1816, location: 'canada' } ]

It happened only one, and relaunching the command did not reproduce the error.

Mario Franze · Answer 1 · Sun Mar 22 2020 03:44:14 GMT+0800 (China Standard Time)

Looks like there was a communication issue and your openode client got a maliformed json back. Does the error occur more often or only once?

Ophir LOJKINE · Answer 2 · Sun Mar 22 2020 19:52:00 GMT+0800 (China Standard Time)

I have currently only seen it once. And yes, it looks like an error in the backend. But anyway, maybe the cli tool could handle this error gracefully ?

Martin Lévesque · Answer 3 · Thu Apr 02 2020 05:27:26 GMT+0800 (China Standard Time)

Hi,

Thanks for reporting. Note that this is a deployment done using the legacy method, we upgraded recently, please see https://www.openode.io/docs/installation/upgrade.md

Will see if it happens also using the new system.

Ophir LOJKINE · Answer 4 · Sat Apr 04 2020 02:36:48 GMT+0800 (China Standard Time)

I am now getting this error systematically

$ npx openode deploy
[Fri Apr 03 2020 20:25:25 GMT+0200 (Central European Summer Time)] -  [+] Authentication valid.
⠸ SyntaxError: Unexpected token o in JSON at position 1
    at JSON.parse (<anonymous>)
    at execSyncFiles (/Users/olojkine/Developpement/whitebophir/node_modules/openode/modules/deploy.js:276:24)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async Object.deploy (/Users/olojkine/Developpement/whitebophir/node_modules/openode/modules/deploy.js:360:7)
    at async progress (/Users/olojkine/Developpement/whitebophir/node_modules/openode/index.js:758:16)
    at async runCommand (/Users/olojkine/Developpement/whitebophir/node_modules/openode/index.js:19:18)
    at async Command.<anonymous> (/Users/olojkine/Developpement/whitebophir/node_modules/openode/index.js:126:7)
SyntaxError: Unexpected token o in JSON at position 1
    at JSON.parse (<anonymous>)
    at execSyncFiles (/Users/olojkine/Developpement/whitebophir/node_modules/openode/modules/deploy.js:276:24)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async Object.deploy (/Users/olojkine/Developpement/whitebophir/node_modules/openode/modules/deploy.js:360:7)
    at async progress (/Users/olojkine/Developpement/whitebophir/node_modules/openode/index.js:758:16)
    at async runCommand (/Users/olojkine/Developpement/whitebophir/node_modules/openode/index.js:19:18)
    at async Command.<anonymous> (/Users/olojkine/Developpement/whitebophir/node_modules/openode/index.js:126:7)

Martin Lévesque · Answer 5 · Sat Apr 04 2020 02:51:11 GMT+0800 (China Standard Time)

Thanks, will investigate this asap.

Martin Lévesque · Answer 6 · Sat Apr 04 2020 05:19:12 GMT+0800 (China Standard Time)

Improvement done (graceful exit with more log details) in the new CLI version (2.0.16), npm i -g openode to upgrade. If the issue still occur, it should output more details.

Keeping it open to monitor

Ophir LOJKINE · Answer 7 · Sat Apr 04 2020 05:33:33 GMT+0800 (China Standard Time)

I updated the cli tool and redeployed, but this time the deploy worked. Did you investigate the issue on the server side ?

Martin Lévesque · Answer 8 · Sat Apr 04 2020 07:33:13 GMT+0800 (China Standard Time)

No, if it still occur we will have more details and look at it again. It seemed to be happening during peak hours, and a "3 seconds" timeout was present and has been removed in the new version.