Could you try the following:
1. Stop the server and GLI.
2. If you have a file called glisite.cfg.in in your top-level Greenstone
folder, then delete another file in the same folder called "glisite.cfg".
If you don't have a file called glisite.cfg.in (I can't remember if this
was only introduced since Greenstone version 2.83), open the file
glisite.cfg in a plain text editor.
3. Delete the line containing the string URL_pending.
4. Then make sure the following values are set in the file:
5. Save the file.
6. Try running GLI again. Does it work now?
The issue you've described can arise if the GLI was ever improperly shut
down (say if it crashed or was terminated with Ctrl-C instead of through
GLI's own exit button). Greenstone v2.83 was adjusted to better deal
with such a situation. From memory, it could also happen if GLI is run
(which launches its own gs2-server instance), and if thereafter the
gs2-server.sh script is run as well. Doing so may end up launching two
instances of the gs2-server application, which might both try to access
and modify the same config file and thus leave it in a confused and
Jim Hart wrote:
> Version 2.82 Linux GLI has been working fine for weeks. All of a sudden,
> today, it's throwing an error:
> java.net.MalformedURLException: no protocol: URL_pending
> The only other weird thing is that when starting the GLI, this morning,
> it tried to launch firefox. I got that to stop by turning off the
> autoenter flag, but it's never happened before.
> The error message doesn't show up in a search of Trac or the developer's
> list archive. Does anyone have an idea of what might be wrong?
> Jim Hart
> Bates College
> greenstone-devel mailing list