xenserver 无法连接 xencenter 以及 xapi 有关问题

等待自由 2016-01-14 01:22:52
使用命令 , xe-toolstack-restart 一切正常
—————————————————————

Executing xe-toolstack-restart
Stopping xapi: [ OK ]
Stopping the v6 licensing daemon: [ OK ]
Stopping the memory ballooning daemon: [ OK ]
Stopping perfmon: [ OK ]
Stopping the xenopsd daemon: [ OK ]
Stopping XCP RRDD plugin xcp-rrdd-iostat: [ OK ]
Stopping XCP RRDD plugin xcp-rrdd-squeezed: [ OK ]
Stopping XCP RRDD plugin xcp-rrdd-xenpm: [ OK ]
Stopping the XCP RRDD daemon: [ OK ]
Stopping the XCP networking daemon: [ OK ]
Stopping the fork/exec daemon: [ OK ]
Stopping the multipath alerting daemon: [ OK ]
Starting the multipath alerting daemon: [ OK ]
Starting the fork/exec daemon: [ OK ]
Starting the XCP networking daemon: . [ OK ]
Starting the XCP RRDD daemon: [ OK ]
Starting XCP RRDD plugin xcp-rrdd-iostat: [ OK ]
Starting XCP RRDD plugin xcp-rrdd-squeezed: [ OK ]
Starting XCP RRDD plugin xcp-rrdd-xenpm: [ OK ]
Starting the xenopsd daemon: [ OK ]
Starting perfmon: [ OK ]
Starting the memory ballooning daemon: [ OK ]
Starting the v6 licensing daemon: [ OK ]
Starting xapi: OK [ OK ]
done.

—————————————————————

但 始终 无法启动 xapi
错误 service xapi status 报出 xapi dead but pid file exists ,
查看 log (/var/log/xensource.log)


Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|Setup DB configuration D:075e22083acf|xapi] parsing db config file
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|Setup DB configuration D:075e22083acf|xapi] [/var/xapi/state.db]
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|Setup DB configuration D:075e22083acf|xapi] mode:no_limit
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|Setup DB configuration D:075e22083acf|xapi] format:xml
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|Setup DB configuration D:075e22083acf|xapi] available_this_boot:true
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|Setup DB configuration D:075e22083acf|xapi]
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|server_init D:0b76ed3d3514|startup] task [Manage Dom0]
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|server_init D:0b76ed3d3514|dummytaskhelper] task Manage Dom0 D:da263bd8f0f1 created by task D:0b76ed3d3514
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|Manage Dom0 D:da263bd8f0f1|mscgen] xapi=>xenops [label="VM.exists"];
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|Manage Dom0 D:da263bd8f0f1|xapi] Raised at unixext.ml:275.3-22 -> unixext.ml:277.31-32 -> xmlrpc_client.ml:193.11-47 -> xapi_xenops.ml:1416.7-38 -> pervasiveext.ml:22.2-9
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|Manage Dom0 D:da263bd8f0f1|backtrace] Raised at pervasiveext.ml:26.22-25 -> server_helpers.ml:76.11-23
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|Manage Dom0 D:da263bd8f0f1|dispatcher] Server_helpers.exec exception_handler: Got exception INTERNAL_ERROR: [ Unix.Unix_error(63, "connect", "") ]
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|Manage Dom0 D:da263bd8f0f1|dispatcher] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|Manage Dom0 D:da263bd8f0f1|backtrace] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|Manage Dom0 D:da263bd8f0f1|xapi] Raised at server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|Manage Dom0 D:da263bd8f0f1|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|server_init D:0b76ed3d3514|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9
Jan 14 13:26:52 xenserver-tapacross xapi: [ warn|xenserver-tapacross|0 thread_zero|server_init D:0b76ed3d3514|startup] task [Manage Dom0] exception: Unix.Unix_error(63, "connect", "")
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|server_init D:0b76ed3d3514|xapi] Raised at pervasiveext.ml:26.22-25 -> startup.ml:73.3-119 -> startup.ml:79.14-17 -> list.ml:69.12-15 -> pervasiveext.ml:22.2-9
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|server_init D:0b76ed3d3514|backtrace] Raised at pervasiveext.ml:26.22-25 -> xapi.ml:810.4-1023 -> server_helpers.ml:76.11-23
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|server_init D:0b76ed3d3514|dispatcher] Server_helpers.exec exception_handler: Got exception INTERNAL_ERROR: [ Unix.Unix_error(63, "connect", "") ]
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|server_init D:0b76ed3d3514|dispatcher] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|server_init D:0b76ed3d3514|backtrace] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|server_init D:0b76ed3d3514|xapi] Raised at server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero|server_init D:0b76ed3d3514|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero||xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero||xapi] xapi top-level caught Unix_error: Connection refused, connect,
Jan 14 13:26:52 xenserver-tapacross xapi: [error|xenserver-tapacross|0 thread_zero||xapi] Caught exception at toplevel: 'Unix.Unix_error(63, "connect", "")'
Jan 14 13:26:52 xenserver-tapacross xapi: [debug|xenserver-tapacross|0 thread_zero||xapi] Raised at pervasiveext.ml:26.22-25 -> xapi.ml:809.4-1023 -> xapi.ml:984.96-99 -> xapi.ml:994.4-8 -> xapi.ml:1000.15-16 -> xapi.ml:1006.3-19
Jan 14 13:26:52 xenserver-tapacross xcp-rrdd: [debug|xenserver-tapacross|0 monitor|main|rrdd_stats] xapi stats (n = 2): size: 17643 KiB; rss: 7815 KiB; data: 3943 KiB; stack: 87 KiB
Jan 14 13:26:52 xenserver-tapacross xapi: [ info|xenserver-tapacross|0 thread_zero||watchdog] received exit code 2
Jan 14 13:26:52 xenserver-tapacross xapi: [ info|xenserver-tapacross|0 thread_zero||watchdog] Received 2 bad exits within no-retry-interval. Giving up.
Jan 14 13:26:52 xenserver-tapacross xcp-rrdd: [debug|xenserver-tapacross|0 monitor|main|rrdd_stats] xenopsd stats (n = 0): size: 0 KiB; rss: 0 KiB; data: 0 KiB; stack: 0 KiB
Jan 14 13:26:57 xenserver-tapacross xcp-rrdd: [debug|xenserver-tapacross|0 monitor|main|rrdd_main] do_read: /opt/xensource/bin/tapdisk-cache-stats 05db4dd3-b4c6-85b0-5d34-ccfb8d0c60c7


以下是 怀疑处


[ warn|xenserver-tapacross|0 thread_zero|server_init D:0b76ed3d3514|startup] task [Manage Dom0] exception: Unix.Unix_error(63, “connect”, “”)
[error|xenserver-tapacross|0 thread_zero||xapi] Caught exception at toplevel: ‘Unix.Unix_error(63, “connect”, “”)’


请 高手们 拉一把 兄弟 哦
...全文
1192 3 打赏 收藏 转发到动态 举报
写回复
用AI写文章
3 条回复
切换为时间正序
请发表友善的回复…
发表回复
jxg945 2017-03-20
  • 打赏
  • 举报
回复
请问,问题解决了吗?我现在遇到了一样的问题,因为意外故障导致服务器宕机,再启动就是这样了。请问如何恢复啊? 能指点一下吗 邮箱 18782364@qq.com
amateur_RD 2016-10-04
  • 打赏
  • 举报
回复
问一下,Xenserver安装时,静态IP地址是怎么设置的?依据是什么?我在xenCenter连接时,总是不成功
运维圈子 2016-06-02
  • 打赏
  • 举报
回复
问题解决了吗

19,612

社区成员

发帖
与我相关
我的任务
社区描述
系统使用、管理、维护问题。可以是Ubuntu, Fedora, Unix等等
社区管理员
  • 系统维护与使用区社区
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧