Al 11/03/11 22:43, En/na Allen Chen ha escrit:
This fixed the problem.
I found one with c_startdate=0!
Wrong data shouldn't be allowed to enter the database, or it should be
sanitized instead of crashing.
Bye
--
Luca Olivetti
Wetron Automatización S.A. http://www.wetron.es/
Tel. +34 93
Mohit Chawla wrote:
On Thu, Mar 10, 2011 at 10:26 PM, Allen Chen
ac...@harbourfrontcentre.com mailto:ac...@harbourfrontcentre.com
wrote:
After I upgraded SOGo to 1.3.5a from 1.3.3, some events from one
user cause SOGo to restart.
Other users have no problems.
Did you run the sql
On 11-03-11 2:58 PM, Allen Chen wrote:
Yes, I run sql-update-1.3.3_to_1.3.4-mysql.sh, and this script just
add c_categories to _quick tables.
I have 10 SOGo calendar users, and only one user has this problem
after upgraded. This user uses web GUI and BB to sync calendar.
On web GUI (SOGo
wget https://user:passw...@sogo.server.com/urlhere
Regards,
Mark
On 11 Mar 2011, at 20:22, Allen Chen ac...@harbourfrontcentre.com wrote:
Hi, Mark,
I don't know if SOGo team wanna fix this problem or not.
This is not good. Data are entered from SOGo, and it causes itself to crash.
BTW,
Hello,
Le Fri, Mar 11, 2011 at 03:22:29PM -0500, Allen Chen ecrivait :
I don't know if SOGo team wanna fix this problem or not.
This is not good. Data are entered from SOGo, and it causes itself to crash.
I have the same problem with one event created on Android and
David Cure wrote:
Hello,
Le Fri, Mar 11, 2011 at 03:22:29PM -0500, Allen Chen ecrivait :
I don't know if SOGo team wanna fix this problem or not.
This is not good. Data are entered from SOGo, and it causes itself to crash.
I have the same problem with one
You can likely find the culprit user from the logs (ie., the incoming
request - you might also want to set SOGoDebugRequests to YES).
Once the user is found, identify its calendar table{s} from
sogo_folder_info (where c_path2 == username) and then look at the
quick table, c_startdate. A
After I upgraded SOGo to 1.3.5a from 1.3.3, some events from one user
cause SOGo to restart.
Other users have no problems.
The web GUI shows no events and the log shows:
2011-03-10 11:49:11.075 sogod[4481] NGCalendarDateRange.m:37 Assertion
failed in NGCalendarDateRange(instance), method
On Thu, Mar 10, 2011 at 10:26 PM, Allen Chen
ac...@harbourfrontcentre.comwrote:
After I upgraded SOGo to 1.3.5a from 1.3.3, some events from one user cause
SOGo to restart.
Other users have no problems.
Did you run the sql update script ( 1.3.3 to 1.3.4 ) ? That might help.
--
users@sogo.nu