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 installed the Kaltura Version 5 VM Image - 64bit and while most areas work fine there are consistant issues of Internal Server Errors when in the Content Section. If I'm on another section and simply click the Content tab the page will load but, then give me the error. I click OK adn the page is fine but, just about anything I click results in the error.
Same issue when I try to upload content from desktop. I can select files then when I click the button to upload them I get the error.
Any help would be appreciated. Haven't got ssh access to get any error logs yet so can't submit at this time.
I did just look at the server and notice that the great majority of files and/or directories for Kaltura are owned by root and belong to group root. Is that correct?
Hi
Did as you posted but still get the same errors. I made sure /opt and everything below was changed to apache:apache.
Other ideas? Surprising using the VM download wouldn't run right.
Bob
That's what I did and it seemed to fix those error issues. The only other thing possibly is to make sure that all the relevant services are running:
Run your populateFromLog script thus:
Apart from that, I dunno. Sorry.
[edit to add]Look at this and see if it helps:
http://www.kaltura.org/internal-server-error-occured-0
Run: ps -aux | grep searchd
if Sphinx is down, run the following:
service sphinx_watch.sh start
If after start Sphinx still doesn't come up, Sphinx's index might be corrupted, try cleaning the Sphinx index:
rm -f /opt/kaltura/log/sphinx/data/*
service sphinx_watch.sh start
Or better yet - install the latest version from: https://github.com/kaltura/ce-packager
instructions for installing on VM: http://kaltura.github.com/ce-packager/docs/screencasts.html
The entire /opt/kaltura/ structure (or wherever you have installed the kaltura CE) should be owned by the HTTPD user and group - usually apache:apache. So, if you can get shell access, run this command:
replacing where applicable to your installation (-R = recursive through child folders and files).