Errors thrown in luceneapi_node.index.inc

Hi Bizarro.

First, I would check that the settings in admin/settings/luceneapi to see if the permissions are too strict. This is what determines the filesystem permissions are set when index files are created. If you think the settings are OK, please report back.

Thanks,
Chris

Hey Rob.

Off hand, do you know if you filed directory resides on a remote filesystem, such as NFS or something similar?

Thanks,
Chris

Hi Bizarro.

Looking through the code, the index cannot be opened by the web server. 99% of the time permissions aren't set correctly which causes this error to be thrown. Make sure you know what user the web server is running as, because generally with FTP the user/group that owns the file is different than the one used by the web server.

Thanks,
Chris

I have the same issue as I migrated the site from local to vps.

cpliakas, how do you find the user web server is running as? When i looked up the users in the OS i found about 25! the folder in question has 777 permission, and still giving error.

Is there a way to remove the index and start from scracth?

Thanks a bunch!

Hi bardya.

What VPS? Could it be using a networked file system? One way to find the user is to do an `ls -l` on the files directory to see what user the files are being written as. Whatever owner / permissions the web server is using is what the index needs to be as well. To me, this issue really seems to be something that is outside the scope of the module and has to do with the environment the site is running on. I have been wrong before, but I am demoting this from a "bug report" to "support request" for that reason.

In terms of wiping the index, you can manually delete the sites/default/files/luceneapi_node directory and then select the "wipe index" button in admin/settings/luceneapi_node/statistics. That should do the trick and start you from scratch.

Thanks,
Chris

cpliakas thanks for getting back to me. I matched the group and owner of the folder to the rest of the site so we are good on the permission side.

On the index side it took a couple of tries:

Attempt I
I did the following:

1. Removed folder named luceneapi_node
2. This allowed me to get the index statistic tab without the error
3. I selected wipe index
4. I ran cron to build index

Result I
When i tried to get access to index statistic i got the following error:
Error thrown in ../sites/all/modules/luceneapi/luceneapi.admin.inc on line 431.

Attempt II
So I repeated steps above with one change

1. Removed folder named luceneapi_node
2. This allowed me to get the index statistic tab without the error
3. I selected wipe index and checked the check box "Rebuild index after operation"
4. Index was built successfully
5. I ran cron

Result II
When i tried to get access to index statistic everything was good and search worked

I'm seeing the luceneapi_node.index.inc error in v6.x-2.4 when I go to /update.php.

Would it not be better if this recorded a watchdog message to warn the site admin of the problem? Try the attached file for a starting point.

Looking through the code some more, the problem may very well simply be that $errstr is passed to the luceneapi_index_open() function before it is declared.

Ok, here's a patch that assigns $errstr an empty string before it is used in every function it's used in.

I added similar tasks for the submodules:

• luceneapi_dym: #946766: $errstr passed to functions before it is assigned.
• luceneapi_morelikethis: #946772: $errstr passed to functions before it is assigned.
• luceneapi_cck: couldn't find any references to $errstr.

Due to end of life announcement.

Thank you bardya!
I had a problem with lucenapi 6.24 :
luceneapi_node.index.inc on line 71

My folder 'default/files/luceneapi_node' on my FTP server wasnt correct. I've deleted it, and wiped the index, Rebuilt -> done ! Thanx