Project

General

Profile

Configuration file that determines which iteration of Redmine to use

Added by lmind stuffs almost 8 years ago

I'm trying to track down which redmine folder is actually being used by a system. For some reason, previous upgrades required leaving older folders in place and I'd like to know which file controls which folder redmine should use. This is on a CentOS 6 64-bit system if that matters at all.


Replies (6)

RE: Configuration file that determines which iteration of Redmine to use - Added by Pavel Potcheptsov almost 8 years ago

It depends of which web server is using.

ps axuw | grep ruby

RE: Configuration file that determines which iteration of Redmine to use - Added by lmind stuffs almost 8 years ago

That command yields no output. Should ruby be running as a process?

The intent is to pull a redmine database (older version) over from an older machine we're attempting to upgrade from CentOS 5 to latest version of CentOS 6.

Does something like /etc/httpd/conf/httpd.conf define which Redmine to use? Also, are there any guides I could follow that would outline necessary steps to get this job done?

Thanks,
John

RE: Configuration file that determines which iteration of Redmine to use - Added by Pavel Potcheptsov almost 8 years ago

There are two redmine instances that work simultaneously on server.
The idea is to find process that opened production.log file. And this file leads to path where redmine is located.

# lsof | grep ruby | grep "production.log" 
ruby       1525    root    6w      REG      253,0  9199838      26253 /var/www/rm303/log/production.log
ruby      15957    root    6w      REG      253,0   289687      31509 /var/www/ruby/log/production.log

RE: Configuration file that determines which iteration of Redmine to use - Added by lmind stuffs almost 8 years ago

Also yields no output.

So, maybe I need to back up a little. As I said earlier, the goal here was to upgrade our running CentOS 5 server to 6, upgrading the version of Redmine, Ruby, rails, etc. I've managed to dump the database from CentOS 5 machine, pull it over to the new Redmine, but from here, I'm having trouble knowing just what I'm lacking for Redmine to be considered ready for production as I wasn't the one who setup Redmine on the older machine.

Any chance there's a guide or something I could look at? All the guides I've seen thus far seem to only discuss upgrading Redmine on the same machine (heavily scripted) and I'd like something that goes into a bit more detail about what all needs to happen for Redmine to stand up on the new machine.

RE: Configuration file that determines which iteration of Redmine to use - Added by Pavel Potcheptsov almost 8 years ago

what needs to happen for Redmine to stand up on the new machine.

- checkout or download and unpack last rm version
- install as usual to get new redmine without data
- change database.yml and point to real database (old)
- proceed with database migration step and restart redmine

    (1-6/6)