Barry Callahan wrote:
I've installed Emilda 1.2.1 on my webserver, but I'm having some issues
with it... I was hoping I could get some assistance tracking down the
problems...
Hello,
Lets see what we can do... ;-)
The first issue I have is that when I go to the login page, I'm always
presented with a message box saying that my setup is not up to date.
The self-test says everything's ok, running "Import MARC fields" says
everything's ok, and updating locales goes ok. Maybe this is related to
the second issue...
If you have a look at the bottom of the setup page, you probably will
see a line saying that the file .setup is not writeable. Thus, there is
a file called .setup in the Emilda root that needs to be writeable. This
file contains no vital information, so there is no problem to making it
just writeable by the web server, alternatively chmod 777
The second problem I'm having is that every time I try searching for a
book, I get the following error text when emilda tries to connect to my
zebra server:
YAZ error: 109 (Database unavailable) (Host: localhost:9999/Default)
I noticed that the nightly demo had the same problem the last few
nights, but it's ok now... Maybe the causes are similar? I've checked
to ensure that the zebra server is running on port 9999, and that port
is not being blocked by iptables....
I assume that you have done all the Zebra related routines described in
http://www.emilda.org/node/36 especially the starting commands in that
particular order. If you still are experiencing this issue, it might be
related to the fact that your database is empty. Zebra tends to throw
this error if your database is empty. Thus, getting MARC.pl working and
adding an item would solve this issue.
My third problem is that I think my apache (2.0.48) server has a
misconfiguration. If I go to add a book to the database (ignoring the
fact that I can't connect to the database) when I click the submit
button, I end up downloading the MARC.pl script instead of running it.
I think I need to just specify the emilda directory as being a
ScriptAlias, but I figured I'd ask. Maybe somebody has a httpd.conf
file they're willing to share? I found a reference to a few samples in
the list archives a while back, but the files don't exist there anymore.
(unless I'm blind, which is possible)
You will need to add some configuration directives to your httpd.conf,
thats correct. The following example will do the trick:
<Location /emilda>
AddHandler cgi-script .pl
Options ExecCGI
</Location>
where the /emilda is the absolute or relative url to your emilda
installation. The <Location> directive can also be replaced by a
<Directory> directive, where you just give the absolute path to your
Emilda installation.
Lets hope this will help you get your system working. There is
documentation online, incase you have not found your way there. Its
under the url http://www.emilda.org/documentation
Regards,
Thanks in advance for any help.
Barry
_______________________________________________
Emilda mailing list
Emilda@xxxxxxxxxxxxxxxxxx
http://lists.realnode.com/mailman/listinfo/emilda
--
Christoffer Landtman
CEO
Oy Realnode Ab
landtman@xxxxxxxxxxxx
www.realnode.com
|
