After successful installation, admin account won't log in and gives no error message on screen

Richard Raether

After a successful installation of Jira Software, I try to log in with the admin account and password I created, but it doesn't work. There's no username or password error that appears on the screen. It simply clears the username and password boxes. I checked the catalina.out file from when I started it up and the last line was this:

11-Oct-2019 16:06:36.950 WARNING [http-nio-8080-exec-24] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI http://myserver@something.com:8080/rest/gadget/1.0/login, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.

Andy Heinzer

Hi Richard,

I understand that you have just setup Jira, but that you are unable to login.  What seems very strange here is that entering a bad password should have Jira give some feedback that the login was invalid.  The way you describe it would tend to indicate that either the HTTP request is bad in some way, which seems very unlikely, or that Jira has some other major configuration problem with the way it was setup.  I am afraid that the warning message you posted is not related to any login problems, that specific warning is known to be an extraneous message that is very common to see in the logs, see also JRASERVER-30406 .

There is a helpful guide you could follow to recover the admin password as noted in Retrieving the JIRA Administrator.  This has a couple of different ways that you can get into a Jira instance, such as by using a startup property, or by directly editing a specific table in the SQL database.

However if this is a fresh setup, and you have no existing data in the database you want, then it might just be easier to scrap the existing Jira database and start over.  By that I mean you can

1. stop Jira
2. delete the $JIRAHOME/dbconfig.xml file
3. The follow the database setup steps per Connecting Jira applications to a database.

For an environment that doesn't have any data we need, these steps can help to ensure that Jira is configured with the expected database settings and could restore a functional Jira site sooner than trying to troubleshoot the source problem here. 

Please let me know if you have any questions or concerns about these recommended steps.

Andy