Nodemon restarts multiple times #1354

LuckStock · 2018-05-23T20:05:20Z

nodemon -v: 1.17.5
node -v: 8.11.2
Operating system/terminal environment:
Windows 10 Pro N, Build 17134
Command you ran:
nodemon --verbose ./node_stock/bin/www

Expected behaviour

Start a server and listen to the file changes

Actual behaviour

Keeps restarting without any changes.

Steps to reproduce

Works normally in -L (legacy mode).

If applicable, please append the --dump flag on your command and include the output here ensuring to remove any sensitive/personal details or tokens.

nodemon --verbose ./node_stock/bin/www

[nodemon] 1.17.5
[nodemon] reading config .\nodemon.json
[nodemon] to restart at any time, enter rs
[nodemon] or send SIGHUP to 12128 to restart
[nodemon] ignoring: .git node_stock/client//* node_stock/node_modules//* npm-debug.log node_stock/node_modules/../node_modules node_stock/.test.js node_stock/fixtures/**/
[nodemon] watching: D:\Projects\luckstock\node_stock//*
[nodemon] watching extensions: js,json
[nodemon] starting node ./node_stock/bin/www
[nodemon] forking
[nodemon] child pid: 6164
[nodemon] watching 763 files
[nodemon] files triggering change check: node_stock\apps\items\itemsStore.js
[nodemon] matched rule: D:\Projects\luckstock\node_stock//*
[nodemon] changes after filters (before/after): 1/1
[nodemon] restarting due to changes...
[nodemon] Node_stock\apps\items\itemsStore.js

[nodemon] files triggering change check: node_stock\apps\orders\index.js
[nodemon] matched rule: D:\Projects\luckstock\node_stock/**/*
[nodemon] changes after filters (before/after): 1/1
[nodemon] restarting due to changes...
[nodemon] Node_stock\apps\orders\index.js
....

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

LuckStock · 2018-05-23T20:12:09Z

Uninstalling/reinstalling nodemon doesn't help.
Reverting to earlier version (1.8.1 for example) doesn't help.
Guess, Microsoft has released some updates to the OS, breaking fsevents module.

lpgera · 2018-05-24T07:31:09Z

Isn't fsevents module an optional dependency, only installed on OS X to access the FSEvents API? I am not sure if it's relevant here.

LuckStock · 2018-05-25T09:24:00Z

In this case, I don't have a clue what could be a reason.
Have tried reverting to older versions, running in legacy mode, uninstalling and reinstalling nodemon, but can't get it running normally as earlier. Keeps restarting even if I simply refresh the browser window.
Restarts 10-20 times before the app starts listening to the port. Development became a nightmare,
What could I do to fix it?

LuckStock · 2018-05-26T14:41:42Z

Still digging this issue and therefore can't develop the project.
I recently found that once "access time" of a project file is updated, nodemon restarts.
Modification time of a file is not affected. Therefore, in live reload accessing the file updates "access timestamp" leading to multiple/looped restarts of nodemon.
Please help!

masterpandabear · 2018-05-28T15:36:59Z

I also have same problem, as a workaround i run node first, then cancel it and then run nodemon and that stops the restart loop for a while, after a while (sort of random) nodemoon loops again.

I checked with my coworkers, the ones that have the lastest Windows 10 update are the ones with this problem.

ayami123 · 2018-05-29T07:01:38Z

oh so this is an issue with windows ?
I mean it constantly Restart due to Changes to me

Dattaya · 2018-05-29T07:37:07Z

I don't know what exactly is going on, has Windows April Update introduced a bug or fixed it and nodemon needs to be patched? As a workaround you can disable access time modifications completely with fsutil behavior set disablelastaccess 1 (open console in an admin mode,) if it doesn't help, try to restart your PC.

LuckStock · 2018-05-30T11:25:16Z

@Dattaya, Thank you very much!
Your solution works. It's not a native solution, but works!

jacsamg · 2018-05-31T22:15:53Z

I have the same problem, I use Windows 10 and a week ago it was updated. Well, I'm glad to know the origin, I was already going crazy.

balciseri · 2018-06-03T09:46:50Z

Same problem here. I'm on windows too, probably i also just updated the SO but i'm not sure. anyway seems that just accessing the files trigger a restart!

AbdelrahmanHafez · 2018-06-06T20:06:04Z

#1354 (comment) solves it!

stale · 2018-06-20T20:09:05Z

This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up.
Thank you for contributing <3

jacsamg · 2018-06-20T21:10:17Z

In Windows it continues to affect.

AbdelrahmanHafez · 2018-06-21T01:58:26Z

@tojacob even after running fsutil behavior set disablelastaccess 1 on an elevated command prompt?

jacsamg · 2018-06-21T16:52:31Z

@AbdelrahmanHafez: After executing the command everything worked normally.

stale · 2018-07-06T10:08:22Z

This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up.
Thank you for contributing <3

TynesideGroup · 2018-07-06T10:29:14Z

fsutil behavior set disablelastaccess 1 also worked for me.

Just adding a dummy comment to stop this issue from being closed!

remy · 2018-07-10T17:28:45Z

Since no one has offered anything by way of pull request, I'm going to add this to the FAQ (as far as I can tell it's Windows triggering an IO event that it shouldn't be).

Something you can also try is a completely fresh installation of nodemon (to pick up the latest version of chokidar - which does the actual watching) - though I doubt if that'll fix anything…

Ref #1354 Ref #1346 [skip ci]

markablov · 2018-08-29T08:25:14Z

Small fix for chokidar - paulmillr/chokidar#762

kamenov · 2018-09-26T13:27:09Z

The same happened to me on MacOS node 10, npm 6, nodemon 1.10. Upgrading nodemon to 1.18 bringing the latest chokidar fixed the issue. Thanks to @markablov for his patch.

apoorvagarwal41 · 2018-12-09T14:01:13Z

fsutil behavior set disablelastaccess 1 worked for me

HJain13 · 2018-12-24T09:26:29Z

Still happening and even fsutil behavior set disablelastaccess 1 doesn't work for me

GRGL-RC · 2019-01-11T21:02:25Z

Still happening here aswell... "fsutil behavior set disablelastaccess 1" doesent work for me neither

deveshsinghal22 · 2019-03-26T07:07:03Z

Please suggest some on this. Still this is happening for me.

remy · 2019-03-26T08:54:19Z

@deveshsinghal22 here you go: upgrade. This issue was filed 9 months ago. Suggest upgrading nodemon. If you're seeing a new issue, please file a new issue.

bilalbutt044 · 2019-05-11T10:31:27Z

Still happening and even fsutil behavior set disablelastaccess 1 doesn't work for me

OS window 8.1
nodemon = 1.19 latest
node = 10.15.1

jatinderkumargupta · 2019-06-12T06:40:07Z

executing following command as administrator:
fsutil behavior set disablelastaccess 1
worked for me on windows 10.

teja123r · 2020-01-02T13:58:10Z

fsutil behavior set disablelastaccess 1
Worked for me Windows 10

tEgRaT · 2021-01-26T02:11:12Z

executing fsutil behavior set disablelastaccess 1 command as administrator and restart computer, then...
it doesn't help.

Windows 7 Pro 64X

oshihirii · 2021-12-01T04:29:57Z

for others searching, per remy's comment updating seems to resolve this issue for me. windows 10. node v16.13.0. nodemon 2.0.15.

LuckStock mentioned this issue May 23, 2018

Restarts for non watched files #1320

Closed

balciseri mentioned this issue Jun 3, 2018

nodemon stuck at restarting #1356

Closed

stale bot added the stale no activity for 2 weeks label Jun 20, 2018

stale bot removed the stale no activity for 2 weeks label Jun 20, 2018

remy added the windows label Jun 22, 2018

This was referenced Jun 22, 2018

Many restarting after any simple change #1368

Closed

nodemon auto restart without any changes in app.js file #1360

Closed

remy mentioned this issue Jul 4, 2018

Nodemon restarts on save #1376

Closed

stale bot added the stale no activity for 2 weeks label Jul 6, 2018

stale bot removed the stale no activity for 2 weeks label Jul 6, 2018

remy closed this as completed Jul 10, 2018

remy added a commit that referenced this issue Jul 10, 2018

docs: add to faq

73aa13f

Ref #1354 Ref #1346 [skip ci]

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Nodemon restarts multiple times #1354

Nodemon restarts multiple times #1354

LuckStock commented May 23, 2018

LuckStock commented May 23, 2018

lpgera commented May 24, 2018

LuckStock commented May 25, 2018

LuckStock commented May 26, 2018

masterpandabear commented May 28, 2018 •

edited

Loading

ayami123 commented May 29, 2018

Dattaya commented May 29, 2018

LuckStock commented May 30, 2018

jacsamg commented May 31, 2018

balciseri commented Jun 3, 2018

AbdelrahmanHafez commented Jun 6, 2018

stale bot commented Jun 20, 2018

jacsamg commented Jun 20, 2018

AbdelrahmanHafez commented Jun 21, 2018

jacsamg commented Jun 21, 2018

stale bot commented Jul 6, 2018

TynesideGroup commented Jul 6, 2018

remy commented Jul 10, 2018

markablov commented Aug 29, 2018

kamenov commented Sep 26, 2018

apoorvagarwal41 commented Dec 9, 2018

HJain13 commented Dec 24, 2018

GRGL-RC commented Jan 11, 2019

deveshsinghal22 commented Mar 26, 2019

remy commented Mar 26, 2019

bilalbutt044 commented May 11, 2019

jatinderkumargupta commented Jun 12, 2019 •

edited

Loading

teja123r commented Jan 2, 2020

tEgRaT commented Jan 26, 2021 •

edited

Loading

oshihirii commented Dec 1, 2021

Nodemon restarts multiple times #1354

Nodemon restarts multiple times #1354

Comments

LuckStock commented May 23, 2018

Expected behaviour

Actual behaviour

Steps to reproduce

LuckStock commented May 23, 2018

lpgera commented May 24, 2018

LuckStock commented May 25, 2018

LuckStock commented May 26, 2018

masterpandabear commented May 28, 2018 • edited Loading

ayami123 commented May 29, 2018

Dattaya commented May 29, 2018

LuckStock commented May 30, 2018

jacsamg commented May 31, 2018

balciseri commented Jun 3, 2018

AbdelrahmanHafez commented Jun 6, 2018

stale bot commented Jun 20, 2018

jacsamg commented Jun 20, 2018

AbdelrahmanHafez commented Jun 21, 2018

jacsamg commented Jun 21, 2018

stale bot commented Jul 6, 2018

TynesideGroup commented Jul 6, 2018

remy commented Jul 10, 2018

markablov commented Aug 29, 2018

kamenov commented Sep 26, 2018

apoorvagarwal41 commented Dec 9, 2018

HJain13 commented Dec 24, 2018

GRGL-RC commented Jan 11, 2019

deveshsinghal22 commented Mar 26, 2019

remy commented Mar 26, 2019

bilalbutt044 commented May 11, 2019

jatinderkumargupta commented Jun 12, 2019 • edited Loading

teja123r commented Jan 2, 2020

tEgRaT commented Jan 26, 2021 • edited Loading

oshihirii commented Dec 1, 2021

masterpandabear commented May 28, 2018 •

edited

Loading

jatinderkumargupta commented Jun 12, 2019 •

edited

Loading

tEgRaT commented Jan 26, 2021 •

edited

Loading