KB Article #180949

Message "No appender named [ServerLog] could be found" when starting ST services


In some cases, after upgrading from an old SecureTransport version to ST 5.3.6 the following message could be logged in the server's console when you start or stop the SecureTransport services:

log4j:ERROR No appender named [ServerLog] could be found


The message is a result of a missing ServerLog appender in the tools-log4j.xml file, located under the $FILEDRIVEHOME/conf folder. To resolve the issue, make a backup of the file, edit it and add the below appender after the closure tag (</appender>) for the ServerLogFallback appender:

<appender name="ServerLog" class="com.tumbleweed.st.server.logging.db.STDBAppender">
    <param name="locationInfo" value="true"/>
    <param name="maxLoggingEventQueueSize" value="10000"/>
    <param name="fallbackLogger" value="ServerLogFallback"/>
    <param name="databaseStatusCheckupDelay" value="60"/>
    <param name="databaseCheckupTimeout" value="30"/>
    <!-- WARNING - changing the id area may cause deletion of existing logs
    and crash of the appender! -->
    <param name="idAreaBegin" value="-460000000000"/>
    <param name="idAreaEnd" value="-360000000000"/>
    <!-- Connection pool parameters -->
    <param name="driverClass" value="com.mysql.jdbc.Driver"/>
    <param name="initialPoolSize" value="5"/>
    <param name="maxPoolSize" value="25"/>
    <param name="minPoolSize" value="5"/>
    <param name="acquireIncrement" value="5"/>
    <param name="maxStatements" value="4000"/>
    <filter class="com.tumbleweed.st.server.logging.STLog4JNDCFilter">
        <param name="ComponentName" value="AUDIT"/>


A sample tools-log4j.xml file is attached to this article. Note that it contains paths, pointing to the default $FILEDRIVEHOME location (/opt/Axway/SecureTransport/) and is not suitable for direct replacement in your environment.