Last modified: 2013-09-14 07:36: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 T54872, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 52872 - eventlogging role requires python server module, port forwarding, and special flags
eventlogging role requires python server module, port forwarding, and special...
Status: RESOLVED DUPLICATE of bug 54042
Product: MediaWiki-Vagrant
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Ori Livneh
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-15 01:44 UTC by spage
Modified: 2013-09-14 07:36 UTC (History)
1 user (show)

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


Attachments

Description spage 2013-08-15 01:44:38 UTC
I added the eventlogging role some time ago, but couldn't run server/bin/eventlogging-devserver

I followed /vagrant/mediawiki/extensions/EventLogging/server/README.rst with a couple of modifications.
a)    $ sudo apt-get install -y python-coverage python-mysqldb python-nose \
        python-pip python-sqlalchemy python-zmq python-pymongo
needs a backslash line continuation character at end of first line

b) `setup.py install` didn't work, python setup.py install failed "error: can't create or remove files in install directory" because it's trying to install to /usr/local/lib/python2.7/dist-packages/.  Ori suggested `sudo python setup.py install`, that worked.

Now I can run `eventlogging-devserver --port 8100`.  These fixes could go in README.rst.

The next problem is my host machine can't connect to port 8100 on the VM, I added the following to Vagrantfile:
    # To enable client-side event logging in the 'eventlogging' role,
    # uncomment these two lines:
    config.vm.network :forwarded_port,
       guest: 8100, host: 8100, id: 'eventlogging'

The next issue is to get eventlogging-devserver to listen to requests from the host machine on the virtual ethernet adapter as well as to local requests within the VM, you need to run `eventlogging-devserver --port 8100 --host 0.0.0.0`.

Some portion of these steps could be automated as part of the eventlogging puppet role, and/or there could be vagrant-specific documentation of them somewhere.

FWIW the naive developer expectation might be that enabling eventlogging role would log both client and server events to vagrant/logs/eventlogging.log.
Comment 1 Andre Klapper 2013-09-11 22:46:13 UTC
[mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.]
Comment 2 Ori Livneh 2013-09-14 07:36:38 UTC
54042 is newer but stands a better chance of being resolved, so marking this one as duplicate.

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

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


Navigation
Links