Does Next.js support pm2 cluster mode? #10675
-
|
Hi guys, My pm2 version is 4.2.3, and express version is 4.17.1. next and related version is below. // pages/index.js
export default function Index() {
return (<div><p>Hello Next.js</p></div>)
}// package.json
{
"name": "test",
"version": "1.0.0",
"description": "",
"dependencies": {
"next": "^9.2.2",
"react": "^16.12.0",
"react-dom": "^16.12.0"
},
"devDependencies": {},
"scripts": {
"dev": "next",
"build": "next build",
"start": "next start"
},
"author": "",
"license": "ISC"
}when I run the next server // test.js (express server)
const express = require('express')
const app = express()
const uuid = require('uuid')
var instance_id = uuid.v4()
const port = 3000
app.get('/', function (req, res) {
res.send(`Hello World! ${instance_id}`)
})
app.listen(port, function () {
console.log(`application is listening on port ${port}...`)
})when I run the express server I posted this on spectrum, too. |
Beta Was this translation helpful? Give feedback.
Replies: 10 comments 32 replies
-
|
I had similar problem (not with pm2, but the error was the same) and the issue in my case was that the version of Node was outdated. Can check what version of Node are you using and update to more recent one? |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Latest stable is 12.16.1 but your version is relatively up-to-date so maybe the problem you have is different than my. |
Beta Was this translation helpful? Give feedback.
-
|
Alright.. thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Did you check the logs outlined there, it shows only 15 lines which is not enough to know why the command failed to boot. Looks like it should be located here: |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
"scripts": {
"dev": "next",
"build": "next build",
"start": "next start",
"pm2": "pm2"
}
{
"apps": [
{
"name": "my-app",
"script": "npm",
"args" : "start",
"instances": "max",
"exec_mode": "cluster"
}
]
}
The configuration above will start as many instances as possible and far as I tried works correctly. I would highly recommend looking into hosting on https://zeit.co/ though it's automatically optimized for Next.js in many ways: https://nextjs.org/docs/deployment#optimized-for-nextjs |
Beta Was this translation helpful? Give feedback.
-
|
Hey @timneutkens. thanks so much, worked perfectly! |
Beta Was this translation helpful? Give feedback.
-
This worked for me as well... but does anyone know what the root issue here is? |
Beta Was this translation helpful? Give feedback.
-
|
@esmalleydev please help me Do you have any other solution? I updated it like that and it worked but the memory increased 56mb -> >500mb and continues to increase |
Beta Was this translation helpful? Give feedback.
-
|
I'd suggest just writing your own nextjs server using the default node cluster mode |
Beta Was this translation helpful? Give feedback.
-
|
Yes, thank you very much! |
Beta Was this translation helpful? Give feedback.
-
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"pm2": "pm2-runtime start pm2.config.js --env production"
}when i run but, if I replace pm2 script to The pm2.config.js is: module.exports = {
apps : [
{
name: 'next',
script: 'npm',
args: 'start',
instances: 4,
exec_mode: 'cluster'
}
]
}; |
Beta Was this translation helpful? Give feedback.
-
|
my solution. |
Beta Was this translation helpful? Give feedback.
-
|
and then Edit: Somehow |
Beta Was this translation helpful? Give feedback.
-
|
@michaelschufi Thx. I have tried your solution, It's OK. |
Beta Was this translation helpful? Give feedback.
-
|
When will this issue be fixed? Same for next 11.0.1 version. @magnnus Do you know why I need to run pm2 list first? |
Beta Was this translation helpful? Give feedback.
-
|
@seungdols I just found this issue. This might be a problem in pm2-runtime when no daemon is running. See Unitech/pm2#4950. |
Beta Was this translation helpful? Give feedback.
-
|
I had nothing but trouble trying to use I did not have a problem where I had to run This is what is working for me:
I can now run Success. |
Beta Was this translation helpful? Give feedback.
-
|
When Next.js is run in a cluster, does every process then have its own copy of things such as statically generated files, optimized images (next/image), etc.? Or will every process share these? |
Beta Was this translation helpful? Give feedback.
-
|
pm2 cluster mode shares the files :-) |
Beta Was this translation helpful? Give feedback.
-
|
Oh that's awesome! Thanks for your quick reply! :D |
Beta Was this translation helpful? Give feedback.
-
|
Does anyone know how we can run it in cluster mode inside docker? I have tried all the steps mentioned here but nothing works inside docker container. My Docker command looks like this : CMD [ "pm2-runtime" ,"start","pm2.json"] pm2.json file Error: (As you can see its looking for .next folder inside pm2.json folder)
|
Beta Was this translation helpful? Give feedback.
-
|
@saachinsiva not sure if you are still facing the issue with Next.JS integrated with Docker and PM2... The problem is only Here is what I did... Dockerfile: package.json: It's important that pm2 is executed before pm2-runtime. Then my pm2.config.js: |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. I will try this and let you know. |
Beta Was this translation helpful? Give feedback.
-
|
It work in my instance ec2 AWS with docker + pm2 + nextjs 14.2.5 ecosystem.config.js DockerFile Thank for this line -> "pm2": "pm2 start ecosystem.config.json && pm2-runtime ecosystem.config.json" |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
In my case it works fine on pm2 when standalone. Try this, Step 1. Enable the value // next.config.js
module.exports = {
...
experimental: {
outputStandalone: true,
}
}Step 2. Build your app next buildStep 3. Run Nextjs app (run standalone mode) with pm2 pm2-runtime start ./node_modules/.bin/next -i 2 |
Beta Was this translation helpful? Give feedback.
-
|
Still same, all process keeps crashing. |
Beta Was this translation helpful? Give feedback.
-
|
I know it's an old comment but to anyone else coming across this. The processes are running in When running in |
Beta Was this translation helpful? Give feedback.
-
|
I solved this issue a while ago. My module.exports = {
apps: [
{
name: 'app-name',
script: "node_modules/next/dist/bin/next",
args: "start",
instances: 4,
exec_mode: 'cluster',
autorestart: true,
},
],
};Afterward, I deleted all PM2 processes using |
Beta Was this translation helpful? Give feedback.
-
Let's fucking go baby. Good job bro |
Beta Was this translation helpful? Give feedback.
-
|
Is anyone facing an issue getting console.log to show up in pm2 logs with this method? Perhaps using a custom express server? |
Beta Was this translation helpful? Give feedback.
and others
pm2in the dependenciesscriptssection like this:pm2.jsonand add the following configuration:{ "apps": [ { "name": "my-app", "script": "npm", "args" : "start", "instances": "max", "exec_mode": "cluster" } ] }npm run buildto build the Next.js app for productionnpm run pm2 start pm2.jsonThe configuration above will start as many instances as possible and fa…