Re: linking (limiting???)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Martin, On 12/15/13, 4:52 PM, Martin Gainty wrote: > Mark I assume you're referring to Virtual DirContext...? path="/mywebapp" docBase="/Users/theuser/mywebapp/src/main/webapp" > > You shouldn't use the "path" attribute, here. You should know this. > className="org.apache.naming.resources.VirtualDirContext" > > extraResourcePaths="/WEB-INF/classes=/Users/theuser/mywebapp/target/classes,/pictures=/Users/theuser/mypictures,/movies=/Users/theuser/mymovies"/> VirtualDirContext > is not necessary, but it is one option. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJSrkvIAAoJEBzwKT+lPKRYZ4cP/1SvH4mwBFUIjmtiGnBfa3vU IHwSsyfHaoyO55p1/1AasP6avv8rjpMl9i8d+kmYolIiYMF461UCGTuE44SzHP1Y O1/VayieLS3A/pn2YS86LqfXTuuKD4pWQ93TDEihchpXpJ+/B3sMfJeCzvRRYue7 PZ32luoXvsHEgA2nt7Qpp88Nz+9RggYAw5KlnTrnndqyMl8FyWLkTccpaqTthOnW LcZgieAW7ySWZRbyAiXNEsk6kVDTat9z/EAeDmMWqN43LJikxLh4Glez3jv80mhy cNtZ43mqroyCRF82nSO6eHxeSxIh70kdVaz6/x7QaBNAWIe96DHlQFTZwBnClzwY T5uHYEBwSTfZ7GFlT/z+zGWxhX0fme9q9auZyXnufEHqPadKWkGdbjFN4dgifYm6 Js/O5o2TsCK9RKYbNomPygZ+fek6AqtFtEOvimyFd0Udml4hoQKzTOc81Rb/Dhx9 J/u47Oj754kTL18mv0Ci1ZOB4IQ1jO8YZDz35RU/9MZeoQ+LKkSxZHZTL1/PaH0u h15XSAWv5MVHelPJM7WZWfrQdGAuYKUR+QOB1T4zoW+HKkcjsY7pilO3FJvrv84Y +Xei2lxZLFPjF8c50HYuawqt5/un9vvARVofo2Hb5xr0E6gNxxma8X7LvIPWJ5YZ 3ii7LoCyfyTASfv7sPk0 =wGs5 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: linking (limiting???)
On 12/15/2013 2:43 PM, Ray Holme wrote: Hmmm - I use JNDI for connections and you lost me with extra paths - although it appears this is exactly what I want. This is exactly what I was thinking, I will start digging to learn how to use properly. Thanks Mark On Sunday, December 15, 2013 4:53 PM, Martin Gainty wrote: Date: Sun, 15 Dec 2013 12:41:55 -0800 From: its_toas...@yahoo.com To: users@tomcat.apache.org Subject: Re: linking (limiting???) On 12/15/2013 8:34 AM, Ray Holme wrote: I am a Linux user and love linking things to reduce copies. Apache/Tomcat (by default) does not allow symbolic linking (nice as it can cross mounted file systems) except in the top apache/lib directory. I use hard links in the Application/WEB-INF/lib directories to reduce copying and help me manage things. HOWEVER, some applications have special needs - e.g. pictures. You don't want to always distribute these with the release of the application (Application.war file), so symbolic links are the way to go (except for MS land, sorry). The nice solution to this is: .../webapps/Application/WEB-INF/context.xml which must contain at least the two below lines: However this allows ALL symbolic linking in the Application directory. I agree with the developers that this is dangerous. Is there some way to allow linking in just ONE sub-directory of the Application?? - e.g. .../webapps/Application/images This would allow all I need to have local images for the application without endangering other things using a symbolic link. If you use Tomcat 7, read the following: http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Resource_Definitions ...Mark I assume you're referring to Virtual DirContext...? . . . just my two cents /mde/ MG>Thanks Mark, If you're deploying in the appBase directory, then this should work (haven't tried it): Place this in either META-INF/context.xml of your web application, or in $CATALINA_BASE/conf/[hostname]/[appname].xml Modify the above to fit your requirements. Note that the META-INF/context.xml file is no longer copied to $CATALINA_BASE/conf/[hostname]/[appname].xml by default. Read the following to understand how these two interact. http://tomcat.apache.org/tomcat-7.0-doc/config/host.html (search for copyXML on the above page). . . . just my two cents. /mde/ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: timing is everything when starting - a 32 bit question
OK, the init.d script was probably very old and it looks like I need to learn systemd control. Did not check apache/logs as there was no sign the script ran, thanks will look there too. yes built and installed mod_jk - the app works fine when I do get it going, yes running SELinux so - time to dig into systemd scripts (after working with Unix BSD and Sys5 for years, I guess I am too used to doing things the old way. argh!!! >My approach would be the following: >1. Create an unprivileged user to run Tomcat >2. Install Tomcat from tomcat.apache.org for this user >3. Create a systemv init script - use tomcat-systemv contents as a guide >4. Wrap the init script in a service file. >5. Use systemctl enable or disable as other systemd services >The init script for Tomcat is pretty ugly - mine's around 575 lines for Tomcat 6 or 7 and CentOS 6.5. The scripts are pretty defensive, which accounts for most of the length. 1-3 are DONE. Yes my script is not quite that long but it is VERY defensive. Time to wrap it in systemd and learn that. Thanks for the pointers. On Sunday, December 15, 2013 3:26 PM, Mark Eggers wrote: Some inline and some at the end: Note, this is almost all off-topic, since it concerns system administration and not Tomcat. Note, I'm also comparing this to Fedora 19. Fedora 18 should be EOL in about 5 weeks. On 12/15/2013 7:51 AM, Ray Holme wrote: > I have a rc.local file setup to auto start tomcat and httpd under fedora 18 > boot. > It works fine on my 64 bit system (and a couple others for a friend) > but there MUST BE a sleep before bringing up httpd (for some reason I >forgot). > > start routine in /etc/init.d/rc.local > S95tomcat start > (sleep 10; S96httpd start) & > date > /tmp/last_start > > stop routine > S96httpd stop > S95tomcat stop > date > /tmp/last_stop # not meaningful unless testing rc.local >as boot wipes /tmp > > for the record S96httpd is a link to /etc/init.d/httpd There is no /etc/init.d/httpd script on Fedora 19. Where did you get this script? > and S95tomcat is a script I wrote which does some extra things >besides calling the > official release apache/tomcat up/down scripts > > I also have a portable 32bit fedora 18 box. After installing all the pieces, > I have tomcat/httpd working fine, BUT > they WILL NOT START FROM THE BOOT up like the 64 bit systems do. Don't do this. Fedora 19 uses systemd. The HTTPD package comes with a /usr/lib/systemd/system/httpd.service file that works just fine to control Apache HTTPD. > > I have tried putting more and longer sleeps in place (before tomcat as well > as httpd). All to no avail. > > BUT WHEN I TYPE IN "rc.local start" AS ROOT, ALL COMES UP FINE. > (after logging into the desktop as me and becoming root with "su") in a >command tool > > The only visible difference I have found is in the httpd log > Tomcat's failure is lost or I have not found it yet (yes I looked in > /var/log/messages where I would expect it). Any logging should happen in catalina.out (unless you've done some changes to a stock Tomcat). That location is dependent on where / how you've installed Tomcat. > > --- so here is the /var/log/httpd/error_log after a boot - not sure if the > first two lines are errors, but the third is > (timestamps shortened up for this note) > > [12/15/2013] [core:notice] [pid 1686] SELinux policy enabled; httpd running > as context system_u:system_r:httpd_t:s0 > [12/15/2013] [suexec:notice] [pid 1686] AH01232: suEXEC mechanism enabled > (wrapper: /usr/sbin/suexec) > [12/15/2013] [jk:emerg] [pid 1686] Error in reading worker properties from > '/etc/httpd/conf/workers.properties' > AH00016: Configuration Failed > > > - and now for the AFTER I boot and run "rc.local start" as root - note > line 1 has different RUNTIME PERMISSIONS > > [12/15/2013] [core:notice] [pid 2302] SELinux policy enabled; httpd running > as context unconfined_u:system_r:unconfined_t:s0-s0:c0.c1023 > [12/15/2013] [suexec:notice] [pid 2302] AH01232: suEXEC mechanism enabled > (wrapper: /usr/sbin/suexec) > [12/15/2013] [auth_digest:notice] [pid 2303] AH01757: generating secret for > digest authentication ... > [12/15/2013] [lbmethod_heartbeat:notice] [pid 2303] AH02282: No slotmem from > mod_heartmonitor > [12/15/2013] [mpm_prefork:notice] [pid 2303] AH00163: Apache/2.4.6 (Fedora) > mod_jk/1.2.37 configured -- resuming normal operations > [12/15/2013] [core:notice] [pid 2303] AH00094: Command line: '/usr/sbin/httpd' > > Looks at first glance like an SELinux problem. Do you have SELinux enabled? Hopefully you do. If you're using an old / custom script for HTTPD, then it may or may not account for SELinux. Also, how did you install mod_jk, and what is the content of your workers.properties file? BTW, I normally put workers.properties in /etc/httpd/conf.d instead of the main /etc/httpd/conf. > -- > So I am guessing here bel
Re: linking (limiting???)
Hmmm - I use JNDI for connections and you lost me with extra paths - although it appears this is exactly what I want. This is exactly what I was thinking, I will start digging to learn how to use properly. Thanks Mark On Sunday, December 15, 2013 4:53 PM, Martin Gainty wrote: > Date: Sun, 15 Dec 2013 12:41:55 -0800 > From: its_toas...@yahoo.com > To: users@tomcat.apache.org > Subject: Re: linking (limiting???) > > On 12/15/2013 8:34 AM, Ray Holme wrote: > > I am a Linux user and love linking things to reduce copies. > > > > Apache/Tomcat (by default) does not allow symbolic linking (nice as > > it can cross mounted file systems) except in the top apache/lib > > directory. I use hard links in the Application/WEB-INF/lib > > directories to reduce copying and help me manage things. > > > > HOWEVER, some applications have special needs - e.g. pictures. You > > don't want to always distribute these with the release of the > > application (Application.war file), so symbolic links are the way to > > go (except for MS land, sorry). The nice solution to this is: > > .../webapps/Application/WEB-INF/context.xml which must contain at > > least the two below lines: > > > > > > > > > > > > However this allows ALL symbolic linking in the Application > > directory. I agree with the developers that this is dangerous. > > > > Is there some way to allow linking in just ONE sub-directory of the > > Application?? - e.g. > > > > .../webapps/Application/images > > > > This would allow all I need to have local images for the application > > without endangering other things using a symbolic link. > > > > If you use Tomcat 7, read the following: > > http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Resource_Definitions ...Mark I assume you're referring to Virtual DirContext...? > . . . just my two cents > /mde/ MG>Thanks Mark, > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org >
RE: linking (limiting???)
> Date: Sun, 15 Dec 2013 12:41:55 -0800 > From: its_toas...@yahoo.com > To: users@tomcat.apache.org > Subject: Re: linking (limiting???) > > On 12/15/2013 8:34 AM, Ray Holme wrote: > > I am a Linux user and love linking things to reduce copies. > > > > Apache/Tomcat (by default) does not allow symbolic linking (nice as > > it can cross mounted file systems) except in the top apache/lib > > directory. I use hard links in the Application/WEB-INF/lib > > directories to reduce copying and help me manage things. > > > > HOWEVER, some applications have special needs - e.g. pictures. You > > don't want to always distribute these with the release of the > > application (Application.war file), so symbolic links are the way to > > go (except for MS land, sorry). The nice solution to this is: > > .../webapps/Application/WEB-INF/context.xml which must contain at > > least the two below lines: > > > > > > > > > > > > However this allows ALL symbolic linking in the Application > > directory. I agree with the developers that this is dangerous. > > > > Is there some way to allow linking in just ONE sub-directory of the > > Application?? - e.g. > > > > .../webapps/Application/images > > > > This would allow all I need to have local images for the application > > without endangering other things using a symbolic link. > > > > If you use Tomcat 7, read the following: > > http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Resource_Definitions ...Mark I assume you're referring to Virtual DirContext...? > . . . just my two cents > /mde/ MG>Thanks Mark, > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org >
Re: linking (limiting???)
On 12/15/2013 8:34 AM, Ray Holme wrote: I am a Linux user and love linking things to reduce copies. Apache/Tomcat (by default) does not allow symbolic linking (nice as it can cross mounted file systems) except in the top apache/lib directory. I use hard links in the Application/WEB-INF/lib directories to reduce copying and help me manage things. HOWEVER, some applications have special needs - e.g. pictures. You don't want to always distribute these with the release of the application (Application.war file), so symbolic links are the way to go (except for MS land, sorry). The nice solution to this is: .../webapps/Application/WEB-INF/context.xml which must contain at least the two below lines: However this allows ALL symbolic linking in the Application directory. I agree with the developers that this is dangerous. Is there some way to allow linking in just ONE sub-directory of the Application?? - e.g. .../webapps/Application/images This would allow all I need to have local images for the application without endangering other things using a symbolic link. If you use Tomcat 7, read the following: http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Resource_Definitions . . . just my two cents /mde/ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: timing is everything when starting - a 32 bit question
Some inline and some at the end: Note, this is almost all off-topic, since it concerns system administration and not Tomcat. Note, I'm also comparing this to Fedora 19. Fedora 18 should be EOL in about 5 weeks. On 12/15/2013 7:51 AM, Ray Holme wrote: I have a rc.local file setup to auto start tomcat and httpd under fedora 18 boot. It works fine on my 64 bit system (and a couple others for a friend) but there MUST BE a sleep before bringing up httpd (for some reason I forgot). start routine in /etc/init.d/rc.local S95tomcat start (sleep 10; S96httpd start) & date > /tmp/last_start stop routine S96httpd stop S95tomcat stop date > /tmp/last_stop# not meaningful unless testing rc.local as boot wipes /tmp for the record S96httpd is a link to /etc/init.d/httpd There is no /etc/init.d/httpd script on Fedora 19. Where did you get this script? and S95tomcat is a script I wrote which does some extra things besides calling the official release apache/tomcat up/down scripts I also have a portable 32bit fedora 18 box. After installing all the pieces, I have tomcat/httpd working fine, BUT they WILL NOT START FROM THE BOOT up like the 64 bit systems do. Don't do this. Fedora 19 uses systemd. The HTTPD package comes with a /usr/lib/systemd/system/httpd.service file that works just fine to control Apache HTTPD. I have tried putting more and longer sleeps in place (before tomcat as well as httpd). All to no avail. BUT WHEN I TYPE IN "rc.local start" AS ROOT, ALL COMES UP FINE. (after logging into the desktop as me and becoming root with "su") in a command tool The only visible difference I have found is in the httpd log Tomcat's failure is lost or I have not found it yet (yes I looked in /var/log/messages where I would expect it). Any logging should happen in catalina.out (unless you've done some changes to a stock Tomcat). That location is dependent on where / how you've installed Tomcat. --- so here is the /var/log/httpd/error_log after a boot - not sure if the first two lines are errors, but the third is (timestamps shortened up for this note) [12/15/2013] [core:notice] [pid 1686] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0 [12/15/2013] [suexec:notice] [pid 1686] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [12/15/2013] [jk:emerg] [pid 1686] Error in reading worker properties from '/etc/httpd/conf/workers.properties' AH00016: Configuration Failed - and now for the AFTER I boot and run "rc.local start" as root - note line 1 has different RUNTIME PERMISSIONS [12/15/2013] [core:notice] [pid 2302] SELinux policy enabled; httpd running as context unconfined_u:system_r:unconfined_t:s0-s0:c0.c1023 [12/15/2013] [suexec:notice] [pid 2302] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [12/15/2013] [auth_digest:notice] [pid 2303] AH01757: generating secret for digest authentication ... [12/15/2013] [lbmethod_heartbeat:notice] [pid 2303] AH02282: No slotmem from mod_heartmonitor [12/15/2013] [mpm_prefork:notice] [pid 2303] AH00163: Apache/2.4.6 (Fedora) mod_jk/1.2.37 configured -- resuming normal operations [12/15/2013] [core:notice] [pid 2303] AH00094: Command line: '/usr/sbin/httpd' Looks at first glance like an SELinux problem. Do you have SELinux enabled? Hopefully you do. If you're using an old / custom script for HTTPD, then it may or may not account for SELinux. Also, how did you install mod_jk, and what is the content of your workers.properties file? BTW, I normally put workers.properties in /etc/httpd/conf.d instead of the main /etc/httpd/conf. -- So I am guessing here below - anyone please correct. Either a) the permissions are critical between the two runs (if so, how to set in rc.local) but ( again ) NO sign of apache tomcat being up either or b) something else is still coming up on the system as both tomcat AND httpd fail originally but later after I login and become root, the system is stable and up they come manually Workarounds I see for now: a) use 64bit machines only or b) manually start tomcat and httpd every time I boot or c) some daemon process is still initializing and I need to ensure that it is done What the HAY Wisdom appreciated! OK, so the following is an outline of how I would run Tomcat as a service on Fedora. Since around Fedora 16, Fedora has been moving to systemd instead of the old System V init scripts. You should no longer use the init method of starting a new service. Instead, use a systemd file to control services. For Tomcat, this means one of two things: 1. Use jsvc and wrap that startup script in a systemd service file 2. Write your own init.d script and wrap it in a systemd service file My approach would be the following: 1. Create an unprivileged user to run Tomcat 2. Install Tomcat f
Re: slim and trim tomcat - which java is needed
Thanks Chuck for hitting the nail on the head - I should have read that first. On Sunday, December 15, 2013 11:56 AM, "Caldarale, Charles R" wrote: > From: Ray Holme [mailto:rayho...@yahoo.com] > Subject: slim and trim tomcat - which java is needed > So do we need the JRE or the JDK or can Tomcat work without either on > a non-sofware development box??? Read the RUNNING.txt file in the standard Tomcat distribution. If you're using a third-party repackaged version, you'll need to contact the supplier of that version. Strongly recommend that you use real Tomcat download, since the third-party ones often turn things into mush. You should also look at this: http://tomcat.apache.org/tomcat-7.0-doc/security-howto.html And the security-related items here: http://wiki.apache.org/tomcat/HowTo - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: slim and trim tomcat - which java is needed
> From: Ray Holme [mailto:rayho...@yahoo.com] > Subject: slim and trim tomcat - which java is needed > So do we need the JRE or the JDK or can Tomcat work without either on > a non-sofware development box??? Read the RUNNING.txt file in the standard Tomcat distribution. If you're using a third-party repackaged version, you'll need to contact the supplier of that version. Strongly recommend that you use real Tomcat download, since the third-party ones often turn things into mush. You should also look at this: http://tomcat.apache.org/tomcat-7.0-doc/security-howto.html And the security-related items here: http://wiki.apache.org/tomcat/HowTo - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
slim and trim tomcat - which java is needed
I have discovered that under the conf/localhost and webapps directories, all of the release directories and xml files can be removed, leaving just the application(s) you want running. I could b wrong but I think this also closes some possible security issues, besides keeping a smart-cookie from playing with the examples ... However I am totally unclear which (if any) java pieces need to be on a distribution machine. Obviously a source machine needs the Java JDK. On a distribution machine, apache compiles JSP code initially so it needs something. One person told me the JRE should be enough, but another said that Apache/Tomcat actually comes with it's own compiler, and yet another says to have the JDK. On my Fedora-18 distribution (before I put in the JDK), there is at least one java compiler (/etc/alternatives/javac). So do we need the JRE or the JDK or can Tomcat work without either on a non-sofware development box???
linking (limiting???)
I am a Linux user and love linking things to reduce copies. Apache/Tomcat (by default) does not allow symbolic linking (nice as it can cross mounted file systems) except in the top apache/lib directory. I use hard links in the Application/WEB-INF/lib directories to reduce copying and help me manage things. HOWEVER, some applications have special needs - e.g. pictures. You don't want to always distribute these with the release of the application (Application.war file), so symbolic links are the way to go (except for MS land, sorry). The nice solution to this is: .../webapps/Application/WEB-INF/context.xml which must contain at least the two below lines: However this allows ALL symbolic linking in the Application directory. I agree with the developers that this is dangerous. Is there some way to allow linking in just ONE sub-directory of the Application?? - e.g. .../webapps/Application/images This would allow all I need to have local images for the application without endangering other things using a symbolic link.
timing is everything when starting - a 32 bit question
I have a rc.local file setup to auto start tomcat and httpd under fedora 18 boot. It works fine on my 64 bit system (and a couple others for a friend) but there MUST BE a sleep before bringing up httpd (for some reason I forgot). start routine in /etc/init.d/rc.local S95tomcat start (sleep 10; S96httpd start) & date > /tmp/last_start stop routine S96httpd stop S95tomcat stop date > /tmp/last_stop # not meaningful unless testing rc.local as boot wipes /tmp for the record S96httpd is a link to /etc/init.d/httpd and S95tomcat is a script I wrote which does some extra things besides calling the official release apache/tomcat up/down scripts I also have a portable 32bit fedora 18 box. After installing all the pieces, I have tomcat/httpd working fine, BUT they WILL NOT START FROM THE BOOT up like the 64 bit systems do. I have tried putting more and longer sleeps in place (before tomcat as well as httpd). All to no avail. BUT WHEN I TYPE IN "rc.local start" AS ROOT, ALL COMES UP FINE. (after logging into the desktop as me and becoming root with "su") in a command tool The only visible difference I have found is in the httpd log Tomcat's failure is lost or I have not found it yet (yes I looked in /var/log/messages where I would expect it). --- so here is the /var/log/httpd/error_log after a boot - not sure if the first two lines are errors, but the third is (timestamps shortened up for this note) [12/15/2013] [core:notice] [pid 1686] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0 [12/15/2013] [suexec:notice] [pid 1686] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [12/15/2013] [jk:emerg] [pid 1686] Error in reading worker properties from '/etc/httpd/conf/workers.properties' AH00016: Configuration Failed - and now for the AFTER I boot and run "rc.local start" as root - note line 1 has different RUNTIME PERMISSIONS [12/15/2013] [core:notice] [pid 2302] SELinux policy enabled; httpd running as context unconfined_u:system_r:unconfined_t:s0-s0:c0.c1023 [12/15/2013] [suexec:notice] [pid 2302] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [12/15/2013] [auth_digest:notice] [pid 2303] AH01757: generating secret for digest authentication ... [12/15/2013] [lbmethod_heartbeat:notice] [pid 2303] AH02282: No slotmem from mod_heartmonitor [12/15/2013] [mpm_prefork:notice] [pid 2303] AH00163: Apache/2.4.6 (Fedora) mod_jk/1.2.37 configured -- resuming normal operations [12/15/2013] [core:notice] [pid 2303] AH00094: Command line: '/usr/sbin/httpd' -- So I am guessing here below - anyone please correct. Either a) the permissions are critical between the two runs (if so, how to set in rc.local) but ( again ) NO sign of apache tomcat being up either or b) something else is still coming up on the system as both tomcat AND httpd fail originally but later after I login and become root, the system is stable and up they come manually Workarounds I see for now: a) use 64bit machines only or b) manually start tomcat and httpd every time I boot or c) some daemon process is still initializing and I need to ensure that it is done What the HAY Wisdom appreciated!
