Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashes that leave git-deamon behind and block restart #112

Closed
oliversalzburg opened this issue Feb 15, 2015 · 3 comments
Closed

Crashes that leave git-deamon behind and block restart #112

oliversalzburg opened this issue Feb 15, 2015 · 3 comments
Labels
Milestone

Comments

@oliversalzburg
Copy link
Contributor

Recently I've seen this happen every other day. private-bower will die for some reason and will not be able to clean up the git-deamon. When it is then restarted, it fails to start, because git-deamon can't start.

Here's an excerpt from our logs:

[bower]  14/2/15 23:40:42   Pulled latest for ng-file-upload
[bower]  14/2/15 23:40:42   Pulled latest for jquery
[bower]  14/2/15 23:40:42   Pulled latest for moment
[bower]  14/2/15 23:40:42   Pulled latest for ng-grid
[bower]  14/2/15 23:43:06   Failed to initialize public repository cache
[bower]  14/2/15 23:43:06   Exception message:Error: stderr maxBuffer exceeded.
    at Socket.<anonymous> (child_process.js:707:13)
    at Socket.emit (events.js:95:17)
    at Socket.<anonymous> (_stream_readable.js:765:14)
    at Socket.emit (events.js:92:17)
    at emitReadable_ (_stream_readable.js:427:10)
    at emitReadable (_stream_readable.js:423:5)
    at readableAddChunk (_stream_readable.js:166:9)
    at Socket.Readable.push (_stream_readable.js:128:10)
    at Pipe.onread (net.js:529:21)
[bower]  14/2/15 23:43:06   Shutting down private-bower
[bower]  14/2/15 23:43:06   Stopping git cache server
error: Forever detected script exited with code: 0
error: Script restart attempt #1
[bower]  14/2/15 23:43:13   Refreshing public packages...
[bower]  14/2/15 23:43:13   Bower server started on port 5678
[bower]  14/2/15 23:43:13   Starting git cache server
[bower]  14/2/15 23:43:13   Failed to initialize public repository cache
[bower]  14/2/15 23:43:13   Exception message:Error: Command failed: [19740] Could not bind to ::1: Address already in use

@tkambler
Copy link

Ditto.

@RyanDickson
Copy link

I have experienced this frequently as well. As an interim fix I removed the verbose flag from the git daemon command in git-repo-cache.js and the maxBuffer on the exec has not been hit since for my setup.

@Hacklone Hacklone added the bug label Mar 29, 2015
@Hacklone Hacklone added this to the 1.0 milestone Mar 29, 2015
@oliversalzburg
Copy link
Contributor Author

@RyanDickson Thanks for the suggestion. I made that change on our server as well. So far, so good.

Hacklone added a commit that referenced this issue Mar 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants