Last modified: 2014-07-25 21:31:38 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 T70525, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 68525 - Standalone jobrunner does not start
Standalone jobrunner does not start
Status: RESOLVED WORKSFORME
Product: MediaWiki-Vagrant
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Ori Livneh
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-07-24 19:03 UTC by Matthew Flaschen
Modified: 2014-07-25 21:31 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Matthew Flaschen 2014-07-24 19:03:57 UTC 
The standalone job runner does not start, either through puppet or manually.  Puppet reports:

---
Error: Could not start Service[jobrunner]: Execution of '/sbin/start jobrunner' returned 1: 
Error: /Stage[main]/Mediawiki::Jobrunner/Service[jobrunner]/ensure: change from stopped to running failed: Could not start Service[jobrunner]: Execution of '/sbin/start jobrunner' returned 1: 
---

Running it manually gives:

---
start: Rejected send message, 1 matched rules; type="method_call", sender=":1.14" (uid=1000 pid=3729 comm="/sbin/start jobrunner ") interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init ")
---
Comment 1 Ori Livneh 2014-07-25 03:59:12 UTC 
(In reply to Matthew Flaschen from comment #0)
> Running it manually gives [...]

Could you try it with sudo?
Comment 2 Matthew Flaschen 2014-07-25 21:31:38 UTC 
This is now working for me.  I believe it was due to low memory (I inadvertently had an old Vagrantfile-extra setting it to a low value).
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links