- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- Re: ISEE Client installation V. A.03.95 - no Entit...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-02-2006 03:50 AM
тАО02-02-2006 03:50 AM
ISEE Client installation V. A.03.95 - no Entitlement available
020206 16:02:26.098 ERROR,[Swizzler] Swizzler.cpp:523 | Swizzler caught an EXCEPTION while sending r
esponse
020206 16:02:26.099 ERROR,[Swizzler] Swizzler.cpp:524 NetworkException (1): socket.cpp:513 (32) Brok
en pipe Socket::write(): send() failed [[10.105.214.142]]
020206 16:02:26.660 ERROR,[Swizzler] Swizzler.cpp:523 | Swizzler caught an EXCEPTION while sending r
esponse
020206 16:02:26.660 ERROR,[Swizzler] Swizzler.cpp:524 NetworkException (1): socket.cpp:513 (32) Brok
en pipe Socket::write(): send() failed [[10.105.214.142]]
020206 16:03:38.538 ERROR,[Synchronize] failed while downloading content bundle: Socket::read(): rec
v() timeout [[10.128.3.155]]
020206 16:03:39.091 ERROR,[Swizzler] Swizzler.cpp:523 | Swizzler caught an EXCEPTION while sending r
esponse
020206 16:03:39.091 ERROR,[Swizzler] Swizzler.cpp:524 NetworkException (1): socket.cpp:513 (32) Brok
en pipe Socket::write(): send() failed [[10.105.214.142]]
020206 16:04:50.941 ERROR,[Synchronize] failed while downloading content bundle: Socket::read(): rec
v() timeout [[10.128.3.155]]
020206 16:06:03.340 ERROR,[Synchronize] failed while downloading content bundle: Socket::read(): rec
v() timeout [[10.128.3.155]]
020206 16:06:03.341 ERROR,[Swizzler] Synchronize with server failed: Socket::read(): recv() timeout
[[10.128.3.155]]
020206 16:13:30.057 ERROR,[Swizzler] Swizzler.cpp:523 | Swizzler caught an EXCEPTION while sending r
esponse
020206 16:13:30.057 ERROR,[Swizzler] Swizzler.cpp:524 NetworkException (1): socket.cpp:513 (32) Brok
en pipe Socket::write(): send() failed [[10.105.214.142]]
What can be the cause?
Thanks
Markus
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-02-2006 08:13 AM
тАО02-02-2006 08:13 AM
Re: ISEE Client installation V. A.03.95 - no Entitlement available
We would need to know the OS of your Server, the ISEE version you are installing.
We also need to know if you already had Firewall port 80 opened.
Please include a copy of motprefs file on your reply.
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-02-2006 07:32 PM
тАО02-02-2006 07:32 PM
Re: ISEE Client installation V. A.03.95 - no Entitlement available
OS Version is HPUX 11.11
ISEE Client: A.03.95
Yes Port 8080 is opened on Proxy
Thanks
Markus
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-03-2006 12:56 AM
тАО02-03-2006 12:56 AM
Re: ISEE Client installation V. A.03.95 - no Entitlement available
You have Advanced Configuration and your HP-UX Servers are communicating with your SPOP eustutmgfisspop1.
Is this SPOP in a DMZ or in the same network as your HP-UX Servers?
Can you try from the non-working Server:
1. nslookup eustutmgfisspop1?
2. telnet eustutmgfisspop1 80
Do you have HP-UX Servers that worked fine?
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-03-2006 01:18 AM
тАО02-03-2006 01:18 AM
Re: ISEE Client installation V. A.03.95 - no Entitlement available
SPOP is in the same network segment than Client. (not in DMZ)
nslookup and telnet works fine:
hpuxeu9a:[opsroot]/u01/ltd/opsroot
[1]> nslookup eustutmgfisspop1
Using /etc/hosts on: hpuxeu9a
looking up FILES
Trying DNS
Name: eustutmgfisspop1.ey.com
Address: 10.128.3.155
hpuxeu9a:[opsroot]/u01/ltd/opsroot
[2]> telnet eustutmgfisspop1 80
Trying...
Connected to eustutmgfisspop1.ey.com.
Escape character is '^]'.
We have two HPUX boxes on which the client works fine. But had to do the installation twice first then the Entitlement infos were viewable
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-03-2006 01:26 AM
тАО02-03-2006 01:26 AM
Re: ISEE Client installation V. A.03.95 - no Entitlement available
Very interesting, can you look at /opt/hpservices/log/mad.log?
If you see time-out error connecting to the SPOP, please check for duplex setting on both ends (HP-UX and SPOP), the setting must match the speed of the switch/hub.
Send me the mad.log too.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-06-2006 01:24 AM
тАО02-06-2006 01:24 AM
Re: ISEE Client installation V. A.03.95 - no Entitlement available
yes, you are right. I saw a lot of timeouts in mad.log. After reconfiguring the SPOP NIC to FD it works fine.
Thanks for your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-06-2006 01:26 AM
тАО02-06-2006 01:26 AM