OpenNode Support Forum
Welcome,
Guest
. Please
login
or
register
.
Did you miss your
activation email
?
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
News:
OpenNode Support Forum is now active!
Home
Help
Login
Register
OpenNode Support Forum
»
OpenNode Console (ONC)
»
Bugs
»
System page
« previous
next »
Print
Pages: [
1
]
Author
Topic: System page (Read 2411 times)
alltheway
Newbie
Posts: 9
System page
«
on:
January 23, 2011, 06:56:14 PM »
I have a 2 node setup running latest beta. Both nodes registered in funcman.
I can only see system information for the node where oms is not running (I can see the other hosts info after a migration)
This is the debug info from funcman:
000095 qx.core.Init: Load runtime: 95ms
000144 qx.core.Init: Main runtime: 49ms
000223 qx.core.Init: Finalize runtime: 79ms
069511 funcman.servlet.RpcReqStore[2824]: failed response -Local error 2: Aborted
069511 funcman.module_1.tab_status.Body_listvm[505]: vm fail
116761 qx.io.remote.RequestQueue[111]: Timeout: transport 2792
116761 qx.io.remote.RequestQueue[111]: 60084ms > 60000ms
116761 Timeout: implementation 2793
116762 qx.data.model.bandwidth"cpu"df"iowait"kernel"memory"network"osrelease"swap"uptime[2791]: TIMEOUT OCCURRED
116762 funcman.servlet.RpcReqStore[2788]: failed response -Local error 1: Local time-out expired
116762 funcman.servlet.RpcReqStore[2788]: Timeout occured
116764 qx.io.remote.RequestQueue[111]: Timeout: transport 2784
116764 qx.io.remote.RequestQueue[111]: 60096ms > 60000ms
116764 Timeout: implementation 2785
116765 qx.data.model.client"result[2783]: TIMEOUT OCCURRED
116765 funcman.servlet.RpcReqStore[2780]: failed response -Local error 1: Local time-out expired
116765 funcman.servlet.RpcReqStore[2780]: Timeout occured
119261 qx.io.remote.RequestQueue[111]: Timeout: transport 2820
119261 qx.io.remote.RequestQueue[111]: 60284ms > 60000ms
119261 Timeout: implementation 2821
119261 qx.data.model.result"type[2819]: TIMEOUT OCCURRED
119261 funcman.servlet.RpcReqStore[2816]: failed response -Local error 1: Local time-out expired
119261 funcman.servlet.RpcReqStore[2816]: Timeout occured
122042 qx.io.remote.RequestQueue[111]: Request qx.io.remote.Request[2922] handler _oncompleted threw an error: No event could be found for the property: bandwidth Stack Trace:
122042 funcman.servlet.RpcReqStore[2919]: failed response -Local error 2: Aborted
158578 qx.io.remote.RequestQueue[111]: Request qx.io.remote.Request[3639] handler _oncompleted threw an error: No event could be found for the property: bandwidth Stack Trace:
158580 funcman.servlet.RpcReqStore[3458]: failed response -Local error 2: Aborted
171181 qx.io.remote.RequestQueue[111]: Request qx.io.remote.Request[3661] handler _oncompleted threw an error: No event could be found for the property: network Stack Trace:
171181 funcman.servlet.RpcReqStore[3658]: failed response -Local error 2: Aborted
Logged
Running 2 x Opennode-1.1-22 and Opennode-oms-1.0-15
on my laptop for testing...
Final setup 2x IBM x3650
frame
activesys
Newbie
Posts: 29
Re: System page
«
Reply #1 on:
January 25, 2011, 11:06:55 PM »
Please update opennode rpm to latest opennode-1.1-22 from opennode-test repo - see if it makes the difference.
Logged
alltheway
Newbie
Posts: 9
Re: System page
«
Reply #2 on:
January 30, 2011, 08:43:37 PM »
I tried to update to latest version.
cpu, men, net and disk in the upper panel in the status page is ok.
Node name and ip address always show the node where oms is not running.
System page still suffers from wrong information.
Logged
Running 2 x Opennode-1.1-22 and Opennode-oms-1.0-15
on my laptop for testing...
Final setup 2x IBM x3650
activesys
Administrator
Full Member
Posts: 172
Re: System page
«
Reply #3 on:
February 16, 2011, 11:55:48 PM »
Seems that funcman can't get updated data from OMS RPC for some reason.
Please restart func on both hardware nodes: service funcd restart
Then reset OMS service in management OVZ VM: service opennode-oms restart
Log again into funcman - see if it makes any difference.
Sometimes func daemon will hang and needs reset on node.
One way to test would be also using func shell directly from OMS.
You can try some standard func stuff or the following:
#list ovz VM IDs and status
func node_hostname call ovzvirt state
Logged
activesys
Administrator
Full Member
Posts: 172
Re: System page
«
Reply #4 on:
February 16, 2011, 11:57:07 PM »
Also - for debugging OMS RPC you might test it with your webbrowser directly - by using RPC API calls documented here:
http://opennode.activesys.org/documentation/api-documentation/
Logged
Print
Pages: [
1
]
« previous
next »
OpenNode Support Forum
»
OpenNode Console (ONC)
»
Bugs
»
System page