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

Trouble Access Control Panel

Discussion in 'Plesk for Linux - 8.x and Older' started by goster@, Jan 21, 2006.

  1. goster@

    goster@ Guest

    0
     
    I am having frequent problems accessing the Plesk Control Panel - I just receive a blank screen. Rebooting the server resolves the problem for a few hours - but within 12 hours the blank screen returns when I try to access the control panel.
    I host through WildWestDomains, and they say that it is a memory problem - but it is my responsibility to fix (now I know why prices are so reasonable...). I have 15 domains currently hosted, all of which are smaller sites, using very little bandwidth.

    Offending Control Panel location is https://68.178.188.25:8443/

    Any ideas how to fix this?

    Thanks,
    Glenn Oster
    ASKaPRO Online Service
    www.ASKaPRO.net
     
  2. ShadowMan@

    ShadowMan@ Guest

    0
     
    Could be a number of things. You have not posted your server OS or hardware specs, which might be helpful. Also Shared/Dedicated/VPS server?

    Bandwidth usage should not necessarily be a factor. The Plesk CP uses a separate copy of Apache which is separate from the Apache used for the hosted domains.

    When the problem occurs, can you SSH into the server and run some commands (such as "top" or "ps -ax |grep 'httpsd' " ??

    We have noticed that on a number of Plesk 7.5.x servers, our process list will often show Zombied Plesk Apache processes:
    Code:
     4983 ?        S      0:00 /usr/local/psa/admin/bin/httpsd
     4987 ?        S      0:01 /usr/local/psa/admin/bin/httpsd
     4988 ?        S      0:01 /usr/local/psa/admin/bin/httpsd
     4989 ?        S      0:00 /usr/local/psa/admin/bin/httpsd
     4990 ?        S      0:00 /usr/local/psa/admin/bin/httpsd
     4991 ?        S      0:01 /usr/local/psa/admin/bin/httpsd
    10745 ?        S      0:00 /usr/local/psa/admin/bin/httpsd
    10822 ?        S      0:01 /usr/local/psa/admin/bin/httpsd
    15949 ?        Z      0:00 [httpsd <defunct>]
    16316 ?        Z      0:00 [httpsd <defunct>]
    18298 ?        Z      0:00 [httpsd <defunct>]
    which sometimes will require a server reboot (or a full PSA restart). This can be done with a cronjob at intervals, doesn't find the problem, but keeps things running without human intervention (I know it's not an ideal solution...)

    I'm assuming it's not related to the earlier Firefox (beta) issue posted a few months back...

    Also, have you checked any of the logs to see if there are any relevant entries ?

    If you're on a VPS, then have you checked to see if you actually are allocated enough memory?
     
Loading...