Konfigurációkezelés gyakorlat-CIM objektum lekérdezés WS-Management-el

+1 vote
asked Apr 2, 2013 in IRF tantárgy by anonymous  
edited Apr 2, 2013

A kiadott gyakorlati anyagban a 14.oldalon WS-Management-el próbálok lekérni távoli gépről CIM objektumot a következő utasítással:

wsman -h localhost -u meres -p LaborImage enumerate \
 'http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_Processor' 

De bárhogy is próbálom mindig Couldn't connect to server választ kapok vissza xml-ben.
Előtte lefuttattam a

wsman --hostname 192.168.131.131 -u meres -p LaborImage identify 

parancsot, ami rendesen működik is. Itt nem mondja, hogy nem tud csatlakozni.
A debug módban futó openwsmand a következőt adja:

Apr  2 20:39:47 [1464] 192.168.131.131:5985 connected (socket 6)
Apr  2 20:39:47 [1464] Conn 6: parsing request: [POST /wsman HTTP/1.1
Host: 192.168.131.131:5985
Accept: */*
Content-Type: application/soap+xml;charset=UTF-8
User-Agent: WS-Management for all
Content-Length: 876

]
Apr  2 20:39:47 [1464] parsing headers (len 149): [Host: 192.168.131.131:5985
Accept: */*
Content-Type: application/soap+xml;charset=UTF-8
User-Agent: WS-Management for all
Content-Length: 876

]
Apr  2 20:39:47 [1464] decide_what_to_do: [/wsman]
Apr  2 20:39:47 [1464] is_alias: aliases []
Apr  2 20:39:47 [1464] 6 (null) stopped. 0 of content data, 150 now in a buffer
Apr  2 20:39:47 [1464] Disconnecting 6 ()
Apr  2 20:39:47 [1464] Sock 6 accepted
Apr  2 20:39:47 [1464] Active sockets: 0, Thread Number: 0
Apr  2 20:39:47 [1464] 192.168.131.131:5985 connected (socket 6)
Apr  2 20:39:48 [1464] Conn 6: parsing request: [POST /wsman HTTP/1.1
Authorization: Basic bWVyZXM6TGFib3JJbWFnZQ==
Host: 192.168.131.131:5985
Accept: */*
Content-Type: application/soap+xml;charset=UTF-8
User-Agent: WS-Management for all
Content-Length: 876

]
Apr  2 20:39:48 [1464] parsing headers (len 196): [Authorization: Basic bWVyZXM6TGFib3JJbWFnZQ==
Host: 192.168.131.131:5985
Accept: */*
Content-Type: application/soap+xml;charset=UTF-8
User-Agent: WS-Management for all
Content-Length: 876

]
Apr  2 20:39:48 [1464] decide_what_to_do: [/wsman]
Apr  2 20:39:48 [1464] is_alias: aliases []
Apr  2 20:39:48 [1464] Done reading request
Apr  2 20:39:48 [1464] Inbound call...
Apr  2 20:39:48 [1464] uri: http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_Processor, action: http://schemas.xmlsoap.org/ws/2004/09/enumeration/Enumerate
Apr  2 20:39:48 [1464] namespace: http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xsd
Apr  2 20:39:48 [1464] namespace: http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2
Apr  2 20:39:48 [1464] Processing Filters: inbound
Apr  2 20:39:48 [1464] Checking Message ID: uuid:0fd28374-d965-1965-8002-eb6c8b290c00
Apr  2 20:39:48 [1464] namespace: http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xsd
Apr  2 20:39:48 [1464] namespace: http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2
Apr  2 20:39:48 [1464] Release endpoint: 0xb6bee7b0
Apr  2 20:39:48 [1464] No wsen:Expires
Apr  2 20:39:48 [1464] CIM Enumeration
Apr  2 20:39:48 [1464] username: meres, password: XXXXX
Apr  2 20:39:48 [1464] Connecting using sfcc XML frontend
Apr  2 20:39:48 [1464] new cimclient: 0xb52149a0
Apr  2 20:39:48 [1464] new cimclient: 1
Apr  2 20:39:48 [1464] no SelectorSet defined
Apr  2 20:39:48 [1464] method or action: Enumerate
Apr  2 20:39:48 [1464] method or action: Enumerate
Apr  2 20:39:48 [1464] enumInstances() rc=1, msg=Couldn't connect to server
Apr  2 20:39:48 [1464] *** CMCIClient enumInstances() failed
Apr  2 20:39:48 [1464] cimclient destroyed
Apr  2 20:39:48 [1464] enumeration fault
Apr  2 20:39:48 [1464] destroy enuminfo
Apr  2 20:39:48 [1464] Processing Filters: outbound
Apr  2 20:39:48 [1464] destroy op
Apr  2 20:39:48 [1464] Inbound call completed
Apr  2 20:39:48 [1464] Response status=500 (Internal Error)
Apr  2 20:39:48 [1464] 6 (null) stopped. 920 of content data, 920 now in a buffer
Apr  2 20:39:48 [1464] Disconnecting 6 ()

Köszönöm a segítséget előre is!

Ugyanezt a hibát adja akkor is, ha a localhoston futót akarom elérni.

commented Apr 3, 2013 by anonymous  
Megoldódott a probléma.
Nem futott az sfcb.
(sudo /etc/init.d/sfcb start)

1 Answer

0 votes
answered Apr 3, 2013 by micskeiz (2,873 points)  

"Megoldódott a probléma.
Nem futott az sfcb.
(sudo /etc/init.d/sfcb start)"

...