I set some new over provisioning values, stopped all running instances, and
restarted the management service. When I logged back in, the system
capacity has not changed. All instances are stopped, yet the dashboard
still reports the same resource usage as before I shut them down. How do I
refres
I tried upgrading from 4.4.0 to 4.4.1 but now I get a 404 error when I try
to access the management console. The localhost.2014-10-03.log shows this
error:
Caused by: java.io.IOException: Resource
[jar:file:/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-api-4.4.1.jar!/META-INF/
com.cloud.utils.exception.CloudRuntimeException: 4.4.0 KVM SystemVm
template not found. Cannot upgrade system Vms
Any ideas about how I can fix this? I had a 4.4.0 KVM SystemVm template
prior to the upgrade.
On Fri, Oct 3, 2014 at 1:39 PM, Ian Young wrote:
> I tried upgrading from 4.4.0 to 4.
Fri, Oct 3, 2014 at 1:51 PM, Ian Young wrote:
> It looks like this is the root of the problem:
>
> 2014-10-03 13:44:47,131 DEBUG [c.c.u.d.Upgrade440to441] (main:null)
> Updating System Vm template IDs
> 2014-10-03 13:44:47,136 DEBUG [c.c.u.d.Upgrade440to441] (main:null)
> Updating
I wanted to bypass the virtual router as the first DNS server so that my
instances would use our existing physical DNS servers. I followed the
instructions here:
http://support.citrix.com/article/CTX138970
I set "use.external.dns" to true and then restarted the virtual router.
The VR remained in
I restarted the agent about a half dozen times and the router magically
started itself. What's the best way to make my instances use our internal
DNS servers?
On Thu, Oct 9, 2014 at 3:33 PM, Ian Young wrote:
> I wanted to bypass the virtual router as the first DNS server so that my
>
This morning I was unable to start new instances. I discovered that I
could SSH into the SSVM and the console proxy but not the virtual router.
Something strange was happening so I thought it might be a good time to
gracefully stop all the instances and reboot the hypervisor to see if the
VR would
gs, better luck next time!
2014-10-10 14:43:41,926 - Failed to get rule logs, better luck next time!
What does this mean?
On Fri, Oct 10, 2014 at 2:11 PM, Ian Young wrote:
> This morning I was unable to start new instances. I discovered that I
> could SSH into the SSVM and the console prox
at 2:48 PM, Ian Young wrote:
> I restarted the libvirtd service and the management service is now fully
> started (there are services listening on ports 8250 and 9090). The SSVM
> health check script now reports no problems.
>
> However, I tried starting an instance and both the i
16:27:33,259 - Failed to get rule logs, better luck next time!
On Fri, Oct 10, 2014 at 3:04 PM, Ian Young wrote:
> I tried to restart the network with the "clean up" option, via the web
> console. After several minutes, it failed to restart the network. The
> SSVM and CP are
[kvm.resource.LibvirtComputingResource]
(Script-3:null) Interrupting script.
On Fri, Oct 10, 2014 at 4:33 PM, Ian Young wrote:
> I've restarted all the services and restarted the servers too. The SSVM
> and CP start with no trouble. Every time I try to start or create an
> instance, I see repeated messa
z2
On Fri, Oct 10, 2014 at 7:28 PM, Ian Young wrote:
> I dropped all the cloud* databases, deleted everything in primary and
> secondary storage, and reinstalled the management server, following the
> guide I wrote for myself the last time I built a stable CloudStack system.
> Then I i
fferent default? Like the router
> service offering memory :P or doesn't that make any sense?
>
> On Sat, Oct 11, 2014 at 5:11 AM, Ian Young wrote:
>
> > Aha! I restarted cloudstack-agent, which caused the virtual router to
> > change to a "stopped" status in t
When I set up CloudStack, I chose my physical DNS servers as both the
internal and external DNS servers. They perform recursion, so they are
suitable for queries about hosts on the LAN as well as on the rest of the
internet. However, the /etc/resolv.conf file in my instances lists the
virtual rou
I upgraded from 4.2.1 to 4.3.0 tonight, following the instructions here:
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3
At the last step, I tried to restart the system VMs. The virtual router
failed to start. Here is the messa
, Ian Young wrote:
> I upgraded from 4.2.1 to 4.3.0 tonight, following the instructions here:
>
>
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3
>
> At the last step, I tried to restart the system VMs.
Did rolling back to 4.2 fix the problem?
On Tue, Apr 29, 2014 at 1:22 PM, stevenliang wrote:
> I met your situation before. Finally I rolled back to 4.2
>
>
> On 29/04/14 04:18 PM, Ian Young wrote:
>
>> I destroyed the old virtual router and was able to create a new o
at least 1GB on CPU and 512MB of RAM
> >>>> your
> >>>> VR will survive the upgrade from 4.2.1 to 4.3.1.
> >>>>
> >>>> I am running KVM, when I upgrade from 4.2.1 to 4.3 my VMs were not
> able
> >>>>
d for user 'cloud'@'localhost'
(using password: YES)
Where are the credentials stored?
On Tue, Apr 29, 2014 at 2:55 PM, Ian Young wrote:
> I think you can do that when you register the new templates in step 1 of
> this guide:
>
>
> http://docs.cloudstack.ap
> >>>>> On 29/04/14 05:19 PM, motty cruz wrote:
> >>>>>
> >>>>> Stevenllang,
> >>>>>
> >>>>>> I had the similar issue with VR, I notice it was because I leave the
> >>>>>> default syste
9, 2014 3:09 PM, "Ian Young" wrote:
> @stevenliang: I take it back--you can't set the VM size when you register
> the template.
>
>
> On Tue, Apr 29, 2014 at 3:02 PM, motty cruz wrote:
>
>> yes, you would have to shutdown the router, then click on "
quot;errorcode":530,"errortext":"Failed
to copy the volume from the source primary storage pool to secondary
storage."}
On Tue, Apr 29, 2014 at 4:15 PM, Ian Young wrote:
> I downgraded to 4.2.1 again but cloudstack-management won't start because
> the database
are all hashes. I really need to get these instances
up and running--there are several months worth of work at stake here.
On Tue, Apr 29, 2014 at 6:13 PM, ma y wrote:
> I got the same problem, and how to downgrade CS 4.3.0 to 4.2.1 safely?
>
>
> 2014-04-30 8:45 GMT+08:0
EBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
>> > (Job-Executor-11:ctx-0a3ead79) Complete async job-501, jobStatus:
>> FAILED,
>> > resultCode: 530, result:
>> >
>> >
>> org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":
ystem
VMs won't start. I suspect there is something in the database that is
causing it to try to use the 4.3 template. How can I delete the template
and make sure the management server is using the older one?
On Tue, Apr 29, 2014 at 8:23 PM, Ian Young wrote:
> Ok, so I've fi
gt; On 30/04/14 02:58 PM, Ian Young wrote:
>
>> I think my problem stems from a partially downloaded system VM template.
>> I
>> just noticed systemvm-kvm-4.3 is stuck at 27% downloaded. It must have
>> been interrupted during the upgrade to 4.3. At the moment I
and
> agent.properties.rpmsave on agents? If so, and the date is correct, you can
> use it rather than db.properties and agent.properties.
> And then restart management and agent services.
>
>
> On 30/04/14 03:26 PM, Ian Young wrote:
>
>> Yes, I restored the DB from the backup. When I try
The address in Infrastructure > Hosts > (management server) is set to the
correct IP address, not 127.0.0.1. Why are the logs referring to 127.0.0.1?
On Wed, Apr 30, 2014 at 3:00 PM, Ian Young wrote:
> I notice my dashboard says "Management server node 127.0.0.1 is up." I
I notice my dashboard says "Management server node 127.0.0.1 is up." It
used to have an actual address, not localhost. Could this be causing
problems and if so, how can I set it back?
On Wed, Apr 30, 2014 at 12:40 PM, Ian Young wrote:
> Yes, I replaced the new files with the
ownloading?
On Wed, Apr 30, 2014 at 3:03 PM, Ian Young wrote:
> The address in Infrastructure > Hosts > (management server) is set to the
> correct IP address, not 127.0.0.1. Why are the logs referring to 127.0.0.1?
>
>
> On Wed, Apr 30, 2014 at 3:00 PM, Ian Young wrote:
I read this article about upgrading the system VMs:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.2+(KVM)+System+Vm+Upgrade
However, there's just an empty set in the template_host_ref table. Is this
no longer used in 4.3?
On Wed, Apr 30, 2014 at 5:41 PM, Ian Young
My management server IP address has always been 192.168.100.6. Ever since
I upgraded to 4.3, it's been set to 127.0.0.1 (mshost.service_ip in the
database). Where is this value being set and how can I change it back to
the original IP address?
n and start over, losing all my VMs in the process.
On Wed, Apr 30, 2014 at 6:00 PM, Ian Young wrote:
> I read this article about upgrading the system VMs:
>
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.2+(KVM)+System+Vm+Upgrade
>
> However, there
I'm reinstalling CloudStack on a single server with lots of RAM, CPU cores,
and storage. I also have a single 192.168.100.0/24 private network, which
was set up before I was hired and can't be easily reconfigured due to the
high number of employee workstations currently connected to it and
occupyi
I forgot to mention this system is entirely for internal purposes. We
don't need a public network.
On Mon, May 5, 2014 at 3:39 PM, Ian Young wrote:
> I'm reinstalling CloudStack on a single server with lots of RAM, CPU
> cores, and storage. I also have a single 192.168.
I reinstalled my single server CloudStack system yesterday, following the
quick start guide precisely. The only difference was that I used
/var/primary and /var/secondary instead of /primary and /secondary, because
the /var partition on this machine is very large. The UI installer reached
the poi
doers configuration had on my problem but I'm pretty sure the NFS setup
was the main issue.
On Thu, May 8, 2014 at 5:33 PM, Ian Young wrote:
> I know this has something to do with idmapd and NFS. This error keeps
> appearing in /var/log/messages:
> May 8 10:29:54 virthos
follow the Cloudstack
> > 4.3 installation guide there is a mistake in system template setup
> section,
> > >
> > > you should change the old URL with:
> > >
> >
> http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-kvm.qcow2
version of Cloudstack you installd? If you follow the Cloudstack
> 4.3 installation guide there is a mistake in system template setup section,
> >
> > you should change the old URL with:
> >
> http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-kvm.qcow2.
the secondary storage is
unreachable?
On Wed, May 7, 2014 at 10:26 AM, Ian Young wrote:
> I reinstalled my single server CloudStack system yesterday, following the
> quick start guide precisely. The only difference was that I used
> /var/primary and /var/secondary instead of /primary
I know this has something to do with idmapd and NFS. This error keeps
appearing in /var/log/messages:
May 8 10:29:54 virthost1 rpc.idmapd[11044]: nss_getpwnam: name '0' does
not map into domain 'redacted.com'
On Thu, May 8, 2014 at 5:20 PM, Ian Young wrote:
> I wip
I decided to create my own internal realhostip.com. My DNS servers use
PowerDNS, not BIND, so the $GENERATE directive was not an option and I
didn't want to have to populate my DNS servers' databases with a record for
every possible IP address. Fortunately, I found the following Lua script:
http
OHtRh7nli7tiq0ZiWUuwCVIn_GSECIK5nC2lBX8cMHvt1_GrmwDVK1PEEAwyueLlgNRgodobz8Lsyv2jEc-mUvMH340AYGt0FyZOuXIA6dunN3yx-bP-vp4rao5Up61eJwOvqFr3PhggNpbq5Up59ObOdYMe2GsBP_3FrL8ZQfBhNBSmViHQ0fKJSyUHDoC9tKlfs2Bb0rPOBxsZeTPfe-hDuaVT-pZxjQXCKM93sujnWw
">
On Wed, May 14, 2014 at 5:41 PM, Ian Young wrote:
> I decided to creat
590c96d30
The management server log keeps reporting that "There is no secondary
storage VM for secondary storage host nfs://192.168.100.6/var/secondary."
Here is a larger section of logs:
http://pastebin.com/NFf5cBx3
On Wed, May 7, 2014 at 10:49 AM, Ian Young wrote:
> I noticed that in
0 0 0.0.0.0:80010.0.0.0:* LISTEN
3491/java
tcp0 0 0.0.0.0:80 0.0.0.0:* LISTEN
3491/java
On Thu, May 15, 2014 at 2:53 PM, Ian Young wrote:
> I just realized I had to set the consoleproxy.url.domain
s not trusted
because it is self-signed but it doesn't give me the option to accept it.
It's not an unreasonable expectation to be able to use self-signed SSL
certificates for an internal site. Is there a setting in CloudStack that
allows them to be trusted?
On Fri, May 16, 2014 at 10:3
omain" refer to?
>
> Thanks,
> Amogh
>
> On 5/14/14 5:41 PM, "Ian Young" wrote:
>
> >I decided to create my own internal realhostip.com. My DNS servers use
> >PowerDNS, not BIND, so the $GENERATE directive was not an option and I
> >didn'
ining this procedure to everyone else. I really hope someone can
think of a more elegant alternative to realhostip.com when 4.4 is released.
It will lead to better product adoption.
On Fri, May 16, 2014 at 10:49 AM, Ian Young wrote:
> Ok, so the console proxy needed to be restarted in
eployment_Guide-en-US/s1-nfs-server-config-exports.html
On Thu, May 15, 2014 at 10:37 AM, Ian Young wrote:
> That quick start guide used to have the wrong URL for the system VM
> template but it looks like it has been corrected since then. Check your
> command line history and
tRh7nli7tiq0ZiWUuwCVIn7K0vuegv6oMAAq_vDY4Vr_f7jwoVQDkxAE1vmK9oRhy9pvBVlmAdCer6hlVjXQlwL9oJEQO4thhSDg2qeNji02xuxlSmDilVKnd9U9xiHqIV-PgktrKq3J2GT1EpcpTvhsew5COQ1h3j8M9IM8KLZpYA0dDp7TejMmfgSiQI8ifZSh_nNLyyqBzYvl1XWxSaDIrnj7UsP3JKUq74kdY5Pg
">
ssl_access_log:
192.168.100.166 - - [15/May/2014:14:44:55 -0700] "GET
/client/console?cmd=access&vm=086b5822-de00-4764-8
Two things to check:
That quick start guide used to have the wrong URL for the system VM
template but it looks like it has been corrected since then. Check your
command line history and see if the template you downloaded was the same as
the one in this section:
http://cloudstack-installation.rea
That quick start guide used to have the wrong URL for the system VM
template but it looks like it has been corrected since then. Check your
command line history and see if the template you downloaded was the same as
the one in this section:
http://cloudstack-installation.readthedocs.org/en/latest
My VMs can reach the rest of our internal network and even the internet but
nothing except the management/hypervisor can reach the VMs. I monitored
eth0 on one of the VMs while I tried to SSH to it from another workstation
and it displayed this:
17:05:29.031584 ARP, Request who-has monitor.cs1clo
I forgot to add ingress rules to the security group. It works now.
On Mon, May 19, 2014 at 5:18 PM, Ian Young wrote:
> My VMs can reach the rest of our internal network and even the internet
> but nothing except the management/hypervisor can reach the VMs. I
> monitored eth0 on o
So I got the console proxy working via HTTPS (by managing my own "
realhostip.com" DNS) last week and everything was working fine. Today, all
of a sudden, the console proxy stopped working again. The browser says,
"Connecting to 192-168-100-159.realhostip.com..." and eventually times out.
I trie
.3 for EL6.
On Tue, May 20, 2014 at 6:21 PM, Ian Young wrote:
> So I got the console proxy working via HTTPS (by managing my own "
> realhostip.com" DNS) last week and everything was working fine. Today,
> all of a sudden, the console proxy stopped working again. The browser
21 20:36:49.682+: 23567: error : virNetSocketReadWire:1370 :
End of file while reading data: Input/output error
On Wed, May 21, 2014 at 10:45 AM, Ian Young wrote:
> I was able to get it working by following these steps:
>
> 1. stop all instances
> 2. service cloudstack-management
stem <http://bugs.centos.org>,
2014-04-07-07:42:04, c6b9.bsys.dev.centos.org)
2014-05-22 17:17:04.362+: 25195: error : qemuMonitorIO:614 : internal
error End of file from monitor
On Wed, May 21, 2014 at 2:07 PM, Ian Young wrote:
> I built and installed a libvirt 1.04 package from the
ys_ioctl+0x81/0xa0
May 22 10:16:07 virthost1 kernel: [] ?
__audit_syscall_exit+0x25e/0x290
May 22 10:16:07 virthost1 kernel: []
system_call_fastpath+0x16/0x1b
On Thu, May 22, 2014 at 10:39 AM, Ian Young wrote:
> The console proxy became unavailable again yesterday afternoon. I could
> SSH i
looks
unusual. Up until then, the error was always name '0'.
On Thu, May 22, 2014 at 11:15 AM, Andrija Panic wrote:
> I have observed this kind of problems ("process blocked for more than xx
> sec...") when I had access with storage - check your disks, smartctl
> etc...
ges:
http://pastebin.com/yDidSbrz
What's wrong with it?
On Thu, May 22, 2014 at 12:55 PM, Ian Young wrote:
> I wonder if something is wrong with the NFS mount. I see this error
> periodically in /var/log/messages even though I have set the Domain in
> /etc/idmapd.conf to the hos
le to create a
deployment for VM[SecondaryStorageVm|s-1-VM]Scope=interface
com.cloud.dc.DataCenter; id=1
On Fri, May 23, 2014 at 10:35 AM, Ian Young wrote:
> I rebooted it and now it's in an even more broken state. It's repeatedly
> trying to stop the console proxy but can&#
Also, is this normal? Every time the server is rebooted, it adds another
record to the mshost table but the "removed" field is always NULL.
http://pastebin.com/q5zDCu4b
On Fri, May 23, 2014 at 10:39 AM, Ian Young wrote:
> The SSVM is stopped. If I try to start it, it co
;;
Now they're both running and I can see the console. There's got to be a
better way to use this system without having to reboot or hack the database
daily.
On Fri, May 23, 2014 at 10:42 AM, Ian Young wrote:
> Also, is this normal? Every time the server is rebooted, it adds anot
10:50 AM, Ian Young wrote:
> I destroyed the SSVM and then tried hacking the database to make
> CloudStack realize that the console proxy is in fact stopped.
>
> mysql> update vm_instance set state='Stopped' where name='v-2-VM';
> mysql> update host set st
My CloudStack 4.3 system is a single server (for the time being, at least).
Since a system VM malfunction is a show-stopper, I would like to host
those on local storage to avoid issues with NFS mounts. I have changed the
value system.vm.use.local.storage to true. I don't see an option for
use.lo
I am trying to set up a server with two NICs as a hypervisor. I would like
to use the two interfaces to separate management and guest traffic, as
recommended by the CloudStack installation guide. This server is connected
to a managed switch, which is connected to a hardware firewall, both of
whic
p separate management
and guest networks in CloudStack?
On Thu, Jul 24, 2014 at 10:56 AM, Ian Young wrote:
> I am trying to set up a server with two NICs as a hypervisor. I would
> like to use the two interfaces to separate management and guest traffic, as
> recommended by the CloudStack instal
>
> Ian, I would imagine that guest traffic can't go out to the net this way.
> Maybe you should swap them. This is only guessing however. What are you
> seeing?
>
> On Fri, Jul 25, 2014 at 2:00 AM, Ian Young wrote:
> > Here's the less verbose version: My hypervis
So if management/storage traffic is on cloudbr0 and guest VMs are on
cloudbr1, would these be the correct settings in agent.properties?
guest.network.device=cloudbr1
private.network.device=cloudbr1
public.network.device=cloudbr1
On Fri, Jul 25, 2014 at 10:11 AM, Ian Young wrote:
> Thank
;
> https://twitter.com/#!/cloudstackguru>
>
> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N
> 4HS
>
>
> On 25 Jul 2014, at 19:18, "Ian Young" iyo...@ratespecial.com>> wrote:
>
> So if management/storage traffic is on cloudbr0 and guest
I've reinstalled CloudStack 4.4 again, configuring the network as follows:
management server:
p4p1 http://pastebin.com/skMXxVtk
hypervisor/storage server:
eth0 http://pastebin.com/LxUxFdpe
eth1 http://pastebin.com/K5si1L4d
cloudbr0 http://pastebin.com/heZGQfVs (management/storage traffic)
cloudbr
loading it. Have you followed the info here:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM,+templates,+Secondary+storage+troubleshooting
> to make sure that the ssvm is actually working properly?
>
>
> On Wed, Jul 30, 2014 at 4:39 PM, Ian Young wrote:
>
late-2014-01-14-master-kvm.qcow2.bz2
On Wed, Jul 30, 2014 at 5:25 PM, Ian Young wrote:
> root@s-2-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh
>
> First DNS server is 192.168.100.2
> PING 192.168.100.2 (192.168.100.2): 48
; then you may also need to:
> service cloud stop && sleep 3 && service cloud start
>
> try the ssvm-check again after that.
>
> My understanding is that this is not a permanent fix, but should get you
> going for now.
>
>
> On Wed, Jul 30, 2014 at 6:00 PM,
>
> On Thu, Jul 31, 2014 at 3:17 AM, Ian Young wrote:
>
> > Yes, that makes the ssvm-check pass all the tests. Thanks. Should I
> > repeat that upgrade with the console proxy?
> >
> >
> > On Wed, Jul 30, 2014 at 6:09 PM, Carlos Reategui
> > wrote:
> > On 19-Dec-2013, at 3:58 PM, Andrei Mikhailovsky wrote:
> >
> > Do you know if there is an easier way? Like via the api calls or the
cloudmonkey command? Or is it currently
> the only way?
> >
> > - Original Message -
> > From: "Jayapal Reddy Uradi" To:
> "
> " Sent:
Yesterday I tried to start an existing instance but it failed. Since it
was basically a brand new installation, I just decided to destroy it and
start over. However, it stayed in an "expunging" state and remains so
today. I cannot create new instances now. The management-server.log shows
numero
I noticed that there are 12 records in the cloud.mshost table, all of which
have an "Up" state. I only have one management server. Should I delete
the other 11 records?
On Thu, Feb 20, 2014 at 10:20 AM, Ian Young wrote:
> Yesterday I tried to start an existing instance but it f
Restarting cloudstack-agent and cloudstack-management made the inactive
management node notice go away but the instance is still stuck in an
"expunging" state. How can I get rid of it?
On Thu, Feb 20, 2014 at 10:55 AM, Ian Young wrote:
> I noticed that there are 12 records in the
Once the VM has been expunged its state in the DB table vm_instance will
> be 'expunging' and there will be a date/time in the 'removed' column (there
> it is again!)
>
> Regards
>
> Geoff Higginbottom
>
> D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +44796816
ri, Feb 21, 2014 at 10:18 AM, Ian Young wrote:
> All the records in the mshost table have a NULL value in the 'removed'
> column (and there are more of them now since I've restarted the service a
> few times). These should have a timestamp instead, right? If so, wha
What about the SSVM's link local address? Can you ping that? It should
begin with 169.254.
On Feb 23, 2014 9:41 PM, "Tejas Gadaria" wrote:
> I have created basic zone, with no security group on CS 4.0.2 and
> hypervisor is xenserver. SSVM and CPVM is running state but I am not able
> to ping SSVM
83 matches
Mail list logo
