- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- Re: ISEE and squid
Insight Remote Support
1752679
Members
5291
Online
108789
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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-18-2004 11:30 PM
02-18-2004 11:30 PM
ISEE and squid
hi there,
I was wondering whether more people have configured ISEE to access the internet through a proxy server. I do get the install of ISEE to work (the three default messages in ISEE), but I do get these errors in the mad.log :
190204 12:18:55.711 ERROR,[Comm] comm.cpp:989 NetworkException (10): Socket::rea
d(): recv() timeout [[128.1.50.250]]
190204 12:18:55.711 ERROR,[Comm] sendReceive FAILED
190204 12:18:55.712 ERROR,[Comm] NetworkException (10): Socket::read(): recv() t
imeout [[128.1.50.250]]
HP support told me it ws a problem in my proxy or firewall configuration. Our firewall is managed by a third party supplier, so I want to be sure whether my squid config needs special changes for ISEE to work before I contact our firewall maintainer.
I'm using squid version 2.4 STABLE 6 with authentication module smb_auth. I already disabled the authentication module to make sure it wasn't the problem. That didn't solve the problem.
thanks for your suggestions
Emiel
I was wondering whether more people have configured ISEE to access the internet through a proxy server. I do get the install of ISEE to work (the three default messages in ISEE), but I do get these errors in the mad.log :
190204 12:18:55.711 ERROR,[Comm] comm.cpp:989 NetworkException (10): Socket::rea
d(): recv() timeout [[128.1.50.250]]
190204 12:18:55.711 ERROR,[Comm] sendReceive FAILED
190204 12:18:55.712 ERROR,[Comm] NetworkException (10): Socket::read(): recv() t
imeout [[128.1.50.250]]
HP support told me it ws a problem in my proxy or firewall configuration. Our firewall is managed by a third party supplier, so I want to be sure whether my squid config needs special changes for ISEE to work before I contact our firewall maintainer.
I'm using squid version 2.4 STABLE 6 with authentication module smb_auth. I already disabled the authentication module to make sure it wasn't the problem. That didn't solve the problem.
thanks for your suggestions
Emiel
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2004 11:48 PM
02-21-2004 11:48 PM
Re: ISEE and squid
Hello Emiel,
some messages in the mad.log do not really mean that the transfer does not work. You said that you recieve the three installation incidents. If you recieve all of them the transfer usually works fine. Did you get the updated user interface containing the entitlement fields? If so the connection seams to work fine. Did you install ISEE on a HPUX system. If so, do "a /opt/resmon/bin/send_test_event disk_em". You should see a disk event 103 in the unser interface. The status of this case (click on the incident in the Client UI and you will see the status) should chance to close after a while. If this happens, everything works fine and you don´t need to worry about the messages logged in the mad.log.
If this does not work and you did not recieve the entitlement information, increase the loglevel of the mad or do a trace.
To increasing the loglevel (for all OS):
- /sbin/init.d/hpservices stop
- vi opt/hpservices/etc/motprefs
- in the sction "GlobalSettings" enter "LOG_LEVEL=5"
- /sbin/init.d/hpservices start
-start a transfer with /opt/hpservices/RemoteSupport/bin/iseeHello.sh
- check /var/opt/hpservices/log/mad.log
Don´t forget to remove the entry again an restart the mad.
To trace the system, do the folloing (HPUX only):
-start tracing: /usr/sbin/nettl -tn pduin pduout -tm 10000 -e ns_ls_ip -f /tmp/trace
- start transfer: /opt/hpservices/RemoteSupport/bin/iseeConnectivityTest.sh
- stop tracing:
/usr/sbin/nettl -tf -e all
- format the logfile:
> /usr/sbin/netfmt -c filter -N -l -f /tmp/trace.TRC0 >/tmp/trace.txt0
and if exists:
#> /usr/sbin/netfmt -c filter -N -l -f /tmp/trace.TRC1 >/tmp/trace.txt1
You can also use ethereal the have a look at the trace, ethereal will do the formating for you.
Regards
Fr
some messages in the mad.log do not really mean that the transfer does not work. You said that you recieve the three installation incidents. If you recieve all of them the transfer usually works fine. Did you get the updated user interface containing the entitlement fields? If so the connection seams to work fine. Did you install ISEE on a HPUX system. If so, do "a /opt/resmon/bin/send_test_event disk_em". You should see a disk event 103 in the unser interface. The status of this case (click on the incident in the Client UI and you will see the status) should chance to close after a while. If this happens, everything works fine and you don´t need to worry about the messages logged in the mad.log.
If this does not work and you did not recieve the entitlement information, increase the loglevel of the mad or do a trace.
To increasing the loglevel (for all OS):
- /sbin/init.d/hpservices stop
- vi opt/hpservices/etc/motprefs
- in the sction "GlobalSettings" enter "LOG_LEVEL=5"
- /sbin/init.d/hpservices start
-start a transfer with /opt/hpservices/RemoteSupport/bin/iseeHello.sh
- check /var/opt/hpservices/log/mad.log
Don´t forget to remove the entry again an restart the mad.
To trace the system, do the folloing (HPUX only):
-start tracing: /usr/sbin/nettl -tn pduin pduout -tm 10000 -e ns_ls_ip -f /tmp/trace
- start transfer: /opt/hpservices/RemoteSupport/bin/iseeConnectivityTest.sh
- stop tracing:
/usr/sbin/nettl -tf -e all
- format the logfile:
> /usr/sbin/netfmt -c filter -N -l -f /tmp/trace.TRC0 >/tmp/trace.txt0
and if exists:
#> /usr/sbin/netfmt -c filter -N -l -f /tmp/trace.TRC1 >/tmp/trace.txt1
You can also use ethereal the have a look at the trace, ethereal will do the formating for you.
Regards
Fr
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP