v1.7 server migration suddenly not working.

Submitted by Guest on Sat, 21/01/2017 - 10:43

Implementation discussion

I've been mucking around now for about 12 months trying to migrate a windows installation to a linux server (yes I know... slow and out of date now).

I restored a database backup from the old server earlier in the week and managed to get it working (mostly) without a printer install and with the documents still failing (which is doing my head in because there in the database so I can't for the life of me work out why there not being found).. but... the main problem now is that I installed cups on the server (ubuntu 14.04) and now when I try and go to anything under openvpms in the browser I'm getting resource not found and it has me totally tossed (knowing nothing about this java *(&&&^).

I'm pretty good with linux, javascript and all of that, but Java just does my head in.

I did make some changes to the database (installing phpmyadmin amongst other things) and it could be that I've broken the login openvpms is using (although I can log in from the command line using openvpms/openvpms) or something else entirely but I have no idea where to even start looking.

Where are the database settings held in the config?

Tomcat seems to be working (I can get to the default page), the permissions look to be OK, where do I start looking for errors?

Peter

Re: v1.7 server migration suddenly not working.

Submitted by tanderson on Sat, 21/01/2017 - 22:33.

Look in openvpms-full.log in the tomcat logs/ directory. It should indicate any OpenVPMS start-up problems.

Re: v1.7 server migration suddenly not working.

Submitted by pnunn (not verified) on Mon, 23/01/2017 - 20:02.

Thanks @tanderson that got it working again. Turns out I'd changed the bind address for the database to allow phpmyadmin to work which broke things.

Now if I could just get soffice to work.

Off to another thread for that one.

Peter.

Re: v1.7 server migration suddenly not working.

Submitted by tanderson on Mon, 23/01/2017 - 23:01.

If you set up soffice to be launched by OpenVPMS (the default), it will try and store its settings in the home directory of the user that launched tomcat.

E.g. /home/tomcat7/.openoffice

The tomcat user home directory must therefore have user read, write and execute permissions.

Re: v1.7 server migration suddenly not working.

Submitted by pnunn (not verified) on Fri, 27/01/2017 - 11:20.

Thanks again for the input @tanderson. After putting in some serious time (rather than just mucking around) I have now got the system transferred to the new server at 1.7 and working happily it seems. Now however, I have to decide on weather to upgrade the running system to 1.9 first and then migrate again or put this one into production and upgrade it... Any thoughts?

Re: v1.7 server migration suddenly not working.

Submitted by tgething (not verified) on Fri, 27/01/2017 - 12:09.

I would be tempted to upgrade the 'new server' to 1.9 so that you know that it will happily run 1.9, and then do the following:

stop Tomcat on the production (1.7) system
create a dump of the production (1.7) system
restore this into the 1.9 'new server' system
run the 1.7 to 1.8 then the 1.8 to 1.9 migration sql's on the 'new server' system
use archload to load the 1.9 archetypes into the 'new server' system
use templateload to load the 1.9 templates into the 'new server' system
have a quick play - if all OK, adjust things so that the users now use the 1.9 'new server' system; if not, restart Tomcat on the 1.7 production system and let the users use this while you figure out what went wrong.

Note that the above approach will allow you to get things set for 1.9: specifically the use of the letterhead facility so that you can switch away from customised invoices etc; and also to switch to using the inbuilt docloader facility (instead of running docloader using cron or the windows scheduler)

That is having upgraded the 1.7 system on the new server to 1.9, you can now use it as a test/training/play with system until the time that you use steps 1-7 above to switch production to the new system.

Regards, Tim G