I just performed a clean install of JIRA Software 7 but im stuck in first access setup with the following error:
Setup admin account: Cannot create user, all the user directories are read-only
I solved it the same way as Tuncay although I think this is not supported (yet). My install is windows 2012 r2, postgresql 9.6 and JIRA 7.2.3x64. (Also see EDIT below)
It's the same root issue I suspect as https://jira.atlassian.com/browse/CONF-44216
I downloaded the latest JDBC driver from https://jdbc.postgresql.org/download.html (in my case the JDBC42 driver), copied the jar into the lib folder, stopped JIRA, renamed the Atlassian prostgresql jar file to *.bak (not sure if that was necessary?), copied in the JDBC42 driver, started JIRA and it all worked from then, no more error.
I a bit of a noob at these products but it worked, so it seems to be issues with the db drivers used by JIRA and their compatibility with the DB in question. Try updating the relevant drivers.
EDIT: Adding that 1) it IS necessary to remove the old jar jdbc file and that 2) this issue does also occur on Linux and has the same solution. I had the issue with CentOS 7, PSQL 9.6 and JIRA 7.2.4.
Works for me, too!
In addiction to the steps mentioned above, i've had to rename the latest jdbc jar to the default Atlassian postgres jdbc name (in my case, from "postgresql-9.4.1212.jar" to "postgresql-9.1-903.jdbc4-atlassian-hosted.jar")
MacOSX 10.11.6, psql 9.6.1, JIRA 7.3.0
Please try using the JDBC connector v5.1.47 as JDBC 8.0.13 is not supported.
The following guide is helpful.
In addition, the supported platforms page is helpful if you are new to Jira(Welcome btw!)
Can you please confirm us your database type, and if the user used to connect with the database has the DROP permission? From previous cases, I've seen this same error when the database user was missing this permission
Since you are working in a clean instance, I would suggest you to create a new database for your JIRA instance then give all the database permissions, including the DROP, and try to setup JIRA again with this new database.
Same issue here!!! JIRA 7.1.5 (I just instal last version)
I TRY :
SET GLOBAL storage_engine = 'InnoDB';
CREATE DATABASE jira CHARACTER SET utf8 COLLATE utf8_bin;
GRANT ALL PRIVILEGES ON jira.* TO 'jira'@'localhost' IDENTIFIED BY 'jira@@jira';
GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP,ALTER,INDEX on jira.* TO 'jira'@'localhost' IDENTIFIED BY 'jira@@jira';
==========> ERROR : (Cannot add user, all the user directories are read-only.)
At page /secure/SetupAdminAccount.jspa
Note : i using root account
Please help me!
Hi, i'm facing the same problem with brand new download and license from Atlassian.
JIRA 7.1.5 on Windows Server 2008 , MSSQL 2008. The user has DBOwner permission.
Error: Cannot add user, all the user directories are read-only. When creating admin user.
This is emergency if anyone can help I really appreciated!
My solution may be limited in scope, but I had to revert to using PostgreSQL version 3 as version 4, when creating a new database, constantly throws the "user directories are read-only." I'm no tech wizard but my problem lied in the tool used to create the database.
Atlassian says that they are db-agnostic guys.
Also, they say that Postgres is their favorite DB.
Also, they say that Jira is pure-java app and doesn't care of kind of Linux running on.
Also, one of the most conservative distros - Debian 8 - is already ships with PostgreSQL 9.6 onboard.
As for me - Atlassian just must officially support PG 9.6 for their products.
I recently ran into this problem when setting up Jira with the following settings.
Jira Version - v7.6.9
Mysql version - 5.7.24
The problem was caused by using the JDBC connector listed above instead of the recommended version which is JDBC version 5.1.
The following guide has the steps needed and the link to the JDBC version 5.1 that is recommended.
This happened to me, when restoring a backup of an old version of Jira(7.1.10) to an AWS RDS postgres(9.6 and/or 10.4) database instance. I was able to resolve this by using an AWS RDS postgres 9.4 instance. So in my case it was database/application compatibility and deploying the application on an older version of postgres fixed it.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events