1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Not opening - Internal Server Error

Discussion in 'Sitebuilder 4.0 for Linux' started by arazas, Sep 1, 2008.

  1. arazas

    arazas Guest

    0
     
    Server is not opening any Sitebuilder link of any domain.

    All links exists on /etc/httpd/conf.d/zz011_sitebuilder.conf

    It was working fine from months and suddenly disappear with following error. Please help ASAP.

    Internal Server Error

    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Please contact the server administrator, root@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.

    More information about this error may be available in the server error log.
    Apache/2.0.52 (Red Hat) Server at sitebuilder.domain.com Port 80






    I can see following error in logs /var/log/httpd/sitebuilder_error.log


    [Tue Sep 02 00:05:30 2008] [error] [client <IP>] (24)Too many open files: couldn't set child process attributes:/opt/php52/cgi-bin/php5

    [Tue Sep 02 00:05:30 2008] [error] [client <IP>] (24)Too many open files: couldn't spawn child process: /opt/php52/cgi-bin/php5
     
  2. Dmitry Frantsev

    Dmitry Frantsev Golden Pleskian

    28
    57%
    Joined:
    Sep 19, 2005
    Messages:
    1,911
    Likes Received:
    0
    It seems there is something wrong with Apache configuration. Did you check Apache error log file - /var/log/httpd/error_log ? Try to check it for some error messages. Also, try to run check.php script through browser http://sitebuilder.hostname/check.php. Does it work? Are there any problems with sites on the server?
     
  3. arazas

    arazas Guest

    0
     
    I can see following error, please advise:

    Can't locate warnings/register.pm in @INC (@INC contains: /usr/lib/perl5/5.8.5/i386-linux-thread-multi /usr/lib/perl5/5.8.5 /$
    BEGIN failed--compilation aborted at /usr/lib/perl5/5.8.5/vars.pm line 7.
    Compilation failed in require at /usr/lib/perl5/5.8.5/Tie/Array.pm line 86.
    BEGIN failed--compilation aborted at /usr/lib/perl5/5.8.5/Tie/Array.pm line 86.
    Compilation failed in require at /usr/lib/perl5/5.8.5/Env.pm line 123.
    BEGIN failed--compilation aborted at /usr/lib/perl5/5.8.5/Env.pm line 123.
    Compilation failed in require at /usr/sbin/sendmail line 4.
    BEGIN failed--compilation aborted at /usr/sbin/sendmail line 4.
     
  4. arazas

    arazas Guest

    0
     
    check.php also gives same 'internal server error'
     
  5. Dmitry Frantsev

    Dmitry Frantsev Golden Pleskian

    28
    57%
    Joined:
    Sep 19, 2005
    Messages:
    1,911
    Likes Received:
    0
    Hard to say what could be the reason for this but it seems there is something wrong with Perl installation or one of the Perl modules. For some reasons warnings/register.pm file could not be found. On my test server:

    # locate warnings/register.pm
    /usr/lib/perl5/5.8.8/warnings/register.pm
    [root@fedora6 ~]# rpm -qf /usr/lib/perl5/5.8.8/warnings/register.pm
    perl-5.8.8-5

    Try to check if everything is fine with Perl on this server:

    # perl -v
    # rpm -V perl
     
  6. arazas

    arazas Guest

    0
     
    Thank you for quick support, please advise now results are as below:

    [root@sm ~]# locate warnings/register.pm
    /usr/lib/perl5/5.8.5/warnings/register.pm

    [root@sm ~]# rpm -qf /usr/lib/perl5/5.8.5/warnings/register.pm
    perl-5.8.5-36.el4_5.2

    [root@sm ~]# perl -v

    This is perl, v5.8.5 built for i386-linux-thread-multi

    Copyright 1987-2004, Larry Wall

    Perl may be copied only under the terms of either the Artistic License or the
    GNU General Public License, which may be found in the Perl 5 source kit.

    Complete documentation for Perl, including FAQ lists, should be found on
    this system using `man perl' or `perldoc perl'. If you have access to the
    Internet, point your browser at http://www.perl.com/, the Perl Home Page.

    [root@sm ~]# rpm -V perl
    ERROR: Multiple different specifications for /usr/local/sitebuilder/tmp(/.*)? (system_u:eek:bject_r:httpd_sys_content_t and system_u:eek:bject_r:tmp_t).
     
  7. Dmitry Frantsev

    Dmitry Frantsev Golden Pleskian

    28
    57%
    Joined:
    Sep 19, 2005
    Messages:
    1,911
    Likes Received:
    0
    Can not say exactly what it could be. Please try to run 'sb_config' utility directly on the server and provide here the output.
     
  8. arazas

    arazas Guest

    0
     
    how exactly I should run this command? Simply sb_config shows only help and options... please advise.
     
  9. arazas

    arazas Guest

    0
     
    please help me on this
     
  10. arazas

    arazas Guest

    0
     
    I can see SWSOFT Parallels failed to fix. They worked well but unfortunately failed to diagnose the actual problem. Per my working I checked the /var/log/httpd/error_log and analyzed and found it large number of descriptors issue. I used the following commands:

    [root@sml104 logs]# ulimit -n
    1024
    [root@sml104 logs]# ulimit -n 2048
    [root@sml104 logs]# ulimit -n
    2048
    [root@sml104 logs]# service httpd restart
    Stopping httpd: [ OK ]
    Starting httpd: [ OK ]
    [root@sml104 logs]# ulimit -n
    2048
    [root@sml104 logs]#

    Now I have fixed it. I just want to know how do I confirm these change will not revert back. The command I used to increase the size is a permanent solution or I need to change anything else?

    Why this descriptors limit needs to be increased, please advise me on this?
     
  11. Dmitry Frantsev

    Dmitry Frantsev Golden Pleskian

    28
    57%
    Joined:
    Sep 19, 2005
    Messages:
    1,911
    Likes Received:
    0
    Actually, it looks like not Sitebuilder or Plesk issue but Apache limitation. Please check following articles for more information and permanent solution: http://kb.odin.com/en/260, http://kb.odin.com/en/2066.
    You can also add following string "ulimit -n 2048" into Apache start script. In this case each time when system rebooted and Apache process is started value will be increased.
     
Loading...