www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryon Dun <nam...@northants.fire-uk.org>
Subject config/4638: Apache will only work in "single user" access with Dual Processor fitted and live
Date Wed, 23 Jun 1999 12:57:09 GMT

>Number:         4638
>Category:       config
>Synopsis:       Apache will only work in "single user" access with Dual Processor fitted
and live
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Jun 23 07:10:00 PDT 1999
>Originator:     nampIT@northants.fire-uk.org
>Release:        1.3b3
Unix 7Mplus 11.2 on Fujitsu K420 SPARC with Delta 3 applied, cc compiler,
320 Mb of memory and a Dual 75Mhz SPARC processor,
Apache is compiled configured as Unixware 2.1.2 as NX7MPlus is not shown.
Prior to upgrading the K420 from 64MB and single 50Mhz SPARC processor, 
Apache worked well, with little processing required and many users online.

After upgrading to 320Mb memory and replacing the processor with
Dual 75Mhz SPARC processors, (and recompiling the Kernel) Apache refuses to 
work in more than single access mode, (i.e. only one browser may access 
it a time).

However, I have identified that by closing one processor (psradm -f 1), and 
allowing only processor 0 to run, Apache runs normally with full multi access)

I have checked that sufficient TCP sockets are configured (512 with only 185 
on average in use) as the error_log (Apache) was indicating SO_SNDBUF / SO_RCVBUF

The problem appears to be that Apache can't run with dual processors (unless 
there is a configuration solution ?? - not apparent)


Not at present, the only option appears to be to turn OFF the second processor,
which is counter-productive, as it was added to increase performance
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

View raw message