Announcement Announcement Module
No announcement yet.
Install STS-2.3.2 permission denied on ubuntu linux Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Install STS-2.3.2 permission denied on ubuntu linux

    I downloaded springsource-tool-suite-2.3.2.RELEASE-e3.5.2-linux-gtk.tar.gz, and extracted to a directory.

    In this directory are three subdirectories

    I navigate to the sts-2.3.2.RELEASE directory and type
    and I get
    [email protected]:/var/workspaces/springsource/sts-2.3.2.RELEASE$ ls -al
    total 876
    drwxr-xr-x   9 mmainguy mmainguy   4096 2010-03-22 21:37 .
    drwxr-xr-x   5 mmainguy mmainguy   4096 2010-03-22 21:37 ..
    drwxr-xr-x   2 mmainguy mmainguy   4096 2010-03-22 20:32 about_files
    -rw-r--r--   1 mmainguy mmainguy    577 2010-02-10 03:26 about.html
    -rw-r--r--   1 mmainguy mmainguy 331481 2010-03-22 21:37 artifacts.xml
    drwxr-xr-x   8 mmainguy mmainguy   4096 2010-03-22 21:37 configuration
    drwxr-xr-x   2 mmainguy mmainguy   4096 2010-03-22 20:32 dropins
    -rw-r--r--   1 mmainguy mmainguy    145 2010-03-22 21:37 .eclipseproduct
    -rw-r--r--   1 mmainguy mmainguy  16536 2005-02-25 12:53 epl-v10.html
    drwxr-xr-x 158 mmainguy mmainguy  12288 2010-03-22 21:37 features
    -rw-r--r--   1 mmainguy mmainguy  66784 2010-03-22 19:17 icon.xpm
    -rwxr-xr-x   1 mmainguy mmainguy 266168 2010-02-10 03:26
    -rw-r--r--   1 mmainguy mmainguy   6506 2005-03-17 11:12 notice.html
    drwxr-xr-x   5 mmainguy mmainguy   4096 2010-03-22 20:27 p2
    drwxr-xr-x  38 mmainguy mmainguy  61440 2010-03-22 21:37 plugins
    drwxr-xr-x   2 mmainguy mmainguy   4096 2010-03-22 20:32 readme
    -rw-r--r--   1 mmainguy mmainguy  11328 2010-03-22 21:37 SPRINGSOURCE-EULA.txt
    -rwxr-xr-x   1 mmainguy mmainguy  52932 2010-02-10 03:26 STS
    -rw-r--r--   1 mmainguy mmainguy    272 2010-03-22 21:37 STS.ini
    [email protected]:/var/workspaces/springsource/sts-2.3.2.RELEASE$ ./STS
    bash: ./STS: Permission denied
    Not sure what's going on here, I guess I can try the installer, but what is the "normal" file for? I assumed it was just going to be a stand-alone linux install. Are there some env variables I need to set or something?

  • #2

    can you check if you are running a 32-bit version of Linux, e.g. by running
    "uname -a"? If you have a 64-bit version you will need to get the 64-bit version of STS.



    • #3
      The problem was that you downloaded the tar file while in Windows or into a Windows partition (FAT/NTSC most likely) and extracted the files there. Those partitions don't support the permissions model used in Linux, so none of the executable scripts have the permission to execute.

      You could just do:
      chmod u+x STS

      But you'll encounter more problems later, because there are other scripts that will need this permissions too. So, extract again, but in a Linux partition.


      • #4
        The problem is that the sts installer unpacks file into /tmp and then tries to run, but Ubuntu won't allow scripts to be run from /tmp. To get your STS running:

        1. changed the installer script to abort before cleaning up unpacked files (warning: the file is huge, do it with vim or another capable editor):

        printf " starting UI installer. please follow instructions on screen..."
        # This and the next line were added by me
        exit 0
        2. run the installer

        3. move the extracted directory from /tmp to your home directory, i.e.

        mv /home/ggonspring/ ~
        4. run from within the new location


        • #5
          I always use the STS installer package and on Ubuntu 10.04 32 bit and never had problems with it.

          Here's what I usually do:

          Download the self extracting .sh installer to my home directory.

          Type "sh <installer-name>.sh".
          Install the STS files into a folder under my home dir.

          I've never had to resort to making changes to installer shell script files to make things work. So I'm not sure why you are having these problems.

          I wonder if perhaps it has something to do with your specific tmp partition as glvanse suggested.


          • #6
            In this particular case the damage is self-inflicted: the /tmp folder was mounted with the noexec option in /etc/fstab.