Hi Axton,
I did not think that the native libraries was critical for this issue. In
any event, I can find nothing to compile.
I noticed before that the version 5.5.23 was below the one supported by
Mid-Tier 7.5, but I thought it was just something they did not do testing
on.
Maybe I should just download and compile a newer version of Tomcat 5.5
from scratch?
I have included the /usr/share/tomcat5/conf/logging.properties file after
my signature.
I have also specified the following lines in my /etc/httpd/conf/httpd.conf
file:
LoadModule jk_module modules/mod_jk.so
JkWorkersFile /etc/tomcat5/workers.properties
JkLogFile /usr/share/tomcat5/logs/arsystest.log
JkLogLevel info
Do we need to look at any other config files?
I have pretty much used the standard config files, and created my own
workers.properties file that look like this:
workers.tomcat_home=/usr/share/tomcat5
workers.java_home=/opt/bmc/jdk1.6.0_21
worker.list=arsys1
worker.arsys1.type=ajp13
worker.arsys1.host=localhost
worker.arsys1.port=8009
worker.wlb.type=lb
worker.wlb.balance_workers=arsys1
worker.jkstatus.type=status
And I must confess that I am not 100% sure of what I am doing...
Thank you for the help!
Best Regards - Misi, RRR AB, http://rrr.se
handlers = 1catalina.org.apache.juli.FileHandler,
2localhost.org.apache.juli.FileHandler,
3manager.org.apache.juli.FileHandler, 4admin.org.apache.juli.FileHandler,
5host-manager.org.apache.juli.FileHandler,
java.util.logging.ConsoleHandler
.handlers = 1catalina.org.apache.juli.FileHandler,
java.util.logging.ConsoleHandler
############################################################
# Handler specific properties.
# Describes specific configuration info for Handlers.
############################################################
1catalina.org.apache.juli.FileHandler.level = FINE
1catalina.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
1catalina.org.apache.juli.FileHandler.prefix = catalina.
2localhost.org.apache.juli.FileHandler.level = FINE
2localhost.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
2localhost.org.apache.juli.FileHandler.prefix = localhost.
3manager.org.apache.juli.FileHandler.level = FINE
3manager.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
3manager.org.apache.juli.FileHandler.prefix = manager.
4admin.org.apache.juli.FileHandler.level = FINE
4admin.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
4admin.org.apache.juli.FileHandler.prefix = admin.
5host-manager.org.apache.juli.FileHandler.level = FINE
5host-manager.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
5host-manager.org.apache.juli.FileHandler.prefix = host-manager.
java.util.logging.ConsoleHandler.level = FINE
java.util.logging.ConsoleHandler.formatter =
java.util.logging.SimpleFormatter
############################################################
# Facility specific properties.
# Provides extra control for each logger.
############################################################
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].level = INFO
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].handlers =
2localhost.org.apache.juli.FileHandler
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager].level
= INFO
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager].handlers
= 3manager.org.apache.juli.FileHandler
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/admin].level
= INFO
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/admin].handlers
= 4admin.org.apache.juli.FileHandler
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/host-manager].level
= INFO
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/host-manager].handlers
= 5host-manager.org.apache.juli.FileHandler
# For example, set the com.xyz.foo logger to only log SEVERE
# messages:
#org.apache.catalina.startup.ContextConfig.level = FINE
#org.apache.catalina.startup.HostConfig.level = FINE
#org.apache.catalina.session.ManagerBase.level = FINE
> I tend to steer away from the bundled tomcat because it is outdated. It
> will always be outdated. 5.5.23 is the version in your logs (released on
> 2007-03-09). 5.5.30 is the latest release for the 5.5 branch. See the
> list
> of fixed issues here:
>
> http://tomcat.apache.org/tomcat-5.5-doc/changelog.html
>
> Some nasty things were fixed. Search for CVE on the page above for those.
> Some other issues around AJP/JK were fixed as well. Those are important
> if
> you intend to use mod_jk.
>
> <http://tomcat.apache.org/tomcat-5.5-doc/changelog.html>For this error:
>
> *"The Apache Tomcat Native library which allows optimal performance
> in production environments was not found on the java.library.path"*
>
> You need to either compile the native lib or install a package/file to
> provide the library. The files needed to compile the lib are in the
> tomcat
> installation directory.
>
> For the null pointer exception, can you provide the contents of your
> config.properties file, particularly those entries dealing with logging?
>
> Axton Grams
>
> The opinions, statements, and/or suggested courses of action expressed in
> this E-mail do not necessarily reflect those of BMC Software, Inc. My
> voluntary participation in this forum is not intended to convey a role as
> a
> spokesperson, liaison or public relations representative for BMC Software,
> Inc.
>
> On Tue, Sep 7, 2010 at 5:46 AM, Misi Mladoniczky <m...@rrr.se> wrote:
>
>> Hi Danny,
>>
>> Thank you for the suggestion. I tried this, and at least got the
>> installer
>> going :-)
>>
>> After this, I installed mod_jk.so, and had some help from Matt
>> Reinfeldts
>> posting:
>> http://www.mattreinfeldt.com/forums/ubbthreads.php/topics/140044/
>>
>> Now when I am starting tomcat, I am getting the following errors, which
>> I
>> have so far been unable to fix. In short, I need more help!
>>
>> I have included the output from /var/log/tomcat5/catalina.out from the
>> startup.
>>
>> Best Regards - Misi, RRR AB, http://rrr.se
>>
>> Using CATALINA_BASE: /usr/share/tomcat5
>> Using CATALINA_HOME: /usr/share/tomcat5
>> Using CATALINA_TMPDIR: /usr/share/tomcat5/temp
>> Using JRE_HOME: /opt/bmc/jre1.6.0_21
>> Created MBeanServer with ID: cs23ta:gdslvhfo.0:www.rrr:1
>> 7-Sep-10 12:16:30 PM org.apache.catalina.core.AprLifecycleListener
>> lifecycleEvent
>> INFO: The Apache Tomcat Native library which allows optimal performance
>> in
>> production environments was not found on the java.library.path:
>> /usr/lib64/gcj-4.1.2:/opt/bmc/ARSystem/midtier/WEB-INF/lib
>> 7-Sep-10 12:16:30 PM org.apache.coyote.http11.Http11BaseProtocol init
>> INFO: Initializing Coyote HTTP/1.1 on http-8080
>> 7-Sep-10 12:16:30 PM org.apache.catalina.startup.Catalina load
>> INFO: Initialization processed in 539 ms
>> 7-Sep-10 12:16:30 PM org.apache.catalina.core.StandardService start
>> INFO: Starting service Catalina
>> 7-Sep-10 12:16:30 PM org.apache.catalina.core.StandardEngine start
>> INFO: Starting Servlet Engine: Apache Tomcat/5.5.23
>> 7-Sep-10 12:16:30 PM org.apache.catalina.core.StandardHost start
>> INFO: XML validation disabled
>> java.lang.NullPointerException
>> at java.lang.String.indexOf(libgcj.so.7rh)
>> at java.lang.String.indexOf(libgcj.so.7rh)
>> at com.remedy.arsys.log.Log$CategoryFilter.isLoggable(Unknown Source)
>> at java.util.logging.Logger.log(libgcj.so.7rh)
>> at java.util.logging.Logger.logImpl(libgcj.so.7rh)
>> at java.util.logging.Logger.logp(libgcj.so.7rh)
>> at java.util.logging.Logger.logp(libgcj.so.7rh)
>> at com.remedy.arsys.log.Log.log(Unknown Source)
>> at com.remedy.arsys.config.Configuration.<init>(Unknown Source)
>> at com.remedy.arsys.config.Configuration.<clinit>(Unknown Source)
>> at java.lang.Class.initializeClass(libgcj.so.7rh)
>> at com.remedy.arsys.stubs.GoatHttpServlet.<clinit>(Unknown Source)
>> at java.lang.Class.initializeClass(libgcj.so.7rh)
>> at java.lang.Class.initializeClass(libgcj.so.7rh)
>> at java.lang.Class.newInstance(libgcj.so.7rh)
>> at
>> org.apache.catalina.core.StandardWrapper.loadServlet(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.StandardWrapper.load(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.StandardContext.loadOnStartup(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.StandardContext.start(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.ContainerBase.addChildInternal(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.ContainerBase.addChild(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.StandardHost.addChild(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.startup.HostConfig.deployDescriptor(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.startup.HostConfig.deployDescriptors(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.startup.HostConfig.deployApps(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.startup.HostConfig.start(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.startup.HostConfig.lifecycleEvent(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.ContainerBase.start(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.StandardHost.start(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.ContainerBase.start(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.StandardEngine.start(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.StandardService.start(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.StandardServer.start(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.startup.Catalina.start(catalina-5.5.23.jar.soym24ww.so
>> )
>> at java.lang.reflect.Method.invoke(libgcj.so.7rh)
>> at org.apache.catalina.startup.Bootstrap.start(bootstrap.jar.so)
>> at org.apache.catalina.startup.Bootstrap.main(bootstrap.jar.so)
>> - Marking servlet SetupServlet as unavailable
>> - Servlet /arsys threw load() exception
>> java.lang.NullPointerException
>> at java.lang.String.indexOf(libgcj.so.7rh)
>> at java.lang.String.indexOf(libgcj.so.7rh)
>> at com.remedy.arsys.log.Log$CategoryFilter.isLoggable(Unknown Source)
>> at java.util.logging.Logger.log(libgcj.so.7rh)
>> at java.util.logging.Logger.logImpl(libgcj.so.7rh)
>> at java.util.logging.Logger.logp(libgcj.so.7rh)
>> at java.util.logging.Logger.logp(libgcj.so.7rh)
>> at com.remedy.arsys.log.Log.log(Unknown Source)
>> at com.remedy.arsys.config.Configuration.<init>(Unknown Source)
>> at com.remedy.arsys.config.Configuration.<clinit>(Unknown Source)
>> at java.lang.Class.initializeClass(libgcj.so.7rh)
>> at com.remedy.arsys.stubs.GoatHttpServlet.<clinit>(Unknown Source)
>> at java.lang.Class.initializeClass(libgcj.so.7rh)
>> at java.lang.Class.initializeClass(libgcj.so.7rh)
>> at java.lang.Class.newInstance(libgcj.so.7rh)
>> at
>> org.apache.catalina.core.StandardWrapper.loadServlet(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.StandardWrapper.load(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.StandardContext.loadOnStartup(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.StandardContext.start(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.ContainerBase.addChildInternal(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.ContainerBase.addChild(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.StandardHost.addChild(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.startup.HostConfig.deployDescriptor(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.startup.HostConfig.deployDescriptors(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.startup.HostConfig.deployApps(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.startup.HostConfig.start(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.startup.HostConfig.lifecycleEvent(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.ContainerBase.start(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.StandardHost.start(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.ContainerBase.start(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.StandardEngine.start(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.StandardService.start(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.core.StandardServer.start(
>> catalina-5.5.23.jar.soym24ww.so)
>> at
>> org.apache.catalina.startup.Catalina.start(catalina-5.5.23.jar.soym24ww.so
>> )
>> at java.lang.reflect.Method.invoke(libgcj.so.7rh)
>> at org.apache.catalina.startup.Bootstrap.start(bootstrap.jar.so)
>> at org.apache.catalina.startup.Bootstrap.main(bootstrap.jar.so)
>>
>> - Configuration file read-only so engine configuration changes will not
>> be
>> saved.
>> 7-Sep-10 12:16:32 PM org.apache.coyote.http11.Http11BaseProtocol start
>> INFO: Starting Coyote HTTP/1.1 on http-8080
>> 7-Sep-10 12:16:32 PM org.apache.jk.common.ChannelSocket init
>> INFO: JK: ajp13 listening on /0.0.0.0:8009
>> 7-Sep-10 12:16:32 PM org.apache.jk.server.JkMain start
>> INFO: Jk running ID=0 time=0/42 config=null
>> 7-Sep-10 12:16:32 PM org.apache.catalina.storeconfig.StoreLoader load
>> INFO: Find registry server-registry.xml at classpath resource
>> 7-Sep-10 12:16:32 PM org.apache.catalina.startup.Catalina start
>> INFO: Server startup in 2541 ms
>>
>>
>> > Maybe it would be best to let it install tomcat alone then install the
>> > modjk after if you really want apache.
>> >
>> > Regards
>> > Danny
>> >
>> > -----Original Message-----
>> > From: Action Request System discussion list(ARSList)
>> > [mailto:arsl...@arslist.org] On Behalf Of Misi Mladoniczky
>> > Sent: 06 September 2010 11:58
>> > To: arslist@ARSLIST.ORG
>> > Subject: Mid-Tier 7.5 Linux Installation Problems
>> >
>> > Hi all,
>> >
>> > I am having problems installing Mid-Tier 7.5.00 patch 003 on a CentOS
>> 5.5
>> > machine.
>> >
>> > CentOS 5.5 should be exactly the same thing as Red Hat Enterprice
>> Linux
>> > 5.5.
>> >
>> > I am getting the following error in the installation GUI:
>> > "Mid Tier Web Server validation error
>> > BMC Remedy Action Request System invalid web server path"
>> >
>> > If I check the log, it seems like the path is actually set to "BMC
>> Remedy
>> > Action Request System", which seems strange indeed...
>> >
>> > (Sep 06 2010 12:17:23.710 PM
>> > +0200),CONFIG,com.bmc.install.task.InstallationPropertiesHelper,
>> > LOG EVENT {Description=[SET PROPERTY
>> > VALIDATION_ERROR_RESULT],Detail=[INVALID_WEB_SERVER_PATH[String:BMC
>> > Remedy Action Request System]]}
>> >
>> > I have attached the relevant section from the install log.
>> >
>> > Can anyone shed any light on this?
>> >
>> > Best Regards - Misi, RRR AB, http://www.rrr.se
>> >
>> > Products from RRR Scandinavia:
>> > * RRR|License - Not enough Remedy licenses? Save money by optimizing.
>> > * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy
>> logs.
>> > Find these products, and many free tools and utilities, at
>> http://rrr.se
>> .
>> >
>> >
>> _______________________________________________________________________________
>> > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend
>> wwrug10
>> > www.wwrug.com ARSlist: "Where the Answers Are"
>> >
>> >
>> _______________________________________________________________________________
>> > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>> > attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>> >
>> > --
>> > This message was scanned by ESVA and is believed to be clean.
>> >
>> >
>>
>>
>> _______________________________________________________________________________
>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>>
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>
> --
> This message was scanned by ESVA and is believed to be clean.
>
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
