I am trying to copy R dataframe to Spark 2.0.1 using copy_to function but it says
The root scratch dir: /tmp/hive on HDFS should be writable. Current permissions are: rw-rw-rw-
I executed winutils.exe to change the permissions but still I get the same Exception of permissions.
%HADOOP_HOME%\bin\winutils.exe chmod 777 \tmp\hive
I tried other variants of the command like -
%HADOOP_HOME%\bin\winutils.exe chmod 777 C:\tmp\hive
%HADOOP_HOME%\bin\winutils.exe chmod 777 /tmp/hive
%HADOOP_HOME%\bin\winutils.exe chmod 777 -R \tmp\hive
but nothing worked. I still get the error
I tried using advanced permission and all my permissions were set to rwx. I tried running ls -l command but was getting an error;
C:/> %HADOOP_HOME%/bin/winutils ls C:/tmp/hive
FindFileOwnerAndPermission error (1789): The trust relationship between this workstation and the primary domain failed.
My system was unable to connect to it's domain controller so I had to connect to VPN and then execute C:/> %HADOOP_HOME%/bin/winutils chmod 777 /tmp/hive.
It worked!
Related
I am using python flask application as backend in my website I'm using apache2 in ubuntu VPS
the website is live but I am getting the error while signup and I can't able to post or like or comment on that site.
I checked that error by using command
cd /var/log/apache2 && cat error.log
the error was
sqlalchemy.exe.OperationalError : (sqlite3.OperationalError) attempt to write a readonly database.
It means It do not have access to edit the sqlite3 DB file.
I tried all chmod command but still I can't able to solve the issue.
help me pleaee
sudo chmod 666 /var/www/webApp/webApp/buzz.db sudo chown root:www-data /var/www/webApp/webApp/buzz.db sudo chmod 660 /var/www/webApp/webApp/buzz.db
this are the some commands that I used
I would like to move the file.txt FROM usr/local/file.txt TO /usr/local/folder/file.txt.
However, every time I try I get a permission denied reply.
I have tried:
sudo mv ~/usr/local/file.txt /usr/local/folder/file.txt
When I got permission denied, I also used chmod and set a 777 just to try and still get permission denied.
What can I do?
Try this:
Check whether you have write access to the folder with
ls -l
Then you can try changing the ownership of the folder to your current user.
sudo chown -R your_username /path/to/folder
See this.
I am trying to upload an image to set a background image for my theme, but I get this error:
Unable to create directory wp-content/uploads/2018/05. Is its parent directory writable by the server?”
I tried to change the access permissions with the help of these blogs:
https://www.digitalocean.com/community/questions/setting-permissions-for-wordpress
https://gist.github.com/Adirael/3383404
But nothing has helped me, and now I also get a 500 error page.
I'm stuck here, can anybody help?
-----------Comment-----------
Output Image for ps -ef| grep httpd
I executed this command
find . type f -exec chmod 644 {} \;
and the 500 error page is not being displayed now. I am able to view my web page. But I am still unable to upload a background image. (same error appears "Unable to create directory wp-content/uploads/2018/05. Is its parent directory writable by the server?")
The following command will fix your issue
sudo chmod -R 777 wp-contents/uploads/
If you're using Bitnami Lamp then run the following commands in your SSH terminal:
sudo chown -R bitnami:daemon /opt/bitnami/apache/htdocs
sudo chmod -R g+w /opt/bitnami/apache/htdocs
sudo chmod 440 /opt/bitnami/apache/htdocs/wp-config.php
sudo chmod 440 /opt/bitnami/apache/htdocs/.htaccess
and if you're using Bitnami WordPress then run the following commands in your SSH terminal:
sudo chown -R bitnami:daemon /opt/bitnami/apps/wordpress/htdocs
sudo chmod -R g+w /opt/bitnami/apps/wordpress/htdocs
sudo chmod 440 /opt/bitnami/apps/wordpress/htdocs/wp-config.php
sudo chmod 440 /opt/bitnami/apps/wordpress/htdocs/.htaccess
The recommended permissions are:
Directories: 775
Files: 640
wp-config.php and.htacess: 440
Thanks
Maybe is already solved, but can help other users with similar issues.
I made a Shell Script on Debian10 to solve permissions issues.
After running it, I make the folder accesible on the Apache2.conf too (WordPress can't Upgrade or Upload Media if not)
What it does:
Set new Owner on all Files and (Sub)Directories ( user:group )
Set Permissions: 755 to Directories and 644 to Files
wp-config.php : Preventing world access for "wp-config.php", leaving it accesible to WordPress (660)
Allow WordPress to manage the "wp-content" (Directories to 755 & Files to 664)
Privatize "wp-content" (Set 755)
Link:
https://github.com/ieselisra/wordpress_fix_permissions_debian10/
To give first some history to this problem; I'm setting up a django site on digitalocean first copied using root and the django folder had as the owner root and I've since worked on fixing this and now the site it up and running but one image still has the 403 forbidden error.
I'm looking for a command that can change the rights of this file.
-rwxr----- 1 sammy sammy 566719 Jul 1 14:52 developer.jpg
Your NGINX user is likely using the www-data or a different user, to verify the user being used by NGINX in a shell execute:
grep user /etc/nginx/nginx.conf
Then to change the file permissions:
chown www-data:www-data developer.jpg
Looking at your file permissions they also needed adjusted - see this answer for recommended perms.
(may require sudo, replace www-data with your NGINX user)
chmod -R 777 folder_name
chmod -R 777 file.name //when You are in directory where this file exist
or
chmod -R 777 file_path/file.name
i've deployed my S2 Project on my remote server (nginx) and when i try to clear the cache i've got an error:
[RuntimeException]
Unable to write in the "/Applications/MAMP/htdocs/Git/S2project/app/cache/prod" directory
why does it point on my local install and not on my server??
you don't have permission to write in cache folder, you should run this command:
chmod -R 777 app/cache/*
and same for the logs folder
chmod -R 777 app/logs/*
You can also try to remove cache "manually"
rm -rf cache/*
and then as suggested by ponciste
chmod 777 -R cache/*
the uname of the app.php file is not set to the right user on your prod server.