Topic: SOGo 2.3.0 sql-update HELP!

[julianweber]

I have inadvertently upgraded my SOGo to version 2.3.2.  The upgrade requires a script be run to change the MYSQL database.  The script is prompting for a password to MYSQL but the MYSQL root password is set to a random password and the SME Server documentation says not to change it. 

Due to the change, the calendar is not working in SOGo.  Can someone help me sort this out?

Julian

[guest22]

stephdl is your man.

[stephdl]

normally it is incorporated in the rpm, from which version you upgraded ???

[julianweber]

I don't know what version I upgraded from.  Unfortunately Yum reported an update via email with instructions to run the upgrade from command prompt.  I followed the Yum instructions and all seemed well.  I just noticed today that my calendar was not syncing from Thunderbird and started looking into it. 

Is there a way to look through the logs and find out?

[stephdl]

from what I recall it was a mysql issue, some fields needed to be created....I don't know if it was related.

look to /var/log/sogo/sogo.log

for the sogo version, you can look to /var/log/messages and /var/log/yum/yum.log

You use sogo as a caldav server ?

[julianweber]

I do use sogo for caldav.
The error in sogo.log looks like to be consistent with the mySQL database needing to have the script run.

Oct 06 17:39:40 sogod [2248]: <0x0x7fc70d8e26c8[GCSFolder]> ERROR(-[GCSFolder writeContent:fromComponent:container:toName:baseVersion:]): cannot insert content : <MySQL4Exception: 0x7fc70dbd6868> NAME:ExecutionFailed REASON:Unknown column 'c_description' in 'field list'
Oct 06 17:39:40 sogod [2248]: [ERROR] <0x0DB2A608[SOGoAppointmentObject]:9f1a7696-64e3-c140-8f9f-ceabf83bcf35.ics> write failed: <MySQL4Exception: 0x7fc70dbd6868> NAME:ExecutionFailed REASON:Unknown column 'c_description' in 'field list'
Oct 06 17:39:40 sogod [2248]: 10.10.10.2 "PUT /SOGo/dav/jwork/Calendar/D0D-525E0D80-F-626BB300/9f1a7696-64e3-c140-8f9f-ceabf83bcf35.ics HTTP/1.1" 500 214/853 0.043 - - 276K

[julianweber]

This is the yum.log  grepped for sogo.  It looks like I was on 2.2.16 and then on sep 08 upgraded to 2.3.1. 
I don't know what the Mar 08 00:29:09 semserver-sogo-1.3-12 is.


Mar 08 00:28:59 Installed: sogo-ealarms-notify-2.2.16-1.centos6.x86_64
Mar 08 00:29:03 Installed: sogo-2.2.16-1.centos6.x86_64
Mar 08 00:29:03 Installed: sogo-tool-2.2.16-1.centos6.x86_64
Mar 08 00:29:03 Installed: sogo-activesync-2.2.16-1.centos6.x86_64
Mar 08 00:29:09 Installed: 9:smeserver-sogo-1.3-12.el6.sme.noarch
Sep 08 09:22:58 Updated: sogo-2.3.1-1.centos6.x86_64
Sep 08 09:22:58 Updated: sogo-tool-2.3.1-1.centos6.x86_64
Sep 08 09:22:59 Updated: sogo-activesync-2.3.1-1.centos6.x86_64
Sep 08 09:23:00 Updated: sogo-ealarms-notify-2.3.1-1.centos6.x86_64
Sep 19 22:39:05 Updated: sogo-2.3.2-1.centos6.x86_64
Sep 19 22:39:05 Updated: sogo-tool-2.3.2-1.centos6.x86_64
Sep 19 22:39:05 Updated: sogo-activesync-2.3.2-1.centos6.x86_64
Sep 19 22:39:07 Updated: sogo-ealarms-notify-2.3.2-1.centos6.x86_64
Oct 06 12:58:40 Updated: 9:smeserver-sogo-1.3-15.el6.sme.noarch
Oct 06 13:36:20 Erased: smeserver-sogo
Oct 06 13:36:21 Erased: sogo-activesync
Oct 06 13:36:22 Erased: sogo-tool
Oct 06 13:36:23 Erased: sogo
Oct 06 13:36:28 Erased: sogo-ealarms-notify
Oct 06 13:40:13 Installed: sogo-2.3.2-1.centos6.x86_64
Oct 06 13:40:13 Installed: sogo-tool-2.3.2-1.centos6.x86_64
Oct 06 13:40:14 Installed: sogo-activesync-2.3.2-1.centos6.x86_64
Oct 06 13:40:14 Installed: sogo-ealarms-notify-2.3.2-1.centos6.x86_64
Oct 06 13:40:21 Installed: 9:smeserver-sogo-1.3-15.el6.sme.noarch

[julianweber]

As you can see below, I am logged in a root and trying to run the sql-update-2.2.17_to_2.3.0-mysql.sh script.

I don't know what username or database I should be using and I also don't have an SQL password.
Do you know?


[root@harry ~]# cd /usr/share/doc/sogo-2.3.2/
[root@harry sogo-2.3.2]# ./sql-update-2.2.17_to_2.3.0-mysql.sh
Username (root): mysql
Hostname (127.0.0.1):
Database (root): mysql
This script will ask for the sql password twice
Converting c_partstates from VARCHAR(255) to mediumtext in calendar quick tables
Adding c_description column as mediumtext in calendar quick tables
Enter password:
ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (111)

[stephdl]

did you reconfigure the server since the update ?

[julianweber]

I ran the following after the upgrade...

signal-event post-upgrade;  signal-event reboot

[stephdl]

As you can see below, I am logged in a root and trying to run the sql-update-2.2.17_to_2.3.0-mysql.sh script.

I don't know what username or database I should be using and I also don't have an SQL password.
Do you know?

take a look to /etc/e-smith/events/actions/sogo_upgrade_2.3....it is integrated

the mysql password can be found at

cat /etc/openldap/ldap.pw or cat /root/.my.cnf

[julianweber]

I just manually ran

/etc/e-smith/events/actions/sogo_upgrade_2.3

and now it is working. 

THANKS!

[stephdl]

please what is the output of

# locate sogo_upgrade_2.3

[julianweber]

[root@harry ~]# locate sogo_upgrade_2.3
/etc/e-smith/events/actions/sogo_upgrade_2.3
/etc/e-smith/events/post-install/templates2expand/etc/e-smith/sql/init/32sogo_upgrade_2.3
/etc/e-smith/events/post-upgrade/templates2expand/etc/e-smith/sql/init/32sogo_upgrade_2.3
/etc/e-smith/events/sogo-modify/templates2expand/etc/e-smith/sql/init/32sogo_upgrade_2.3
/etc/e-smith/templates/etc/e-smith/sql/init/32sogo_upgrade_2.3
[root@harry ~]#

[stephdl]

can you catch something in logs messages when you do 'signal-event sogo-modify'