Re: Logfiles not working RESOLVED SOMEWHAT!
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 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 >>> 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
Re: Logfiles not working
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 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 >> 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-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
Recent work on Apache James @Linagora: Distributed Guice James server, reactor, and more!
Hi Apache James community, We, at Linagora had been working hard on the past few months on making James a fully distributed email server. This work had been achieved on top of the Guice product 'Cassandra-ElasticSearch-RabbitMQ'. Our team did rewrite most of the mailbox event system, introducing a new EventBus component, which has a memory InVM based implementation, as well as a RabbitMQ one. Mailbox events are used by MailboxListeners to: - Extend the MDA capabilities of the Mailbox. We can find examples like Mailbox Indexing, SpamAssassin feedback, quota updates, etc... - Notifications. Like IMAP IDLE. And in the future this will be used by JMAP PUSH - Note that using Guice products, an admin can load custom mailbox listeners (achieving MDA extensibility) We did pay a close look to error handling: - MailboxListener should now delegate error handling to the eventBus - The eventBus will retry MailboxListener execution, using a backoff strategy - When the maximum number of retries is exceeded, the event is stored in "dead-letters" so that the admin can diagnose issues and re-schedule delivery. - RabbitMQ eventBus ensures "at least once" delivery We wrote an article about the RabbitMQ EventBus here: [1] We now intend to further test and experiment with this brand new distributed James server! An external eventBus like RabbitMQ also means that we need to serialize events. Being not satisfied of the verbose approach using Jackson, the team did write this serialization logic using Scala (well isolated, well tested, and well integrated to Java 8 code) with satisfying results. We wrote a quick article about scala JSON serialization here: [2] Another recent topic had been mail aliases. We introduced a specific mapping type to highlight this intent. And we allowed listing sources from a given mapping (here listing the aliases of a user). The associated webadmin routes can be found here: [3]. Last but not least, we are porting existing code of specific modules (Cassandra, rabbitMQ) to Reactor, to allow easier to maintain, and more efficient asynchronous code. You can read about this ongoing effore here [4]. [1] https://medium.com/p/b159f46704be/ : Some explanations about the RabbitMQ eventBus [2] https://medium.com/linagora-engineering/toward-a-polyglot-james-server-c3f3c92655db : Toward a polyglot James server... Scala and JSON serialization for mailbox events [3] https://github.com/apache/james-project/blob/master/src/site/markdown/server/manage-webadmin.md#creating-address-aliases : Aliases routes documentation [4] https://medium.com/p/3be69af3f0a9/ : Our journey with Reactor. Other James related readings: [5] https://medium.com/linagora-engineering/next-level-java-8-staged-builders-602530f68b75 : Next level Java 8 staged builders, a design pattern we used to provide nice builders for Mailbox Events Best regards, Benoit TELLIER - To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
Re: Logfiles not working
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 > 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
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 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 >
