|
From: Greenstone D. L. T. <gre...@wa...> - 2026-05-07 23:02:00
|
Hi again, Just to be clear about your 3.12 installation: Did you already have a greenstone installation and you have installed 3.12 over the top of it? - This is bad. Or is C:\BNGS312 a completely fresh 3.12 install, (BNGS312 was a brand new folder) into which you have copied 3.09 collections? - This is good. Iin GLI, if you had to change the collect path, which it seems that you did - this means that previously you were building the collection in whatever collect directory had been specified before. Not in the current greenstone folder. This means the activation wouldn't work. Now that this collect path is correct, you are building the collection in the right place. But again the activation is not working. When greenstone builds a collection, it starts with input files in the import directory. "import" converts them to our xml archive format, in "archives". Then we build indexes and classifiers and metadata database, in the "building" directory. then an activate step moves building to index, and reloads the collection on the server. thank you for sending me the log from expert mode. It has a lot more information in it. >From your build log we can see that the build went through but the activation didn't work. buildcol.pl> ************************ buildcol.pl> * Running Collection Activation Stage buildcol.pl> ************************ buildcol.pl> buildcol.pl> not well-formed (invalid token) at line 44, column 34, byte 1409 at C:/BNGS312/gs2build/bin/windows/strawberry-perl/perl/vendor/lib/XML/Parser.pm line 187. buildcol.pl> Error: Failed to run: "C:\BNGS312\gs2build\bin\windows\strawberry-perl\perl\bin\Perl.exe" -S activate.pl "-library_name" "library" "-collectdir" "C:\BNGS312\web\sites\localsite\collect" "-builddir" "C:\BNGS312\web\sites\localsite\collect\eau01\building" "-site" "localsite" "-verbosity" "2" "-removeold" "eau01" buildcol.pl> No such file or directory buildcol.pl> Can't spawn ""C:\BNGS312\gs2build\bin\windows\strawberry-perl\perl\bin\Perl.exe" -S buildcol.pl -removeold "-gli" "-language" "fr" "-activate" "-site" "localsite" "-library_name" "library" "-collectdir" "C:\BNGS312\web\sites\localsite\collect" "eau01"": No error at C:\BNGS312\gs2build\bin\script\full-buildcol.pl line 45. buildcol.pl> Error: Failed to run: "C:\BNGS312\gs2build\bin\windows\strawberry-perl\perl\bin\Perl.exe" -S buildcol.pl -removeold "-gli" "-language" "fr" "-activate" "-site" "localsite" "-library_name" "library" "-collectdir" "C:\BNGS312\web\sites\localsite\collect" "eau01" buildcol.pl> La commande a échoué. One thing to try - please shut GLI, and stop the greenstone server. Then go to C:\BNGS312\web\sites\localsite\collect\eau01. Is there a building folder? delete index and rename building to index. Then restart the greenstone server. Can you see the new documents in your collection now? If yes, it means that the rest of the collection build was ok, it was just the activation that failed. If you can no longer see the collection in the library - then something has also gone wrong in the build. Can you check the index/buildConfig.xml file - is it valid XML? Opening it in a browser should tell you if its well formed XML or not. Can you please also: start GLI, start a brand new collection, add a single document. You can leave other settings at their defaults. Then do a complete build. Does this work? Or do you get the same error about activation? If this works ok, then it must be something about the eau01 collection that is going wrong, rather than something wrong with your installation. Once we get the answers to all these questions, we will have more idea about where to go from here. Can I also just check - are you using the official 3.12 binary release? (not a release candidate, or a nightly release?) And what version of windows are you using? Regards, Katherine ________________________________ From: Amadou K. Tall <tal...@gm...> Sent: Thursday, 7 May 2026 1:44 pm To: Greenstone Digital Library Team <gre...@wa...> Subject: Re: [Greenstone-users] Retour Hello Ms. Katherine, thank you again for your professionalism. I don't think I described the problem clearly enough. I installed GS312 in a folder containing an older version. The older documents are visible in the library, but the problem is that if I add new documents and run the build with GLI, it gives an error message at the end. Although the GLI log indicates that the documents are added and taken into account, they don't appear in the library. I checked the connection preferences and corrected them by specifying the correct path, but after the build, the same message reappears, and the new documents are not in the library. Diego Spano is also helping me, but the error persists. I'm sending you the GLI log. Sincerely, Katherine. Le mer. 6 mai 2026 à 22:23, Greenstone Digital Library Team <gre...@wa...<mailto:gre...@wa...>> a écrit : Hi Amadou, Thanks for your various emails. Did you try all the things I mentioned in my previous email? It is fine to install greenstone in C:\BNGS312, And it is also fine to copy in collections from previous greenstone installations. But GLI may be confused about which greenstone collect folder it is working with. When you start up GLI do you get a warning about non-standard collect home? - This means GLI is using the wrong collect folder, its using one set up for a previous greenstone. (Note I'll be working on fixing this for the next release) Did you check the file->preferences->connection settings? Is the collect folder specified the one in BNGS312? If not, change it to the correct one. C:\BNG312\web\sites\localsite\collect If that doesn't fix the problem, then next: Find the C:\Documents and Settings\<username>\Application Data\Greenstone\GLI folder. I think different versions of windows sometimes use a different path. eg it could be AppData instead of Application Data. Note, this is NOT where you install greenstone, but instead where GLI stores some config files for when its running. There should be a gonfi3.xml in there. Shut down GLI, then delete the config3.xml file. Restart GLI - do you see your collection? does it have the newly added documents in it? If not, re-add them, rebuild - does it work this time? You can also check the collection folder on the file system - does the import folder contain the new documents you added using GLI? If, after you have tried all the above, you are still having trouble, then do the following: Please put GLI into expert mode, rebuild the collection, and send me the log. The log you sent was using librarian mode, so doesn't have any useful information in it. Regards, Katherine ________________________________ |