I have the same problem.

Quick note: manually running the migration script after the installation fixes the calendar issue.

Is there anything else I have to do before running the script?
Stop some services etc?
Or should I just execute script?

Just run the script. It is mentioned in the upgrade instructions - both in the guide and in the annonce message. We will most likely never automate this process.

I ran script, got error:

2015-06-03 17:31:11.940 sogo-tool[16657] ERROR(+[GCSFolderManager defaultFolderManager]): default 'OCSFolderInfoURL' is not configured.
Couldn't fetch OCSFolderInfoURL value, aborting

changed update script to this:

indextable=$(sogo-tool dump-defaults -f /home/sogo/GNUstep/Defaults/.GNUstepDefaults | awk -F\" '/ OCSFolderInfoURL =/ {print $2}' | awk -F/ '{print $NF}')
if [ -z "$indextable" ]; then
echo "Couldn't fetch OCSFolderInfoURL value, aborting" >&2

My GNUstepDeafults file:

<dict>
<key>OCSFolderInfoURL</key>
<string>mysql://sogo:tormsogosql@localhost:3306/sogo/sogo_folder_info</string>
<key>OCSSessionsFolderURL</key>

What am I missing?

sudo -u sogo sogo-tool dump-defaults
{
OCSFolderInfoURL = "mysql://sogo:tormsogosql@localhost:3306/sogo/sogo_folder_info";
OCSSessionsFolderURL = "mysql://sogo:tormsogosql@localhost:3306/sogo/sogo_session_folder";

An alternative would be to display upgrade instructions during apt-get upgrade, especially when a specific migration operation is required.

One step forward and another error:

sudo -u sogo sh sql-update-2.1.17_to_2.3.0-mysql.sh

Username (sogo): sogo
Hostname (127.0.0.1): 127.0.0.1
Database (sogo): sogo
sql-update-2.1.17_to_2.3.0-mysql.sh.bak: 41: sql-update-2.1.17_to_2.3.0-mysql.sh.bak: Syntax error: "(" unexpected

line 41:

function adjustSchema() {
oldIFS="$IFS"
IFS=" "
part1="echo -e \"ALTER TABLE $table MODIFY c_partstates mediumtext;\\n\"";
part2="echo -e \"ALTER TABLE $table ADD COLUMN c_description mediumtext;\\n\"";
sqlscript="$sqlscript$part1$part2"
IFS="$oldIFS"
}

Next error:

bash sql-update-2.1.17_to_2.3.0-mysql.sh
Username (sogo): root
Hostname (127.0.0.1): localhost
Database (sogo): sogo
This script will ask for the sql password twice
Converting c_partstates from VARCHAR(255) to mediumtext in calendar quick tables
Enter password:
Enter password:
ERROR 1060 (42S21) at line 1: Duplicate column name 'c_description'

Was able to update my database. So this topic can be closed.

Same problem on automatic upgrade on Ubuntu system.

sudo -u sogo sogo-tool dump-defaults does display
{
...
OCSFolderInfoURL = "mysql://sogo:xxxxxxx@localhost:3306/sogo/sogo_folder_info";
OCSSessionsFolderURL = "mysql://sogo:xxxxxxxxx@localhost:3306/sogo/sogo_sessions_folder";
...

sudo -u sogo bash sql-update-2.1.17_to_2.3.0-mysql.sh

fails with: "Couldn't fetch OCSFolderInfoURL value, aborting"

Suggestions?

I have exactly the same problem.

Anyone has suggestion?

I've tracked down the problem to the assumption that /etc/sogo/sogo.conf contains the defaults for the current installation. Ubuntu does not and it has not changed this with previous upgrades.

While the upgrade notes for 2.0.5 provide instructions for this transition, I am hesitant to follow all these notes as Ubuntu seems to follow its own set of conventions regarding the placement of some settings files.

My guess is that one alteration is needed to those instructions. The final instruction should be changed from

sudo -u sogo mv ~/GNUstep/Defaults/.GNUstepDefaults \
~/GNUstep/Defaults/GNUstepDefaults.old

to

sudo -u sogo mv /var/lib/sogo/GNUstep/Defaults/.GNUstepDefaults \
/var/lib/sogo/GNUstep/Defaults/.GNUstepDefaults.old

So, is there someone from the Ubuntu package group who can confirm the steps are for Ubuntu to move to a set of defaults in /etc/sogo/ ?

I managed to get past the "Couldn't fetch OCSFolderInfoURL value, aborting" error with the tip above. But when I try to run the script now, everytime I get sql-update-2.1.17_to_2.3.0-mysql.sh: 41: sql-update-2.1.17_to_2.3.0-mysql.sh: Syntax error: "(" unexpected

This is NOT an Ubuntu box btsihw, but a Debian 7 box.

@raido: you said you were able to update your database. Care to share with the class how you managed that? :)

@ludovic: I think that the severity should be upgraded, this affects quite a lot of people and a large portion of SOGo is now unuseable for the people affected!

I bit the bullet, and it seems to have worked on my Ubuntu machine.

I ran the upgrade instructions for 2.0.5 as root, changing the rename line as noted in my post #8618 above (http://www.sogo.nu/bugs/view.php?id=3230#c8618)

I was then able to run the update script for 2.3. (I did move the sample settings in /etc/sogo/ first, so you may need to do that too.)

YMMV.

Debian7: Move /etc/sogo/sogo.conf out or remove "-f /etc/sogo/sogo.conf" from the script.

I run the script by sogo user, but had to change "sogo-tool" to "/usr/sbin/sogo-tool".

Since I just upgrade to 2.3.0 I will try to add some clarifiying comments to some of the problems above:

Comment #8618:

In current ubuntu package (sogo-2.3.0-1) /etc/sogo.conf is included in the package. So it should be safe to perform the documented upgrade procedure to move configuration to sogo.conf.

Comments #8583 and #8627:

The syntax error '"(" unexpected ...' occurs if the script is executed with another interpreter than bash. Ubuntu uses dash by default which uses another function declaration syntax (see https://wiki.ubuntu.com/DashAsBinSh for more information). Try executing "bash update-sql....sh" instead of "sh update-sql....sh". Otherwise you have to remove the "function" keyword (and probably have to edit the escape sequences in echo expressions as well).

Comment #8572
An alternative would be to display upgrade instructions during apt-get upgrade, especially when a specific migration operation is required.

This would be in my opinion expected behavior and would have saved us from the (calendar) downtime and the trouble attached to that.

My Workaround for Ubuntu/Debian was to execute following after the upgrade:

chown -R sogo /etc/sogo
sudo -u sogo sogo-tool dump-defaults > /etc/sogo/sogo.conf
sudo -u sogo /usr/doc/sogo/sql-update-2.1.17_to_2.3.0[-mysql].sh

Installation/upgrade of binary packages from now on will show an on-screen note to remind the system maintainer to check for database schema upgrades.

Already included in nightly builds; will be part of the next set of releases for v2 and v3.