Diego, please go ahead and file a bug with Priority Critical against CS. Looks like there is some bug in a way to commit db statement in transaction resulting in the DB not being updated:
2014-03-17 13:14:15,431 TRACE [db.Transaction.Transaction] (RouterMonitor-1:null) txn: Not committing because transaction started elsewhere: -GenericDaoBase.update:814-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-GenericDaoBase.update:774-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-GenericDaoBase.update:1262-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-VirtualNetworkApplianceManagerImpl$NetworkUsageTask.run:948-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267 / -VirtualNetworkApplianceManagerImpl$NetworkUsageTask.run:900-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:701 : update, update, update, -VirtualNetworkApplianceManagerImpl$NetworkUsageTask.run:900-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:701, Attach the latest log from this email to the bug. Unfortunately, there is no way to workaround it on your side as its a code issue. -Alena. From: Diego Spinola Castro <spinolacas...@gmail.com<mailto:spinolacas...@gmail.com>> Date: Monday, March 17, 2014 at 11:25 AM To: Alena Prokharchyk <alena.prokharc...@citrix.com<mailto:alena.prokharc...@citrix.com>> Cc: "users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>" <users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>> Subject: Re: NetworkUsage Hi, sorry. i went lost with this huge log. 2014-03-17 15:10 GMT-03:00 Alena Prokharchyk <alena.prokharc...@citrix.com<mailto:alena.prokharc...@citrix.com>>: Diego, the log you’ve provided, doesn’t contain “Rolling back the transaction” statement. You should wait for this particular error to happen (while logging on TRACE), and then take a log snippet. From: Diego Spinola Castro <spinolacas...@gmail.com<mailto:spinolacas...@gmail.com>> Date: Monday, March 17, 2014 at 11:00 AM To: Alena Prokharchyk <alena.prokharc...@citrix.com<mailto:alena.prokharc...@citrix.com>> Cc: "users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>" <users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>> Subject: Re: NetworkUsage Hi, Alena. thanks for the tips, i got some logs: http://www.fpaste.org/86141/13950791/ 2014-03-17 14:27 GMT-03:00 Alena Prokharchyk <alena.prokharc...@citrix.com<mailto:alena.prokharc...@citrix.com>>: Diego, Unfortunately CS lock lack the needed info for debugging the problem. I see only transaction roll back statement: 2014-03-17 06:01:22,363 DEBUG [db.Transaction.Transaction] (RouterMonitor-1:null) Rolling back the transaction: Time = 2 Name = -VirtualNetworkApplianceManagerImpl$NetworkUsageTask.run:900-Executors$Runn ableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAnd Reset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165- To debug it further, you need to change the log level from DEBUG to TRACE for a certain class by modifying log4 properties (no MS restart is required) Here is the link on how to do it: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Useful+Tips+and+Tric ks, "How to enable trace logging for a particular class in CloudStack?² section. Replace category name with: <category name=³com.cloud.utils.db"> <priority value=³TRACE"/> </category> After the change is done, wait till you see TRACE statements in the log, and till the error "Rolling back the transaction" occurs again. Take the log snippet and send it out. After you are done with that, you will need to remove TRACE config from log4 properties file, otherwise your logs will grow huge. -Alena. On 3/17/14, 9:48 AM, "Diego Spinola Castro" <spinolacas...@gmail.com<mailto:spinolacas...@gmail.com>> wrote: >Hi guys, i've been running into a issue when getting network traffic from >usage server. All records are Zero, i have a CS 4.2.0 install. > >Here the usage.logs http://www.fpaste.org/86116/13950748/ >And management-server.log http://www.fpaste.org/86118/07486613/ > >Does anyone know what is wrong ?
