Fsevents: FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc()

[jackyon]

hi, I am crazy about the below errors, the below errors were came out after I run build on my webpack/react project.

I have tried upgrade nodejs, reinstall fsevent, remove node_modules foler, switch to different nodejs version but still can't find the solution.

plz save me, much appreciate!

2016-04-30 15:42 node[2412] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21) 2016-04-30 15:42 node[2412] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21) 2016-04-30 15:42 node[2412] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21) 2016-04-30 15:42 node[2412] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21) 2016-04-30 15:42 node[2412] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21) 2016-04-30 15:42 node[2412] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21) 2016-04-30 15:42 node[2412] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21) 2016-04-30 15:42 node[2412] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21) 2016-04-30 15:42 node[2412] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21) 2016-04-30 15:42 node[2412] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21) 2016-04-30 15:42 node[2412] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21) 2016-04-30 15:42 node[2412] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21) 2016-04-30 15:42 node[2412] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21) 2016-04-30 15:42 node[2412] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21) 2016-04-30 15:42 node[2412] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21) 2016-04-30 15:42 node[2412] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21) 2016-04-30 15:42 node[2412] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21) 2016-04-30 15:42 node[2412] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)

[bnoordhuis]

See https://github.com/strongloop/fsevents/issues/42 for an explanation. In a nutshell, you're probably watching too many files at once.

[jackyon]

@bnoordhuis , sorry, I already finish reading #42, seems like that post not provide any solution? so how to solve this?

I just found a temporary solution:

1. install nvm
2. using nvm to install two version of nodejs (v4 & v5)
3. switch to v4 if v5 got the errors
4. npm rebuild node-sass
5. errors disappeared.

don't know why, but this works for me.

[bnoordhuis]

I believe FSEvents (the framework itself, not this module) ties resources persistently to the binary that requests them, that's probably why switching versions makes the problem go away. In that vein, you may also want to check that you don't have node processes running in the background.

[jackyon]

thx for your reminding, I will try that later.

[vjpr]

Had the same issue and it turned out to be just watching too many files by using a glob that was too broad. It started happening when I was upgrading things to Node@8. I might have updated chokidar and fsevents too which might have had an impact - because I used the same glob before and didn't have an issue.

[davidcalhoun]

I was getting this error when running webpack-dev-server.

Not sure what was going on, maybe some bug with macOS (running Sierra 10.12.6). It seems to have happened after my computer spontaneously restarted on its own...

The bug persisted with a new terminal window. I finally fixed the issue by restarting iTerm completely.

If that doesn't work, maybe try restarting the entire computer.

[pipobscure]

Closing since this is going to be outdated with 2.0.0 from #238

[reidx882]

fixed by remove node_module and Reinstall .