Hi again...
so, after upgrading to SOGo 2.0.4b-1 on lucid, I decided to upgrade to
Ubuntu Precise (finally).
Now after the dist-upgrade process, apt told me to upgrade sogo from
2.0.4b-1 to 2.0.4b-1 (yes, seriously).
I thought, it would be ok to do so - possibly just changes because of
the change of the repository from lucid to precise.
Now I get the following error (partially in German, sorry):
sogo (2.0.4b-1) wird eingerichtet ...
* Restarting SOGo sogo
No process in pidfile
'/var/run/sogo/sogo.pid' found running; none killed.
/etc/init.d/sogo: line 61: 4500 Segmentation fault (core dumped)
start-stop-daemon -c $USER --quiet --start --pidfile $PIDFILE --exec
$DAEMON -- $DAEMON_OPTS
invoke-rc.d: initscript sogo, action "restart" failed.
dpkg: Fehler beim Bearbeiten von sogo (--configure):
Unterprozess installiertes post-installation-Skript gab den Fehlerwert
139 zurück
Fehler traten auf beim Bearbeiten von:
sogo
Any ideas, how to fix this?
Best regards and thanks in advance,
Peter
--------------------------------------------
Bixa TechnoConsulting
Web: www.bixa.cc
Mail: [email protected]
Tel.: 0676 / 6384970
On 2013-03-13 17:46, Peter Schmidt wrote:
Hi Christian!
On 2013-03-13 17:20, Christian Mack wrote:
Am 2013-03-13 16:24, schrieb Peter Schmidt:
Hi!
I was happily using SOGo 1.3.12c (I use it for now only to be
independent from Google for syncing my contacts and calendars and as a
playground for future installations).
I decided to upgrade to 2.0.4b-1 via aptitude now and all worked like a
charm.
Then I ran the sql-upgrade scripts and made a mistake (because to me the
naming and documentation is not so clear):
I ran the sql-update-1.3.16_to_1.3.17-mysql.sh script, instead of the
sql-update-1.3.11_to_1.3.12-mysql.sh, which I think I should have ran
first.
Now when I try to run the latter one, I get an Error:
ERROR 1068 (42000) at line 1: Multiple primary key defined
Does this mean, that my DB is already broken, or are the scripts
supposed to be run when the version was below the ones given in the
filename? As I said, to me the naming of the files and documentation in
the userguide is not so clear.
Are the section titles n chapter "Upgrading" - e.g. "1.3.17" - meant
like "Upgrading FROM 1.3.17" or "Upgrading to 1.3.17" - because the
first paragraph says "...when upgrading to the current version...", so I
would read it as "upgrading FROM 1.3.17".
Is there a way to check the integrity of the database?
My suggestion to ease the handling of database upgrades in the future:
Adding a version table that keeps track of the db structure upgrades
would allow checking of the validity of an update and would therefore
allow db-auto-update scripts. This is a widely accepted best practise
anyway.
As you already have a 1.3.12 version of SOGo, you do not use
sql-update-1.3.11_to_1.3.12-mysql.sh at all!!!
Running sql-update-1.3.16_to_1.3.17-mysql.sh is all you have to do.
Thanks, well then I am fine.
The more I think about it, the more it makes sense to me now. Still I
think the documentation about upgrading could be a bit more detailed and
the mentioned database version table would be an easy feature that can
make a lot things easier when it comes to updating versions.
Best regards,
Peter
--
[email protected]
https://inverse.ca/sogo/lists
