[jira] [Commented] (CLOUDSTACK-9347) SS VM agent fails to start due to Java error (clone from #8234)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15474214#comment-15474214 ] Dominic Blais commented on CLOUDSTACK-9347: --- Find every cloudstack-* package and replace them with packages you built from sources (Follow instructions on the cloudstack website about how to do it). Just do it with the same version you already have... -- Dominic Blais > SS VM agent fails to start due to Java error (clone from #8234) > > > Key: CLOUDSTACK-9347 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9347 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: SystemVM >Affects Versions: 4.5.0 > Environment: CentOS 6, KVM >Reporter: Dominic Blais >Priority: Critical > Labels: secondary_storage, ssvm > > After an upgrade from 4.4.2 everything appears to go smoothly except the SSVM > agent which fails to start: > From the VM's /var/log/cloud.log: > ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent: Resource > class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource > due to: java.lang.ClassNotFoundException: > com.cloud.storage.resource.PremiumSecondaryStorageResource > More here http://fpaste.org/183058/34269811/raw/ > Java is installed: > root@s-386-VM:~# dpkg -l| grep jre > ii openjdk-7-jre-headless:amd64 7u75-2.5.4-1~deb7u1 amd64 >OpenJDK Java runtime, using Hotspot JIT (headless) > The HV and management servers are also on openjdk 7 (1.7.0) from CentOS 6 > stock. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9347) SS VM agent fails to start due to Java error (clone from #8234)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15473939#comment-15473939 ] Dominic Blais commented on CLOUDSTACK-9347: --- I found out the management server package is non-oss while the agents are oss... or the other way around?! I fixed the issue by creating packages from sources (All oss). -- Dominic Blais > SS VM agent fails to start due to Java error (clone from #8234) > > > Key: CLOUDSTACK-9347 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9347 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: SystemVM >Affects Versions: 4.5.0 > Environment: CentOS 6, KVM >Reporter: Dominic Blais >Priority: Critical > Labels: secondary_storage, ssvm > > After an upgrade from 4.4.2 everything appears to go smoothly except the SSVM > agent which fails to start: > From the VM's /var/log/cloud.log: > ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent: Resource > class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource > due to: java.lang.ClassNotFoundException: > com.cloud.storage.resource.PremiumSecondaryStorageResource > More here http://fpaste.org/183058/34269811/raw/ > Java is installed: > root@s-386-VM:~# dpkg -l| grep jre > ii openjdk-7-jre-headless:amd64 7u75-2.5.4-1~deb7u1 amd64 >OpenJDK Java runtime, using Hotspot JIT (headless) > The HV and management servers are also on openjdk 7 (1.7.0) from CentOS 6 > stock. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-9347) SS VM agent fails to start due to Java error (clone from #8234)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15241289#comment-15241289 ] Dominic Blais edited comment on CLOUDSTACK-9347 at 4/14/16 2:43 PM: Hi! I could upgrade but how do I install the systemvm model for 4.8 without the SSVM?? I see openjdk 6 and 7 are installed on each nodes (management and compute nodes). Running java -version returns: java version "1.7.0_95" OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2) OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode) was (Author: deejay2): Hi! I could upgrade but how do I install the systemvm model for 4.8 without the SSVM?? > SS VM agent fails to start due to Java error (clone from #8234) > > > Key: CLOUDSTACK-9347 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9347 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: SystemVM >Affects Versions: 4.5.0 > Environment: CentOS 6, KVM >Reporter: Dominic Blais >Priority: Critical > Labels: secondary_storage, ssvm > > After an upgrade from 4.4.2 everything appears to go smoothly except the SSVM > agent which fails to start: > From the VM's /var/log/cloud.log: > ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent: Resource > class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource > due to: java.lang.ClassNotFoundException: > com.cloud.storage.resource.PremiumSecondaryStorageResource > More here http://fpaste.org/183058/34269811/raw/ > Java is installed: > root@s-386-VM:~# dpkg -l| grep jre > ii openjdk-7-jre-headless:amd64 7u75-2.5.4-1~deb7u1 amd64 >OpenJDK Java runtime, using Hotspot JIT (headless) > The HV and management servers are also on openjdk 7 (1.7.0) from CentOS 6 > stock. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9347) SS VM agent fails to start due to Java error (clone from #8234)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15241289#comment-15241289 ] Dominic Blais commented on CLOUDSTACK-9347: --- Hi! I could upgrade but how do I install the systemvm model for 4.8 without the SSVM?? > SS VM agent fails to start due to Java error (clone from #8234) > > > Key: CLOUDSTACK-9347 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9347 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: SystemVM >Affects Versions: 4.5.0 > Environment: CentOS 6, KVM >Reporter: Dominic Blais >Priority: Critical > Labels: secondary_storage, ssvm > > After an upgrade from 4.4.2 everything appears to go smoothly except the SSVM > agent which fails to start: > From the VM's /var/log/cloud.log: > ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent: Resource > class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource > due to: java.lang.ClassNotFoundException: > com.cloud.storage.resource.PremiumSecondaryStorageResource > More here http://fpaste.org/183058/34269811/raw/ > Java is installed: > root@s-386-VM:~# dpkg -l| grep jre > ii openjdk-7-jre-headless:amd64 7u75-2.5.4-1~deb7u1 amd64 >OpenJDK Java runtime, using Hotspot JIT (headless) > The HV and management servers are also on openjdk 7 (1.7.0) from CentOS 6 > stock. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9347) SS VM agent fails to start due to Java error (clone from #8234)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15240468#comment-15240468 ] Dominic Blais commented on CLOUDSTACK-9347: --- Well, I have the same error in cloud.log under the SSVM. I upgraded from 4.3.2 to 4.5.2. I really need help with this please! > SS VM agent fails to start due to Java error (clone from #8234) > > > Key: CLOUDSTACK-9347 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9347 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: SystemVM >Affects Versions: 4.5.0 > Environment: CentOS 6, KVM >Reporter: Dominic Blais >Priority: Critical > Labels: secondary_storage, ssvm > > After an upgrade from 4.4.2 everything appears to go smoothly except the SSVM > agent which fails to start: > From the VM's /var/log/cloud.log: > ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent: Resource > class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource > due to: java.lang.ClassNotFoundException: > com.cloud.storage.resource.PremiumSecondaryStorageResource > More here http://fpaste.org/183058/34269811/raw/ > Java is installed: > root@s-386-VM:~# dpkg -l| grep jre > ii openjdk-7-jre-headless:amd64 7u75-2.5.4-1~deb7u1 amd64 >OpenJDK Java runtime, using Hotspot JIT (headless) > The HV and management servers are also on openjdk 7 (1.7.0) from CentOS 6 > stock. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9347) SS VM agent fails to start due to Java error (clone from #8234)
Dominic Blais created CLOUDSTACK-9347: - Summary: SS VM agent fails to start due to Java error (clone from #8234) Key: CLOUDSTACK-9347 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9347 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.5.0 Environment: CentOS 6, KVM Reporter: Dominic Blais Priority: Critical After an upgrade from 4.4.2 everything appears to go smoothly except the SSVM agent which fails to start: >From the VM's /var/log/cloud.log: ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent: Resource class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource due to: java.lang.ClassNotFoundException: com.cloud.storage.resource.PremiumSecondaryStorageResource More here http://fpaste.org/183058/34269811/raw/ Java is installed: root@s-386-VM:~# dpkg -l| grep jre ii openjdk-7-jre-headless:amd64 7u75-2.5.4-1~deb7u1 amd64 OpenJDK Java runtime, using Hotspot JIT (headless) The HV and management servers are also on openjdk 7 (1.7.0) from CentOS 6 stock. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8234) SS VM agent fails to start due to Java error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15240466#comment-15240466 ] Dominic Blais commented on CLOUDSTACK-8234: --- Exactly same issue here after upgrading from 4.3.2 to 4.5.2 . Same error in cloud.log in the SSVM. I really need help with this please! > SS VM agent fails to start due to Java error > > > Key: CLOUDSTACK-8234 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8234 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: SystemVM >Affects Versions: 4.5.0 > Environment: CentOS 6, KVM >Reporter: Nux >Priority: Critical > Labels: secondary_storage, ssvm > > After an upgrade from 4.4.2 everything appears to go smoothly except the SSVM > agent which fails to start: > From the VM's /var/log/cloud.log: > ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent: Resource > class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource > due to: java.lang.ClassNotFoundException: > com.cloud.storage.resource.PremiumSecondaryStorageResource > More here http://fpaste.org/183058/34269811/raw/ > Java is installed: > root@s-386-VM:~# dpkg -l| grep jre > ii openjdk-7-jre-headless:amd64 7u75-2.5.4-1~deb7u1 amd64 >OpenJDK Java runtime, using Hotspot JIT (headless) > The HV and management servers are also on openjdk 7 (1.7.0) from CentOS 6 > stock. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-2383) Entity already exists error at automatic virtual router VM creation.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Blais closed CLOUDSTACK-2383. - Resolution: Fixed Entity already exists error at automatic virtual router VM creation. -- Key: CLOUDSTACK-2383 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2383 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.0.2 Environment: Ubuntu 12.04.2 on management node and compute nodes. Reporter: Dominic Blais In advanced networking mode, whenever I have a new network created and needs to spawn one or two virtual routers VM, as soon as I create a user VM attached to that network, there will be a Entity already exists error. The user VM is then in error state and the virtual router(s) is created but in stopped state. That's also true for RVR with both VR. If I try again do create a user VM, it's always the same thing. To start a user VM on a new network, I need to: - Create a VM on a new network OR create a network and attach a new VM to it for the first time - Launch the VM - Wait for the error - Start the virtual router manually - Launch the VM. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-2388) HA Host Allocator returning 0 suitable hosts but starting the VM manually finds one.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Blais closed CLOUDSTACK-2388. - Resolution: Fixed HA Host Allocator returning 0 suitable hosts but starting the VM manually finds one. -- Key: CLOUDSTACK-2388 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2388 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.0.2 Environment: Ubuntu 12.04.2 amd64 Server on management and compute nodes. Reporter: Dominic Blais Attachments: Management Logs.txt Whenever I try to crash a compute node for the purpose of testing HA respawning of VM on another host, HA-Worker returns Host Allocator returning 0 suitable hosts. 2013-05-08 09:11:18,179 DEBUG [cloud.deploy.FirstFitPlanner] (HA-Worker-2:work-2) Calling HostAllocators to find suitable hosts 2013-05-08 09:11:18,179 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-2:work-2 FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:1 2013-05-08 09:11:18,181 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-2:work-2 FirstFitRoutingAllocator) FirstFitAllocator has 0 hosts to check for allocation: [] 2013-05-08 09:11:18,183 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-2:work-2 FirstFitRoutingAllocator) Found 0 hosts for allocation after prioritization: [] 2013-05-08 09:11:18,184 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-2:work-2 FirstFitRoutingAllocator) Looking for speed=4000Mhz, Ram=4096 2013-05-08 09:11:18,184 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-2:work-2 FirstFitRoutingAllocator) Host Allocator returning 0 suitable hosts The thing is, starting the VM manually right after is working because there are plenty enough of ressources -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2383) Entity already exists error at automatic virtual router VM creation.
Dominic Blais created CLOUDSTACK-2383: - Summary: Entity already exists error at automatic virtual router VM creation. Key: CLOUDSTACK-2383 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2383 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.0.2 Environment: Ubuntu 12.04.2 on management node and compute nodes. Reporter: Dominic Blais In advanced networking mode, whenever I have a new network created and needs to spawn one or two virtual routers VM, as soon as I create a user VM attached to that network, there will be a Entity already exists error. The user VM is then in error state and the virtual router(s) is created but in stopped state. That's also true for RVR with both VR. If I try again do create a user VM, it's always the same thing. To start a user VM on a new network, I need to: - Create a VM on a new network OR create a network and attach a new VM to it for the first time - Launch the VM - Wait for the error - Start the virtual router manually - Launch the VM. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2388) HA Host Allocator returning 0 suitable hosts but starting the VM manually finds one.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Blais updated CLOUDSTACK-2388: -- Attachment: Management Logs.txt Management Server Logs showing the issue... HA Host Allocator returning 0 suitable hosts but starting the VM manually finds one. -- Key: CLOUDSTACK-2388 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2388 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.0.2 Environment: Ubuntu 12.04.2 amd64 Server on management and compute nodes. Reporter: Dominic Blais Attachments: Management Logs.txt Whenever I try to crash a compute node for the purpose of testing HA respawning of VM on another host, HA-Worker returns Host Allocator returning 0 suitable hosts. 2013-05-08 09:11:18,179 DEBUG [cloud.deploy.FirstFitPlanner] (HA-Worker-2:work-2) Calling HostAllocators to find suitable hosts 2013-05-08 09:11:18,179 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-2:work-2 FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:1 2013-05-08 09:11:18,181 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-2:work-2 FirstFitRoutingAllocator) FirstFitAllocator has 0 hosts to check for allocation: [] 2013-05-08 09:11:18,183 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-2:work-2 FirstFitRoutingAllocator) Found 0 hosts for allocation after prioritization: [] 2013-05-08 09:11:18,184 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-2:work-2 FirstFitRoutingAllocator) Looking for speed=4000Mhz, Ram=4096 2013-05-08 09:11:18,184 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-2:work-2 FirstFitRoutingAllocator) Host Allocator returning 0 suitable hosts The thing is, starting the VM manually right after is working because there are plenty enough of ressources -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
