Last modified: 2014-04-16 01:43:47 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T62384, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 60384 - hhvm not working
hhvm not working
Status: RESOLVED DUPLICATE of bug 63683
Product: MediaWiki-Vagrant
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Ori Livneh
: hhvm
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-01-23 23:33 UTC by spage
Modified: 2014-04-16 01:43 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description spage 2014-01-23 23:33:01 UTC
I enabled the hhvm role and ran `vagrant provision`.  I had a problem with hhvm's libmemcached6 conflicting with my outdated php5-memcached's libmemcached10, but `sudo apt-get install php5-memcached` fixed that and then `vagrant provision` worked. I have a /usr/bin/hhvm binary that runs.

However, my Special:Version says "PHP  5.3.10-1ubuntu3.9 (fpm-fcgi)".

I've tried:
* `sudo apachectl restart`, ps shows "/usr/sbin/apache2 -D HHVM -k start"

* I noticed I have a number of "php-fpm: pool www" processes. I did `sudo service php5-fpm stop` and restarted apache again, and then apache error log failed with
 [Thu Jan 23 23:08:48 2014] [error] [client 10.0.2.2] (111)Connection refused: FastCGI: failed to connect to server "/usr/lib/cgi-bin/php5-hhvm":
 I have no such file.

* `vagrant reload` didn't help

* I tried `sudo /etc/init.d/hhvm start` , /vagrant/logs/hhvm-error.log contains:
  Unable to read pid file /var/run/hhvm/pid for any meaningful pid
  Unable to start page server
  Shutting down due to failure(s) to bind in HttpServer::run

I'm not sure what's going on.
Comment 1 Gerrit Notification Bot 2014-02-24 10:44:26 UTC
Change 115134 had a related patch set uploaded by Ori.livneh:
HHVM role: use "hhvm-fastcgi" package

https://gerrit.wikimedia.org/r/115134
Comment 2 Gerrit Notification Bot 2014-02-24 10:45:06 UTC
Change 115134 merged by jenkins-bot:
HHVM role: use "hhvm-fastcgi" package

https://gerrit.wikimedia.org/r/115134
Comment 3 Ori Livneh 2014-02-24 10:45:40 UTC
Change 115134 should fix it. Please re-open otherwise.
Comment 4 spage 2014-02-25 11:03:44 UTC
Thanks, but still no luck.  I updated mediawiki/vagrant.git to master (and installed latest Vagrant 1.4.3 and enabled NFS server on my host), then ran `vagrant enable-role hhvm`, `vagrant provision`, and although in `vagrant ssh` aptitude reports
 Package: hhvm-fastcgi             
 State: installed

I get 500 errors and apache2/error.log contains

[Tue Feb 25 10:28:02 2014] [notice] FastCGI: process manager initialized (pid 4195)
[Tue Feb 25 10:28:02 2014] [notice] Apache/2.2.22 (Ubuntu) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.3.10-1ubuntu3.9 with Suhosin-Patch configured -- resuming normal operations
[Tue Feb 25 10:30:29 2014] [error] [client 10.0.2.2] (104)Connection reset by peer: FastCGI: comm with server "/usr/lib/cgi-bin/php5-hhvm" aborted: read failed
[Tue Feb 25 10:30:29 2014] [error] [client 10.0.2.2] FastCGI: incomplete headers (0 bytes) received from server "/usr/lib/cgi-bin/php5-hhvm"

Again there's still no program in /usr/lib/cgi-bin/php5-hhvm.  I tried manually running `sudo /etc/init.d/hhvm-fastcgi restart` and that started hhvm. One time Special:Version succeeded, and reported PHP is running php5-fpm (not hhvm), but hhvm.log contained a bunch of
  SlowTimer [5044ms] at curl: http://:0/stop
lines, and on reload I was back to 500 errors.

(As always I'm never entirely sure how to reset MediaWiki-Vagrant to a clean state.)
Comment 5 Ori Livneh 2014-04-16 01:43:47 UTC

*** This bug has been marked as a duplicate of bug 63683 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links