ghost error with db file - sqlite

I am trying to run ghost on the localhost. When I am doing
npm start
I am getting the below error.
ERROR: Unable to open sqlite3 database file for read/write EACCES,
permission denied
'/home/letsalign/Projects/letsalign-blog/content/data/ghost-dev.db'
Check that the sqlite3 database file permissions allow read and write
access.
Although the db has the read and write permission.
Please help

Related

"EACCES: permission denied" when using "firebase serve"

I am using "firebase serve" to test my Firebase web app locally. I ran into this error every time:
Error: EACCES: permission denied, open
'/Users/[my_user_name]/.config/configstore/#google-cloud/functions-emulator/.functions.json'
You don't have access to this file.
Error: EACCES: permission denied, open
'/usr/local/lib/node_modules/firebase-tools/node_modules/#google-cloud/functions-emulator/logs/cloud-functions-emulator.log'
It does work with a sudo. But I don't want to type in my sudo password every time. Every other command works fine without sudo except for this one.
If you don't want to run sudo every time, you need to install node in your home directory where you have full control. Don't use the node that you may have installed with a package manager using the system's default settings. The typical tool to help you with a home directory installation is Node Version Manager (nvm).

Deploying a file in Artifactory's Web GUI generates an '<filename> undefined' error

I am using Artifactory Professional, version 5.6.0 rev 50600900
When I try to deploy a file through the Artifactory web UI, I'm getting an error: '<filename> is undefined' in a red popup box.
When I look in the system log, I see:
2018-05-15 08:25:41,037 [http-nio-8081-exec-123] [ERROR] (o.a.r.c.e.GlobalExceptionMapper:48) - Permission denied
java.io.IOException: Permission denied
The time corresponds to the time I tried the deploy
Uploads using a curl command or via the Artifactory plugin in Jenkins work without any problems.
I am an administrator on Artifactory. other users with Delete/Overwrite, Deploy/Cache, Annotate and Read also are not able to upload to repos via the web UI.
I get the undefined error with all files i try to deploy, large or small. this error occurs for users on windows, mac os and linux.
thanks in advance for any help.
Looks like an file system permissions issue. Make sure that the OS user running Artifactory has write permissions to <ARTIFACTORY_HOME>/data/tmp.
The artifacts uploaded from the UI are temporally saved under this folder.

Symfony 2 fatal error on cache directory

I ssh to my VPS where there is a vagrant box that runs a symfony project.
When i try to access the project i am getting the error:
`Fatal error: Uncaught RuntimeException: Failed to write cache file` and
`Fatal error: Uncaught exception 'RuntimeException' with message 'Could not create cache directory`
I have tried fixing file permissions as mentioned here: http://symfony.com/doc/current/setup/file_permissions.html
and even changed chmod to 777. But still getting same error.
I also tried everything there: symfony2 : failed to write cache directory
It just won't work. Any help would be much appreciated.
My VPS is running ubuntu 16.04 and vagrant is latest version with image ubuntu/trusty
If you are running Apache check your /etc/httpd/conf/httpd.conf file and find your entry for your website in there. Check to see what user Apache is running the site as. You'll want to make sure the directories and files that make up your Symfony app belong to that user and the group the user is in as well. If you are logged in as root and are in the your Symfony directory you can run:
chown -R user:group *
to change all the files and directories to that user and group. Note to replace user and group in the command above with the actual username and group.
If you still have troubles after you've found the user apache is running as, try removing your symfony files completely (if it is a fresh project that you haven' been working on) and rebuild it while you are superuser'd (su) as that user. You probably built your project as root or another user.

Error: EACCES: permission denied in Meteor

Sorry for my english. When I want to write file in Meteor on production, I have an error.
[Error: EACCES: permission denied, open '/app/bundle/programs/server/../web.browser/app/data/market-prices-list.json']
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/app/bundle/programs/server/../web.browser/app/data/market-prices-list.json'
I think that it is related to the rights to the folder. I use Ubuntu for development and Meteor Galaxy for production.
Galaxy does not provide means for persistent storage.
For temporary files, you can use /tmp, but if you need persistent storage, you should use an external service or another deployment target.

Drupal 7 configuration error with Postgresql in Mac OS 10.6.5

I am trying to configure Drupal 7 with Postgres. At the database setup step, I get the following error.
Warning: PDO::_construct(): [2002] No such file or directory (trying to connect via unix:///var/mysql/mysql.sock) in DatabaseConnection->_construct() (line 300 of /Users/shamod/Sites/drupal/7/includes/database/database.inc).
In order for Drupal to work, and to continue with the installation process, you must resolve all issues reported below. For more help with configuring your database server, see the installation handbook. If you are unsure what any of this means you should probably contact your hosting provider.
Failed to connect to your database server. The server reports the following message: SQLSTATE[HY000] [2002] No such file or directory.
Is the database server running?
Does the database exist, and have you entered the correct database name?
Have you entered the correct username and password?
Have you entered the correct database hostname?
NOTE: I am trying to connect to Postgresql but it fails on var/mysql/mysql.sock error. I have setup the database connection string in settings.php for Postgresql. It still does not work.
Any idea?
Evidently you are trying to connect to a MySQL database instance, so you should review your database driver and connection configuration.
Just came up against this error myself when trying to use the web installer - might come down to a similar issue.
On the install page I wasn't given an option to use Postgres driver so I assumed I needed to use the "Mysql (or other)" option. However, looks like the Drupal install script checks which database drivers are compiled into PHP and only offers you what is available - my system didn't have php-pgsql installed by default.
So I needed to install the postgresql drivers to PHP first, reload apache then try the install again.
On CentOS-5:
sudo yum install php-pgsql
sudo service httpd restart
Then reload the install page and all worked fine.

Resources