Last modified: 2014-09-17 22:12:39 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 T72967, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 70967 - labs-vagrant: hhvm.hhbc can fill tmpfs
labs-vagrant: hhvm.hhbc can fill tmpfs
Status: NEW
Product: MediaWiki-Vagrant
Classification: Unclassified
labs-vagrant (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-09-17 22:12 UTC by spage
Modified: 2014-09-17 22:12 UTC (History)
4 users (show)

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


Attachments

Description spage 2014-09-17 22:12:39 UTC
After updating and labs-vagrant provision of a flow-tests labs instance, I was getting 503 errors.  /var/log/hhvm/error.log contained

[Wed Sep 17 20:41:47 2014] [hphp] [24230:7fb9ed1fe6c0:0:000001] [] Failed to initialize central HHBC repository:\n  Failed to initialize schema in /var/run/hhvm/hhvm.hhbc: RepoQuery::step(repo=0x7fb9dd467000) error: 'CREATE TABLE main.writable_4cd91499a6638cdf8f21e85093dc7dab65e909e0(canary INTEGER);' --> (13) database or disk is full\n  Failed to open /var/www/.hhvm.hhbc: 14 - unable to open database file\n

Turns out /var/run/hhvm/hhvm.hhbc was 200MB which filled the tmpfs on /run that is only 201MB on this small labs instance.

The workaround is to delete hhvm.hhbc.  Note that you need to stop and start both hhvm and jobrunner, because both services have a handle to this file.

There was IRC discussion of placing hhvm.hhbc in a better location, e.g. /srv somewhere.

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


Navigation
Links