Ryfujk

How to tell a function to use the default argument values?

I would say: "You are another teacher", but she is a woman and I am a man

Zip/Tar file compressed to larger size?

Expand and Contract

Why no variance term in Bayesian logistic regression?

Is "remove commented out code" correct English?

What's the in-universe reasoning behind sorcerers needing material components?

Do scales need to be in alphabetical order?

What exploit are these user agents trying to use?

Why is it a bad idea to hire a hitman to eliminate most corrupt politicians?

What killed these X2 caps?

How would I stat a creature to be immune to everything but the Magic Missile spell? (just for fun)

Why was the shrinking from 8″ made only to 5.25″ and not smaller (4″ or less)?

Is there an expression that means doing something right before you will need it rather than doing it in case you might need it?

Size of subfigure fitting its content (tikzpicture)

Why are the 737's rear doors unusable in a water landing?

Intersection Puzzle

Why do bosons tend to occupy the same state?

Unlock My Phone! February 2018

Am I breaking OOP practice with this architecture?

If human space travel is limited by the G force vulnerability, is there a way to counter G forces?

Can my sorcerer use a spellbook only to collect spells and scribe scrolls, not cast?

Assassin's bullet with mercury

Im going to France and my passport expires June 19th

wildfly and logrotate: wildfly still logs messages to already rotated server.log

Logrotate creates long names and does not delete logslogrotate not rotating the logsLogrotate does not remove old logslogrotate daily and size?Logrotate Creating Empty Rotated Fileslogrotate — moving logs by sizeHow to stop logrotate from changing the rotated logs ownerUsing logrotate to ONLY delete logs that are managed/rotated by another serviceLogrotate running according to cron, but logs are not rotatedlogrotate: What means the message “log has been already rotated”

0

1

For wildfly (on linux) I need following logging scenario: daily rotation of server.log and removing old log files which are older than 90 days. I don't see a way to configure this in wildfly/log4j (the problem is here to remove old log files, but I will be happy for tips to do this directly with wildfly configuration). So I have to use linux logrotate for this. I have following logrotate configuration file:

/var/log/wildfly/capp/*.log {

    missingok

    daily

    notifempty

    rotate 90

    maxage 90

    dateext

    dateformat -%Y%m%d

}

The server.log will be rotated successfully in the early morning. But: wildfly is still writing the log messages into the already logrotated file (see at the timestamps of the last write access):

#> ls -la

-rw-r--r-- 1 wildfly-capp wildfly-capp      0  4. Apr 03:40 server.log

-rw-r--r-- 1 wildfly-capp wildfly-capp 368909  4. Apr 07:00 server.log-20190404

Is there a way to force wildfly to use the server.log file instead the already rotated file (without restarting wildfly)? Or is it possible to change the wildfly logging configuration to remove logging files which are older than x days?

The wildfly logging configuration is:

<subsystem xmlns="urn:jboss:domain:logging:5.0">

        <console-handler name="CONSOLE">

            <level name="INFO"/>

            <formatter>

                <named-formatter name="COLOR-PATTERN"/>

            </formatter>

        </console-handler>

        <file-handler name="FILE" autoflush="true">

            <formatter>

                <named-formatter name="PATTERN"/>

            </formatter>

            <file relative-to="jboss.server.log.dir" path="server.log"/>

            <append value="true"/>

        </file-handler>

        <logger category="com.arjuna">

            <level name="WARN"/>

        </logger>

        <logger category="org.jboss.as.config">

            <level name="DEBUG"/>

        </logger>

        <logger category="sun.rmi">

            <level name="WARN"/>

        </logger>

        <root-logger>

            <level name="INFO"/>

            <handlers>

                <handler name="CONSOLE"/>

                <handler name="FILE"/>

            </handlers>

        </root-logger>

        <formatter name="PATTERN">

            <pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"/>

        </formatter>

        <formatter name="COLOR-PATTERN">

            <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"/>

        </formatter>

</subsystem>

linux logrotate wildfly

share

asked 2 mins ago

SteffenSteffen

4431820

add a comment | 

0

1

For wildfly (on linux) I need following logging scenario: daily rotation of server.log and removing old log files which are older than 90 days. I don't see a way to configure this in wildfly/log4j (the problem is here to remove old log files, but I will be happy for tips to do this directly with wildfly configuration). So I have to use linux logrotate for this. I have following logrotate configuration file:

/var/log/wildfly/capp/*.log {

    missingok

    daily

    notifempty

    rotate 90

    maxage 90

    dateext

    dateformat -%Y%m%d

}

The server.log will be rotated successfully in the early morning. But: wildfly is still writing the log messages into the already logrotated file (see at the timestamps of the last write access):

#> ls -la

-rw-r--r-- 1 wildfly-capp wildfly-capp      0  4. Apr 03:40 server.log

-rw-r--r-- 1 wildfly-capp wildfly-capp 368909  4. Apr 07:00 server.log-20190404

Is there a way to force wildfly to use the server.log file instead the already rotated file (without restarting wildfly)? Or is it possible to change the wildfly logging configuration to remove logging files which are older than x days?

The wildfly logging configuration is:

<subsystem xmlns="urn:jboss:domain:logging:5.0">

        <console-handler name="CONSOLE">

            <level name="INFO"/>

            <formatter>

                <named-formatter name="COLOR-PATTERN"/>

            </formatter>

        </console-handler>

        <file-handler name="FILE" autoflush="true">

            <formatter>

                <named-formatter name="PATTERN"/>

            </formatter>

            <file relative-to="jboss.server.log.dir" path="server.log"/>

            <append value="true"/>

        </file-handler>

        <logger category="com.arjuna">

            <level name="WARN"/>

        </logger>

        <logger category="org.jboss.as.config">

            <level name="DEBUG"/>

        </logger>

        <logger category="sun.rmi">

            <level name="WARN"/>

        </logger>

        <root-logger>

            <level name="INFO"/>

            <handlers>

                <handler name="CONSOLE"/>

                <handler name="FILE"/>

            </handlers>

        </root-logger>

        <formatter name="PATTERN">

            <pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"/>

        </formatter>

        <formatter name="COLOR-PATTERN">

            <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"/>

        </formatter>

</subsystem>

linux logrotate wildfly

share

asked 2 mins ago

SteffenSteffen

4431820

add a comment | 

For wildfly (on linux) I need following logging scenario: daily rotation of server.log and removing old log files which are older than 90 days. I don't see a way to configure this in wildfly/log4j (the problem is here to remove old log files, but I will be happy for tips to do this directly with wildfly configuration). So I have to use linux logrotate for this. I have following logrotate configuration file:

/var/log/wildfly/capp/*.log {

    missingok

    daily

    notifempty

    rotate 90

    maxage 90

    dateext

    dateformat -%Y%m%d

}

The server.log will be rotated successfully in the early morning. But: wildfly is still writing the log messages into the already logrotated file (see at the timestamps of the last write access):

#> ls -la

-rw-r--r-- 1 wildfly-capp wildfly-capp      0  4. Apr 03:40 server.log

-rw-r--r-- 1 wildfly-capp wildfly-capp 368909  4. Apr 07:00 server.log-20190404

Is there a way to force wildfly to use the server.log file instead the already rotated file (without restarting wildfly)? Or is it possible to change the wildfly logging configuration to remove logging files which are older than x days?

The wildfly logging configuration is:

<subsystem xmlns="urn:jboss:domain:logging:5.0">

        <console-handler name="CONSOLE">

            <level name="INFO"/>

            <formatter>

                <named-formatter name="COLOR-PATTERN"/>

            </formatter>

        </console-handler>

        <file-handler name="FILE" autoflush="true">

            <formatter>

                <named-formatter name="PATTERN"/>

            </formatter>

            <file relative-to="jboss.server.log.dir" path="server.log"/>

            <append value="true"/>

        </file-handler>

        <logger category="com.arjuna">

            <level name="WARN"/>

        </logger>

        <logger category="org.jboss.as.config">

            <level name="DEBUG"/>

        </logger>

        <logger category="sun.rmi">

            <level name="WARN"/>

        </logger>

        <root-logger>

            <level name="INFO"/>

            <handlers>

                <handler name="CONSOLE"/>

                <handler name="FILE"/>

            </handlers>

        </root-logger>

        <formatter name="PATTERN">

            <pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"/>

        </formatter>

        <formatter name="COLOR-PATTERN">

            <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"/>

        </formatter>

</subsystem>

linux logrotate wildfly

share

asked 2 mins ago

SteffenSteffen

4431820

/var/log/wildfly/capp/*.log {

    missingok

    daily

    notifempty

    rotate 90

    maxage 90

    dateext

    dateformat -%Y%m%d

}

#> ls -la

-rw-r--r-- 1 wildfly-capp wildfly-capp      0  4. Apr 03:40 server.log

-rw-r--r-- 1 wildfly-capp wildfly-capp 368909  4. Apr 07:00 server.log-20190404

<subsystem xmlns="urn:jboss:domain:logging:5.0">

        <console-handler name="CONSOLE">

            <level name="INFO"/>

            <formatter>

                <named-formatter name="COLOR-PATTERN"/>

            </formatter>

        </console-handler>

        <file-handler name="FILE" autoflush="true">

            <formatter>

                <named-formatter name="PATTERN"/>

            </formatter>

            <file relative-to="jboss.server.log.dir" path="server.log"/>

            <append value="true"/>

        </file-handler>

        <logger category="com.arjuna">

            <level name="WARN"/>

        </logger>

        <logger category="org.jboss.as.config">

            <level name="DEBUG"/>

        </logger>

        <logger category="sun.rmi">

            <level name="WARN"/>

        </logger>

        <root-logger>

            <level name="INFO"/>

            <handlers>

                <handler name="CONSOLE"/>

                <handler name="FILE"/>

            </handlers>

        </root-logger>

        <formatter name="PATTERN">

            <pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"/>

        </formatter>

        <formatter name="COLOR-PATTERN">

            <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"/>

        </formatter>

</subsystem>

share

asked 2 mins ago

SteffenSteffen

4431820

share

asked 2 mins ago

SteffenSteffen

4431820

asked 2 mins ago

SteffenSteffen

4431820

asked 2 mins ago

SteffenSteffen

4431820