Error from remote server

Manon,

Reindex has always been a problem when your section reaches a certain number of records. It depends on your PHP server settings, the way Cobalt reindexes its data, the Cobalt data structure itself and how much data (all fields together) every record stores.

For the PHP settings, the reindex script tries to override the max_execution_time setting, the bigger problem is the PHP allocated memory, based on the way the reindex works now.

The script reads ALL content of ALL records from a section together at once which can easily result in a memory problem, once you have a certain number of records in your section.

Using PHP 7 can help here a little, since it will allow reindexing more records based on lower memory consumption.

Another issue is the number of indices the #js_res_record table uses. Reindexing will be a massive process for the database here. Even simple inserts can slow down everything with several users adding records at the same time. If Cobalt development continues, improvement of the index handling should be a priority to allow Cobalt to be used with bigger datasets.

The best advice for your reindex problem would be an improved reindex script (your own script). To study the existing process, see /plugins/mint/toolset/toolset.php

I just remember that i had a similar error message when creating complex PDF lists from Cobalt on a local Mac Server. --> Proxy Error 502

I solved it in adding the ProxyTimeout based on the suggestions of this discussion: Click here to link...

Important point was, to restart the Apache instance which provides the proxy service. link

Can you adjust PHP settings? what if you create php.ini in the root of your site?

Sackgesicht If Cobalt development continues, improvement of the index handling should be a priority to allow Cobalt to be used with bigger datasets.

I remember that.

Update: the helpdesk finally advised me to copy the whole database to a local webserver (XAMPP) and then run the reindextool. I'v tried this, and the good news is: the reindex tool works fine. It takes 2 minutes, and then I get the message '10.650 records reindexed' (or soemthing like that). So that's in my case not a problem. The rest of the problem is not solved yet, but for those who are interested, I thought I'd let you know.

Most of the time the reindex produces an "Out of Memory" error. I had to increase the memory limit to 1GB from the default 128MB to be able to reindex some sections.

Reindex improvement:

PHP7 helps here a lot. Another thing to reduce the memory consumption is to adjust the reindex SQL query on line 246. Removing the unnecessary column "fields" will reduce the memory consumption big time.