You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Marc Chamberlin <ma...@marcchamberlin.com> on 2019/01/26 05:41:02 UTC
Logfiles not working
I have noticed that most of the log files for Apache James 3.2 do not
seem to be getting any log messages after running the server for awhile -
bigbang:/mail/apache-james-3.2/james-server-app-3.2.0/log # ll
total 248
-rw-r--r-- 1 root root 0 Jan 25 20:30 dnsservice.log
-rw-r--r-- 1 root root 0 Jan 25 20:30 domainlist.log
-rw-r--r-- 1 james mail 0 Oct 31 09:41 .dummy
-rw-r--r-- 1 root root 0 Jan 25 20:30 fetchmail.log
-rw-r--r-- 1 root root 0 Jan 25 20:30 imapserver.log
-rw-r--r-- 1 root root 103794 Jan 25 21:19 james-server.log
-rw-r--r-- 1 root root 0 Jan 25 20:30 lmtpserver.log
-rw-r--r-- 1 root root 0 Jan 25 20:30 mailboxmanager.log
-rw-r--r-- 1 root root 0 Jan 25 20:30 mailetcontainer.log
-rw-r--r-- 1 root root 0 Jan 25 20:30 mailqueuefactory.log
-rw-r--r-- 1 root root 0 Jan 25 20:30 mailrepositorystore.log
-rw-r--r-- 1 root root 0 Jan 25 20:30 pop3server.log
-rw-r--r-- 1 root root 0 Jan 25 20:30 smtpserver.log
-rw-r--r-- 1 root root 0 Jan 25 20:30 usersrepository.log
-rw-r--r-- 1 root root 0 Jan 25 20:30 virtualusertable.log
-rw-r--r-- 1 root root 147065 Jan 25 21:19 wrapper.log
The log4j.properties file is simply as it was installed. Looking through
it, it seems like I should be getting lots of info messages for each of
the main components, such as imapserver.log and smtpserver.log but nada.
I fooled around with log4j.properties a bit, by just adding DEBUG level
logging to the smtpserver.log and imapserver.log but no joy so I undid
those changes and restored the log4j.properties back to it's original
state. Any ideas why I am not getting log messages in the rest of these
log files?
And where can I find more complete documentation about how to set the
properties in the log4j.properties file? What I have found so far does
not explain much. I am looking at -
https://james.apache.org/server/3/monitor-logging.html Thanks... Marc..
--
Linux Counter
Re: Logfiles not working RESOLVED SOMEWHAT!
Posted by Benoit Tellier <bt...@linagora.com>.
Hi Marc,
Sorry for the late reply.
I investigated this issue and found out that there was a dependency to
logback-classic in the Spring project.
mvn dependency:tree
...
[INFO] +- org.apache.james:james-server-cli:jar:3.3.0-SNAPSHOT:compile
[INFO] | +-
org.apache.james:james-server-mailbox-jmx:jar:3.3.0-SNAPSHOT:compile
[INFO] | +- com.google.guava:guava:jar:25.1-jre:compile
[INFO] | | +- com.google.code.findbugs:jsr305:jar:3.0.2:compile
[INFO] | | +- org.checkerframework:checker-qual:jar:2.0.0:compile
[INFO] | | +-
com.google.errorprone:error_prone_annotations:jar:2.1.3:compile
[INFO] | | +- com.google.j2objc:j2objc-annotations:jar:1.1:compile
[INFO] | | \-
org.codehaus.mojo:animal-sniffer-annotations:jar:1.14:compile
[INFO] | +- ch.qos.logback:logback-classic:jar:1.2.3:runtime
[INFO] | | \- ch.qos.logback:logback-core:jar:1.2.3:runtime
[INFO] | \- commons-cli:commons-cli:jar:1.4:compile
...
This dependency causes the log4J dependency to be overwritten.
See bug report: https://issues.apache.org/jira/browse/JAMES-2654
See the fix: https://github.com/linagora/james-project/pull/2144
In the meantime you can either build a version of James including that
fix, and apploy log4J configuration OR apply temporarily logback
configuration [1]
[1] : https://logback.qos.ch/manual/configuration.html
I hope this solves your issue, and sorry for the late answer - I had
been busy recently.
Best regards,
Benoit TELLIER
On 1/29/19 1:04 PM, Marc Chamberlin wrote:
> Oh! :-( Thank Garry for responding... Well this issue is not a
> showstopper, just a false flag then, I guess, that I have been chasing.
> Probably should be flagged for debugging/fixing of the code or flagged
> for updating the documentation so others won't chase this. BTW I was
> able to hack the log4j.properties file a bit and got some of the
> warnings quieted down by following in Simon's footsteps changing the
> references to DailyRollingFileAppender to RollingFileAppender, removing
> the DatePattern property specifications, and with the additional
> following change -
>
> log4j.rootLogger=DEBUG
> changed to
> log4j.rootLogger=DEBUG, CONS
>
> Anywise, I will move on and ping my other outstanding question/thread,
> about the rewrite recipient SQL query, which is a showstopper for me at
> the moment, and hopefully find a guru who can send me down a path that
> will let me get Apache James working...
>
> Marc...
>
> On 01/28/2019 08:42 PM, Garry Hurley wrote:
>> Yeah, the extra logs seem like a good idea, but details are either logged in the james-server.log for out-of-the-box components, or wrapper.log for custom code.
>>
>> Sent from my iPhone
>>
>>> On Jan 28, 2019, at 9:27 PM, Marc Chamberlin <ma...@marcchamberlin.com> wrote:
>>>
>>> Thanks Simon for your thoughts, I tried making the change as you
>>> suggested but still no joy! You gave me a path to explore so I am
>>> digging into log4j and trying to understand it better... And I am
>>> seeing some warnings in the wrapper log file that look ominous so I am
>>> digging in to those as well...
>>>
>>> INFO | jvm 1 | 2019/01/28 08:29:29 | log4j:WARN No appenders could
>>> be found for logger (org.apache.commons.configuration.ConfigurationUtils).
>>> INFO | jvm 1 | 2019/01/28 08:29:29 | log4j:WARN Please initialize
>>> the log4j system properly.
>>> INFO | jvm 1 | 2019/01/28 08:29:29 | log4j:WARN See
>>> http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
>>> INFO | jvm 1 | 2019/01/28 08:29:30 | INFO 08:29:29,938 |
>>> org.apache.james.container.spring.context.JamesServerApplicationContext
>>> | Bean 'logprovider' of type [class org.apache.j
>>> ames.container.spring.lifecycle.LogProviderImpl] is not eligible for
>>> getting processed by all BeanPostProcessors (for example: not eligible
>>> for auto-proxying)
>>> INFO | jvm 1 | 2019/01/28 08:29:30 | 14 James WARN
>>> [WrapperSimpleAppMain] openjpa.Runtime - An error occurred while
>>> registering a ClassTransformer with PersistenceUnitInfo: name 'James',
>>> root URL [file:/mail/apache-james-3.2/james-server-app-3.2.0/conf]. The
>>> error has been consumed. To see it, set your openjpa.Runtime log level
>>> to TRACE. Load-time class transformation will not be available.
>>>
>>> Marc...
>>>
>>>> On 01/28/2019 04:04 AM, Simon Levesque wrote:
>>>> Hi Marc,
>>>> I had the same issue and found out they are using
>>>> "DailyRollingFileAppender". My fix was to use "DailyRollingFileAppender".
>>>> You can see the full file I am using here:
>>>> https://github.com/foilen/foilen-infra-plugins-core/blob/master/src/main/resources/com/foilen/infra/resource/email/james/log4j.properties
>>>>
>>>> HTH
>>>>
>>>> On Sat, 26 Jan 2019 at 00:41, Marc Chamberlin <ma...@marcchamberlin.com>
>>>> wrote:
>>>>
>>>>> I have noticed that most of the log files for Apache James 3.2 do not
>>>>> seem to be getting any log messages after running the server for awhile -
>>>>>
>>>>> bigbang:/mail/apache-james-3.2/james-server-app-3.2.0/log # ll
>>>>> total 248
>>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 dnsservice.log
>>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 domainlist.log
>>>>> -rw-r--r-- 1 james mail 0 Oct 31 09:41 .dummy
>>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 fetchmail.log
>>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 imapserver.log
>>>>> -rw-r--r-- 1 root root 103794 Jan 25 21:19 james-server.log
>>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 lmtpserver.log
>>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailboxmanager.log
>>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailetcontainer.log
>>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailqueuefactory.log
>>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailrepositorystore.log
>>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 pop3server.log
>>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 smtpserver.log
>>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 usersrepository.log
>>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 virtualusertable.log
>>>>> -rw-r--r-- 1 root root 147065 Jan 25 21:19 wrapper.log
>>>>>
>>>>> The log4j.properties file is simply as it was installed. Looking through
>>>>> it, it seems like I should be getting lots of info messages for each of
>>>>> the main components, such as imapserver.log and smtpserver.log but nada.
>>>>> I fooled around with log4j.properties a bit, by just adding DEBUG level
>>>>> logging to the smtpserver.log and imapserver.log but no joy so I undid
>>>>> those changes and restored the log4j.properties back to it's original
>>>>> state. Any ideas why I am not getting log messages in the rest of these
>>>>> log files?
>>>>>
>>>>> And where can I find more complete documentation about how to set the
>>>>> properties in the log4j.properties file? What I have found so far does
>>>>> not explain much. I am looking at -
>>>>> https://james.apache.org/server/3/monitor-logging.html Thanks... Marc..
>>>>>
>>>>>
>>>>> --
>>>>> Linux Counter
>>>>>
>>> --
>>> Linux Counter
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Logfiles not working RESOLVED SOMEWHAT!
Posted by Marc Chamberlin <ma...@marcchamberlin.com>.
Oh! :-( Thank Garry for responding... Well this issue is not a
showstopper, just a false flag then, I guess, that I have been chasing.
Probably should be flagged for debugging/fixing of the code or flagged
for updating the documentation so others won't chase this. BTW I was
able to hack the log4j.properties file a bit and got some of the
warnings quieted down by following in Simon's footsteps changing the
references to DailyRollingFileAppender to RollingFileAppender, removing
the DatePattern property specifications, and with the additional
following change -
log4j.rootLogger=DEBUG
changed to
log4j.rootLogger=DEBUG, CONS
Anywise, I will move on and ping my other outstanding question/thread,
about the rewrite recipient SQL query, which is a showstopper for me at
the moment, and hopefully find a guru who can send me down a path that
will let me get Apache James working...
Marc...
On 01/28/2019 08:42 PM, Garry Hurley wrote:
> Yeah, the extra logs seem like a good idea, but details are either logged in the james-server.log for out-of-the-box components, or wrapper.log for custom code.
>
> Sent from my iPhone
>
>> On Jan 28, 2019, at 9:27 PM, Marc Chamberlin <ma...@marcchamberlin.com> wrote:
>>
>> Thanks Simon for your thoughts, I tried making the change as you
>> suggested but still no joy! You gave me a path to explore so I am
>> digging into log4j and trying to understand it better... And I am
>> seeing some warnings in the wrapper log file that look ominous so I am
>> digging in to those as well...
>>
>> INFO | jvm 1 | 2019/01/28 08:29:29 | log4j:WARN No appenders could
>> be found for logger (org.apache.commons.configuration.ConfigurationUtils).
>> INFO | jvm 1 | 2019/01/28 08:29:29 | log4j:WARN Please initialize
>> the log4j system properly.
>> INFO | jvm 1 | 2019/01/28 08:29:29 | log4j:WARN See
>> http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
>> INFO | jvm 1 | 2019/01/28 08:29:30 | INFO 08:29:29,938 |
>> org.apache.james.container.spring.context.JamesServerApplicationContext
>> | Bean 'logprovider' of type [class org.apache.j
>> ames.container.spring.lifecycle.LogProviderImpl] is not eligible for
>> getting processed by all BeanPostProcessors (for example: not eligible
>> for auto-proxying)
>> INFO | jvm 1 | 2019/01/28 08:29:30 | 14 James WARN
>> [WrapperSimpleAppMain] openjpa.Runtime - An error occurred while
>> registering a ClassTransformer with PersistenceUnitInfo: name 'James',
>> root URL [file:/mail/apache-james-3.2/james-server-app-3.2.0/conf]. The
>> error has been consumed. To see it, set your openjpa.Runtime log level
>> to TRACE. Load-time class transformation will not be available.
>>
>> Marc...
>>
>>> On 01/28/2019 04:04 AM, Simon Levesque wrote:
>>> Hi Marc,
>>> I had the same issue and found out they are using
>>> "DailyRollingFileAppender". My fix was to use "DailyRollingFileAppender".
>>> You can see the full file I am using here:
>>> https://github.com/foilen/foilen-infra-plugins-core/blob/master/src/main/resources/com/foilen/infra/resource/email/james/log4j.properties
>>>
>>> HTH
>>>
>>> On Sat, 26 Jan 2019 at 00:41, Marc Chamberlin <ma...@marcchamberlin.com>
>>> wrote:
>>>
>>>> I have noticed that most of the log files for Apache James 3.2 do not
>>>> seem to be getting any log messages after running the server for awhile -
>>>>
>>>> bigbang:/mail/apache-james-3.2/james-server-app-3.2.0/log # ll
>>>> total 248
>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 dnsservice.log
>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 domainlist.log
>>>> -rw-r--r-- 1 james mail 0 Oct 31 09:41 .dummy
>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 fetchmail.log
>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 imapserver.log
>>>> -rw-r--r-- 1 root root 103794 Jan 25 21:19 james-server.log
>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 lmtpserver.log
>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailboxmanager.log
>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailetcontainer.log
>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailqueuefactory.log
>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailrepositorystore.log
>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 pop3server.log
>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 smtpserver.log
>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 usersrepository.log
>>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 virtualusertable.log
>>>> -rw-r--r-- 1 root root 147065 Jan 25 21:19 wrapper.log
>>>>
>>>> The log4j.properties file is simply as it was installed. Looking through
>>>> it, it seems like I should be getting lots of info messages for each of
>>>> the main components, such as imapserver.log and smtpserver.log but nada.
>>>> I fooled around with log4j.properties a bit, by just adding DEBUG level
>>>> logging to the smtpserver.log and imapserver.log but no joy so I undid
>>>> those changes and restored the log4j.properties back to it's original
>>>> state. Any ideas why I am not getting log messages in the rest of these
>>>> log files?
>>>>
>>>> And where can I find more complete documentation about how to set the
>>>> properties in the log4j.properties file? What I have found so far does
>>>> not explain much. I am looking at -
>>>> https://james.apache.org/server/3/monitor-logging.html Thanks... Marc..
>>>>
>>>>
>>>> --
>>>> Linux Counter
>>>>
>> --
>> Linux Counter
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
--
Linux Counter
Re: Logfiles not working
Posted by Garry Hurley <ga...@gmail.com>.
Yeah, the extra logs seem like a good idea, but details are either logged in the james-server.log for out-of-the-box components, or wrapper.log for custom code.
Sent from my iPhone
> On Jan 28, 2019, at 9:27 PM, Marc Chamberlin <ma...@marcchamberlin.com> wrote:
>
> Thanks Simon for your thoughts, I tried making the change as you
> suggested but still no joy! You gave me a path to explore so I am
> digging into log4j and trying to understand it better... And I am
> seeing some warnings in the wrapper log file that look ominous so I am
> digging in to those as well...
>
> INFO | jvm 1 | 2019/01/28 08:29:29 | log4j:WARN No appenders could
> be found for logger (org.apache.commons.configuration.ConfigurationUtils).
> INFO | jvm 1 | 2019/01/28 08:29:29 | log4j:WARN Please initialize
> the log4j system properly.
> INFO | jvm 1 | 2019/01/28 08:29:29 | log4j:WARN See
> http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
> INFO | jvm 1 | 2019/01/28 08:29:30 | INFO 08:29:29,938 |
> org.apache.james.container.spring.context.JamesServerApplicationContext
> | Bean 'logprovider' of type [class org.apache.j
> ames.container.spring.lifecycle.LogProviderImpl] is not eligible for
> getting processed by all BeanPostProcessors (for example: not eligible
> for auto-proxying)
> INFO | jvm 1 | 2019/01/28 08:29:30 | 14 James WARN
> [WrapperSimpleAppMain] openjpa.Runtime - An error occurred while
> registering a ClassTransformer with PersistenceUnitInfo: name 'James',
> root URL [file:/mail/apache-james-3.2/james-server-app-3.2.0/conf]. The
> error has been consumed. To see it, set your openjpa.Runtime log level
> to TRACE. Load-time class transformation will not be available.
>
> Marc...
>
>> On 01/28/2019 04:04 AM, Simon Levesque wrote:
>> Hi Marc,
>> I had the same issue and found out they are using
>> "DailyRollingFileAppender". My fix was to use "DailyRollingFileAppender".
>> You can see the full file I am using here:
>> https://github.com/foilen/foilen-infra-plugins-core/blob/master/src/main/resources/com/foilen/infra/resource/email/james/log4j.properties
>>
>> HTH
>>
>> On Sat, 26 Jan 2019 at 00:41, Marc Chamberlin <ma...@marcchamberlin.com>
>> wrote:
>>
>>> I have noticed that most of the log files for Apache James 3.2 do not
>>> seem to be getting any log messages after running the server for awhile -
>>>
>>> bigbang:/mail/apache-james-3.2/james-server-app-3.2.0/log # ll
>>> total 248
>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 dnsservice.log
>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 domainlist.log
>>> -rw-r--r-- 1 james mail 0 Oct 31 09:41 .dummy
>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 fetchmail.log
>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 imapserver.log
>>> -rw-r--r-- 1 root root 103794 Jan 25 21:19 james-server.log
>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 lmtpserver.log
>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailboxmanager.log
>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailetcontainer.log
>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailqueuefactory.log
>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailrepositorystore.log
>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 pop3server.log
>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 smtpserver.log
>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 usersrepository.log
>>> -rw-r--r-- 1 root root 0 Jan 25 20:30 virtualusertable.log
>>> -rw-r--r-- 1 root root 147065 Jan 25 21:19 wrapper.log
>>>
>>> The log4j.properties file is simply as it was installed. Looking through
>>> it, it seems like I should be getting lots of info messages for each of
>>> the main components, such as imapserver.log and smtpserver.log but nada.
>>> I fooled around with log4j.properties a bit, by just adding DEBUG level
>>> logging to the smtpserver.log and imapserver.log but no joy so I undid
>>> those changes and restored the log4j.properties back to it's original
>>> state. Any ideas why I am not getting log messages in the rest of these
>>> log files?
>>>
>>> And where can I find more complete documentation about how to set the
>>> properties in the log4j.properties file? What I have found so far does
>>> not explain much. I am looking at -
>>> https://james.apache.org/server/3/monitor-logging.html Thanks... Marc..
>>>
>>>
>>> --
>>> Linux Counter
>>>
>
> --
> Linux Counter
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Logfiles not working
Posted by Marc Chamberlin <ma...@marcchamberlin.com>.
Thanks Simon for your thoughts, I tried making the change as you
suggested but still no joy! You gave me a path to explore so I am
digging into log4j and trying to understand it better... And I am
seeing some warnings in the wrapper log file that look ominous so I am
digging in to those as well...
INFO | jvm 1 | 2019/01/28 08:29:29 | log4j:WARN No appenders could
be found for logger (org.apache.commons.configuration.ConfigurationUtils).
INFO | jvm 1 | 2019/01/28 08:29:29 | log4j:WARN Please initialize
the log4j system properly.
INFO | jvm 1 | 2019/01/28 08:29:29 | log4j:WARN See
http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
INFO | jvm 1 | 2019/01/28 08:29:30 | INFO 08:29:29,938 |
org.apache.james.container.spring.context.JamesServerApplicationContext
| Bean 'logprovider' of type [class org.apache.j
ames.container.spring.lifecycle.LogProviderImpl] is not eligible for
getting processed by all BeanPostProcessors (for example: not eligible
for auto-proxying)
INFO | jvm 1 | 2019/01/28 08:29:30 | 14 James WARN
[WrapperSimpleAppMain] openjpa.Runtime - An error occurred while
registering a ClassTransformer with PersistenceUnitInfo: name 'James',
root URL [file:/mail/apache-james-3.2/james-server-app-3.2.0/conf]. The
error has been consumed. To see it, set your openjpa.Runtime log level
to TRACE. Load-time class transformation will not be available.
Marc...
On 01/28/2019 04:04 AM, Simon Levesque wrote:
> Hi Marc,
> I had the same issue and found out they are using
> "DailyRollingFileAppender". My fix was to use "DailyRollingFileAppender".
> You can see the full file I am using here:
> https://github.com/foilen/foilen-infra-plugins-core/blob/master/src/main/resources/com/foilen/infra/resource/email/james/log4j.properties
>
> HTH
>
> On Sat, 26 Jan 2019 at 00:41, Marc Chamberlin <ma...@marcchamberlin.com>
> wrote:
>
>> I have noticed that most of the log files for Apache James 3.2 do not
>> seem to be getting any log messages after running the server for awhile -
>>
>> bigbang:/mail/apache-james-3.2/james-server-app-3.2.0/log # ll
>> total 248
>> -rw-r--r-- 1 root root 0 Jan 25 20:30 dnsservice.log
>> -rw-r--r-- 1 root root 0 Jan 25 20:30 domainlist.log
>> -rw-r--r-- 1 james mail 0 Oct 31 09:41 .dummy
>> -rw-r--r-- 1 root root 0 Jan 25 20:30 fetchmail.log
>> -rw-r--r-- 1 root root 0 Jan 25 20:30 imapserver.log
>> -rw-r--r-- 1 root root 103794 Jan 25 21:19 james-server.log
>> -rw-r--r-- 1 root root 0 Jan 25 20:30 lmtpserver.log
>> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailboxmanager.log
>> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailetcontainer.log
>> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailqueuefactory.log
>> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailrepositorystore.log
>> -rw-r--r-- 1 root root 0 Jan 25 20:30 pop3server.log
>> -rw-r--r-- 1 root root 0 Jan 25 20:30 smtpserver.log
>> -rw-r--r-- 1 root root 0 Jan 25 20:30 usersrepository.log
>> -rw-r--r-- 1 root root 0 Jan 25 20:30 virtualusertable.log
>> -rw-r--r-- 1 root root 147065 Jan 25 21:19 wrapper.log
>>
>> The log4j.properties file is simply as it was installed. Looking through
>> it, it seems like I should be getting lots of info messages for each of
>> the main components, such as imapserver.log and smtpserver.log but nada.
>> I fooled around with log4j.properties a bit, by just adding DEBUG level
>> logging to the smtpserver.log and imapserver.log but no joy so I undid
>> those changes and restored the log4j.properties back to it's original
>> state. Any ideas why I am not getting log messages in the rest of these
>> log files?
>>
>> And where can I find more complete documentation about how to set the
>> properties in the log4j.properties file? What I have found so far does
>> not explain much. I am looking at -
>> https://james.apache.org/server/3/monitor-logging.html Thanks... Marc..
>>
>>
>> --
>> Linux Counter
>>
--
Linux Counter
Re: Logfiles not working
Posted by Simon Levesque <si...@simonlevesque.com>.
Hi Marc,
I had the same issue and found out they are using
"DailyRollingFileAppender". My fix was to use "DailyRollingFileAppender".
You can see the full file I am using here:
https://github.com/foilen/foilen-infra-plugins-core/blob/master/src/main/resources/com/foilen/infra/resource/email/james/log4j.properties
HTH
On Sat, 26 Jan 2019 at 00:41, Marc Chamberlin <ma...@marcchamberlin.com>
wrote:
> I have noticed that most of the log files for Apache James 3.2 do not
> seem to be getting any log messages after running the server for awhile -
>
> bigbang:/mail/apache-james-3.2/james-server-app-3.2.0/log # ll
> total 248
> -rw-r--r-- 1 root root 0 Jan 25 20:30 dnsservice.log
> -rw-r--r-- 1 root root 0 Jan 25 20:30 domainlist.log
> -rw-r--r-- 1 james mail 0 Oct 31 09:41 .dummy
> -rw-r--r-- 1 root root 0 Jan 25 20:30 fetchmail.log
> -rw-r--r-- 1 root root 0 Jan 25 20:30 imapserver.log
> -rw-r--r-- 1 root root 103794 Jan 25 21:19 james-server.log
> -rw-r--r-- 1 root root 0 Jan 25 20:30 lmtpserver.log
> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailboxmanager.log
> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailetcontainer.log
> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailqueuefactory.log
> -rw-r--r-- 1 root root 0 Jan 25 20:30 mailrepositorystore.log
> -rw-r--r-- 1 root root 0 Jan 25 20:30 pop3server.log
> -rw-r--r-- 1 root root 0 Jan 25 20:30 smtpserver.log
> -rw-r--r-- 1 root root 0 Jan 25 20:30 usersrepository.log
> -rw-r--r-- 1 root root 0 Jan 25 20:30 virtualusertable.log
> -rw-r--r-- 1 root root 147065 Jan 25 21:19 wrapper.log
>
> The log4j.properties file is simply as it was installed. Looking through
> it, it seems like I should be getting lots of info messages for each of
> the main components, such as imapserver.log and smtpserver.log but nada.
> I fooled around with log4j.properties a bit, by just adding DEBUG level
> logging to the smtpserver.log and imapserver.log but no joy so I undid
> those changes and restored the log4j.properties back to it's original
> state. Any ideas why I am not getting log messages in the rest of these
> log files?
>
> And where can I find more complete documentation about how to set the
> properties in the log4j.properties file? What I have found so far does
> not explain much. I am looking at -
> https://james.apache.org/server/3/monitor-logging.html Thanks... Marc..
>
>
> --
> Linux Counter
>