DX NetOps Manager

Expand all | Collapse all

MAXRequest workers in httpd of ehealth

Jump to Best Answer
  • 1.  MAXRequest workers in httpd of ehealth

    Posted 06-15-2017 03:28 PM

    Hi We are running ehealth 6.3.2 on solaris 10.

    When too many https sessions are opened then the webconsole of the same hang in ehealht..

    and below errors was found on the NH_HOME/web/http-errors file.

    [Thu Jun 15 16:17:10.040172 2017] [access_compat:error] [pid 4782:tid 26] [client 23.99.122.165:1049] AH01797: client denied by server configuration: /concord/ehealth63/web/output/
    [Thu Jun 15 21:26:40.801561 2017] [auth_basic:error] [pid 15583:tid 22] [client 78.100.159.42:60860] AH01617: user esc: authentication failure for "/web/frames/": Password Mismatch, referer: http://ehealth.qtelsla.net.qa:8081/bin/welcome.sh
    [Thu Jun 15 21:27:39.580368 2017] [mpm_event:error] [pid 4748:tid 1] AH00484: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers

     

    ash-3.2$ cd bin
    -bash-3.2$ nhHttpd stop
    Stopping eHealth Web Server (PID=4748) . . .
    Stopping eHealth Web Server (PID=15547) . . .
    Stopping eHealth Web Server (PID=15367) . . .
    Stopping eHealth Web Server (PID=15313) . . .
    Stopping eHealth Web Server (PID=15583) . . .
    Stopping eHealth Web Server (PID=15328) . . .
    Stopping eHealth Web Server (PID=4763) . . .
    Stopping eHealth Web Server (PID=15495) . . .
    Stopping eHealth Web Server (PID=15358) . . .
    Stopping eHealth Web Server (PID=4782) . . .
    Stopping eHealth Web Server (PID=15511) . . .
    Stopping eHealth Web Server (PID=15475) . . .
    Stopping eHealth Web Server (PID=15366) . . .
    Stopping eHealth Web Server (PID=15351) . . .
    Stopping eHealth Web Server (PID=4767) . . .
    Stopping eHealth Web Server (PID=4765) . . .
    Stopping eHealth Web Server (PID=4764) . . .
    Stopping eHealth Tomcat Server . . .
    Killing eHealth Tomcat Server (PID=4761) . . .
    -bash-3.2$ nhHttpd start
    Starting eHealth Web Server . . .

     

    Pleaes let me know how ot increase the same..

     

    Regards

    Thiru



  • 2.  Re: MAXRequest workers in httpd of ehealth
    Best Answer

    Posted 06-15-2017 04:36 PM

    Hello Thiru,

     

    You can add the maxRequestWorkers within the Custom Basic section of the httpd.tpl file. This file is used as an information source and is used to recreate the httpd.conf file.

     

    Per past cases reporting that message you can try a value of 1024 but you should keep an eye on the system to check if the hardware is able to handle it without performance issues.

     

    Here is a KB article with more info on making changes like this:

    Customizations to httpd.conf file are removed after configuration changes (Legacy KB ID CNC TS34911 ) 

     

    As the KB references all the new lines or modified values should be placed between the “# Custom Protect Section" lines of the httpd.tpl file:

    ....                                                                     

    # Custom Protect Section                                                   

    <<place the values here>>

    # End Custom Protect Section                                             

    ....                                                                     

       

    So make those changes, then recreate the httpd.conf file and signal the web server to reread the new httpd.conf either by adding or modify the permissions of a web user from the web UI or using the nhHttpdCfg command.

     

    Let us know if that helps answer this question.

     

    Thanks,

    Michael



  • 3.  Re: MAXRequest workers in httpd of ehealth

    Posted 11-19-2017 01:23 AM

    HI Michael,

     

    Still the problem is continuing and iam not able to make the change in the httpd.tpl  file.. caz if i make the below change 

    and re create httpd.conf its failing.. Is the format of of how i put the 1024 needs a change??

    # Custom Protect Section                                                   

    <<1024>>

    # End Custom Protect Section