Updates for ]project-open[ 3.x

[[tutorial_updates#32-34|Update from 3.2.x to 3.4.x]]
Update from 3.1. to 3.x.
Troubleshooting cvs issues on linux

Update from 3.2.x to 3.4.x - Step by Step instructions

Updating your system requires a connection to our CVS server. If you are behind a firewall, make sure that TCP port 2401 is open and follow the steps as described underneath:

a) Run a database backup

http://[YOUR_SERVER]/intranet/admin/backup/

b) Make a backup of the /web/projop/packages folder:

Use putty to open a SSH console to your Virtual machine (default user: root, default password: root)
In order to monitor cvs output make sure that in the putty configuration attribute Window - Lines of scroll backis at least 10000.

cp -r /web/projop/packages /web/projop/packages.backup

c) Continue working with the console - become user 'projop':

su - projop

d) Change to directory /web/projop/packages/

cd /web/projop/packages/

e) Use cvs to update your packages folder:

cvs login (no password - just 'enter')

cvs update -dPA

Monitor the output and watch for CVS conflicts, indicated with a 'C' at the beginning of a line. Conflicts usually happen only when local code had been changed.
Conflicts not resolved will lead to a malfunctioning system so please watch the output carefully.

f) Use the packet manager in the ADMIN section to update your modules and follow instructions given on the update pages:

http://[YOUR_SERVER]/acs-admin/apm/packages-install?update_only_p=1

g) Restart your system

http://[YOUR_SERVER]/acs-admin/server-restart

h) wait a moment until the server is up and running again and go to your 'home'

http://[YOUR_SERVER]/intranet/

Updates from 3.1.x

This particular upgrade can only be done semi-automatically because we had to make some adjustments to basic 'pillars' of the application in order to prepare ]po[ better for future requirements such as the integration of leading ERP systems. Please search the forum for information about the steps involved. Thomas Wabner reported a successful update from 3.1 to the VM3.2 and posted the steps involved on his blog . In case you want us to help you with this update please get in touch with us.

Troubleshooting cvs issues on linux

In case cvs updates do not perform as expected please check the following:

a) Check availability of CVS server:

ping berlin.dnsalias.com

In case responses do time out please check your DNS server entries in /etc/resolv.conf

b) Check /etc/hosts

Some older ]po[ VM's have an entry to a local IP for berlin.dnsalias.com Please delete this entry.

c) Check if you can connect to the cvs server:

su - projop
cvs login

usually results in

Logging in to :pserver:anonymous@berlin.dnsalias.com:2401/home/cvsroot
CVS password:

This prompt is send from the local cvs tool. Just hit for 'no password' and you should be able to execute cvs commands. Check this by doing the following:

cd /web/projop/packages/intranet-core/
cvs status intranet-core.info

The result should be something like:

===================================================================
File: intranet-core.info        Status: Needs Patch

   Working revision:    1.104
   Repository revision: 1.108   /home/cvsroot/intranet-core/intranet-core.info,v
   Sticky Tag:          (none)
   Sticky Date:         (none)
   Sticky Options:      (none)

d) CVS server busy?

In case everything worked fine, a cvs update might time out due to to maxim number of allowed to connections. Please try to run the update at a later point in time again.

References to this Page: en:faq_maintenance, en:tutorial_updates Categories: Tutorials (Contents)

Contents

Updates for ]project-open[ 3.x

Update fro­m 3.2.x to 3.4­.x - Step by Step instructions­

Updates from 3.1.x

Troubleshooting cvs issues on linux

Update from 3.2.x to 3.4.x - Step by Step instructions