Advanced OpenDiscovery Search [is not working}

💬 General Discussion
1

Hello guys today i experenci some problem with Advanced OpenDiscovery Search is not working wen we search in the bar it appear in blank with no error or a warning

http://awesomescreenshot.com/02d2vgwbc3

Log
Optimise AOD Index running 05/27/2014 12:00am 05/27/2014 12:30am
Optimise AOD Index done 05/26/2014 09:00pm 05/26/2014 09:00pm
Optimise AOD Index done 05/26/2014 06:00pm 05/26/2014 06:00pm
Optimise AOD Index done 05/26/2014 03:00pm 05/26/2014 03:00pm
Optimise AOD Index done 05/26/2014 12:00pm 05/26/2014 12:00pm
Optimise AOD Index done 05/26/2014 09:00am 05/26/2014 09:00am
Optimise AOD Index done 05/26/2014 06:00am 05/26/2014 06:00am
Optimise AOD Index done 05/26/2014 03:00am 05/26/2014 03:00am
Optimise AOD Index done 05/26/2014 12:00am 05/26/2014 12:00am
Optimise AOD Index done 05/25/2014 09:00pm 05/25/2014 09:00pm

2

Did you set up a cron job?

3

yep the Advanced OpenDiscovery Search have been working today i found that is not working anymore.

4

still have this problem… any solution

5

Are you sure the cron job is running and not throwing an error?

You should put the SuiteCRM cron command in a .sh script along with something that will let you know the job ran… like “touch test.txt” .

My bet is you have a cron glitch. Maybe talk with your ISP.

6

I get this messange

/home/domain/public_html/suitecrm/cron.php: line 1: ?php: No such file or directory
/home/domain/public_html/suitecrm/cron.php: line 2: syntax error near unexpected token 'sugarEntry'' /home/domain/public_html/suitecrm/cron.php: line 2: if(!defined(‘sugarEntry’))define(‘sugarEntry’, true);’

7

Check cron.php file. Looks like it’s missing PHP opening tag <?php
Maybe it was edited with vim and first character was removed with “x” key or something like that.

8

Looks like I cant edit my previous post.
It could be also bad entry in crontab. If you’re running it without php or path to php it will try to interpret php script as bash script.

Depending how your cron jobs are setup edit it for user www-data (if you’re on Ubuntu)

crontab -u www-data -e

then make sure you have something like that:

* * * * *       cd /home/domain/public_html/suitecrm; php -f cron.php > /dev/null 2>&1

If the job looks good and you have php executing cron.php make sure php CLI executes properly.
check where is your php binary:

whereis php

then make sure that path (usually: /usr/bin) is in your global environment

vi /etc/environment
9


Here is my setup is 0,30 because my host Siteground NOT allow 0 minutes

The strange thing is it was working fine and a motn ago stop working

10

Advanced OpenDiscovery does not work for us either. Please point us to a guide on how to configure this. The earlier reply “Did you set up a cron job” is too vague for us to understand.

Thank you.

11

Hi Nick,

Is the cron job set up in your server to allow AOD to index the records? Are you getting errors, or is it simply displaying a white screen? I presume AOD is enabled in Admin -> AOD Settings?

Thanks,

Will.

12

Hello Will, I do not know if “the cron job is set up.” Could you point me to some instructions?

I am getting the white screen. I have (had) AOD enabled. I disabled it a few hours ago. The inbuilt global search works in that case.

Thank you.

13

Hi Nick,

What is your server setup? Please navigate to Admin -> Schedulers and navigate into ‘Optimise AOD Index’ and ‘Perform Lucene Index’. Are there entries in the job log? When was the last successful run?

Thanks,

Will.

14

I am on CentOS + Apache 2.2.15
The Lucene index job has never run. After I reply, I will search.

15

I have attempted to find the instructions to configure the cron jobs. Can you point me to something?

16

Hi Will this is my log for ‘Optimise AOD Index’ and ‘Perform Lucene Index’
Optimise AOD Index running 07/31/2014 09:00am 07/31/2014 09:00am
Optimise AOD Index done 07/31/2014 08:00am 07/31/2014 08:00am
Optimise AOD Index done 07/31/2014 07:00am 07/31/2014 07:00am
Optimise AOD Index done 07/31/2014 06:00am 07/31/2014 06:00am
Optimise AOD Index done 07/31/2014 05:00am 07/31/2014 05:00am
Optimise AOD Index done 07/31/2014 04:00am 07/31/2014 04:00am
Optimise AOD Index done 07/31/2014 03:00am 07/31/2014 03:00am
Optimise AOD Index done 07/31/2014 02:00am 07/31/2014 02:00am
Optimise AOD Index done 07/31/2014 01:00am 07/31/2014 01:00am
Optimise AOD Index done 07/31/2014 12:00am 07/31/2014 12:00am

Perform Lucene Index done 07/31/2014 12:00am 07/31/2014 12:00am
Perform Lucene Index done 07/30/2014 12:00am 07/30/2014 12:00am
Perform Lucene Index done 07/29/2014 12:00am 07/29/2014 12:00am
Perform Lucene Index done 07/28/2014 12:00am 07/28/2014 12:00am
Perform Lucene Index done 07/27/2014 12:00am 07/27/2014 12:00am
Perform Lucene Index done 07/26/2014 12:00am 07/26/2014 12:00am
Perform Lucene Index done 07/25/2014 12:00am 07/25/2014 12:00am
Perform Lucene Index done 07/24/2014 02:30pm 07/24/2014 02:30pm
Perform Lucene Index done 07/23/2014 02:30pm 07/24/2014 02:30pm

17

Hi there,

@jninhilario - It may be worth checking your logs to see why the ‘Optimise AOD Index’ job is still running. You can kill the job in ‘job_queue’ but it would be worth checking for errors which may have caused this, before killing it.

@Nick - Normally on a linux setup, you would ssh onto the server and then run ‘sudo crontab -e’ which would open up the cron tab. You would then navigate to Admin -> Schedulers in SuiteCRM and copy the link shown @ the bottom of the list of schedulers and paste this into the crontab file and then do ‘Ctrl+X’ and press Y to confirm.

Note: These settings/options may differ depending on your environment and it is always advisable to run a test before performing changes on your production environment.

Thanks,

Will.

18

Here is my sugarcrm.log
http://tempsend.com/0D75189C61

1 Like
19

My issue is resolved. Your steps were perfect.

  1. SSH and sudo into crontab using sudo crontab -e
  2. In SuiteCRM’s admin panel, find Schedulers page
  3. Using the crontab default VI editor, paste the cron setup line from the bottom of the Schedulers page into the cron file.
  4. Save and exit from VI
20

Hi Nick,

That’s great. If you have any further issues, please let us know!

Thanks,

Will.