On the 19th in the morning I've done several trial, after 9.30 a.m. I don't
remember exactly when.
The day before (when I've installed it) everything was working fine.
2015-06-22 11:49 GMT+02:00 Abhishek Shrivastava abhis...@cloudbyte.com:
Hi Silvia,
One more thing, can you please tell me the
Silvia,
Sorry about that. I missed that.
If you have installed devstack, then you can use the screen sessions for
checking the logs. Following is a link which provides the different
commands for accessing screen sessions and the short cuts to access it.
Yes, and because of that problem only the new Instances are not been
created.
On Mon, Jun 22, 2015 at 3:39 PM, Silvia Fichera fichera@gmail.com
wrote:
The day before I've created several times groups of 5/6 instances and than
deleted. They were correctly launched (except for the allocation
Good morning.
As I told I can't find the folder /var/log/nova.
So which log should I check?
Thanks
2015-06-19 16:23 GMT+02:00 Salvatore Orlando sorla...@nicira.com:
I would check for errors in the nova compute logs.
In some cases I had the same error, but the actual root cause was that the
The day before I've created several times groups of 5/6 instances and than
deleted. They were correctly launched (except for the allocation of the IP
addresses in compute hosts that are not also controller, but I thinks this
was a problem of the VTN configuration with OpenDayLight).
2015-06-22
Hi Jamal,
as I already told previously I don't have nor nova nor neutron in /var/log
because I have Installed openstack using devstack.
I will look for errors in /opt/stack/logs and, if I find somthing I will
post it.
Thanks
2015-06-22 10:16 GMT+02:00 Jamal Arif jam...@plumgrid.com:
You can
Hi Abhishek,
it seems there are some errors in the log you suggested to check.
I've attached it as a G-drive link because it's too big.
Thanks
Silvia
screen-n-cpu.log
https://drive.google.com/file/d/0ByUj7Zpz-6NFR2NvVnJkOHE2Rm8/edit?usp=drive_web
2015-06-22 10:49 GMT+02:00 Abhishek
Nova has different log files, one for the scheduler, one for the conductor,
one for the api-server, and one for the compute agent. If you don't see
anything at all regarding openstack in /var/log, is there a chance you've
enabled syslog logging?
If you're running from devstack, you might have
Hi Silvia,
One more thing, can you please tell me the exact time when you have created
the Instance.
On Mon, Jun 22, 2015 at 3:07 PM, Silvia Fichera fichera@gmail.com
wrote:
Hi Abhishek,
it seems there are some errors in the log you suggested to check.
I've attached it as a G-drive link
Hi all, I have 4 VMs in a server, managed by ESXi. One of these perform as
OVS, one is the Openstack controller and the other two are the compute
hosts. Yesterday I set up Openstack via devstack with Opendaylight
integration for VTN. There was some issue in the VTN configuration but I
was able to
I would check for errors in the nova compute logs.
In some cases I had the same error, but the actual root cause was that the
nova compute log was failing to setup networking for an instance. The
request went back to the scheduler, which selected another compute node,
but failed in the same way
11 matches
Mail list logo
