Leaking /tmp/mongodb*.sock files
John Arbash Meinel
john at arbash-meinel.com
Wed Jul 17 10:44:07 UTC 2013
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I don't have the time to investigate this today, but I wanted to let
people know about it.
I think the reason the bot is a bit slow is because we are leaking
file handles in /tmp.
On my work machine, if I run:
ls /tmp/mongodb-*.sock | wc -l
It gives me 535 stale sock files.
On go-bot, it hasn't completed yet (presumably * is taking too long to
evaluate).
I'll nuke the ones we have there now, and probably go-bot will be
happy for a while.
But we need someone to submit a bug and investigate how we are leaking
these connections.
It might be that we only leak if there is a crash / ^C /failure
whatever. But I have a *lot* of them locally, and the bot seems to be
accruing them over time.
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlHmdXcACgkQJdeBCYSNAAPzzgCfdimZa7aaYwwiz3YDzVqJFIjK
dWMAoMcH0lgtpN3sxJHt7iTJoh6OQNMF
=Ohdw
-----END PGP SIGNATURE-----
More information about the Juju-dev
mailing list