Lukas and Michael, Thanks for your replays. I was able to get rid all the errors. Then after one other change, get the web page to come up. One was to remove the jspapi.jar in the /usr/share/tomcat5/webapps/rhn/WEB-INF/lib dir (which was a soft link to the same file else where. There seems to be many links, some of which are links to links to links, which seems a bit inefficient and confusing). The other was to change the permissions in the /usr/share/tomcat5/conf file.
This got rid of the errors, but the web page still would give the "Not Available" message. What looks to have fixed this was to change the following line in the /etc/rhn/rhn.conf file hibernate.connection.driver_proto=jdbc:oracle:oci to hibernate.connection.driver_proto=jdbc:oracle:thin Then the page came up. I'm going to go through the install again to day again, as I did several other changes to make sure this is the reason why it came up. Also, during setup I have had to create directories and change permissions on files before the Spacewalk install takes place, as it has not created or changed them them during the install process, to make sure they get populated correctly. The install process needs to be run twice, as the /tftpboot directory does not get populated on the first run. My environment is a standalone one, where I need to import all files to, so I'm not sure if that has anything to do with this problem. Thanks again Scott On Mon, Dec 6, 2010 at 3:20 AM, Lukas Zapletal <[email protected]<lzap%[email protected]> > wrote: > On 12/02/2010 04:12 PM, Scott Rakow wrote: > >> % WARNING: User database is not persistable - no write permissions on >> % directory >> >> Which directory? >> >> This has been one of the frustrating things is that I don't know. And >> turning up logging in Tomcat has not helped. I have changed the >> permissions in several directories to no avail. By default for >> Spacewalk, where is Oracle dropping it? >> >> Your link helped point me to the docBase problem and after reading up >> more on Tomcat I was able to get rid of the docBase error by adding a >> Context line to the server.xml file. However the Offending class error >> is still present. So, I'm doing more reading on Tomcat to see what else >> may be causing the problems. Any other ideas or suggestions? >> > > Hello, > > the solution is really simple --- to remove the offending JAR. You can > delete it safely and we did - in the current master (Spacewalk 1.3) it wont > be distributed any longer. > > About the appBase warning - you can ignore it. Does not indicate a real > problem. > > Thanks > > -- > Later, > Lukas "lzap" Zapletal > > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
