Server.sh generating errors when run from command line

Discussion in 'Installation/Configuration' started by jluros, Jan 31, 2011.

  1. jluros

    jluros New Member

    I've suspected a problem with server.sh on my ISPConfig 3.0.3.2 server, specifically when creating new websites. I created a test site and ran server.sh as root and it generated the following errors:

    /usr/local/ispconfig/server/server.sh
    chmod: cannot access `/var/www/clients/client1/web31/*': No such file or directory

    Warning: copy(/etc/apache2/sites-available/destinationforlife.com.vhost): failed to open stream: No such file or directory in /usr/local/ispconfig/server/plugins-available/apache2_plugin.inc.php on line 833
    finished.

    Thoughts? What is the net effect of those errors? Can I resolve those manually?
     
  2. falko

    falko Super Moderator ISPConfig Developer

    Did you somehow delete /var/www/clients/client1/web31/?
     
  3. jluros

    jluros New Member

    No. I added the client using the web GUI, then I ran server.sh from the command line.
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    There is no need to run server.sh manually, the script is run automatically by a cronjob once a minute. If you run server.sh manually under a wrong user, it may cause problems on your server, so better do not touch it.
     

Share This Page