2:59 AM
>> To: "users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>" <
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>>
>> Cc: "ehle...@gmail.com<mailto:ehle...@gmail.com>" > <mailto:ehle...@gmail.com>>
>>
oudstack.apache.org>"
mailto:users@cloudstack.apache.org>>
Date: Thursday, May 22, 2014 at 2:59 AM
To: "users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>"
mailto:users@cloudstack.apache.org>>
Cc: "ehle...@gmail.com<mailto:ehle...@gmail
t;mailto:users@cloudstack.apache.org>"
mailto:users@cloudstack.apache.org>>
Cc: "ehle...@gmail.com<mailto:ehle...@gmail.com>"
mailto:ehle...@gmail.com>>
Subject: Re: Major stability problems lately
Hi Timothy and all,
Apologise for replying to an old thread. I n
Hi Timothy and all,
Apologise for replying to an old thread. I noticed that nobody replied to
you on this thread, may I know if you have managed to find the root cause
of the problem, and the solution? I seems to have similar issues with one
of our hypervisors. We are using CloudStack 4.2.0 and KV
What is this error? "Cannot connect because we still have 5" Coult it be
the cause?
for i in `cat cpeg`;do ssh root@$i 'hostname && zgrep "Cannot connect
because we still have " /var/log/cloud/agent/agent.log* |less |awk "{print
\$1}" |uniq -c |sort';done
cpegh0001
1 /var/log/cloud/agent/a
