Re: [SOGo] Problem with WoWatchDogChild
Hi,
Group are enable, but our LDAP is not yet fill.
Ludovic.
Ludovic Hutin
Université De Strasbourg
Le 20/02/2014 17:26, Francis Lachapelle a écrit :
Hi Ludovic
On Feb 20, 2014, at 2:49 AM, Ludovic Hutin ludovic.hu...@unistra.fr wrote:
A little up...
Feb 20 08:41:16 sogod [8591]: [ERROR] 0x0x7f3a12195aa0[WOWatchDogChild]
FAILURE receiving status for child 19846
Feb 20 08:41:16 sogod [8591]: [ERROR] 0x0x7f3a12195aa0[WOWatchDogChild] socket:
NGActiveSocket[0x0x7f3a12122e10]: mo
de=rw address=(null) connectedTo=0x0x7f3a1227b010[NGLocalSocketAddress]:
/tmp/_ngsocket_0x218f_0x7f3a11efb8e0_000 rece
ive-timeout=1.000s
Feb 20 08:41:16 sogod [8591]: [ERROR] 0x0x7f3a12195aa0[WOWatchDogChild]
exception: NGSocketConnectionResetException:
0x7f3a1210f1c0 NAME:NGSocketConnectionResetException REASON:reached end of stream
NGActiveSocket[0x0x7f3a12122e10]: mo
de=rw address=(null) connectedTo=0x0x7f3a1227b010[NGLocalSocketAddress]:
/tmp/_ngsocket_0x218f_0x7f3a11efb8e0_000 recei
ve-timeout=1.000s INFO:{errno = 104; error = Connection reset by peer; stream =
{object = NGActiveSocket[0x0x7f3a121
22e10]: mode=rw address=(null)
connectedTo=0x0x7f3a1227b010[NGLocalSocketAddress]:
/tmp/_ngsocket_0x218f_0x7f3a11efb8e0_
000 receive-timeout=1.000s;}; } │
Feb 20 08:41:16 sogod [8591]: 0x0x7f3a12195aa0[WOWatchDogChild] sending
terminate signal to pid 19846
Feb 20 08:41:16 sogod [8591]: [ERROR] 0x0x7f3a12195aa0[WOWatchDogChild]
FAILURE notifying child 19846
Feb 20 08:41:16 sogod [8591]: 0x0x7f3a12195aa0[WOWatchDogChild] sending
terminate signal to pid 19846
Feb 20 08:41:16 sogod [8591]: 0x0x7f3a12195aa0[WOWatchDogChild] child 19846
exited
Feb 20 08:41:16 sogod [8591]: 0x0x7f3a122fa7d0[WOWatchDog] child spawned with
pid 20243
By the way, we found something strange when a Thunderbird + Lightining +
Integrator + Connector is not yet configured (with a wrong password, or empty
password)
We got many many many line with that
Feb 20 08:29:25 sogod [12499]: 0x0x7f8d65479610[LDAPSource] NSException:
0x7f8d65cddc50 NAME:LDAPException REASON:operation bind failed: Invalid credentials (0x31)
INFO:{login = uid=,ou=people,o=annuaire; }
But for each connexion, SOGo open an LDAP socket, and when we do a netstat -b |
grep 389 | wc -l
We got arround 1200 connection on the LDAP serveur.
SOGo will open a new socket for each LDAP connexion ? There is no persistent
socket for that ?
Do you use LDAP groups? If so, we fixed a bug related to LDAP group expansion
last week:
https://github.com/inverse-inc/sogo/commit/75c8362df833bc4204bf6a83cc037eaa719d20cf
This fix will be part of release 2.2.0.
Thanks,
Francis
--
flachape...@inverse.ca :: +1.514.755.3640 :: http://www.inverse.ca
Inverse :: Leaders behind SOGo (http://sogo.nu) and PacketFence
(http://packetfence.org)
--
users@sogo.nu
https://inverse.ca/sogo/lists
Re: [SOGo] Problem with WoWatchDogChild
Hi,
A little up...
Feb 20 08:41:16 sogod [8591]: [ERROR]
0x0x7f3a12195aa0[WOWatchDogChild] FAILURE receiving status for child 19846
Feb 20 08:41:16 sogod [8591]: [ERROR]
0x0x7f3a12195aa0[WOWatchDogChild] socket:
NGActiveSocket[0x0x7f3a12122e10]: mo
de=rw address=(null)
connectedTo=0x0x7f3a1227b010[NGLocalSocketAddress]:
/tmp/_ngsocket_0x218f_0x7f3a11efb8e0_000 rece
ive-timeout=1.000s
Feb 20 08:41:16 sogod [8591]: [ERROR]
0x0x7f3a12195aa0[WOWatchDogChild] exception:
NGSocketConnectionResetException:
0x7f3a1210f1c0 NAME:NGSocketConnectionResetException REASON:reached end
of stream NGActiveSocket[0x0x7f3a12122e10]: mo
de=rw address=(null)
connectedTo=0x0x7f3a1227b010[NGLocalSocketAddress]:
/tmp/_ngsocket_0x218f_0x7f3a11efb8e0_000 recei
ve-timeout=1.000s INFO:{errno = 104; error = Connection reset by
peer; stream = {object = NGActiveSocket[0x0x7f3a121
22e10]: mode=rw address=(null)
connectedTo=0x0x7f3a1227b010[NGLocalSocketAddress]:
/tmp/_ngsocket_0x218f_0x7f3a11efb8e0_
000 receive-timeout=1.000s;}; } │
Feb 20 08:41:16 sogod [8591]: 0x0x7f3a12195aa0[WOWatchDogChild]
sending terminate signal to pid 19846
Feb 20 08:41:16 sogod [8591]: [ERROR]
0x0x7f3a12195aa0[WOWatchDogChild] FAILURE notifying child 19846
Feb 20 08:41:16 sogod [8591]: 0x0x7f3a12195aa0[WOWatchDogChild]
sending terminate signal to pid 19846
Feb 20 08:41:16 sogod [8591]: 0x0x7f3a12195aa0[WOWatchDogChild] child
19846 exited
Feb 20 08:41:16 sogod [8591]: 0x0x7f3a122fa7d0[WOWatchDog] child
spawned with pid 20243
By the way, we found something strange when a Thunderbird + Lightining +
Integrator + Connector is not yet configured (with a wrong password, or
empty password)
We got many many many line with that
Feb 20 08:29:25 sogod [12499]: 0x0x7f8d65479610[LDAPSource]
NSException: 0x7f8d65cddc50 NAME:LDAPException REASON:operation bind
failed: Invalid credentials (0x31) INFO:{login =
uid=,ou=people,o=annuaire; }
But for each connexion, SOGo open an LDAP socket, and when we do a
netstat -b | grep 389 | wc -l
We got arround 1200 connection on the LDAP serveur.
SOGo will open a new socket for each LDAP connexion ? There is no
persistent socket for that ?
Best regards,
Ludovic Hutin
Université De Strasbourg
Le 18/02/2014 14:28, Ludovic Hutin a écrit :
Hi all,
Since 1 week we got many line with that error :
Feb 18 14:25:08 sogod [23937]: [ERROR]
0x0x7fa770ba3e80[WOWatchDogChild] FAILURE receiving status for child
16016
Feb 18 14:25:08 sogod [23937]: [ERROR]
0x0x7fa770ba3e80[WOWatchDogChild] socket:
NGActiveSocket[0x0x7fa770cde3a0]: mode=rw address=(null)
connectedTo=0x0x7fa770c93210[NGLocalSocketAddress]:
/tmp/_ngsocket_0x5d81_0x7fa77090d8e0_000 receive-timeout=1.000s
Feb 18 14:25:08 sogod [23937]: [ERROR]
0x0x7fa770ba3e80[WOWatchDogChild] exception:
NGSocketTimedOutException: 0x7fa770b2e0a0
NAME:NGSocketTimedOutException REASON:the socket was shutdown
INFO:{errno = 11; error = Resource temporarily unavailable; stream =
{object = NGActiveSocket[0x0x7fa770cde3a0]: mode=rw address=(null)
connectedTo=0x0x7fa770c93210[NGLocalSocketAddress]:
/tmp/_ngsocket_0x5d81_0x7fa77090d8e0_000 receive-timeout=1.000s;}; }
Feb 18 14:25:08 sogod [23937]: 0x0x7fa770ba3e80[WOWatchDogChild]
sending terminate signal to pid 16016
Feb 18 14:25:08 sogod [23937]: [ERROR]
0x0x7fa770ba3e80[WOWatchDogChild] FAILURE notifying child 16016
...
Feb 18 14:25:12 sogod [23937]: [ERROR]
0x0x7fa770d06960[WOWatchDogChild] FAILURE receiving status for child
18922
Feb 18 14:25:12 sogod [23937]: [ERROR]
0x0x7fa770d06960[WOWatchDogChild] socket:
NGActiveSocket[0x0x7fa770b2abc0]: mode=rw address=(null)
connectedTo=0x0x7fa770b12b90[NGLocalSocketAddress]:
/tmp/_ngsocket_0x5d81_0x7fa77090d8e0_000 receive-timeout=1.000s
Feb 18 14:25:12 sogod [23937]: [ERROR]
0x0x7fa770d06960[WOWatchDogChild] exception:
NGSocketTimedOutException: 0x7fa770b100c0
NAME:NGSocketTimedOutException REASON:the socket was shutdown
INFO:{errno = 11; error = Resource temporarily unavailable; stream =
{object = NGActiveSocket[0x0x7fa770b2abc0]: mode=rw address=(null)
connectedTo=0x0x7fa770b12b90[NGLocalSocketAddress]:
/tmp/_ngsocket_0x5d81_0x7fa77090d8e0_000 receive-timeout=1.000s;}; }
Feb 18 14:25:12 sogod [23937]: 0x0x7fa770d06960[WOWatchDogChild]
sending terminate signal to pid 18922
Feb 18 14:25:12 sogod [23937]: [ERROR]
0x0x7fa770d06960[WOWatchDogChild] FAILURE notifying child 18922
.
If you have an idea how to fix that :-)
--
users@sogo.nu
https://inverse.ca/sogo/lists
[SOGo] Problem with WoWatchDogChild
Hi all,
Since 1 week we got many line with that error :
Feb 18 14:25:08 sogod [23937]: [ERROR]
0x0x7fa770ba3e80[WOWatchDogChild] FAILURE receiving status for child 16016
Feb 18 14:25:08 sogod [23937]: [ERROR]
0x0x7fa770ba3e80[WOWatchDogChild] socket:
NGActiveSocket[0x0x7fa770cde3a0]: mode=rw address=(null)
connectedTo=0x0x7fa770c93210[NGLocalSocketAddress]:
/tmp/_ngsocket_0x5d81_0x7fa77090d8e0_000 receive-timeout=1.000s
Feb 18 14:25:08 sogod [23937]: [ERROR]
0x0x7fa770ba3e80[WOWatchDogChild] exception:
NGSocketTimedOutException: 0x7fa770b2e0a0
NAME:NGSocketTimedOutException REASON:the socket was shutdown
INFO:{errno = 11; error = Resource temporarily unavailable; stream =
{object = NGActiveSocket[0x0x7fa770cde3a0]: mode=rw address=(null)
connectedTo=0x0x7fa770c93210[NGLocalSocketAddress]:
/tmp/_ngsocket_0x5d81_0x7fa77090d8e0_000 receive-timeout=1.000s;}; }
Feb 18 14:25:08 sogod [23937]: 0x0x7fa770ba3e80[WOWatchDogChild]
sending terminate signal to pid 16016
Feb 18 14:25:08 sogod [23937]: [ERROR]
0x0x7fa770ba3e80[WOWatchDogChild] FAILURE notifying child 16016
...
Feb 18 14:25:12 sogod [23937]: [ERROR]
0x0x7fa770d06960[WOWatchDogChild] FAILURE receiving status for child 18922
Feb 18 14:25:12 sogod [23937]: [ERROR]
0x0x7fa770d06960[WOWatchDogChild] socket:
NGActiveSocket[0x0x7fa770b2abc0]: mode=rw address=(null)
connectedTo=0x0x7fa770b12b90[NGLocalSocketAddress]:
/tmp/_ngsocket_0x5d81_0x7fa77090d8e0_000 receive-timeout=1.000s
Feb 18 14:25:12 sogod [23937]: [ERROR]
0x0x7fa770d06960[WOWatchDogChild] exception:
NGSocketTimedOutException: 0x7fa770b100c0
NAME:NGSocketTimedOutException REASON:the socket was shutdown
INFO:{errno = 11; error = Resource temporarily unavailable; stream =
{object = NGActiveSocket[0x0x7fa770b2abc0]: mode=rw address=(null)
connectedTo=0x0x7fa770b12b90[NGLocalSocketAddress]:
/tmp/_ngsocket_0x5d81_0x7fa77090d8e0_000 receive-timeout=1.000s;}; }
Feb 18 14:25:12 sogod [23937]: 0x0x7fa770d06960[WOWatchDogChild]
sending terminate signal to pid 18922
Feb 18 14:25:12 sogod [23937]: [ERROR]
0x0x7fa770d06960[WOWatchDogChild] FAILURE notifying child 18922
.
If you have an idea how to fix that :-)
--
Ludovic Hutin
Département Services Métiers
Direction Informatique
Université De Strasbourg
--
users@sogo.nu
https://inverse.ca/sogo/lists
Re: [SOGo] SOGo / IE7
Hi, A little popup should be enough. Best regards, Ludovic. Le 05/02/2014 01:04, Ludovic Marcotte a écrit : Hi, As some of you might have experienced since v2.1, IE7 is no longer well supported. This is due to the fact that we keep up-to-date with CKEditor (the HTML editor being used in SOGo) to benefit from new features but more importantly, bug fixes. CKEditor 4.1.3 was the last release to support Internet Explorer 7. That being said, other parts of SOGo work well with IE7 - even sending mails in plain text. It's just the HTML editor that is broken. What you guys prefer - blocking IE7 from logging in (and suggesting an upgrade to IE8+) or you guys dealing with user complaints that the HTML editor doesn't work? Thanks, -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Active Sync support in SOGo
Hello, Any good news for this feature ? Ludovic. Le 26/11/2013 14:38, Ludovic Marcotte a écrit : On 2013-11-26 8:15 AM, Márcio Merlone wrote: Any update on this? Can't wait for that. :) The work is ongoing. We expect an initial working version by the end of this week or the next one. Thanks, -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Large deployments
Hello Dhinel Díaz, Le 04/12/2013 17:34, Dhionel Díaz a écrit : Hello all, Do you have references of very large deployments of SOGo? Something on the order of 30 users or more, or the biggest deployments known. In the web site there are some testimonials but I haven't found references to the size of the deployments. We are currently evaluating groupware software and that references would be very helpful. Thanks in advance, -- Dhionel Díaz Centro Nacional de Desarrollo e Investigación en Tecnologías Libres Ministerio del Poder Popular para Ciencia, Tecnología e Innovación At the University of Strasbourg in France, we have ~120 000 account with ~15 000 differents users per day. If we can help us Best regards, Ludovic. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] SOGo + Internet Explorer 11
Hi, That's a good news, we will try this as son as possible. Ludovic. Le 05/12/2013 15:34, Francis Lachapelle a écrit : Hi On Dec 4, 2013, at 12:34 PM, Laz C. Peterson l...@paravis.net wrote: I can confirm that the first issue you mention is trouble. While not entirely impossible to click there, I was only able to click-to-focus two times out of many tries. It seems that going off the side of the “usable area” helped, though that was inconsistent. The latest version of SOGo (2.1.1b) includes the latest version of CKEditor (4.3.0) that fixes IE11 compatibility. It should therefore fix the problems with the mail editor. For your second issue, the bar is shown in my browser, though I am using IE11 64-bit on Windows 8.1. Maybe the behavior is different in Windows 7. Quite interesting for your last issue. In the new Windows 8.1 tiles mode, whatever it is called, if I go to “Calendar” and attempt to create a new event, I get a blank screen in the main window, but the thumbnail icon in the bottom of the screen shows the content to be there. That is quite odd. After trying it in whatever the regular mode is, with the desktop etc., I am able to view this window. However, regarding your specific issue, I don’t know exactly what you mean by creating a meeting, next/previous, etc. Would you mind giving me a walkthrough on where to click? I generally don’t like to let any of my users install anything past IE9 at this point. IE10 was a horrible mess to administrate, and I don’t expect IE11 to be any better. This is just more reason to avoid. Thanks Ludovic. On Dec 3, 2013, at 12:08 AM, Ludovic Hutin ludovic.hu...@unistra.fr wrote: Hi, With my Windows 7 64bits, when i write a new mail it's impossible to click on the content message, i have to use tab to add the focus. When you write a mail, on the option menu, the horizontal bar between priority and ask for receipe is not shown. When you want to make a meeting with participant and you click many time on the next or previous in the suggestion, the UI crash. Nothing is shown. Some user have talled me they can't answer anwser to a mail, if they take too much time to write, the mail is not sent. I can't reproduce it on my IE 11 Ludovic Le 02/12/2013 23:24, Laz C. Peterson a écrit : Hi Ludovic, What issues are you having? I just recently installed Windows 8.1 for testing, and my SOGo seems to be working properly with IE 11 (all features I tried). I can try to see if I also suffer from the same issue if you can give me more specific info. Thanks. ~Laz On Dec 2, 2013, at 2:18 AM, Ludovic Hutin ludovic.hu...@unistra.fr wrote: Hi, We have just upgrade our SOGo to 2.1.1a and we got some user who complain about IE 11 problem. Did Someone test with IE 11 and got problem ? Or i am alone with that ? Best regards, Ludovic. -- flachape...@inverse.ca :: +1.514.755.3640 :: http://www.inverse.ca Inverse :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) --- Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection avast! Antivirus est active. http://www.avast.com -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] SOGo + Internet Explorer 11
Hi, With my Windows 7 64bits, when i write a new mail it's impossible to click on the content message, i have to use tab to add the focus. When you write a mail, on the option menu, the horizontal bar between priority and ask for receipe is not shown. When you want to make a meeting with participant and you click many time on the next or previous in the suggestion, the UI crash. Nothing is shown. Some user have talled me they can't answer anwser to a mail, if they take too much time to write, the mail is not sent. I can't reproduce it on my IE 11 Ludovic Le 02/12/2013 23:24, Laz C. Peterson a écrit : Hi Ludovic, What issues are you having? I just recently installed Windows 8.1 for testing, and my SOGo seems to be working properly with IE 11 (all features I tried). I can try to see if I also suffer from the same issue if you can give me more specific info. Thanks. ~Laz On Dec 2, 2013, at 2:18 AM, Ludovic Hutin ludovic.hu...@unistra.fr wrote: Hi, We have just upgrade our SOGo to 2.1.1a and we got some user who complain about IE 11 problem. Did Someone test with IE 11 and got problem ? Or i am alone with that ? Best regards, Ludovic. -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] SOGo + Internet Explorer 11
Hi, We have just upgrade our SOGo to 2.1.1a and we got some user who complain about IE 11 problem. Did Someone test with IE 11 and got problem ? Or i am alone with that ? Best regards, Ludovic. -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] TB 24.1.1 + sogo connector 24.0.2 + sogo integrator 24.0.2 + lightning 2.6.3
Hello all, I have test the news version of the plugin and Ok you the address books is now working again... But calendar no more work... (test on a new install) Can you fixed it ? Best regards, Ludovic. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] TB 24.1.1 + sogo connector 24.0.2 + sogo integrator 24.0.2 + lightning 2.6.3
Le 25/11/2013 14:41, Szládovics Péter a écrit : 2013-11-25 09:41 keltezéssel, Ludovic Hutin írta: Hello all, I have test the news version of the plugin and Ok you the address books is now working again... But calendar no more work... (test on a new install) Can you fixed it ? Fresh the calendar extension manually to 2.6.3, and it will works. What do you mean by fresh the calendar extension manually ? -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] News from SOGo project
Hello All, I have a little question about news release of SOGo. Can we expect new fonctionnality for SOGo ? New design ? If i see the github log, i can read during the last month the SOGo project is in support mode only. I hope i mistake myself. I can't see major feature :-( Any new roadmap for the SOGo project ? Best regards, Ludovic. -- Ludovic Hutin -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Problem with signature
Hello all, We have upgraded our version to 2.0.6 and we have a strange problem with the Signature option. It is impossible to copy / paste HTML document with an image in the signature popup. Someone have the same problem ? Best regards, Ludovic. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Thunderbird 17 still asks for the password several times [was Re: SOGo extensions for Thunderbird 10!]
Le 28/02/2013 14:47, Martin (Lists) a écrit : Am 11.01.2013 21:51, schrieb Nobody: I noticed myself after upgrading to Thunderbird 17 that I was being prompted to authenticate seemingly for every calendar I was subscribed to in addition to once for my mail. After a lot of tinkering with versions and settings, I found myself digging through the extracted contents of the Lightning extension. There, I found the file calAuthUtils.jsm in the modules sub directory. I've found that if I overwrite the cal.auth.Prompt.prototype definition/code block, with the version from lightning-1.0b2.105i (Inverse Edition for the 3.x release), and of course, re-zip the extension back up and re-install it, I get the old behavior of only being prompted to enter my password twice, once for mail and once for all of my calendars. This appears to work on Linux and OSX with 17.0.2. I've yet to test with the 10.x series or with Windows but I suspect its the same issue. I believe it has to do with the way the authentication realms are being handled for CalDAV auth, but I'm no expert. Hope maybe this will help and not break too much stuff. Seems to work. Is there something new regarding this toppic? Since I moved from TB10 to TB17 I got the master password login dialog three times on my linux box as well (with the old TB10 I had it on windows only). I have to type in the password only once and can close the other two boxes by hitting ESC button. Regards Martin Hi, Personnaly i use the module master password+ 1.21 in order to display only one password popup. The other popup are hidden with this plugin. It's very usefull ! Regards Ludovic -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] SOGo die : (terminated due to signal 6, coredump)
Hello, We have found the origin of this bug. In the quick table of the Calendar user, one entry got an empty c_name field. The event was generate in 2011 with Ical. We delete this line, and now it work's fine. Ludovic. Le 22/02/2013 08:56, Ludovic Hutin a écrit : Hello, Here is the stack trace : (gdb) bt #0 -[NSException raise] (self=0x564437b0, _cmd=0x75736f00) at NSException.m:955 #1 0x75283231 in +[NSException raise:format:] (self=0x75737080, _cmd=optimized out, name=0x757370f0, format=0x77da0140) at NSException.m:835 #2 0x77b37d95 in -[SOGoObject initWithName:inContainer:] (self=0x56443890, _cmd=0x77da39f0, _name=0x7fffe9d724a0, _container=0x5620f750) at SOGoObject.m:183 #3 0x77b3ea2c in -[SOGoContentObject initWithRecord:inContainer:] (self=0x56443890, _cmd=0x77da3950, objectRecord=0x56223c40, newContainer=0x5620f750) at SOGoContentObject.m:123 #4 0x77b3e584 in +[SOGoContentObject objectWithRecord:inContainer:] (self=0x7fffecbdd140, _cmd=0x77da9cb0, objectRecord=0x56223c40, newContainer=0x5620f750) at SOGoContentObject.m:53 #5 0x77b45228 in -[SOGoGCSFolder createChildComponentWithRecord:] (self=0x5620f750, _cmd=0x77da9d20, record=0x56223c40) at SOGoGCSFolder.m:727 #6 0x77b45508 in -[SOGoGCSFolder lookupName:inContext:acquire:] (self=0x5620f750, _cmd=0x7fffecbe5bd0, key=0x7fffe9d724a0, localContext=0x55e29800, acquire=0 '\000') at SOGoGCSFolder.m:768 #7 0x7fffec9b2ebf in -[SOGoAppointmentFolder lookupName:inContext:acquire:] (self=0x5620f750, _cmd=0x76e643a0, _key=0x7fffe9d724a0, _ctx=0x55e29800, _flag=0 '\000') at SOGoAppointmentFolder.m:1914 #8 0x76b413d9 in -[SoObjectDataSource davFlatQuery:inContext:] (self=0x55f5feb0, _cmd=optimized out, _fs=0x55f93e60, _ctx=0x55e29800) at SoObjectDataSource.m:156 #9 0x76b41766 in -[SoObjectDataSource fetchObjects] (self=0x55f5feb0, _cmd=optimized out) at SoObjectDataSource.m:265 #10 0x76b40b2a in -[NSObject(SoObjectDAVQueries) performWebDAVQuery:inContext:] (self=0x5620f750, _cmd=optimized out, _fs=0x55f93e60, _ctx=0x55e29800) at SoObject+SoDAVQuery.m:276 #11 0x76b43dbb in -[SoObjectWebDAVDispatcher doPROPFIND:] (self=0x561664f0, _cmd=optimized out, _ctx=0x55e29800) at SoObjectWebDAVDispatcher.m:550 #12 0x76b4775c in -[SoObjectWebDAVDispatcher dispatchInContext:] (self=0x561664f0, _cmd=optimized out, _ctx=0x55e29800) at SoObjectWebDAVDispatcher.m:1775 #13 0x76b27978 in -[SoObjectRequestHandler handleRequest:inContext:session:application:] () from /usr/lib/libNGObjWeb.so.4.9 #14 0x76abbc75 in -[WORequestHandler handleRequest:] (self=0x55b33040, _cmd=optimized out, _request=0x55f9bd30) at WORequestHandler.m:237 #15 0x76a83736 in -[WOCoreApplication dispatchRequest:usingHandler:] (self=0x55ab93d0, _cmd=optimized out, _request=0x55f9bd30, handler=0x55b33040) at WOCoreApplication.m:712 #16 0xb751 in -[SOGo dispatchRequest:] (self=0x55ab93d0, _cmd=0x76e32300, _request=0x55f9bd30) at SOGo.m:453 #17 0x76b1748d in -[WOHttpTransaction _run] (self=0x55e87770, _cmd=optimized out) at WOHttpTransaction.m:581 #18 0x76b18e18 in -[WOHttpTransaction run] (self=0x55e87770, _cmd=optimized out) at WOHttpTransaction.m:634 #19 0x76b13ab9 in -[WOHttpAdaptor runConnection:] (self=0x55de02b0, _cmd=optimized out, _socket=0x55f361f0) at WOHttpAdaptor.m:367 #20 0x76b14b06 in -[WOHttpAdaptor _handleAcceptedConnection:] (self=0x55de02b0, _cmd=optimized out, _connection=0x55f361f0) at WOHttpAdaptor.m:401 #21 0x76b14eba in -[WOHttpAdaptor _handleConnection:] (self=0x55de02b0, _cmd=optimized out, connection=0x55f361f0) at WOHttpAdaptor.m:460 #22 0x76b14f5d in -[WOHttpAdaptor acceptConnection:] (self=0x55de02b0, _cmd=optimized out, _notification=optimized out) at WOHttpAdaptor.m:521 #23 0x752bf48d in -[NSNotificationCenter _postAndRelease:] (self=0x55869ee0, _cmd=optimized out, notification=0x55e68a80) at NSNotificationCenter.m:1162 #24 0x753b9f62 in -[GSRunLoopCtxt pollUntil:within:] (self=0x55b11610, _cmd=optimized out, milliseconds=0, contexts=0x55c43c80) at GSRunLoopCtxt.m:636 #25 0x75308170 in -[NSRunLoop acceptInputForMode:beforeDate:] (self=0x55b3dc00, _cmd=optimized out, mode=0x75779390, limit_date=optimized out) at NSRunLoop.m:1198 #26 0x75307250 in -[NSRunLoop runMode:beforeDate:] (self=0x55b3dc00, _cmd=optimized out, mode=0x75779390, date=0x55b0bdf0) at NSRunLoop.m:1266 #27 0x76a8309e in -[WOCoreApplication run] (self=0x55ab93d0, _cmd=optimized out) at WOCoreApplication.m:584 #28 0xae71 in -[SOGo run] (self=0x55ab93d0
[SOGo] SOGo die : (terminated due to signal 6, coredump)
Hello all, We have this strange problem : We have a user who have a Calendar, when you subscribe to his Calendar you can see it in web gui without any trouble. When you want to see it with Thunderbird + Lightning (1.9.1) + SOGo Integrator + SOGo Connector it is impossible to see any event. We always got a warning behind the Calendar witch is tempory unavalible. It's is the same behaviour with the cadaver command In the /var/log/sogo/sogo.log we can see this : :::: - - [21/Feb/2013:15:16:05 GMT] HEAD /SOGo/index HTTP/1.0 302 0/0 0.001 - - 0 :::: - - [21/Feb/2013:15:16:13 GMT] OPTIONS /SOGo/dav/ludovic.hutin/Calendar/XXX_personal/ HTTP/1.0 401 0/0 0.003 - - 0 :::: - - [21/Feb/2013:15:16:14 GMT] HEAD /SOGo/index HTTP/1.0 302 0/0 0.001 - - 0 :::: - - [21/Feb/2013:15:16:14 GMT] HEAD /SOGo/index HTTP/1.0 302 0/0 0.001 - - 0 :::: - - [21/Feb/2013:15:16:20 GMT] OPTIONS /SOGo/dav/ludovic.hutin/Calendar/XXX_personal/ HTTP/1.0 200 0/0 0.175 - - 0 2013-02-21 15:16:20.263 sogod[31759] File NSKeyValueCoding.m: 913. In -[NSObject(KeyValueCoding) valuesForKeys:] This method is deprecated, use -dictionaryWithValuesForKeys: :::: - - [21/Feb/2013:15:16:20 GMT] PROPFIND /SOGo/dav/ludovic.hutin/Calendar/XXX_personal/ HTTP/1.0 207 598/288 0.157 - - 24K EXCEPTION: NSException: 0x7fa77fc578d0 NAME:NSInvalidArgumentException REASON:'_name' must not be an empty string INFO:(null) Feb 21 15:16:30 sogod [31754]: 0x0x7fa77f49f6b0[WOWatchDogChild] child 31759 exited Feb 21 15:16:30 sogod [31754]: 0x0x7fa77f49f6b0[WOWatchDogChild] (terminated due to signal 6, coredump) Feb 21 15:16:30 sogod [31754]: 0x0x7fa77f3726d0[WOWatchDog] child spawned with pid 2305 Feb 21 15:16:35 sogod [2305]: 0x0x7fa77f7d02f0[SOGoCache] Cache cleanup interval set every 300.00 seconds Feb 21 15:16:35 sogod [2305]: 0x0x7fa77f7d02f0[SOGoCache] Using host(s) '192.168.135.10' as server(s) 2013-02-21 15:16:35.675 sogod[2305] Note(SoObject): SoDebugKeyLookup is enabled! 2013-02-21 15:16:35.676 sogod[2305] Note(SoObject): SoDebugBaseURL is enabled! 2013-02-21 15:16:35.676 sogod[2305] Note(SoObject): relative base URLs are enabled. :::: - - [21/Feb/2013:15:16:35 GMT] HEAD /SOGo/index HTTP/1.0 302 0/0 0.001 - - 0 2013-02-21 15:16:35.682 sogod[2305] ERROR(-[NGBundleManager bundleWithPath:]): could not create bundle for path: '/usr/share/GNUstep/Libraries/gnustep-base/Versions/1.22/Resources/SSL.bundle' 2013-02-21 15:16:35.690 sogod[2305] WOxElemBuilder: could not locate builders: WOxExtElemBuilder,WOxExtElemBuilder 2013-02-21 15:16:35.690 sogod[2305] WOCompoundElement: pool embedding is on. 2013-02-21 15:16:35.690 sogod[2305] WOCompoundElement: id logging is on. :::: - - [21/Feb/2013:15:16:35 GMT] HEAD /SOGo/index HTTP/1.0 302 0/0 0.024 - - 2M Here is the trace with gdb. sogo@XX:~$ gdb /usr/sbin/sogod core GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://bugs.launchpad.net/gdb-linaro/... Reading symbols from /usr/sbin/sogod...Reading symbols from /usr/lib/debug/usr/sbin/sogod...done. done. [New LWP 10197] warning: Can't read pathname for load map: Input/output error. [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Core was generated by `/usr/sbin/sogod'. Program terminated with signal 6, Aborted. #0 0x7f0fb4606425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt full #0 0x7f0fb4606425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x7f0fb4609b8b in abort () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #2 0x7f0fb82644ec in -[SOGo handleException:inContext:] (self=0x7f0fb9a340d0, _cmd=0x7f0fb702f690, _exc=0x7f0fba47f780, _ctx=0x7f0fb9fe4eb0) at SOGo.m:400 No locals. #3 0x7f0fb6d1a34d in -[WORequestHandler handleRequest:] (self=0x7f0fb9d73790, _cmd=optimized out, _request=optimized out) at WORequestHandler.m:264 localException = 0x7f0fba47f780 startHandling = 0 app = 0x7f0fb9a340d0 response = optimized out context = 0x7f0fb9fe4eb0 thread = optimized out sessionId = optimized out session = 0x0 uri = optimized out #4 0x7f0fb6ce1736 in -[WOCoreApplication dispatchRequest:usingHandler:] (self=0x7f0fb9a340d0, _cmd=optimized out, _request=0x7f0fba049c00, handler=0x7f0fb9d73790) at
Re: [SOGo] SOGo die : (terminated due to signal 6, coredump)
) at WOWatchDogApplicationMain.m:1031 #31 0xa145 in main (argc=13, argv=0x7fffe608, env=0x7fffe678) at sogod.m:53 Le 21/02/2013 17:26, Ludovic Marcotte a écrit : On 21/02/13 10:51, Ludovic Hutin wrote: When you want to see it with Thunderbird + Lightning (1.9.1) + SOGo Integrator + SOGo Connector it is impossible to see any event. We always got a warning behind the Calendar witch is tempory unavalible. It's is the same behaviour with the cadaver command Set the breakpoint on [NSException raise] and repost a stacktrace. -- users@sogo.nu https://inverse.ca/sogo/lists
