Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+socket\s+24\s+errors\s*$/: 3 ]

Total 3 documents matching your query.

1. [Veritas-bu] socket 24 errors (score: 1)
Author: sixbury AT celeritas DOT com (Sixbury, Dan)
Date: Tue, 5 Jun 2001 10:13:57 -0500
ALL: I am still having problems with our sun server which worked fine when it was a 2.6, but doesn't work now that it is solaris 8. The message I always get is socket 24. I also noticed that it seems
/usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2001-06/msg00066.html (14,168 bytes)

2. [Veritas-bu] socket 24 errors (score: 1)
Author: sdvorak AT veritas DOT com (Steve Dvorak)
Date: Tue, 5 Jun 2001 09:29:19 -0700
Dan, The hosts not equal error is not a big deal, NBU works through a process of reverse look-ups and hostname vs FQDN comparison. It wouldn't even start any data transfer if this were a problem. One
/usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2001-06/msg00068.html (15,257 bytes)

3. [Veritas-bu] socket 24 errors (score: 1)
Author: sixbury AT celeritas DOT com (Sixbury, Dan)
Date: Tue, 5 Jun 2001 11:28:57 -0500
In my case I have the latest Solaris 8 patches, and I actually put the client_read_timeout to be 7200. It was 3600. The only other thing I wonder about is when the system was rebuilt, (long story sho
/usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2001-06/msg00071.html (15,894 bytes)


This search system is powered by Namazu