I have installed spring roo version 1.2.3.RELEASE on Ubuntu Linux 12.04 using these instructions: http://static.springsource.org/spring-roo/reference/html/intro.html#intro-installation
I then create an empry directory and try to start roo as instructed in the tutorial:
http://static.springsource.org/spring-roo/reference/html/beginning.html#beginning-step-1
But I get this error:
java.lang.Exception: Unable to create bundle cache lock file: java.io.FileNotFoundException: /usr/share/roo/cache/cache.lock (Permission denied)
And indeed my user does not have permission to write to this file, it is owned by root as expected and if I run sudo roo everything seems to work. Does the installation instructions miss some vital part about permissions? Not knowing that much about roo yet, I would prefer not running it as root.
Can you not just give your user (or group) write access to the roo dir (and sub dirs)?
Why don't you install Roo in a path that you're allowed to use? For instance, in your home: ~/Applications/spring-roo-1.2.3.RELEASE
Related
As the title suggests I am receiving the error
/usr/bin/env: node: Permission denied
when trying to run
npm run build
for my react app. The following link is the leadup to this point with all that I've done and tried, not to be included here for the sake of not duplicating questions Error with react-scripts in npm run build.
Additionally, I have viewed this posting, Getting Error /usr/bin/env: node : Permission Denied, and it was unhelpful to me.
Any help is much appreciated.
I was working in a dockerized node environment and noticed that the mounted source code directory had different ownership (running the container as root) from host environment. Changing the ownership using:
chown -R root:root .
made the error go away for me!
The issue ended up being a matter of file ownership. Root was the owner of many things for the project rather than my profile. Simply changed the ownership from root to me.
For me, re-installing node with NVM solved the issue:
Install nvm
nvm install 14
nvm use 14
you should running command as super user sudo npm run build
For anyone else hitting this, there is another avenue of investigation. There might be another factor affecting execute permissions. There's an exec flag on drive mounts to enable script execution (neat safety feature for automounted usb sticks!). So if your code is on a drive that you've mounted, you need that option set to run scripts on it. Tell-tale signs are the permissions on the script being correct (appropriate user, group and execute bits set), but it still complaining about the shebang line (1st line) being the permission denied. Also, if you type mount, you might see noexec set on the mount point where your source code is (it may not show here if exec is set). How your mount is set up varies greatly, but a place to start is your /etc/fstab.
I’m trying to run the below command,
C:\hadoop\bin\winutils.exe chmod -R 777 C:\SparkProject
But it gives me error saying
The application was unable to start correctly (0xc000007b)
I have kept the winutils.exe in \hadoop\bin, also set up the environment variable for HADOOP_HOME.
If I run the spark program which writes in local system from intellij idea. it fails. But but I can see zero byte files are created in that folder (a .crc file).
I’m using windows 10.
I have tried all the winutils available as I was not sure of the version that I need.
Finally I have downloaded one latest from GitHub for hadoop-3.3.0.
link: https://github.com/kontext-tech/winutils/blob/master/hadoop-3.3.0/bin/winutils.exe
And it's working now. I'm able to give permission via winutils.exe as well as write into local file system.
I installed Yii2 on Ubuntu 16.04 using Vagrant and when I try to load some page, Yii gives me an error:
The directory is not writable by the Web process: /web/assets
I found some solutions but they don't work because of SELinux. I tried to disable it using setenforce 0 but command line prints:
setenforce: command not found.
I noticed that almost no one has this error and I don't know what did I do wrong or what should I do. Please help!
chmod 777 /path/to/web/assets
This allows any user to read/write/execute. On servers, this is usually not recommended, but in some cases its hard to avoid. We had to do this for the runtime, the assets and the uploads folder with Vagrant. It might be worth noting that we only used Vagrant in the development environment but not in production.
I'm new to Sonar, and i was trying to install Sonar 2.8 on my server (Linux 64 on HP-UX)
When i tried to launch it (sonar.sh start) i got the following message
[myHomeDirectory]/sonar/2.8/bin/linux-x86-64/./wrapper: Execute permission denied.
what drives me crazy is that i've putthe whole package on 777 permissions, so i really don't understand what's exactly happening.
Can anyone help with this please ?
Thanks in advance !
I hit a similar issue hence why I came to this post. I was attempting to install SonarQube's scanner in a Docker container but when I was running it, I was getting something along the lines of:
/root/sonar-scanner-2.6.1/bin//sonar-scanner: 103: exec: : Permission denied
I had given the whole /root/ folder all permissions so I was curious about the permission denied. In the end for me it wasn't anything to do with permissions. I simply needed to RTFM.
Sonar-scanner needs a JRE to run and my Docker container didn't have one installed. So if anyone else does the same thing as me, I hope this saves you a few minutes of head scratching.
Not really convinced in the way you are launching it. To get Sonar running I recommend running it on tomcat, providing you just want to use the default database that comes with Sonar. The steps would be:
Install Tomcat
Navigate to your /war directory within your sonar instance and run the command: $] ./build-war.sh.
When this finishes you should see a sonar.war file in the same directory.
Rename the war file ROOT.war instead of sonar.war: $] mv sonar.war ROOT.war
This ensures that sonar runs on tomcat's default port.
Move the war file into the tomcat webapps directory: $] mv ROOT.war /tomcathome/webapps
Navigate to the tomcat /bin folder and run the command $] ./catalina.sh start
Type your server hostname in your browser with a port :8080 at the end and you should see sonar running.
These steps will have sonar running on the default database, though. If you want a MySQL database i'd look at sonar tutorials on how to do that.
I finally came out with the conclusion that the binary file (wrapper) is simply not compiled to run under HP-UX
when launching a file command on wrapper under a Linux i get : <ELF-64 executable object file> which doesn't match the <ELF-64 executable object file - IA64> required by HP-UX running on a Itanium processor
Please check if you have java installed on the machine. Java should be installed on the machine before running sonar-runner.
Use this to check java : java -version
I have Jenkins set up on a machine with the NodeJS plugin. Sadly, whenever I try to use the plugin in a build, it fails with:
[workspace] $ node /tmp/hudson3477900862350780409.js
FATAL: command execution failed
java.io.IOException: Cannot run program "node" (in directory
"/var/lib/jenkins/jobs/XXX/workspace"): error=2, No such file or directory
When I log into the machine as the jenkins user, I can use node through command line. I also added the path to node (/opt/node-0.6.18/bin) into the Configuration screen for the current working node (which is only one: master).
I've been stuck with this for a while, any help would be highly appreciated.
Cheers!
Well, this isn't the most elegant of solutions, but it worked: I simply made a symlink to from /bin/ to the installation path for node and now the problem's gone.
ah easy, you need to tick "Provide Node/npm bin folder to PATH" when running a "execute shell" build task"
I am using NVM and I had the same issue. One workaround was to create a symlink:
ln -s /root/.nvm/versions/node/v8.11.3/bin/node /bin/node
ln -s /root/.nvm/versions/node/v8.11.3/bin/npm /bin/npm
For Jenkins running in Docker, use jenkins/jenkins:latest image to avoid this issue.
the error came up just because you did't install node in your machine.after you installed it,and add it to PATH,then the problem can be solved.
hope it helps.