3 registered users
in last 24 hours
Updates for ]project-open[ 3.x / 4.x
Linux: Update von 4.0.x to the most recent version
Please follow LINUX:Update from 3.2.x to 3.5.x (stable) - Step by Step instructions but update from CVS HEAD: csv update -dPA instead from stable branch b3-5-0-patches as described below. Please note that you'll update from the "cutting edge" version until we have released a stable branch, so you should better know what you do!
LINUX: Update from 3.2.x to 3.5.x (stable) - 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
b) Make a backup of the /web/projop/packages folder:
Use putty to open a SSH console to your server/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 back" has a value of 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 to the stable version 3.5:
cvs login (no password - just 'enter')
cvs update -r b3-5-0-patches
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:
g) Restart your system
h) Wait a moment until the server is up and running again and go to your 'home'
Windows: Update from 3.2.x to 3.5.x - Step by Step instructions
Probably the easiest way to manually update the WIN version of ]po[ is using the Open Source tool TortoiseCVS which is available for download from their website.
After installation, new items are added to the context menu (right mouse click) of the Windows File Manager.
Now you can update your server using TurtoiseCVS:
a) Run a database backup
b) Make a security copy of the packages folder.
Default location is C:/project-open/servers/projop/packages/
c) Use TurtoiseCVS to update all packages
Open a WINDOWS File Manager and navigate to your "packages" folder. Mark all directories this folder contains, right-click on the selection and choose CVS update Special from the context menu and select branch 'b3-5-0-patches' .
Monitor the output and watch for CVS conflicts that are indicated with a 'C' at the beginning of a line. Conflicts usually occur only when local code had been changed.
Conflicts not resolved will lead to a malfunctioning system so please watch the output carefully. In case you have done some local changes to the application you can resolve those conflicts manually.
If TurtoiseCVS indicates conflicts even though you have not done any changes to the code, look at the messages and follow the instructions given there.
In many cases deleting the affected files and repeat the CVS update should resolve the issue.
d) Run update scripts
If you log on to ]po[ as a System Administrator you should find on home (http://localhost:8000/intranet/) a portlet listing update scripts to be executed:
Alternativiley use the packet manager in the ADMIN section to update your modules and follow instructions given by the ]po[/OpenACS Update Wizard:
e) Restart your system
Wait a moment until the server is up and running again and go to your 'home' http://localhost:8000/intranet/
[Please note that in some WIN versions you might need to stop/start the web server manually using the scripts accessible through the Windows START (]project-open[/ Stop ]project-open[ / Start ]project-open[) menu.]
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:
1) Check availability of CVS server:
In case responses do time out please check your DNS server entries in /etc/resolv.conf
2) Check /etc/hosts
Some older ]po[ VM's have an entry to a local IP for berlin.dnsalias.com Please delete this entry.
3) Check if you can connect to the cvs server:
su - projop
usually results in
Logging in to :pserver:email@example.com:2401/home/cvsroot
This prompt is send from the local cvs tool. Just hit ENTER for 'no password' and you should be able to execute cvs commands. Check this by doing the following:
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)
4) 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.