Thanks, Wilder
So, I'm not that familiar looking through those log files, but I
copy/pasted what seemed like relevant parts below.
Would you be able to take a quick look and see if anything sticks out
(there are some failure messages, but it's not clear to me why)?
Thanks!
This is part of my Xe
Hi Mike,
I’m actually using the same VHD as you and it is just working fine.
Have you checked the /var/log/SMlog on your xen host?
Also, if you can check the logs of the SSVM under /var/log/cloud.log and see
what it says concerning the communication between the SSVM and the agent would
be nice
That's what I'm thinking.
On Thu, Apr 30, 2015 at 1:04 AM, Marcus wrote:
> So it could be a systemvm template change, perhaps?
>
> On Wed, Apr 29, 2015 at 11:13 PM, Mike Tutkowski
> wrote:
> > I logged into the VR, noticed the IP addresses weren't showing up as
> > expected when I ran ifconfig,
So it could be a systemvm template change, perhaps?
On Wed, Apr 29, 2015 at 11:13 PM, Mike Tutkowski
wrote:
> I logged into the VR, noticed the IP addresses weren't showing up as
> expected when I ran ifconfig, then I restarted networking services, which
> set the IP addresses up properly.
>
> On
I logged into the VR, noticed the IP addresses weren't showing up as
expected when I ran ifconfig, then I restarted networking services, which
set the IP addresses up properly.
On Thu, Apr 30, 2015 at 12:08 AM, Marcus wrote:
> Logged into the router?
>
>
> On Wed, Apr 29, 2015 at 10:58 PM, Mike
Logged into the router?
On Wed, Apr 29, 2015 at 10:58 PM, Mike Tutkowski
wrote:
> Well, I seem to be able to reproduce this every time I start up the VR in
> my environment.
>
> I'm not sure, though, if this is only my environment or if other people who
> are making brand new CS clouds with 4.6
Well, I seem to be able to reproduce this every time I start up the VR in
my environment.
I'm not sure, though, if this is only my environment or if other people who
are making brand new CS clouds with 4.6 also see this issue.
On Wed, Apr 29, 2015 at 11:50 PM, Daan Hoogland
wrote:
> Op do 30 ap
Op do 30 apr. 2015 om 07:26 schreef Mike Tutkowski <
mike.tutkow...@solidfire.com>:
...
> Should I open a ticket for this?
>
if you can reproduce, please.
Thanks for your comments, everyone.
So, it looks like I got it to work. I logged in and then immediately
restarted networking services.
/etc/init.d/networking restart
Once I did that, I ran ifconfig and saw that the VR had the necessary IP
addresses and I was able to successfully ping the CS MS.
Log into the vm and look at the /var/log/cloud.log. It might be that
the agent isn't starting (e.g. you require non-oss build but have oss
build, and agent fails to find PremiumSecondaryStorageResource or
whatever)
On Wed, Apr 29, 2015 at 12:36 PM, Mike Tutkowski
wrote:
> Hey Wilder,
>
> Thanks f
Hey Wilder,
Thanks for the reply.
I was wondering if you could point me to the system VM template that you
used?
This is what I used and am having trouble with:
http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master
Hi Mike,
I just built, deploy and created isolated network, VPC and VMS using latest
master (4.6.0). I put some screenshots on imgur: http://imgur.com/a/OmSyy.
In addition, I created FW + PF rules and SSH (using the routers’ pub ip) to the
VM:
[wrodrigues@mct-wrodrigues ~]$ ssh root@192.168.22
Anything in /var/log/cloud.log?
--
Erik
On Tue, Apr 28, 2015 at 11:58 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> Unfortunately I'm not able to make out any errors on the console.
>
> Is there something within the VM's OS that I can look at to debug this?
>
> I see that SSVM and
Unfortunately I'm not able to make out any errors on the console.
Is there something within the VM's OS that I can look at to debug this?
I see that SSVM and CPVM have IP addresses, but the VR does not.
Any hints would be great as unfortunately I had to postpone a CloudStack
demo for a potential
One of the reasons for VR not to come up is, once CS creates VR on
hypervisor, it does a ping on VR's management interface for centain no.of
of times. If it does not receive any response then it will shut down the
VR.
So when VR is coming up check its console and see any network issues.
On Tue, A
Huh...it doesn't work on KVM either (this is on Ubuntu 14.04). The failure
is a bit different, though. In this case, the SSVM stays in the Running
state, but the agent doesn't seem to ever come up.
Oh well...I guess I'll try ESXi later.
On Mon, Apr 27, 2015 at 11:45 PM, Mike Tutkowski <
mike.tutk
Thanks for the message, Abhi.
I went ahead and deleted the host tag from each of my XenServer hosts (it's
a new environment, so I only had one host tag per host). I then performed a
force reconnect on each host.
Unfortunately, I still seem to be encountering the same issue (even after
destroying
Had similar problem where SSVM and CPVM came up but not the VR.
In my case I traced it to systemvm.iso not getting updated on XenServer, due to
the old host-tag.
On deleting the host tag the MS was able to copy the systemvm.iso to Xen and
things were fine after that.
-abhi
> On 28-Apr-2015, at
Hi,
Tonight I tried to re-create a cloud from scratch and made use of the
following system template:
http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-4.6.0-xen.vhd.bz2
My SSVM and CPVM get IP addresses and seem
19 matches
Mail list logo
