From: Dale P. <ldp...@gm...> - 2013-03-31 21:05:54
|
Thanks. Problem solved. I decided to check the logs again. This time I started and stopped the installation, once as root- where everything worked - and once as my preferred user which did not allow me access via the browser, but the system was running. I copied the appropriate sections out of the log and pasted them into NoteTab separate files and 'blinked' back and forth between the files looking for different lines. I finally found what I had been overlooking when just reading the logs. There was a small file in the /tmp folder 'xfTestConfigOneElementInMemory.data', or something like that which was owned by root. Probably created when I installed eXist. I changed the ownership to my preferred user and that solved the problem. Moral of my story is to learn to read the logs creatively. Thanks everyone. Dale On Wed, Mar 27, 2013 at 1:43 PM, Dmitriy Shabanov <sha...@gm...>wrote: > Anything at logs? > > > On Wed, Mar 27, 2013 at 6:07 AM, Dale Patterson <ldp...@gm...>wrote: > >> Good day everyone - >> I still have a puzzle using eXist 1.4.3 on CentOS. I have discovered >> that I can start the program using /etc/init.d/exist or services exist >> start and the program will start. However, if I have set the RUN-AS_USER >> to a user id, then the eXist is invisible through the browser. What I >> mean is if I use PS aux I can see that eXist is running and if II use >> 'service exist status' I get a response that it is running. But when I >> enter its url in the browser I get a failed response when I access the >> site ( i.e. IP:8080/exist). But if I comment out RUN-AS_USER so that it >> runs under root, then I can access the site. I looked in the wrapper.log >> and it said I had a mis-match with the wrapper, that I was running a 32-bit >> wrapper under a 64-bit JVM system (and the CentOS I am on is a 64 bit >> system). So I changed the wrapper to the 64 bit version and there was no >> change. I even downloaded a 32 bit version JVM and still the problem >> persists. >> >> It really feels like some type of permission issue. But all the eXist >> files are owned by the preferred user and folders like /tmp are also >> accessible. Any suggestions would be appreciated. Thank you. >> > > -- > Dmitriy Shabanov > |