Is the Chrome servicing process running on port 3000?
The following error shows up in Rails app logs and in my Chrome JavaScript console, but only in Chrome and only when the app is running on localhost on port 3000:
Started GET "/service-worker.js" for 127.0.0.1 at 2015-12-15 09:31:04 -0800
ActionController::RoutingError (No route matches [GET] "/service-worker.js"):
Apparently someone else had the same problem, but solved it by reinstalling the OS (!). This is not an option for me.
According lsof
to some other process on port 3000:
COMMAND PID FD TYPE NODE NAME
Google 49368 174u IPv4 TCP localhost:55612->localhost:hbci (CLOSE_WAIT)
ruby 57985 17u IPv4 TCP *:hbci (LISTEN)
Other Notes:
- NodeJS installed
- Chrome version 47.0.2526.80 (64-bit) on OS X 10.10.5
- Material in
chrome://flags/
the default reset - I have disabled all Chrome extensions.
- If I kill this google process it reappears
What is this uninvited process?
source to share
Please visit chrome://serviceworker-internals/
to view a list of working services.
Click the "Unregister" button to remove the offender's registration.
The Google Web Starter Kit includes a service worker that can continue to run after using its local development server.
ALL CREDIT for this answer goes to Jeff Poschick . Just thought this question should have a formal answer that is easy to find as it was driving me crazy before I came across this page :)
source to share