Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[NITRO] WARN [worker] listen EADDRINUSE: address already in use

See original GitHub issue

Environment

------------------------------
- Operating System: `Linux`
- Node Version:     `v17.8.0`
- Nuxt Version:     `3.0.0-27477996.646c2f6`
- Package Manager:  `yarn@3.2.0`
- Builder:          `vite`
- User Config:      `modules`
- Runtime Modules:  `normalizedModule()`, `normalizedModule()`
- Build Modules:    `-`
------------------------------

Reproduction

Hapen randomly

Describe the bug

Sometimes I get this error during development in the console. It seems completely random but often.

Additional context

Nuxt runs in my clean Docker container:

FROM node:17.8.0-alpine3.15 as nuxtBuild

WORKDIR /app

COPY ./client ./

RUN yarn config set npmRegistryServer https://registry.npmmirror.com/ \
    && yarn install \
    && yarn run build

FROM node:17.8.0-alpine3.15

WORKDIR /app

COPY ./client/package.json /app/package.json
COPY ./docker-entrypoint.sh /usr/local/bin/oxy-entrypoint
COPY --from=nuxtBuild /app/.output /app/.output

RUN chmod +x /usr/local/bin/oxy-entrypoint

ENV NUXT_HOST=0.0.0.0

ENTRYPOINT ["oxy-entrypoint"]

Entrypoint:

#!/bin/sh
set -e

if [ "$NODE_ENV" = "production" ]; then
    yarn run start
else
    yarn install
    yarn run dev
fi

Logs

WARN  [worker] listen EADDRINUSE: address already in use /tmp/nitro/worker-74-2.sock
 
   at Server.setupListenHandle [as _listen2] (node:net:1355:21)
   at listenInCluster (node:net:1420:12)
   at Server.listen (node:net:1519:5)
   at .nuxt/nitro/index.mjs:140:8
   at ModuleJob.run (node:internal/modules/esm/module_job:198:25)
   at async Promise.all (index 0)
   at async ESMLoader.import (node:internal/modules/esm/loader:385:24)
   at async loadESM (node:internal/process/esm_loader:88:5)
   at async handleMainPromise (node:internal/modules/run_main:61:12)

Issue Analytics

State:
Created a year ago
Reactions:11
Comments:25 (14 by maintainers)

Top GitHub Comments

8reactions

EugeneGpilcommented, Oct 10, 2022

I changed 1 line in package.json to solve it. At least for now

"dev": "nuxt dev", to "dev": "rm -rf /tmp/nitro && nuxt dev",

8reactions

kalaomercommented, Jun 21, 2022

Guys, I have this issue with docker and this thing is getting boring. Every file change brings this issue, I can not do the hot reload. Is there any progress?

Top Results From Across the Web

How to kill server when seeing “EADDRINUSE: address ...

A tutorial on how to kill the process manually when “EADDRINUSE” happens on Mac/Linux and Windows. Nodejs listen EADDRINUSE: address already in ......

Node / Express: EADDRINUSE, Address already in use - Kill ...

First, you would want to know which process is using port 3000 sudo lsof -i :3000. this will list all PID listening on...

nuxt Error: listen EADDRINUSE: address already in use Code ...

psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: No such file or directory Is the server running locally and accepting ...

Angular template if else if - Weebly

Conclusion In this tutorial, we discovered how we can use the power of the ... address already in use :::31641 Error: listen EADDRINUSE:...

The definitive Node.js handbook – Learn Node for Beginners

Now the npm registry hosts almost 500,000 open source packages you can freely use. A sample Node.js application. The most common example Hello ......