/var/www/sharedip/ <--Lots of hits there

Discussion in 'General' started by yurtboy1, Apr 4, 2008.

  1. yurtboy1

    yurtboy1 New Member

    Just wondering if this is cause there is a link on the server related to an IP.
    For example we carried over and old site and maybe in one of those files is a link that people are visiting that goes back to ip and then ispconfig things to go here.
    I am seeing this in the apache error log and it causes a segmentation fault after about a day or of hits.
     
  2. falko

    falko Super Moderator ISPConfig Developer

    If there's an IP linked on one of your web sites, then this is the reason.
     
  3. yurtboy1

    yurtboy1 New Member

    yes what is happening is that people are using

    our applet but wrapping it wrong or what ever so the server is coming back here for other things.
    Is there a way to block this request so apache just ignores it and there is no hit to the server?
    Like make that folder non readable?
    Or put an .htaccess file in there saying you are not allowed?
     
  4. falko

    falko Super Moderator ISPConfig Developer

    You can remove the Shared IP vhost from Vhosts_ispconfig.conf (right at the beginning), but you'd also have to remove it from the function make_vhost() in /root/ispconfig/scripts/lib/config.lib.php.
     
  5. yurtboy1

    yurtboy1 New Member

    what will then happen?

    does apache just not even take note?
    Or is it still considered a mis-hit?
    Thanks
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    If you remove the sharedIP vhsots, the request will be redirected to the first vhost which uses this IP. If the requested page does not exist in this vhsot, apache will throw a 404 error.
     
  7. yurtboy1

    yurtboy1 New Member

    Okay maybe I should also mention that the log has

    tons of these
    [Fri Apr 11 01:04:43 2008] [notice] child pid 4048 exit signal Segmentation fault (11)
    [Fri Apr 11 01:04:52 2008] [notice] child pid 10915 exit signal Segmentation fault (11)

    And the two seems to show up at the same time until finally the server stops serving.

    So by redirecting this to 404 would it all really matter to apache and server load?
     
  8. falko

    falko Super Moderator ISPConfig Developer

Share This Page