SyntaxError: Unexpected token import #4588

krystianjj · 2020-01-21T10:47:50Z

What's going wrong?

When try to run pm2 start server.js I have error

    import(process.env.pm_exec_path);
    ^^^^^^
SyntaxError: Unexpected token import
    at new Script (vm.js:51:7)
    at createScript (vm.js:138:10)
    at Object.runInThisContext (vm.js:199:10)
    at Module._compile (module.js:624:28)
    at Object.Module._extensions..js (module.js:671:10)
    at Module.load (module.js:573:32)
    at tryModuleLoad (module.js:513:12)
    at Function.Module._load (module.js:505:3)
    at Function.Module.runMain (module.js:701:10)
    at startup (bootstrap_node.js:193:16)
/usr/local/node/node-

How could we reproduce this issue?

Start pm2 with latest version

Supporting information

Until today morning everything working great. I see that yesterday pm2 was updated to version 4.2.2

$ pm2 report
--- PM2 report ----------------------------------------------------------------
Date                 : Tue Jan 21 2020 12:12:00 GMT+0100 (CET)
===============================================================================
--- Daemon -------------------------------------------------
pm2d version         : 4.2.2
node version         : 9.4.0
node path            : /usr/local/node/node-default/bin/pm2
argv                 : /usr/local/node/node-v9.4.0/bin/node,/usr/local/node/node-v9.4.0/lib/node_modules/pm2/lib/Daemon.js
argv0                : node
user                 : root
uid                  : 0
gid                  : 0
uptime               : 129min
===============================================================================
--- CLI ----------------------------------------------------
local pm2            : 4.2.2
node version         : 9.4.0
node path            : /usr/local/node/node-default/bin/pm2
argv                 : /usr/local/node/node-v9.4.0/bin/node,/usr/local/node/node-default/bin/pm2,report
argv0                : node
user                 : root
uid                  : 0
gid                  : 0
===============================================================================
--- System info --------------------------------------------
arch                 : x64
platform             : linux
type                 : Linux
cpus                 : Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
cpus nb              : 2
freemem              : 423391232
totalmem             : 1887514624
home                 : /root
===============================================================================
--- PM2 list -----------------------------------------------
┌─────┬────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id  │ name   │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │
├─────┼────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0   │ WEB    │ default     │ 0.1.0   │ fork    │ 0        │ 0      │ 15   │ errored   │ 0%       │ 0b       │ root     │ disabled │
└─────┴────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
===============================================================================
--- Daemon logs --------------------------------------------
/root/.pm2/pm2.log last 20 lines:
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] exited with code [1] via signal [SIGINT]
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] starting in -fork mode-
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] online
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] exited with code [1] via signal [SIGINT]
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] starting in -fork mode-
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] online
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] exited with code [1] via signal [SIGINT]
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] starting in -fork mode-
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] online
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] exited with code [1] via signal [SIGINT]
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] starting in -fork mode-
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] online
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] exited with code [1] via signal [SIGINT]
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] starting in -fork mode-
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] online
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] exited with code [1] via signal [SIGINT]
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] starting in -fork mode-
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] online
PM2        | 2020-01-21T10:02:42: PM2 log: App [WEB:0] exited with code [1] via signal [SIGINT]
PM2        | 2020-01-21T10:02:42: PM2 log: Script /var/www/html/vhost-service0/server.js had too many unstable restarts (16). Stopped. "errored"

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

Unitech · 2020-01-21T14:12:46Z

Fixed thanks for reporting

npm install pm2 -g
pm2 update

krystianjj · 2020-01-21T14:15:01Z

Great, thanks!

szkrd · 2020-02-09T12:06:10Z

Is it possible that when I'm using pm2 from the command line the --interpreter version (below v10) still affects this? The pm2 execution context is v10.19.0, but I'm trying to use node v6, and I still have an import error:

petr166 · 2020-02-19T22:59:02Z

@Unitech I have a similar issue as @szkrd. I'm running node@12.4.1 and trying to start a process with interpreter: 'node@8.17.0'. This results in the import error

jonluca · 2020-02-24T01:25:19Z

I am still seeing this issue with pm2 v4.2.3

3|SOC2  | 2020-02-23T17:24:35.463: /home/jonluca/.nvm/versions/node/v13.8.0/lib/node_modules/pm2/lib/ProcessContainerFork.js:29
3|SOC2  | 2020-02-23T17:24:35.463:     import(process.env.pm_exec_path);
3|SOC2  | 2020-02-23T17:24:35.463:     ^^^^^^
3|SOC2  | 2020-02-23T17:24:35.463:
3|SOC2  | 2020-02-23T17:24:35.463: SyntaxError: Unexpected token import
3|SOC2  | 2020-02-23T17:24:35.463:     at new Script (vm.js:51:7)
3|SOC2  | 2020-02-23T17:24:35.463:     at createScript (vm.js:136:10)
3|SOC2  | 2020-02-23T17:24:35.463:     at Object.runInThisContext (vm.js:197:10)
3|SOC2  | 2020-02-23T17:24:35.463:     at Module._compile (module.js:626:28)
3|SOC2  | 2020-02-23T17:24:35.463:     at Object.Module._extensions..js (module.js:673:10)
3|SOC2  | 2020-02-23T17:24:35.463:     at Module.load (module.js:575:32)
3|SOC2  | 2020-02-23T17:24:35.463:     at tryModuleLoad (module.js:515:12)
3|SOC2  | 2020-02-23T17:24:35.463:     at Function.Module._load (module.js:507:3)
3|SOC2  | 2020-02-23T17:24:35.463:     at Function.Module.runMain (module.js:703:10)
3|SOC2  | 2020-02-23T17:24:35.463:     at startup (bootstrap_node.js:193:16)

These are simple applications started with a pm2.config.js file that looks like:

module.exports = {
  /**
   * Application configuration section
   * http://pm2.keymetrics.io/docs/usage/application-declaration/
   */
  apps: [// First application
    {
      name: 'SOC2',
      script: 'bin/www',
      log_date_format: 'YYYY-MM-DDTHH:mm:ss.SSS',
      env: {
        NODE_ENV: 'production'
      }
    }

  ]
};

jonluca · 2020-02-24T01:35:18Z

@Unitech I was able to temporarily fix this by changing lib/God.js and lib/God/ForkMode.js to always load the legacy version

/**
 * Override cluster module configuration
 */
cluster.setupMaster({
    windowsHide: true,
    exec : path.resolve(path.dirname(module.filename), 'ProcessContainerLegacy.js')
  });

This is on Node v13.9.0

jubarbie · 2020-03-10T14:51:19Z

I am also experiencing the same issue, I'm running node v12.0.0 and PM2 4.2.3.
Can someone help ? I'm unable to load my app

szkrd · 2020-03-11T07:58:13Z

@Unitech can you reopen this, or should it be a different issue? I enforced the two affected microservices I work with to node 10 in the end, but it seems to be that others might experience the same issue.

krystianjj · 2020-03-11T08:45:58Z

Can you show the error log and pm2 report ?

szkrd · 2020-03-11T15:57:07Z

@krystianjj I attached two > dumps, but since I'm now fine on node 10 with the offending microservices, maybe others should come forward... nevertheless, here they are:
log-6.txt
report.txt

Unitech added a commit that referenced this issue Jan 21, 2020

fix: #4588 import syntax on Node 9.x

278d4b2

Unitech added the S: In progress label Jan 21, 2020

Unitech closed this as completed Jan 21, 2020

inerc pushed a commit to inerc/pm2 that referenced this issue Feb 11, 2020

fix: Unitech#4588 import syntax on Node 9.x

31cb2af

kimmobrunfeldt mentioned this issue Apr 24, 2020

SyntaxError: Unexpected token import when starting with --interpreter node<10 #4686

Closed

tdonohue mentioned this issue Oct 4, 2023

Angular dspace doesn't start with pm2 after reboot DSpace/dspace-angular#2495

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

SyntaxError: Unexpected token import #4588

SyntaxError: Unexpected token import #4588

krystianjj commented Jan 21, 2020 •

edited

Unitech commented Jan 21, 2020

krystianjj commented Jan 21, 2020

szkrd commented Feb 9, 2020

petr166 commented Feb 19, 2020

jonluca commented Feb 24, 2020

jonluca commented Feb 24, 2020

jubarbie commented Mar 10, 2020

szkrd commented Mar 11, 2020

krystianjj commented Mar 11, 2020

szkrd commented Mar 11, 2020

SyntaxError: Unexpected token import #4588

SyntaxError: Unexpected token import #4588

Comments

krystianjj commented Jan 21, 2020 • edited

What's going wrong?

How could we reproduce this issue?

Supporting information

Unitech commented Jan 21, 2020

krystianjj commented Jan 21, 2020

szkrd commented Feb 9, 2020

petr166 commented Feb 19, 2020

jonluca commented Feb 24, 2020

jonluca commented Feb 24, 2020

jubarbie commented Mar 10, 2020

szkrd commented Mar 11, 2020

krystianjj commented Mar 11, 2020

szkrd commented Mar 11, 2020

krystianjj commented Jan 21, 2020 •

edited