On Sun, Oct 30, 2011 at 09:12:22AM -0400, Ludovic Marcotte wrote:
That's probably a sign of having old SOPE packages around after
proceeding with the SOGo update. Make sure you update all SOPE
packages to the latest version and restart the SOGo service after.
Yes, looks like you had some
Am 30.10.2011 08:29, schrieb Christian Naumer:
After the Upgrade to 1.3.9 I get the following Error in sogolog:
Oct 30 08:22:44 sogod [11571]: [ERROR] 0x0xa38050c[GCSFolder]
-[GCSFolder fetchFields:fetchSpecification:ignoreDeleted:]: cannot
execute quick-fetch SQL 'SELECT
Am 30.10.2011 09:53, schrieb Christian Naumer:
There are some others as well for
a.c_deleted
b.c_component
but there are only c_component fields in the table and no fields with
deleted in there. But this is the same in the working system on Centos6
I have to correct this the
Am Sonntag, 30. Oktober 2011 schrieb Christian Naumer:
Am 30.10.2011 09:53, schrieb Christian Naumer:
There are some others as well for
a.c_deleted
b.c_component
but there are only c_component fields in the table and no fields
with deleted in there. But this is the same in the
Same problem on SL6.1: sogo seems to attempt fetching fields from the quick
tables that are really in the full tables:
Oct 30 12:46:27 sogod [5457]: [ERROR] 0x0x2d063b8[GCSFolder] -[GCSFolder
fetchFields:fetchSpecification:ignoreDeleted:]: cannot execute quick-fetch SQL
'SELECT
On 30/10/11 07:03, Martin (Lists) wrote:
And if I change the table names ('b' for the _quick table and 'a' for
the normal one) it went through smoothly.
Besides this sogod tries to load libgnustep-base.so.1.23 and
libgnustep-base.so.1.20. The command 'ldd /usr/sbin/sogod | grep base'
reports:
Am Sonntag, 30. Oktober 2011 schrieb Ludovic Marcotte:
On 30/10/11 07:03, Martin (Lists) wrote:
And if I change the table names ('b' for the _quick table and 'a'
for the normal one) it went through smoothly.
Besides this sogod tries to load libgnustep-base.so.1.23 and
Same here, thank you for the quick solution! My sope packages were less
outdated but still outdated. I think the problem yum wise was this: new
version is 1.3.9-2, old version had a higher number so yum considered it
newer.
--
met vriendelijke groet,
Jeroen Beerstra
j.beers...@upcmail.nl
--
