| Title: | SEAL |
| Moderator: | GALVIA::SMITH |
| Created: | Mon Mar 21 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1989 |
| Total number of notes: | 8209 |
I have been tortured for several weeks on the following AVFU's wwwproxy problem which I ever posted to this note a week ago: The customer complainted that, after opening the wwwproxy access, the proxy halted due to being unable to fork new wwwproxy processes. Then I tried to modified the system parameter "maxuser" from default 64 to 256, but this action made no solution. Several days later, I tried again to modified the system parameter "uprc" from default 64 to 1024 - this action worked - the proxy no more halted, but the new www clients could not access the proxy due to timeout after the gatekeeper already had 390 active processes - the total number of activce processes seemed to be not over the max uprc limit. For the newest case, I have not much idea for it. Any guide for it ? -Arthur- [Posted by WWW Notes gateway]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1818.1 | questions | EEMELI::EINAMO | Thu Feb 27 1997 01:49 | 17 | |
Some size issuses 1. Cpu / mem type 2. Customer size ( how many www-browsers) 3. internet connection speed 4. firewall version questions. is your DNS working ? is there errors on proxy error log ? How fast does the proxy work for those who can get it work MARKO | |||||
| 1818.2 | My customer's firewall machine configuration | NETRIX::"[email protected]" | Arthur Lin | Thu Mar 06 1997 22:03 | 37 |
About the problem I mentioned, the following is my customer's firewall related
configuration:
------------------------------------------------------------------------------
-
H/W: AlphaStation 4/255 with 256M DRAM
S/W: Digital Firewall for UNIX V2.0 on Digital UNIX
V3.2D
Internet Connection Speed: T1
Internal Sites: as much as 6000 (BUT only about one hundred of them
are frequent users)
DNS Setting: OK
------------------------------------------------------------------------------
-
Note: 1. I dodn't think the problem is related to the hardware or network
bandwidth
because there was no such problem after the customer replacing our
wwwproxy
with an existed proxy server.
2. I don't either think the problem can be solve by just tuning the
system
parameters, such as "maxusers" or "maxuprc", because I have tried and
got
no progress.
3. I guess that there is a parameter in wwwproxy.conf to limit the
maximum www
conection because there IS similar parameter in Netscape or other
vender's
proxy server- if so, the problem I mentioned can be solved. But I
dodn't
know how to tune such a parameter.
-Arthur-
[Posted by WWW Notes gateway]
| |||||