I had a similar issue, and it turned out to be with SSL. You said earlier
that during installation you set ssl.available=false. Has that been
corrected? I believe the installer hard-codes your truststore location and
password into the shell scripts fedora-admin.sh, fedora-ingest.sh, etc.
Open up fedora-admin.sh and look for this line:
(exec "$JAVA" -Xms64m -Xmx96m \
-cp
$FEDORA_HOME/client:$FEDORA_HOME/client/fedora-client-3.1.jar \
-Djava.endorsed.dirs=$FEDORA_HOME/client/lib \
-Djavax.net.ssl.trustStore=$FEDORA_HOME/client/truststore \
-Djavax.net.ssl.trustStorePassword=yourpassword \
-Dfedora.home=$FEDORA_HOME \
If the information here is incorrect, you can change it manually. But it is
probably wrong in all your script files, in which case it might be easier to
re-run the installer.
Just a shot in the dark, but it solved my problem.
Cheers,
Bill
On Wed, Mar 25, 2009 at 11:23 AM, arne anka <[email protected]>wrote:
> thanks, but sadly, no, it doesn't help.
>
> i do it from localhost ...
>
> > data/fedora-xacml-policies/repository-policies/default/deny-apim-if-
> > not-localhost.xml
>
> .. but since the pc got an ip via eth0 too i added that to the file and
> restarted tomcat -- but to no avail.
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Fedora-commons-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
>
------------------------------------------------------------------------------
_______________________________________________
Fedora-commons-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
