Yes, Fridolyn is correct, the problem is when launching the cronjob
manually using rebuild_zebra.pl -v -b -r
I added one record manually into the catalog, and that one is showing
up. But the ones that were loaded by taking from the primary instance
(we duplicated the database) don't come up in
Yes, Fridolyn is correct, the problem is when launching the cronjob
manually using rebuild_zebra.pl -v -b -r
I added one record manually into the catalog, and that one is showing
up. But the ones that were loaded by taking from the primary instance
(we duplicated the database) don't come up in
On Tue, Apr 12, 2011 at 11:38 AM, Tomas Cohen Arazi wrote:
> 2011/4/12 Fridolyn SOMERS :
> > Hie,
> >
> > There is one problem with multi instances that you maybe didn't notice :
> >
> > The environment variables KOHA_CONF and PERL5LIB are the same for each
> > instance
> > (they are redefined in
2011/4/12 Fridolyn SOMERS :
> Hie,
>
> There is one problem with multi instances that you maybe didn't notice :
>
> The environment variables KOHA_CONF and PERL5LIB are the same for each
> instance
> (they are redefined in cronjobs and apache conf).
> They are mandatory for lauching perl scripts ma
Hie,
There is one problem with multi instances that you maybe didn't notice :
The environment variables *KOHA_CONF* and *PERL5LIB* are the same for each
instance
(they are redefined in cronjobs and apache conf).
They are mandatory for lauching perl scripts manually.
I think that's why rebuild_ze
All,
We created a second instance of Koha using the instructions at
http://wiki.koha-community.org/wiki/Installing_Multiple_Instances_of_Koha
We dumped the data from our original instance and then reloaded it into
the koha_test instance. We have tried to reindex several time by using
rebuild_
