https://bugzilla.wikimedia.org/show_bug.cgi?id=71370
Nik Everett changed:
What|Removed |Added
Keywords||upstream
Status|NEW
https://bugzilla.wikimedia.org/show_bug.cgi?id=71370
--- Comment #14 from Dan Duvall ---
I'm running into this as well. FWICT, it's not necessarily hitting an open
files limit but the mysql max_connections limit (defaults to 151).
To reproduce and verify:
1) Disable zend role if enabled and pr
https://bugzilla.wikimedia.org/show_bug.cgi?id=71370
--- Comment #13 from Nik Everett ---
I have the following vagrant roles enabled:
apisandbox
betafeatures
cirrussearch
geodata
And that triggers it. Zend stops it.
You can reproduce it simply by reloading the main page about 40-50 times.
It
https://bugzilla.wikimedia.org/show_bug.cgi?id=71370
--- Comment #12 from Nik Everett ---
Since I sunk a day into figuring things out I should make it clear what I found
before I put this aside. The issue is that hhvm was holding on to all open
files and sockets after the request ended. You get
https://bugzilla.wikimedia.org/show_bug.cgi?id=71370
Nik Everett changed:
What|Removed |Added
Keywords||hhvm
Priority|Unprioritized
https://bugzilla.wikimedia.org/show_bug.cgi?id=71370
--- Comment #10 from Nik Everett ---
Looks like enabling the zend role fixes the problem for me. Sadly, I might
have to give up on debugging this for a while and use zend.
--
You are receiving this mail because:
You are the assignee for the
https://bugzilla.wikimedia.org/show_bug.cgi?id=71370
--- Comment #9 from Nik Everett ---
OK! I smashed my instance (again again) and rebuilt it and it still fails just
like this. The trouble is that the hhvm service hangs on to stuff forever.
Just never lets go.
I commented out 10-CirrusSearc
https://bugzilla.wikimedia.org/show_bug.cgi?id=71370
Nik Everett changed:
What|Removed |Added
CC||neverett+bugzilla@wikimedia
https://bugzilla.wikimedia.org/show_bug.cgi?id=71370
--- Comment #7 from Bryan Davis ---
(In reply to Vogone from comment #6)
> Also occurs on Labs-Vagrant, apparently. Is there a way to resolve this
> there other than waiting for a few hours? As far as I know, no vagrant
> halt/vagrant up exists
https://bugzilla.wikimedia.org/show_bug.cgi?id=71370
--- Comment #6 from Vogone ---
Also occurs on Labs-Vagrant, apparently. Is there a way to resolve this there
other than waiting for a few hours? As far as I know, no vagrant halt/vagrant
up exists for Labs-Vagrant.
--
You are receiving this m
https://bugzilla.wikimedia.org/show_bug.cgi?id=71370
Prateek Saxena changed:
What|Removed |Added
CC||psax...@wikimedia.org
--- Comment #5
https://bugzilla.wikimedia.org/show_bug.cgi?id=71370
--- Comment #4 from Jon ---
After switching to zend I have not had this problem all day.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
https://bugzilla.wikimedia.org/show_bug.cgi?id=71370
--- Comment #3 from Jon ---
It's happening every hour or so for me. I've switched to zend, will report back
my experience later.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
https://bugzilla.wikimedia.org/show_bug.cgi?id=71370
Bryan Davis changed:
What|Removed |Added
CC||bda...@wikimedia.org
--- Comment #2 from
https://bugzilla.wikimedia.org/show_bug.cgi?id=71370
Vogone changed:
What|Removed |Added
CC||leon.liese...@wikipedia.de
--- Comment #1 fro
15 matches
Mail list logo