Content is stale on the manage content screen

8 replies [Last post]
Joined: 05/23/2011
Points: 41

My content on the manage content is not updating. It's pulling results but they are old. I'm thinking it's an issue with sphinx. Does anyone know all of the sphinx scripts that should be running?

Joined: 05/23/2011
Points: 41

Found it:

/usr/bin/php /opt/kaltura/app/plugins/sphinx_search/scripts/populateFromLog.php /opt/kaltura/app/plugins/sphinx_search/scripts/configs/server-sphinx.php

Joined: 05/23/2011
Points: 41

Kaltura guys,

Any chance I could get a list of the scripts that should be start on boot?

Joined: 02/15/2011
Points: 0

- Apache
- MySql
- Memcached
- Sphinx – /etc/init.d/sphinx_watch.sh
- Batch Manager - /opt/dev/kaltura/app/scripts/serviceBatchMgr.sh restart
- Sphinx Populate - /opt/dev/kaltura/app/plugins/sphinx_search/scripts/populateFromLog.php /opt/kaltura/app/plugins/sphinx_search/scripts/configs/server-sphinx.php

Joined: 05/23/2011
Points: 41

Thanks!

Joined: 07/01/2011
Points: 37

I spent some time getting these listed services to auto start using Kaltura CE 4.0 running on Ubuntu 10.4 x64 server. Here's the steps I took to ensure the Kaltura specific services were auto started on server reboot (I was comfortable that the items installed through the ubuntu repos: apache, mysql, memcachd were all starting correctly on server reboot).

I hope this is of some help.

Gavin.

## auto starts searchd, by creating symbolic link and then adding references to the run level
$ sudo ln -s /opt/kaltura/app/scripts/watch_sphinx.sh /etc/init.d/watch_sphinx.sh

## auto starts searchd, populateFromLog.sh and serviceBatchMgr.sh using root crontab. this unix command enters crontab editor (unix command line)
$ sudo crontab -e

##add the following three lines to crontab (note I output the results of the crontab action to log files)
@reboot /opt/kaltura/app/scripts/serviceBatchMgr.sh restart >> /opt/kaltura/log/cron_onreboot_serviceBatchMgr.log 2>&1
@reboot /opt/kaltura/app/plugins/sphinx_search/scripts/watch.populate.sh /opt/kaltura/app/plugins/sphinx_search/scripts/configs/server-sphinx.php >> /opt/kaltura/log/cron_onreboot_watch_populate.log 2>&1
@reboot /etc/init.d/sphinx_watch.sh start >> /opt/kaltura/log/cron_onreboot_sphinx_watch.log 2>&1

Joined: 11/29/2010
Points: 108

Gavin thanks for reply to my other thread so here I am.

I've done the above and the sphinx_watch script still says this:

"
Thu Nov 3 13:47:37 GMT 2011 searchd on kaltura.hull-college.ac.uk was restarted
sudo: sorry, you must have a tty to run sudo
Exit code for stop was 1
sudo: sorry, you must have a tty to run sudo
"
on repeat in its log file. The file is expanding every 20s or so, so the run on reboot bit seems to be working.

Might this be why I can't even log in to the adminconsole?

Joined: 05/23/2011
Points: 41

It appears that your user have rights to use sudo? Is your user in the sudoers file? What distro are you running on?

Joined: 11/18/2011
Points: 28

Run visudo
visudo

Find line "Defaults requiretty"
:/requiretty

comment it out
#Defaults     requiretty

exit visudo
:wq

no more "you must have tty to run sudo".