Bug in ftp_logs.php ?

Discussion in 'Installation/Configuration' started by Trosan0, Aug 30, 2007.

  1. Trosan0

    Trosan0 New Member

    I recently took a look at my server again and was shocked. 99% user CPU load. That can't be.

    Top showed me, that there were dozens of php processes each consum 1.1% CPU load and a time+ with about 9000 (!) [so, many different values up to 9000]

    Using "ps aux" I got this output (shortened a bit):
    (to be continued in next posting)
     
  2. Trosan0

    Trosan0 New Member

    (continuing...)

    That makes me feel it's ISPConfig's fault.



    This is my crontab line:

    Interestingly enough, I can find daily updated "vsftpd.log" files in my /var/log directory (each 0 bytes in size), but my proftpd.log in /var/log/proftpd hasn't been copied over to proftpd.log.0 for 30 days (which is perhaps right?)


    Now, after using "killall php", the problems is gone. Question is just: for how long?


    PS: I am using ispconfig 2.2.14
     
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    Do you use proftpd or vsftpd?
     
  4. Trosan0

    Trosan0 New Member

    Sorry for forgetting this - proftpd
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    Did you select the correct ftp application in ISPConfig under management > server > settings ?
     
  6. Trosan0

    Trosan0 New Member

    Yes, I did!
     
  7. falko

    falko Super Moderator Howtoforge Staff

    Please run
    Code:
    /root/ispconfig/php/php /root/ispconfig/scripts/shell/ftp_logs.php
    on the shell. Do you get any errors then?
     
  8. Trosan0

    Trosan0 New Member

    No, this one doesn't hang... strange..

    By the way, as mentioned, I did a killall php yesterday. Now there's again this process:
    (truncated due to console width)

    Can't find the one I just started, so there seems to be a problem when run from a crontab...

    Perhaps it's due to an overload. I just changed the crontab so that the start time for the ftp_logs.php differs from the other two php jobs which were previously at the same time.. Dunno if it'll help though (will see)
     

Share This Page