Copyright © 2012 Kaltura Inc.
All Rights Reserved. Designated trademarks and brands are the property of their respective owners.
Use of this web site constitutes acceptance of the Terms of Use and Privacy Policy.
EduVideo.org
Hi,
We have installed kalturaCE_v5.0.0 in centos server in a resolved domain.
When we browse the below URLs and we get 404 not found error.
http://domainname.com/admin_console
Please advise how to fix.
Thanks,
JP
Hi ,
We are getting below error when we run the command - grep "ERR:\|PHP\|Stack trace" /opt/kaltura/log/*.log
/opt/kaltura/log/kaltura_sphinx_populate.log:PHP Fatal error: Uncaught exception 'PropelException' with message ' [wrapped: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away]' in /opt/kaltura/app/vendor/propel/util/BasePeer.php:467
/opt/kaltura/log/kaltura_sphinx_populate.log:Stack trace:
Run: ps -aux | grep searchd
If Sphinx is down, run the following: service sphinx_watch.sh start
If Sphinx still doesn't come up, Sphinx's index might be corrupted, try cleaning the Sphinx index:
Also check if you have enough space in your drive. df -kh
Hi,
Please find the results when we run the commands
# ps -aux | grep searchd
Warning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.8/FAQ
root 4471 0.0 0.0 103236 872 pts/0 S+ 14:25 0:00 grep searchd
root 9113 0.0 0.0 23500 1060 ? S Dec17 0:00 /opt/kaltura/bin/sphinx/searchd --config /opt/kaltura/app/configurations/sphinx/kaltura.conf
root 9114 0.0 0.0 159572 5208 ? Sl Dec17 5:41 /opt/kaltura/bin/sphinx/searchd --config /opt/kaltura/app/configurations/sphinx/kaltura.conf
# service sphinx_watch.sh start
Starting Sphinx Watch Daemon: [ OK ]
Starting Sphinx populateFromLog watch: 13916 [FAILED]
The disk space levels are normal only. There is no issue in disk space.
Please help us to resolve this .
Thanks,
Jaiprasad.
Please help us on this issue.
Need help from kaltura team
It seems that your MySQL is either not running or is not accessible by Sphinx.
Check the file: /opt/kaltura/app/configurations/db.ini
Make sure that the DB credentials and hostname are correct.
Try running the following, just in case you will get more info (it's slightly more accurate than the one before):
grep "ERR:\|PHP\|trace\|CRIT" /opt/kaltura/log/*.log
Also try changing in max_allowed_packet = 16M in my.cnf and restarting mysql.
A 404 error would indicate improper Apache setup, as in the configuration is not being loaded. - Try verifying your apache settings according to the prerequisites.
Confirm that SELinux is set to Disabled or Permissive by typing the command getenforce
1 . The db.ini file is not present in the below path of the server
/opt/kaltura/app/configurations/db.ini
2 . Got below error when we run the command grep "ERR:\|PHP\|trace\|CRIT" /opt/kaltura/log/*.log
/opt/kaltura/log/kaltura_sphinx_populate.log:PHP Fatal error: Uncaught exception 'PropelException' with message ' [wrapped: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away]' in /opt/kaltura/app/vendor/propel/util/BasePeer.php:467
/opt/kaltura/log/kaltura_sphinx_populate.log:Stack trace:
3 . SELinux is set to Disabled only.
We are using parallel plesk panel for web hosting control panel. In that they need to set lower_case_table_names = 0 as zero in my.cnf, but for kaltura it need to set as 1.If we set as 1 all the the sites are not working.So we set as lower_case_table_names = 0 only.
Please advise us.
@jaiprasad - currently you can't run Kaltura with such a deployment.
You should dedicate a server with all prerequisites configured, including the my.cnf file settings as advise in the install guide.
So kaltura have to be install in dedicated server without plesk control panel.
Please Reply .Waiting for your update.
So kaltura have to be install in dedicated server without plesk control panel.
Kaltura team,Please Reply .Waiting for your update.
Hi Team,
Can you please update us for the below query
"Kaltura have to be install in dedicated server without plesk control panel."
I think Zohar's response was quite clear, you need to install kaltura on a different server.
Any errors show up on your log files?
Use the following find errors in the Kaltura logs -
grep "ERR:\|PHP\|Stack trace" /opt/kaltura/log/*.log