I take it that you created and built this collection with the 2.40a
release of GLI, before upgrading to 2.41. I'd forgotten that we'd
changed how we name log files. It was necessary to move the build status
letters, 's' (which signifies a successful build), 'f', 'c' or 'u',
inside the log itself.
To fix this, open the folder:
where you'll find several log files named something like
build_log.1071271572338s.txt. These log files are obsolete and should be
renamed from .txt to .old or deleted altogether. You should then find
GLI starts properly (you may still have to steal the lock if a lock file
has been left behind by an earlier unexpected exit from GLI).
I'm sorry about this, and I'll immediately add a bit of code to detect
and ignore these older log files, so future generations of GLI users
won't have the same problem.
Cheers, and Merry Christmas
Greenstone Project, NZDL, University of Waikato
Carl Jones wrote:
> I'm on version 2.41, and after having some limited success creating a
> collection when I try to go back add additional documents using GLI
> the application detects the presence of a lockfile:
>> The presence of a lock file suggests this collection is already open
>> Do you with to 'steal' the control of this lockfile (not recommended)?
> If I _do_ choose to steal the lockfile, the GLI interface doesn't
> open and I'm dropped back to the command line with the following:
> Running the Greenstone Librarian Interface...
> java.lang.NumberFormatException: For input string: "1071271572338s"
> at java.lang.Long.parseLong(Long.java:332)
> at java.lang.Long.parseLong(Long.java:381)
> at org.greenstone.gatherer.Gatherer.run(Gatherer.java:286)
> at org.greenstone.gatherer.Gatherer.main(Gatherer.java:614)
> Conversely, if I choose 'cancel' (don't steal the lock file) and then
> try to open a collection I get the following error:
> The collection at: <pathname>
> cannot be opened because:
> For input string: "1071271572338s"
> Has anyone seen similar behavior and have a workaround?
> greenstone-users mailing list