Keywords: Redmine - OS X - Technical issue - OtherDescription: Initial installation was done in 2014 under OS X 10.8 and survived an update to OS X 10.9.5 with no issues. Worked still fine.After exchanging the internal HD by cloning it and jumping to OS X 10.12.6 in December 2017 no test for the Bitnami Redmine stack was performed by me.

When I now try to start the Redmine stack again, the Application log from the "manager- osx" app shows the following output:

thanks for taking time and checking my issue. I really appreciate the hard work being done to provide complex tools readily available.

After doing additional reading following the creation my posting above, I came to the same conclusion: my installation is far too old and a new installation is strongly advised.

I tried to follow the Bitnami Redmine upgrade instructions but ran into several problems even before doing the steps:

1) the whole Redmine instruction page jumps - in some sections - back and forth between the OS X installer version (the old method) and the OS VM version (the new method). But as of now, a Redmine package for OS X is only available as VM, not as an installer. https://bitnami.com/stack/redmine/installer

2) The upgrade instruction section does not take into account that files have been saved as attachements to Redmine tickets. Therefore the "files" folder from the htdocs folder has to be copied manually to the new installation besides doing the MySQL database dump. This was confirmed in another community posting but not in the instructions.

3) The new OS X VM approach isolates the Redmine stack totally from the surrounding OS X, file wise and IP wise. I appreciate that no more lib issues may arise from this move. But now all my knowledge aquired regarding all the file path on localhost is useless as the Bitnami app folder is mounted as NFS volume, which itself separates logically from the surrounding Debian as part of the VM, but this is only visible for the OS X Terminal user who fiddles around with PWD and LS. And copying the MySQL database dump requires a writeable folder which is also not specified. In the end I have choosen the htdocs folder which was fine after CDing myself there for the import command.

The import itself ran fine with no errors, all instructions were accurate and understandable. My customised Redmine Login paged appeared and I was very pleased to see it again after a long time.

But now I am facing the next issue: my Redmine user credentials are no longer accepted by the system. Also written down in a TXT file there should be no uncertainty about what to enter. Ok, in general I open PhpMyAdmin and open the user table to fix this. As the old localhost address from the installer version is no longer available (see #3) there is a hard coded link to instructions on the Redmine Login page pointing to this URL:https://docs.bitnami.com/installer/apps/redmine/components/phpMyAdmin/

Sorry, I cannot work with instructions from a 404 page. I tried to find a better page and ended here:

And thanks for reading that much - but I always want things to be fixed if they are broken, and the OS X sections need some inspection.

Thank you for reporting this. I'll help you with the upgrade process and I'll also share this information with the documentation team to improve our pages

Carsten_BN-Issues:

1) the whole Redmine instruction page jumps - in some sections - back and forth between the OS X installer version (the old method) and the OS VM version (the new method). But as of now, a Redmine package for OS X is only available as VM, not as an installer. https://bitnami.com/stack/redmine/installer

Yes, we only offer the OS X VM for Redmine

Carsten_BN-Issues:

2) The upgrade instruction section does not take into account that files have been saved as attachements to Redmine tickets. Therefore the "files" folder from the htdocs folder has to be copied manually to the new installation besides doing the MySQL database dump. This was confirmed in another community posting but not in the instructions.

Thank you for sharing this information.

Carsten_BN-Issues:

And copying the MySQL database dump requires a writeable folder which is also not specified. In the end I have choosen the htdocs folder which was fine after CDing myself there for the import command.

You can also create a new folder and modify its permissions using the "Open Terminal" option in the OS X VM

sudo mkdir -p /opt/bitnami/temp
sudo chmod 777 /opt/bitnami/temp/

And copy the file to that temp folder.

Carsten_BN-Issues:

The import itself ran fine with no errors, all instructions were accurate and understandable. My customised Redmine Login paged appeared and I was very pleased to see it again after a long time.

But now I am facing the next issue: my Redmine user credentials are no longer accepted by the system.

Did you remove the Redmine database before importing your .sql file?

Carsten_BN-Issues:

As the old localhost address from the installer version is no longer available (see #3) there is a hard coded link to instructions on the Redmine Login page pointing to this URL:https://docs.bitnami.com/installer/apps/redmine/components/phpMyAdmin/

We are working on fixing this issue in the installers. Thanks for reporting this

Carsten_BN-Issues:

Sorry, I cannot work with instructions from a 404 page. I tried to find a better page and ended here:

Thank you again - especially for pointing to the current PhPAdmin method for the new OS X VM. Again, a very good approach to deny default access to a critical subsystem if the main system goes into production and is open for the planet.

The MySQL access allowed me to peek into the user table and to figure out that I made a terrible mistake in the past when I performed my first update attempt of the Bitnami Redmine stack three years ago. I messed up user account names which might be related to a long frustating journey through man pages, readmes and howtos available at that time - that's all what I remember from that day.

To make a fresh start now, I followed your advice and went through all import steps again and ended successfuly in my old Redmine installation. Thank you!

But now Redmine itself showed errors on some pages. I remembered that I installed several plugins and checked again the page section you recommended. And to my surprise the Troubleshooting section below showed most of the missing information necessary to fully update a Bitnami Redmine stack.

I ended up copying the most of the two sections into an BBEdit window and rearranged the order a little bit. Then I went though all steps once again: I copied (and updated) the plugins and the files folder, dropped the database, created a new one, granted permissions and imported the database dump etc. And I let the Ruby magic stuff happen.

Now nearly everything is up and running as expected. But only 2 out of 3 plugins are visible in the plugins section, and only 1 of this 2 is working as expected. But that is another story.

Long story short: documentation has to meet reality not only for 95%. Being a support guy by myself I know how important this is. Please let the documentation team know that all pieces are there, but only have to be glued together in a helpful manner.

Thanks again for reading that much, but I want the products I use to be great - and this can only be achieved by shipping them with all information.

Long story short: documentation has to meet reality not only for 95%. Being a support guy by myself I know how important this is. Please let the documentation team know that all pieces are there, but only have to be glued together in a helpful manner.

Thank you for sharing all this information here, I forwarded it with our documentation team and it will take care of updating it to improve the experience of the users.