While developing nodes using nodemon, I checked the following problems.
[nodemon] Internal watch failed: ELOOP: too many symbolic links encountered, stat
I've tried several searches to solve this problem, but I haven't found the right solution yet. If I do nodemon as usual, it works well, but I am experiencing this problem for a little special reason.
I registered a script to run nodemon in rc.local. Because I wanted to set up the server to open by automatically running nodemon when the computer boots.
rc.local is working well. I checked the status, and it was confirmed as below. `
$ sudo systemctl status rc-local.service
● rc-local.service - /etc/rc.local Compatibility
Loaded: loaded (/lib/systemd/system/rc-local.service; enabled; vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/rc-local.service.d
└─debian.conf
Active: active (running)
Docs: man:systemd-rc-local-generator(8)
Process: - ExecStart=/etc/rc.local start (code=exited, status=0/SUCCESS)
Tasks: - (limit: -)
Memory: -
CPU: -
CGroup: /system.slice/rc-local.service
├─**** /bin/bash run_server.sh
├─**** node /usr/local/bin/nodemon app.js
└─**** /usr/bin/node app.js
` I checked the log as below after this attempt.
rc.local[****]: [nodemon] Internal watch failed: ELOOP: too many symbolic links encountered, stat '/run/udev/watch/*'
If anyone has experienced a similar phenomenon to me, could you tell me the solution?
My node and nodemon versions are as follows:
$ node -v v12.22.12, $ nodemon -v2.0.20
I changed the nodemon to node and did the same thing, and it was working exactly!
But I don't know why the server will suddenly stop working.
Therefore, I would like to change this to nodemon.
