Since the Upgrade from 1.3.8a to 1.3.9 and 1.3.10 we have a problem with sogo. We are running on Centos6 x64 (before it was centos5 32bit). We have a calendar we display using phphicalendar. For this I wrote a cronjob which gets the ics file via wget from sogo.
wget --http-user=XXX --no-check-certificate --http-password="XXX" -O XXX.ics https://sogo.brain-biotech.de/SOGo/dav/sogo/Calendar/725B-4C31DB00-235-3C8963C0.ics Since the update to 1.3.9 and 1.3.10 I get the following errors when the command is run (in 90% of the cases). localhost - - [06/Dec/2011:17:22:53 GMT] "GET /SOGo/dav/sogo/Calendar/725B-4C31DB00-235-3C8963C0.ics HTTP/1.1" 200 573380/0 18.470 - - 1040M Dec 06 17:22:53 sogod [28187]: <0x0x10bf0d8[WOWatchDogChild]> child 28246 exited Dec 06 17:22:53 sogod [28187]: <0x0x10bf288[WOWatchDog]> child spawned with pid 28308 Dec 06 17:22:56 sogod [28308]: <0x0x151c258[SOGoCache]> Cache cleanup interval set every 300.000000 seconds Dec 06 17:22:56 sogod [28308]: <0x0x151c258[SOGoCache]> Using host(s) 'localhost' as server(s) And shortly afterwards this: Dec 06 17:23:37 sogod [28187]: [ERROR] <0x0x10bf0d8[WOWatchDogChild]> FAILURE receiving status for child 28308 Dec 06 17:23:37 sogod [28187]: [ERROR] <0x0x10bf0d8[WOWatchDogChild]> socket: <NGActiveSocket[0x0x12adbb8]: mode=rw address=(null) connectedTo=<0x0x126d4c8[NGLocalSocketAddress]: /tmp/_ngsocket_0x6e1b_0x1073248_000> receive-timeout=1.000s> Dec 06 17:23:37 sogod [28187]: [ERROR] <0x0x10bf0d8[WOWatchDogChild]> exception: <NGSocketTimedOutException: 0x12af108> NAME:NGSocketTimedOutException REASON:the socket was shutdown INFO:{errno = 11; error = "Die Ressource ist zur Zeit nicht verf\U00FCgbar"; stream = "{object = <NGActiveSocket[0x0x12adbb8]: mode=rw address=(null) connectedTo=<0x0x126d4c8[NGLocalSocketAddress]: /tmp/_ngsocket_0x6e1b_0x1073248_000> receive-timeout=1.000s>;}"; } Dec 06 17:23:37 sogod [28187]: <0x0x10bf0d8[WOWatchDogChild]> sending terminate signal to pid 28308 Dec 06 17:23:37 sogod [28187]: [ERROR] <0x0x10bf0d8[WOWatchDogChild]> FAILURE notifying child 28308 Dec 06 17:23:37 sogod [28187]: <0x0x10bf0d8[WOWatchDogChild]> sending terminate signal to pid 28308 This happens until all the workers are used up and the sogo doesn't respond anymore. What I wonder is why is this such a large value? localhost - - [06/Dec/2011:17:22:53 GMT] "GET /SOGo/dav/sogo/Calendar/725B-4C31DB00-235-3C8963C0.ics HTTP/1.1" 200 573380/0 18.470 - - 1040M ^^^^^^^ The calendar is large but in sogo you can't define a time frame so this 2 years of calendar entries. And the problem wasn't there before. Anyone have an idea? -- Dr. Christian Naumer Senior Scientist Analytics & Engineering B.R.A.I.N Aktiengesellschaft Darmstaedter Str. 34-36, D-64673 Zwingenberg e-mail c...@brain-biotech.de, homepage www.brain-biotech.de fon +49-6251-9331-30 / fax +49-6251-9331-11 Sitz der Gesellschaft: Zwingenberg/Bergstrasse Registergericht AG Darmstadt, HRB 24758 Vorstand: Dr. Holger Zinke (Vorsitz), Dr. Jürgen Eck Vorsitzender des Aufsichtsrats: Ulrich Putsch -- users@sogo.nu https://inverse.ca/sogo/lists
