nova-compute周期性错误日志

今天在查找windows 2012的镜像启动实例时间很长都在转菊花而不能就绪时发现一个周期性错误，不知道会有啥影响：

2015-10-26 10:48:29.522 14878 INFO nova.virt.disk.vfs.api [req-60422de8-311c-4a82-aadc-c9b84c11fdb6 471cbeffcd2b476bb1519c80954893cd 2e17c20866a74e1dbb1f0da46fc555c7 - - -] Unable to import guestfs, falling back to VFSLocalFS

2015-10-26 10:48:34.858 14878 INFO nova.compute.manager [req-b6a8d0c9-f4ab-4e58-8f2f-2a82f25dfac2 - - - - -] [instance: 66fefb1a-8e40-4ed8-b935-58edbe687df5] VM Started (Lifecycle Event)

2015-10-26 10:48:34.985 14878 INFO nova.compute.manager [req-b6a8d0c9-f4ab-4e58-8f2f-2a82f25dfac2 - - - - -] [instance: 66fefb1a-8e40-4ed8-b935-58edbe687df5] During sync_power_state the instance has a pending task (spawning). Skip.

2015-10-26 10:48:34.985 14878 INFO nova.compute.manager [req-b6a8d0c9-f4ab-4e58-8f2f-2a82f25dfac2 - - - - -] [instance: 66fefb1a-8e40-4ed8-b935-58edbe687df5] VM Paused (Lifecycle Event)

2015-10-26 10:48:35.102 14878 INFO nova.compute.manager [req-b6a8d0c9-f4ab-4e58-8f2f-2a82f25dfac2 - - - - -] [instance: 66fefb1a-8e40-4ed8-b935-58edbe687df5] During sync_power_state the instance has a pending task (spawning). Skip.

2015-10-26 10:48:36.783 14878 INFO nova.compute.manager [req-b6a8d0c9-f4ab-4e58-8f2f-2a82f25dfac2 - - - - -] [instance: 66fefb1a-8e40-4ed8-b935-58edbe687df5] VM Resumed (Lifecycle Event)

2015-10-26 10:48:36.788 14878 INFO nova.virt.libvirt.driver [-] [instance: 66fefb1a-8e40-4ed8-b935-58edbe687df5] Instance spawned successfully.

2015-10-26 10:48:36.923 14878 INFO nova.compute.manager [req-b6a8d0c9-f4ab-4e58-8f2f-2a82f25dfac2 - - - - -] [instance: 66fefb1a-8e40-4ed8-b935-58edbe687df5] During sync_power_state the instance has a pending task (spawning). Skip.

2015-10-26 10:48:36.924 14878 INFO nova.compute.manager [req-b6a8d0c9-f4ab-4e58-8f2f-2a82f25dfac2 - - - - -] [instance: 66fefb1a-8e40-4ed8-b935-58edbe687df5] VM Resumed (Lifecycle Event)

2015-10-26 10:48:37.088 14878 INFO nova.compute.manager [-] [instance: 66fefb1a-8e40-4ed8-b935-58edbe687df5] During sync_power_state the instance has a pending task (spawning). Skip.

2015-10-26 08:39:40.607 14878 ERROR nova.compute.manager [req-a98de6d3-c196-4c4e-a713-379a9d258253 - - - - -] [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084] An error occurred while refreshing the network cache.

2015-10-26 08:39:40.607 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084] Traceback (most recent call last):

2015-10-26 08:40:40.648 14878 ERROR nova.compute.manager [req-a98de6d3-c196-4c4e-a713-379a9d258253 - - - - -] [instance: 12a75174-bfb0-4978-9206-2b1f48d10b8f] An error occurred while refreshing the network cache.

2015-10-26 08:40:40.648 14878 TRACE nova.compute.manager [instance: 12a75174-bfb0-4978-9206-2b1f48d10b8f] Traceback (most recent call last):

2015-10-26 09:41:46.628 14878 ERROR nova.compute.manager [req-a98de6d3-c196-4c4e-a713-379a9d258253 - - - - -] [instance: 12a75174-bfb0-4978-9206-2b1f48d10b8f] An error occurred while refreshing the network cache.

2015-10-26 09:41:46.628 14878 TRACE nova.compute.manager [instance: 12a75174-bfb0-4978-9206-2b1f48d10b8f] Traceback (most recent call last):

2015-10-26 09:42:47.693 14878 ERROR nova.compute.manager [req-a98de6d3-c196-4c4e-a713-379a9d258253 - - - - -] [instance: 173cfc60-bf66-4fc0-89a1-aec374879f09] An error occurred while refreshing the network cache.

2015-10-26 09:42:47.693 14878 TRACE nova.compute.manager [instance: 173cfc60-bf66-4fc0-89a1-aec374879f09] Traceback (most recent call last):

2015-10-26 10:44:39.670 14878 ERROR nova.compute.manager [req-a98de6d3-c196-4c4e-a713-379a9d258253 - - - - -] [instance: 05d6b82c-9dbd-43bb-abe7-252fd36bd99e] An error occurred while refreshing the network cache.

2015-10-26 10:44:39.670 14878 TRACE nova.compute.manager [instance: 05d6b82c-9dbd-43bb-abe7-252fd36bd99e] Traceback (most recent call last):

2015-10-26 11:46:37.653 14878 ERROR nova.compute.manager [req-a98de6d3-c196-4c4e-a713-379a9d258253 - - - - -] [instance: 05d6b82c-9dbd-43bb-abe7-252fd36bd99e] An error occurred while refreshing the network cache.

2015-10-26 11:46:37.653 14878 TRACE nova.compute.manager [instance: 05d6b82c-9dbd-43bb-abe7-252fd36bd99e] Traceback (most recent call last):

2015-10-26 12:47:27.094 14878 WARNING nova.compute.manager [req-a98de6d3-c196-4c4e-a713-379a9d258253 - - - - -] While synchronizing instance power states, found 7 instances in the database and 12 instances on the hypervisor.

2015-10-26 12:47:37.609 14878 ERROR nova.compute.manager [req-a98de6d3-c196-4c4e-a713-379a9d258253 - - - - -] [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084] An error occurred while refreshing the network cache.

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084] Traceback (most recent call last):

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 5652, in _heal_instance_info_cache

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]     self._get_instance_nw_info(context, instance)

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1369, in _get_instance_nw_info

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]     return self.network_api.get_instance_nw_info(context, instance)

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]   File "/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 747, in get_instance_nw_info

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]     preexisting_port_ids)

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]   File "/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 763, in _get_instance_nw_info

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]     preexisting_port_ids)

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]   File "/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 1519, in _build_network_info_model

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]     data = client.list_ports(**search_opts)

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]   File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 99, in with_params

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]     ret = self.function(instance, *args, **kwargs)

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]   File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 497, in list_ports

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]     **_params)

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]   File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 304, in list

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]     for r in self._pagination(collection, path, **params):

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]   File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 317, in _pagination

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]     res = self.get(path, params=params)

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]   File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 290, in get

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]     headers=headers, params=params)

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]   File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 267, in retry_request

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]     headers=headers, params=params)

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]   File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 208, in do_request

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]     self._handle_fault_response(status_code, replybody)

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]   File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 182, in _handle_fault_response

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]     exception_handler_v20(status_code, des_error_body)

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]   File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 80, in exception_handler_v20

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]     message=message)

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084] NeutronClientException: Authentication required

2015-10-26 12:47:37.609 14878 TRACE nova.compute.manager [instance: 295353b9-79b2-42f7-bc43-b08b4ee17084]

2015-10-26 13:50:32.653 14878 ERROR nova.compute.manager [req-a98de6d3-c196-4c4e-a713-379a9d258253 - - - - -] [instance: 66fefb1a-8e40-4ed8-b935-58edbe687df5] An error occurred while refreshing the network cache.

2015-10-26 13:50:32.653 14878 TRACE nova.compute.manager [instance: 66fefb1a-8e40-4ed8-b935-58edbe687df5] Traceback (most recent call last):

时间： 2024-10-14 16:57:40

nova-compute周期性错误日志的相关文章

【工具推荐】ELMAH——可插拔错误日志工具

ELMAH 是 Error Logging Modules and Handlers for ASP.NET 的缩写.ELMAH可以让你记录下你的网站发生的任何一个错误,在将来,你可以重新检查这些错误.你可以从ELMAH项目的官方网站免费下载ELMAH:http://code.google.com/p/elmah/. ELMAH既支持ASP.NET Web Forms 又支持 ASP.NET MVC.你可以对ELMAH进行配置来存储各种不同的错误(XML文件,事件日志,Access数据库,SQL

nginx日志及错误日志详解

nginx错误日志信息介绍 配置记录nginx的错误信息是调试nginx服务的重要手段,属于核心功能模块(ngx_core_module)的参数,该参数名字为error_log,可以放在Main区块中全局配置,也可以放置不同的虚拟主机中单独记录虚拟主机的错误信息. error_log的语法格式及参数语法说明如下: error_log    file    level; 关键字        日志文件    错误日志级别 其中,关键字error_log不能改变,日志文件可以指定任意存放日志的目录,

mysql错误日志

1.错误日志路径查询 show variables like '%log_error%'; log_error记录了错误日志路径. 2.告警日志设置 show variables like '%log_warnings%'; log_warnings:0表示不记录警告信息,1表示记录警告信息到错误日志,大于1表示"失败的连接"的信息和创建新连接时"拒绝访问"类的错误信息也会被记录到错误日志中.

MS SQL 监控错误日志的告警信息

SQL Server的错误消息(Error Message)按照消息的严重级别一共划分25个等级,级别越高,表示严重性也越高.但是如果你统计sys.messages,你会发现,实际上只有16(SQL SERVER 2008/2012)或17个(SQL SERVER 2005)个级别.猜测应该是一些留作扩展用,一些留作用户自定义错误消息的级别. sys.messages中有个字段is_event_logged,取值为1时表示出现错误时将消息记入事件日志. 对于 message_id 中的所有消息语

Nginx错误日志整理

Nginx错误日志说明 错误日志类型 类型1: upstream timed out 类型2: connect() failed 类型3: no live upstreams 类型4: upstream prematurely closed connection 类型5: 104: Connection reset by peer 类型6: client intended to send too large body 类型7: upstream sent no valid HTTP/1.0 he

C# 记录错误日志

程序的错误日志如何记录下来? 可以在遇到异常时,Catch异常,然后把异常的信息输出到txt文件中即可 /// <summary> /// 错误日志 /// </summary> public class LogHelper { private static object lockFlag = new object(); private static string LOG_FILE_PATH = AppDomain.CurrentDomain.BaseDirectory + &qu

Hadoop错误日志

1.错误日志:Directory /tmp/hadoop-root/dfs/name is in an inconsistent state: storage directory does not exist or is not accessible. 错误原因:在Linux下Hadoop等的各种数据默认保存在 /tmp目录下.当重启系统后 /tmp目录中的数据信息被清除,导致Hadoop启动失败.确定目录 /tmp/hadoop-root/dfs/name是否存在解决方案: 使用命令bin/h

记录C#错误日志工具

在编程过程中,我们经常会用try...catch处理可能出错的代码块.如果程序出现错误,则直接show出错误信息. 当然,大型的系统都有错误日志处理模块,用数据库记录错误日志信息,有相应的写入错误日志和读取操作日志的功能,功能强大,实现起来肯定也是相当的复杂. 可有时我们只是想方便的查看错误日志信息,但又不想带来复杂的代码实现.鱼和熊掌都想要?好吧,我来满足你. 1.我们需要把项目的目标框架设置为.Net Framework 4.0: 2.找到项目的代码生成路径,比如我的是bin\Debug\,

MySQL 错误日志(Error Log)

同大多数关系型数据库一样,日志文件是MySQL数据库的重要组成部分.MySQL有几种不同的日志文件,通常包括错误日志文件,二进制日志,通用日志,慢查询日志,等等.这些日志可以帮助我们定义mysqld内部发生的事情,数据库性能故障,记录数据的变更历史,用户恢复数据库等等.本文主要描述错误日志文件. 1.MySQL日志文件系统的组成   a.错误日志:记录启动.运行或停止mysqld时出现的问题.   b.通用日志:记录建立的客户端连接和执行的语句.   c.更新日志:记录更改数据的语句.该日志在M