Forum OpenACS Q&A: openacs.org upgrade status

Collapse
7: openacs.org upgrade status (response to 2)
Posted by Malte Sussdorff on
I succeded in executing the first two steps of the upgrade.sh script written by Joel on an openacs.org dump on my own server. To get all of it to work though, I had to install a couple of things first.
  1. Install PostgreSQL 7.2.5 on my computer (in /usr/local/pg-7.2.4)
  2. Install intarray support for PG 7.2.5
  3. Install PG 7.4.5
  4. Install intarray support for PG 7.4.5
  5. Dump the openacs.org database (on angora): /usr/local/pgsql-7.2.4/bin/pg_dump -f /web/openacs.org/openacs.org-2004-09-28.dmp -p 5724
  6. Copy the upgrade.sh script (/web/upgrade-oo-5/etc/upgrade.sh) and the .dmp file to my machine.
  7. Make a fresh checkout of oacs-5-1
  8. Make changes to upgrade.sh to reflect my setup of files
  9. Start screen (my internet connection is reset every 24 hours...)
  10. sh upgrade.sh 2>&1 >upgrade.log
  11. detach screen
The first two steps roughly took 3 hours to complete, the 3rd step takes ages and is still running, will post once it is finished.
Collapse
Posted by Malte Sussdorff on
I got further in the upgrade, now I need some help from someone else. The following packages are not available in OpenACS 5.1 anymore:

/acs-content/
/acs-util/
/acs-workflow/
/irc-logger/
/viewcvs/

If someone has the time to at least port irc-logger and viewcvs from the current code of openacs.org to be suiteable for and useable in OpenACS 5.1, that would be great.

Collapse
Posted by Malte Sussdorff on
daveb: sussdorff: you don't need acs-workflow, acs-util or acs-contnet, you can uninstall those.

jcdldn: +viewcvs has no datamodel and irc-logger is in contrib

I guess we are set then :)

Collapse
Posted by Malte Sussdorff on
I forgot to add that I had to create the user upgrade-oo-5 in both databases. Furthermore, as I was not running the upgrade as user upgrade-oo-5 I had to create a user for myself as well.
Collapse
Posted by Malte Sussdorff on
Good news, the upgrade runs through in 45 minutes on my machine. The bad news: There are still some errors and it does not work, so I have to figure out what to do about it. Just wanted to let you know.
Collapse
Posted by Malte Sussdorff on
Restarted the upgrade process again, let's see how far I get this time. Forgot to change the "fsync" line in my postgres installation which resulted in a considerably longer import...
Collapse
Posted by Malte Sussdorff on
The good news: It works, meaning I got the kernel, content repository file-storage and others to work.

The bad news: Forums takes *AGES* to upgrade. And bug-tracker does not upgrade well due to problems with workflow, but I will dig into this once forums has been finished.

Collapse
Posted by Malte Sussdorff on
More things I figured out.

Do not run:

notifications/upgrade-4.6.1-4.6.2

acs-content-repository/upgrade-4.6.1-4.6.2

etp/upgrade-1.1d-1.2

bug-tracker/(all upgrade.sql). Run them manually after the upgrade. Make sure to use the same user that is the owner of the site.

file-storage/upgrade-4.6.1-4.6.2

It seems that the site is already running on 4.6.2 though noone told the packages this :).

Furthermore, it is wise to run all SQL scripts for forums starting with the second and doing the first one last. I actually added the other upgrade scripts manually to the first one, so it (hopefully) speeds up a little bit.

Collapse
Posted by Malte Sussdorff on
Dave actually wrote it all down already :).

https://openacs.org/projects/openacs/5.0/upgrade-openacs-org

Collapse
Posted by Malte Sussdorff on
I did the following and succeded in all but bug-tracker (to my knowledge).

Run the upgrade.sh.

Copy zzz-upgrade.tcl to /tcl

Start the server.

Remove zzz-upgrade.tcl

Restart the server.

got to /acs-admin/apm/packages/install.

Select *all* upgrades and workflow. *SKIP* bug-tracker.

When you come to select the SQL files, skip the following:

notifications 4.6.1-4.6.2
content-repository 4.6.1-4.6.2
subsite 4.5-xxx
etp 1.1d-1.2
fs everything <4.6.2
forums *all*

install (should run smoothly)
restart the server
install the bug-tracker upgrade
unselect all data-model scripts and upgrade.
run bug-tracker.sql (special file)
restart the server
realize bug-tracker does not work 😟.

You can check it out at http://sussdorff.dyndns.org:8000

Collapse
Posted by Malte Sussdorff on
Bugtracker woes solved, now we just have to make the site look like before again. For this we need to make sure the ETP Applications work and that the /www/templates/general-master template works. Suggestion is to ammend /www/default-master to include the looks of /www/templates/general-master.

In a first step I commented out #oacs_set_login_vars in /www/templates/general-master so you can check out the master template as it is supposed to be at samoyed.

Collapse
Posted by Malte Sussdorff on
Finished :). Well, kindoff, but the site is running happily at http://samoyed.furfly.net and looks just like openacs.org.

A couple of things are still missing:

- Forums pagination
- Full Text Search
- Performance

Especially for performance the developer support is still working, so feel free to make use of it, though don't expect the nice toolbar due to the fact that I did not mix the master templates.

Please take a look at the site and provide feedback, as I'd like to upgrade soon so to avoid Andrew et.al. to chase after queries that bring down openacs.org if we know we will upgrade very soon now (TM).

Collapse
Posted by Nima Mazloumi on
For all who are interested in a great ticket system:
http://doc.otrs.org/1.2/en/html/

Maybe there are some concepts we can use for bug-tracker.

Greetings,
Nima