Indeed, that’s important. Make sure you run java7 and not java8.
On 24/11/15 18:39, "Yiping Zhang" wrote:
>Which version of OS and java are you using ?
>
>We had encountered a similar error before. AFAICT, we were running RHEL 6.5
>and CS 4.3.2 at the time on a newly setup management server.
Which version of OS and java are you using ?
We had encountered a similar error before. AFAICT, we were running RHEL 6.5
and CS 4.3.2 at the time on a newly setup management server. The java version
installed was IBM version when we saw this error. Once we changed java package
back to java-1
Update / FYI:
After faking the particular VRu in sql, I tried to restart that network,
and it always fails. To me it looks like the update_config.py - which
takes almost all cpu ressources - runs way longer any watchdog will
accept.
I'm able to mitigate that by very nasty workarounds:
a) start the
I heard about discussions for secondary storage migration feature.
Is that something what comes in one of the next releases?
Regards,
Ingo
--
This email was Virus checked by UTM 9. http://www.sophos.com
Hi List!
After upgrading from 4.5.2 to 4.6.0 I faced a problem with one
virtualrouter. This particular VR has about 10 IPs w/ LB and FW rules
defined. During the upgrade process, and after about 4-5 minutes a
watchdog kicks in and kills the respective VR due to no response.
So far I didn't find a
Hi,
We create 40 VMs in a network concurrently by cloudmonkey in CS 4.6.0. It is
slower than in CS 4.5.2. The agent log shows the VR tooks more time to
process CS commands. It seems that the more VMs the worse.
Any idea?
Our env:
CS 4.6.0/4.5.2 + KVM(CentOS 6.5)
--
Qian
Keerhiraja,
This one exists:
https://issues.apache.org/jira/browse/CLOUDSTACK-7446, but is connected
to OVS component that is a part of PVLAN functionality.
Vadim.
On 2015-11-24 11:06, Keerthiraja SJ wrote:
Regarding this issue is anyone raised issue in Jira if so please
provide me
it
Perform yum update nss on your Manageemnt server or downgrade your java version
then restart your MS.Hope that addresses your problem
Regards
Sadhu
-Original Message-
From: Abhinandan Prateek [mailto:abhinandan.prat...@shapeblue.com]
Sent: Tuesday, November 24, 2015 2:50 PM
To: users
Check the ‘host’ name entry in configuration table (or global settings via UI).
This is the ip that ssvm/cpvm will use to try to connect back to MS.
Make sure that it is reachable and points to MS.
Abhinandan Prateek
S: +44 20 3603 0540 | M: +91 97011 99011
abhinandan.prat...@shapeblue.com
Regarding this issue is anyone raised issue in Jira if so please provide me
it will help me to follow.
Thanks,
Keerthi
On Tue, Nov 24, 2015 at 1:29 PM, Vadim Kimlaychuk
wrote:
> Dear Stavros,
>
> We also use XS 6.5 with bonding(active-backup) and VLANs, but this
> discussion is about PVLAN
You need the 4.5 and 4.6 systemvm templates when upgrading (will be fixed in
4.6.1). We tried upgrading from 4.4 and that works.
Do you use xenserver? There were many changes in 4.4 regarding xenha. Be sure
to check that.
Testing it in a lab before actually performing the upgrade is always a
11 matches
Mail list logo