Installation verify
YangBain opened this issue · comments
@ALL
Does anyone who knows how to solve the following problem (HTTP ... error 404: Not found)?
**~/vatic$ turkic status --verify
/usr/lib/python2.7/dist-packages/pkg_resources.py:1031: UserWarning: /home/byeonghak/.python-eggs is writable by group/others and vulnerable to attack when used with get_resource_filename. Consider a more secure location (set with .set_extraction_path or the PYTHON_EGG_CACHE environment variable).
warnings.warn(msg, UserWarning)
Configuration:
Sandbox: True
Database: mysql://root@localhost/vatic
Localhost: http://localhost/
Testing access to Amazon Mechanical Turk... ERROR! Signature or access key missing
Testing access to database server... OK
Testing access to web server... ERROR! HTTP Error 404: Not Found
One or more tests FAILED!**
Any help from you will be greatly appreciated.
Bin Yang
@YangBain Have you been able to resolve the problem? I am stuck too.
I have followed this config file but still no luck.
@sjoycode When I change the path to DocumentRoot /path/to/vatic/public <Directory /path/to/vatic/public>, no double vatic path just one, it works.
Thank you, @YangBain, for your response.
It seems both of us messed up with the path-to-the-public directory of vatic. Let me describe my mistake in the following, and how I resolved it.
I started out with the installation, for some strange reason, by first cloning vatic's github directory, going inside it, and then executing vatic-install.sh. It is NOT the proper way to install vatic (I came to realize it later). The proper way of vatic installation (after installing dependencies) is to wget the vatic-install.sh, and execute it as suggested by the main documentation. In my case, with the cloning of vatic's github repository I ended up with two "public" directories (which caused the confusion).
Nevertheless, even with this improper installation I got rid of the HTTP Error 404 by updating the right-path-to-vatic's-public directory in the apache2 config file, and restarting the server (with graceful command), before executing the turkic status --verify command.
@sjoycode When I reinstall vatic and run $ turkic setup --database. I get ImportError: No module named parsedatetime. But when I run python
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
python
Python 2.7.13 |Anaconda custom (64-bit)| (default, Dec 20 2016, 23:09:15)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
Anaconda is brought to you by Continuum Analytics.
Please check out: http://continuum.io/thanks and https://anaconda.org
import parsedatetime
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
There is no problem. So do you know why I get this error. Thank you very much,
@YangBain, sorry about the late response.
I vaguely remember having faced similar difficulty, and finding one github thread useful to resolve the issue. I can't remember exactly which thread it was but have you taken a look at this thread?
https://github.com/maebert/jrnl/issues/75
Interestingly, this useful article on vatic installation has also hinted at the same way of upgrading parsedatetime.
I am facing the similar difficulty with YangBain, but I can't open the two links: https://github.com/maebert/jrnl/issues/75 and http://cs-people.bu.edu/sameki/blog2.pdf.
Can you help me? Thank you very much.