> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Sch
> eduledThreadPoolExecutor.java:267)
> at
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:11
> 46)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Wo
concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:11
46)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6
15)
at java.lang.Thread.run(Thread.java:679)
-Original Message-
From: Ahmad Emneina [mailto:[email protected]]
Sent: Wednesday
Hey Warren, it could be a slew of reasons. I'd like to see more before i
make a recommendation. Would you be able to paste more logs. Say 100-200
more lines above the stack trace you cited.
On Apr 24, 2013 12:12 PM, "Warren Nicholson"
wrote:
> Using Cloudstack 3.02.
>
>
>
> I've done this a coupl
Using Cloudstack 3.02.
I've done this a couple of times now, with the same result.
After importing the cloud and the cloud_usage DB files from
the mysql backup run from the original controller, the replacement
Controller appears fully functional with one exception.
All templates, in
