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

Strange /admin with .jsp files for every domain

Discussion in 'Plesk for Linux - 8.x and Older' started by [MaDBuCe], Oct 2, 2005.

  1. [MaDBuCe]

    [MaDBuCe] Guest

    0
     
    Hi,

    I added some domains on our new Reloaded VPS.
    Strange thing is that when i add /admin to that domain or the ip address of the vps i get a strange folder with .jsp files.

    I cannot find what it is, i only know that it refering to the terminfo folder.

    Does anyone know what this is? Some of our scripts have an admin folder and now shows the folder with .jsp files.

    **edit
    I now know that it's related to the Tomcat Admin tool.
    I have Tomcat disabled, but where can i change the link so that it's not included with each domain?
     
  2. hardweb

    hardweb Guest

    0
     
    In which folder exactly do you get these files? Do you have anything like this in the skel directory at /home/httpd/vhosts/.skel?
     
  3. [MaDBuCe]

    [MaDBuCe] Guest

    0
     
    Hi Hardweb,

    I get the files after very domain or ip.
    So http://www.xxxx.com/admin will show tomcat files
    http://123.345.567/admin will do either.

    I'm on a RHEL3 VPS so the .skel is in another folder and the structure is like /var/www/vhosts/.skel/0/httpdocs

    but there is only index.html
     
  4. graffix

    graffix Guest

    0
     
    I have exactly the same issue on our server on vps based hosting.
    So is there a fast solution for this?
    Our customer are laughing, because the new plesk 7.5.4 is full og bugs at the moment.
     
  5. MisterB

    MisterB Guest

    0
     
    There is ;)
    The reason you're seeing the files is because Plesk creates an alias for Tomcat (two actually, /admin and /test) with the Options Indexing set. The alias is global hence it will work with all domains you create. The simple solution is to remove the alias.

    To do that comment the following lines in the file /etc/httpd/conf/mod_jk.conf and restart apache (/etc/init.d/httpd restart)
    Code:
    Alias /admin "/var/lib/tomcat4/server/webapps/admin"
    <Directory "/var/lib/tomcat4/server/webapps/admin">
        Options Indexes FollowSymLinks
    </Directory>
    
    Alias /test "/var/lib/tomcat4/webapps/test"
    <Directory "/var/lib/tomcat4/webapps/test">
        Options Indexes FollowSymLinks
    </Directory>
    
    This will solve the issue, but will *most* probably break Tomcat if you're using that (at the very least you will no longer have the /admin and /test interface). But I'm not using it :D
     
  6. [MaDBuCe]

    [MaDBuCe] Guest

    0
     
     
  7. MisterB

    MisterB Guest

    0
     
    That's a better solution then. Thanks for the tip.
     
  8. carver6

    carver6 Guest

    0
     
    Unbelievable

    I am not going to take the time to find out as I have already wasted to many hours digging through conf files.

    It doesn't matter if its Plesk or Tomcat, anyone who packages an app and puts a global alias to "/admin" is an idiot! How many applications out there install to "/admin"? A lot! This breaks too many other apps.

    What if I were to make it "/tomcatadmin" Is there any reason this would resolve the problem.?
     
  9. ShadowMan@

    ShadowMan@ Guest

    0
     
    As you infer from your post, there are many other packages which also use /admin, so what is the big deal? You will still have the same problem if you were to install several of those other apps as well....
     
  10. carver6

    carver6 Guest

    0
     
    In some cases

    I understand what you're saying. I'm just frustrated..:rolleyes:

    I have several apps to install in various domains. First time with Plesk and never had to deal with Tomcat before. My pain is for all those who try installing php apps (OS Commerce, Gallery, and the like) that default to using /admin. Which is fine. But as soon as you put /admin in http.conf as a global alias or rewrite, that screws everyone up.

    As a client trying to install apps, I would have to move /admin (within my domain) to somewhere else and reconfigure the software. This is the last thing I want to have to do for clients:eek:
     
  11. ShadowMan@

    ShadowMan@ Guest

    0
     
    I know it's frustrating. If you and your clients don't use Tomcat, then I would uninstall it, but leave the Tomcat4 packages:

    # rpm -qa |grep tomcat
    tomcat4-webapps-4.1.24-full.2jpp
    psa-tomcat-configurator-7.5.3-rh9.build75050506.13
    tomcat4-4.1.24-full.2jpp
    tomcat4-admin-webapps-4.1.24-full.2jpp
     
  12. [MaDBuCe]

    [MaDBuCe] Guest

    0
     
    I thinks it's not so difficult to change this.
    If your future customers want to use Tomcat and you have to reinstall it could cause bigger problems.

    Code:
    Alias /tomcatadmin "/var/lib/tomcat4/server/webapps/admin"
    <Directory "/var/lib/tomcat4/server/webapps/admin">
        Options FollowSymLinks
    </Directory>
    
    Alias /tomcattest "/var/lib/tomcat4/webapps/test"
    <Directory "/var/lib/tomcat4/webapps/test">
        Options FollowSymLinks
    </Directory>
    
    Worked fine for me :D
     
Loading...