GabrielBrascher edited a comment on issue #4067:
URL: https://github.com/apache/cloudstack/issues/4067#issuecomment-626571957


   **4.14.0.0 RC2 on Ubuntu 18.04**
   
   I just checked the usage.log and I can see that it loaded Bean 
`IPAddressUsageParser` successfully.
   ```
   2020-05-11 10:53:44,992 DEBUG [usage.parser.IPAddressUsageParser] 
(Usage-Job-1:null) (logid:) Parsing IP Address usage for account: 3
   2020-05-11 10:53:44,993 DEBUG [usage.parser.IPAddressUsageParser] 
(Usage-Job-1:null) (logid:) No IP Address usage for this period
   2020-05-11 10:53:45,009 DEBUG [usage.parser.IPAddressUsageParser] 
(Usage-Job-1:null) (logid:) Parsing IP Address usage for account: 5
   2020-05-11 10:53:45,010 DEBUG [usage.parser.IPAddressUsageParser] 
(Usage-Job-1:null) (logid:) No IP Address usage for this period
   2020-05-11 10:53:48,442 DEBUG [usage.parser.IPAddressUsageParser] 
(Usage-Job-1:null) (logid:) Parsing IP Address usage for account: 6
   2020-05-11 10:53:48,444 DEBUG [usage.parser.IPAddressUsageParser] 
(Usage-Job-1:null) (logid:) Total usage time 86400000ms
   2020-05-11 10:53:48,444 DEBUG [usage.parser.IPAddressUsageParser] 
(Usage-Job-1:null) (logid:) Creating IP usage record with id: 526, usage: 24, 
startDate: Sun Jul 14 02:00:00 CEST 2019, endDate: Mon Jul 15 01:59:59 CEST 
2019, for account
   ```
   
   Just for the record, the INFO regarding Bean 'transactionContextBuilder' is 
also logged, but there is no WARN regarding `IPAddressUsageParser` at the 
usage.log:
   ```
   2020-05-11 10:48:52,572 INFO  
[context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker] 
(main:null) (logid:) Bean 'transactionContextBuilder' of type 
[com.cloud.utils.db.TransactionContextBuilder] is not eligible for getting 
processed by all BeanPostProcessors (for example: not eligible for 
auto-proxying)
   ```
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to