ISEE Setup - http://myUNIX:5060/start.html - Page Not Found

[Basheer_2]

Hello
I Installed ISEE on my B.11.11
ISEEPlatform A.03.90.872 ISEE Platform

grep 5060 /etc/services (not there)
do I have to add it to services.

From PC, When I open up browser and type
http://myUNIX:5060/start.html


I get Page Can't be Displayed.

Any Help
Thanks

[Frauke Denker_2 · Accepted solution]

Hello,
the hpservices are not entered in the /etc/services. There is a startup script at /sbin/init.d/ called hpservices. When you run "/sbin/init.d/hpservices start" and do a netstat -an|grep 5060 you should see a process listening to that port and is you do a ps -ef|grep mad you should see a "mad -u root -g bin".
If this is not the case check the /var/opt/hpservices/log/mad.log for error messages.
Regards
Frauke

[Basheer_2]

Thanks Frauke

started isee

From the ISEE posts, I think you are an EXPERT on isee.

one more Q
when i do http://.....:5060/start.html
it does NOT show New_Installation
it shows others Entitlement_Check and Isee_connectivity

But When I do /opt/hpservices/Remotesupport/config/firstSync

Then it shows up.
Again when I stop/start isee
it goes away and mad.log has these errors

290605 08:20:08.310 ERROR,[Swizzler] Swizzler.cpp:523 | Swizzler caught an EXCEPTION while sending response

290605 08:20:08.316 ERROR,[Swizzler] Swizzler.cpp:524 NetworkException (1): socket.cpp:513 (32) Broken pipe Socket::write(): send
() failed [[10.10.10.123]]

290605 08:25:44.863 ERROR,[Swizzler] Swizzler.cpp:523 | Swizzler caught an EXCEPTION while sending response

290605 08:25:44.863 ERROR,[Swizzler] Swizzler.cpp:524 NetworkException (1): socket.cpp:513 (32) Broken pipe Socket::write(): send
() failed [[10.10.10.123]]

================= Logging initialized at 290605 08:27:22.075 =================
290605 08:30:00.136 ERROR,[VendorProxyServer] Error in handling request: socket.cpp:513 (32) Broken pipe Socket::write(): send()
failed [[10.10.10.123]]
290605 08:30:00.139 ERROR,[WebServer] WebServer exception:
290605 08:30:00.139 ERROR,[WebServer] NetworkException (1): socket.cpp:159 (233) No buffer space available ServerSocket::accept()
failed

290605 08:30:28.280 ERROR,[VendorProxyServer] Error in handling request: socket.cpp:513 (32) Broken pipe Socket::write(): send()
failed [[10.10.10.123]]
290605 08:30:28.286 ERROR,[WebServer] WebServer exception:
290605 08:30:28.287 ERROR,[WebServer] NetworkException (1): socket.cpp:159 (233) No buffer space available ServerSocket::accept()
failed

290605 08:37:23.764 ERROR,[MsgHandler] setQueued for incident in wrong state: id=1715736376.1@goldux, state=QUEUED

[Frauke Denker_2]

Hello,
the error messages in the mad.log look like this incident has not been submitted. I just checked our backend and see only 2 incidents - so I guess this has really not been submitted. The one that I am missing is the entitlement check but I saw that the entitlement infos are transmitted - so it should be ok. I suggest you send a send_test_event dm_memory to make sure the connection betweeen isee and ems works fine. Check that the status of the incidents changes to "send" and in the end to "closed". It seams that the incidents that caused the error messages in the mad.log just changed the status to "queued" - which means that it is not in our database.
Regards
Frauke

[Basheer_2]

Thanks Frauke
when i do the send_test_event dm_memory
I get this in the submitIncident.log

Wed Jul 6 08:36:22 CDT 2005 TRACE: Successfully appended /opt/hpservices/vendors/HP_Services/content/template/client.properties File to Incident Property file
Wed Jul 6 08:36:23 CDT 2005 FAILURE: 134 is an unknown return code. (134); /opt/hpservices/bin/matcli -ds -v HP_Services -p "EMS Event" -m ISEESubmitIncident -t "ISEE 3.00 Event" -d "dm_memory event 103 detected from goldux.goldeagle.com" -s -A propertyFile="/opt/hpservices/tmp/propTempa21504/rstDBAa27599.prop" -A dataFile1="/opt/hpservices/tmp/propTempa21504/rstDBAa27599.txt" -A title1="txt"

[Frauke Denker_2]

For the submitIncident.log I would guess that this incident has not been submitted and I can confirm this from a check in out backend. I see a several incidents from that system but no EMS event. The rstemslistener has detected the EMS event. I can tell wether it shows up in the UI. Maybe you can check with another monitor (f.e. disk_em) and have a look at the UI (does it work now?) wether the event is shown up there. You can click on the incident to see the status.
Regards
Frauke