|
|
first test done with TB.
tested also with lastet nightly:
while accepting an invitation "noch'n Neuer Termin"
with web client i've got a popup:
Warning
received code: 500 error: <?xml version="1.0" encoding="ISO-8859-1"?> <html xmlns="http://www.w3.org/1999/xhtml"> <body><h3>An error occurred during object publishing</h3><p>fatal pgsql error (channel=<0x0x2783448[PostgreSQL72Channel]: connection=<0x0x23e3de8[PGConnection]: connection=0x0x26b1740>>): FEHLER: Syntaxfehler bei »n« ZEILE 7: ...ck', 1, 0, 'vevent', 0, 1321437600, 0, '', 'noch\'n Neuer Te... ^ </p></body> </html> |
|
wsourdeau
2011-11-15 14:44
viewer
~0003005
|
Hi,
Can you list which versions of the SOPE packages you have installed?
I cannot reproduce this problem. |
|
|
|
yum --enablerepo=sogo-nightly-rhel6 update, booted server update
sope49-appserver.x86_64 4.9-20111114_1664.el6.1@sogo-nightly-rhel6
sope49-cards.x86_64 1.3.9-2.centos6@sogo-rhel6
sope49-core.x86_64 4.9-20111114_1664.el6.1@sogo-nightly-rhel6
sope49-gdl1.x86_64 4.9-20111114_1664.el6.1@sogo-nightly-rhel6
sope49-gdl1-contentstore.x86_64 1.3.9-2.centos6@sogo-rhel6
sope49-gdl1-postgresql.x86_64 4.9-20111114_1664.el6.1@sogo-nightly-rhel6
sope49-ldap.x86_64 4.9-20111114_1664.el6.1@sogo-nightly-rhel6
sope49-mime.x86_64 4.9-20111114_1664.el6.1@sogo-nightly-rhel6
sope49-sbjson.x86_64 2.3.1-20111114_1664.el6.1@sogo-nightly-rhel6
sope49-xml.x86_64 4.9-20111114_1664.el6.1@sogo-nightly-rhel6
to reproduce:
- with web client: create an appointment with title:
noch'n Termin
result's in
Nov 15 15:56:20 sogod [9888]: [ERROR] <0x02824638[SOGoAppointmentObject]:26A0-4EC27D80-1-59C3EA00.ics> write failed: <PostgreSQL72Exception: 0x29142a8> NAME:PostgreSQL72FatalError REASON:fatal pgsql error (channel=<0x0x2742de8[PostgreSQL72Channel]: connection=<0x0x2669388[PGConnection]: connection=0x0x207b8c0>>): FEHLER: Syntaxfehler bei »n«
ZEILE 1: ...o2', 1, 0, 'vevent', 0, 1321444800, 0, '', 'noch\'n Termin',...
^
and (look's like an regression ) also in description it fails:
Nov 15 15:56:54 sogod [9888]: [ERROR] <0x0256B808[SOGoAppointmentObject]:26A0-4EC27D80-7-59C3EA00.ics> write failed: <PostgreSQL72Exception: 0x2811b68> NAME:PostgreSrror REASON:fatal pgsql error (channel=<0x0x2742de8[PostgreSQL72Channel]: connection=<0x0x2669388[PGConnection]: connection=0x0x207b8c0>>): FEHLER: Syntaxfehler be
ZEILE 7: DESCRIPTION:noch\'n Termin |
|
wsourdeau
2011-11-15 16:49
viewer
~0003007
|
Hi,
Your SOGo packages are actually outdated since you are using 1.3.9. We just rebuilt the nightlies for today, as there was a problem with them, I would suggest you to remove sope49-gdl1-contentstore sope49-cards as well as all the SOGo packages, and then reinstall them. The other SOPE packages do not need removal in order to get updated... |
|
|
|
i've updated completely to nightly:
sogo.x86_64 2.0_20111115-1.centos6@sogo-nightly-rhel6
sogo-ealarms-notify.x86_64 2.0_20111115-1.centos6@sogo-nightly-rhel6
sogo-slapd-sockd.x86_64 2.0_20111115-1.centos6@sogo-nightly-rhel6
sope49-appserver.x86_64 4.9-20111115_1664.el6.1@sogo-nightly-rhel6
sope49-cards.x86_64 2.0_20111115-1.centos6@sogo-nightly-rhel6
sope49-core.x86_64 4.9-20111115_1664.el6.1@sogo-nightly-rhel6
sope49-gdl1.x86_64 4.9-20111115_1664.el6.1@sogo-nightly-rhel6
sope49-gdl1-contentstore.x86_64 2.0_20111115-1.centos6@sogo-nightly-rhel6
sope49-gdl1-postgresql.x86_64 4.9-20111115_1664.el6.1@sogo-nightly-rhel6
sope49-ldap.x86_64 4.9-20111115_1664.el6.1@sogo-nightly-rhel6
sope49-mime.x86_64 4.9-20111115_1664.el6.1@sogo-nightly-rhel6
sope49-sbjson.x86_64 2.3.1-20111115_1664.el6.1@sogo-nightly-rhel6
sope49-xml.x86_64 4.9-20111115_1664.el6.1@sogo-nightly-rhel6
now this is fixed
thanks
but i've this message while starting sogod:
root@sogo ~]# service sogod restart
/etc/init.d/sogod: Zeile 73: /usr/GNUstep/System/Library/Makefiles/GNUstep.sh: Datei oder Verzeichnis nicht gefunden
Restarting SOGo
it seems as if sogo is working fine |
|
wsourdeau
2011-11-16 14:19
viewer
~0003013
|
The latter problem is one related to the init script. It's going to be fixed for the next nightly builds. Meanwhile I am closing this particular report since the postgres issue can be considered fixed. |
|
