Re: [SOGo] Activesync Errors

2018-12-04 Thread Ludovic Marcotte

On 2018-12-04 11:26 AM, Riccardo Bicelli (r.bice...@gmail.com) wrote:


Does sync continues anyway or have I to worry?


It should continue to sync.

Thanks,

--
Ludovic Marcotte
lmarco...@inverse.ca  ::  +1.514.755.3630  ::  https://inverse.ca
Inverse inc. :: Leaders behind SOGo (https://sogo.nu), PacketFence 
(https://packetfence.org) and Fingerbank (https://fingerbank.org)

--
users@sogo.nu
https://inverse.ca/sogo/lists


[SOGo] Activesync Errors

2018-12-04 Thread Riccardo Bicelli
Hello,
using activesync with latest nightly i have this errors:

2018-12-04 17:23:09.092 sogod[1667] parseTimeZone: cannot parse time
notation 'GMT'
2018-12-04 17:23:09.093 sogod[1667] parseTimeZone: cannot parse time
notation 'GMT'
2018-12-04 17:23:09.093 sogod[1651] parseTimeZone: cannot parse time
notation 'GMT'
2018-12-04 17:23:09.093 sogod[1651] parseTimeZone: cannot parse time
notation 'GMT'
2018-12-04 17:23:09.448 sogod[1651] parseTimeZone: cannot parse time
notation 'GMT'
2018-12-04 17:23:09.449 sogod[1651] parseTimeZone: cannot parse time
notation 'GMT'
2018-12-04 17:23:09.450 sogod[1667] parseTimeZone: cannot parse time
notation 'GMT'
2018-12-04 17:23:09.451 sogod[1667] parseTimeZone: cannot parse time
notation 'GMT'
Dec 04 17:23:10 sogod [1650]: [WARN] <0x0x5571491aa900[WOWatchDogChild]>
pid 1657 has been hanging in the same request for 3 minutes
Dec 04 17:23:10 sogod [1658]: <0x0x7fedcdd821a0[NSString]> iconv_wrapper:
Could not handle iconv encoding. FromEncoding:UNKNOWN-8BIT to
encoding:UTF-16LE
Dec 04 17:23:10 sogod [1658]: <0x0x7fedcef51e80[NGMimeType]> +[NGMimeType
stringEncodingForCharset:]: unknown charset 'unknown-8bit'
Dec 04 17:23:10 sogod [1658]: <0x0x7fedcdd821a0[NSString]> iconv_wrapper:
Could not handle iconv encoding. FromEncoding:UNKNOWN-8BIT to
encoding:UTF-16LE
Dec 04 17:23:10 sogod [1658]: <0x0x7fedcef51e80[NGMimeType]> +[NGMimeType
stringEncodingForCharset:]: unknown charset 'unknown-8bit'
Dec 04 17:23:10 sogod [1658]: <0x0x7fedcdd821a0[NSString]> iconv_wrapper:
Could not handle iconv encoding. FromEncoding:UNKNOWN-8BIT to
encoding:UTF-16LE
Dec 04 17:23:10 sogod [1658]: <0x0x7fedcef51e80[NGMimeType]> +[NGMimeType
stringEncodingForCharset:]: unknown charset 'unknown-8bit'
Dec 04 17:23:10 sogod [1658]: <0x0x7fedcdd821a0[NSString]> iconv_wrapper:
Could not handle iconv encoding. FromEncoding:UNKNOWN-8BIT to
encoding:UTF-16LE
Dec 04 17:23:10 sogod [1658]: <0x0x7fedcef51e80[NGMimeType]> +[NGMimeType
stringEncodingForCharset:]: unknown charset 'unknown-8bit'

Does sync continues anyway or have I to worry?

Cheers
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

[SOGo] Activesync Errors

2018-11-22 Thread Riccardo Bicelli
Hello!
I'm trying to tune activesync.

In Activesync I have this error:

Nov 22 08:57:50 sogod [324]: [ERROR] <0x0x55e23408b150[WOHttpTransaction]>
client disconnected during delivery of response for
 (len=13): the
socket was shutdown

My relevant settings are:

Setup is nginx (reverse Proxy) ->httpd->SOGo:

sogo.conf
/* ActiveSync */
WOWorkersCount = 48;
WOWatchDogRequestTimeout = 3540;
SOGoMaximumPingInterval = 3540;
SOGoMaximumSyncInterval = 3540;
SOGoInternalSyncInterval = 30;

/etc/httpd/conf.d/SOGo.conf on sogo side:

 ProxyPass /Microsoft-Server-ActiveSync \
 http://127.0.0.1:2/SOGo/Microsoft-Server-ActiveSync \
 retry=60 connectiontimeout=75 timeout=3540

sogo.conf on nginx side:

location /{
proxy_redirectoff;
proxy_set_header Host $http_host;
proxy_set_header x-webobjects-server-protocol HTTP/1.0;

proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Connection close;
proxy_pass_header Content-Type;
proxy_pass_header Content-Disposition;
proxy_pass_header Content-Length;
proxy_passhttp://[MASKED];

proxy_connect_timeout 90;
proxy_send_timeout 90;
proxy_read_timeout 90;
proxy_buffer_size 4k;
proxy_buffers 4 32k;
proxy_busy_buffers_size 64k;
proxy_temp_file_write_size 64k;
}

location /Microsoft-Server-ActiveSync{
access_log /var/log/nginx/activesync.log;
error_log  /var/log/nginx/activesync-error.log;
resolver [MASKED];

proxy_connect_timeout 75;
proxy_send_timeout 3540;
proxy_read_timeout 3540;

proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

proxy_pass http://[MASKED]/SOGo/Microsoft-Server-ActiveSync;
proxy_redirect http://[MASKED]/SOGo/Microsoft-Server-ActiveSync
/;
}

}

My question is: are these errors normal of is there any parameter I can
tune?

Cheers
Riccardo
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

[SOGo] Activesync errors

2014-11-06 Thread sigurd
Hi !

We have tried to get ActiveSync working since August for our Outlook users.
In the meantime, we have used IMAP/CalDav/ContactDav with varying results.

We now try to get ActiveSync working with the nightly build since there seems
to be a lot of bug fixes.
Unfortunately, we seem to get stuck at the same point as in August.

Using Outlook 2013 I get a lot of different errors in sogo.log for the nightly
build 141106.
The end result is that Outlook won't pick up any emails at all - it just hangs
waiting for server response.

I suspect one (or both) of the following errors might have something to do
with this :

File NSData.m: 3093. In -[NSDataMappedFile initWithContentsOfMappedFile:]
mapping failed for /tmp/OGo7BCD545B4AC148BA.tmp - Invalid argument

xml2wbxmlFromContent: failed: Parsing of XML Document Failed

The xml2wbxmlFromContent references a huge XML file in /tmp which seems to
contain all emails in this particular mailbox.

xmllint says :

 parser error : xmlParseCharRef: invalid xmlChar value 57211
#55356;#57224;#55356;#57224;#55356;#57224;#55356;#57211;#55356;#57211;

So for now, ActiveSync doesn't seem to work.

Is there any way to avoid this - prefiltering the XML file to remove invalid
characters perhaps ?

Regards,
Sigurd Holter
-- 
users@sogo.nu
https://inverse.ca/sogo/lists


Re: [SOGo] Activesync errors

2014-11-06 Thread Christian Mack
Hello Sigurd Holter

Am 2014-11-06 um 11:29 schrieb sig...@westaudio.no:
 
 We have tried to get ActiveSync working since August for our Outlook users.
 In the meantime, we have used IMAP/CalDav/ContactDav with varying results.
 
 We now try to get ActiveSync working with the nightly build since there seems
 to be a lot of bug fixes.
 Unfortunately, we seem to get stuck at the same point as in August.
 
 Using Outlook 2013 I get a lot of different errors in sogo.log for the nightly
 build 141106.
 The end result is that Outlook won't pick up any emails at all - it just hangs
 waiting for server response.
 
 I suspect one (or both) of the following errors might have something to do
 with this :
 
 File NSData.m: 3093. In -[NSDataMappedFile initWithContentsOfMappedFile:]
 mapping failed for /tmp/OGo7BCD545B4AC148BA.tmp - Invalid argument
 
 xml2wbxmlFromContent: failed: Parsing of XML Document Failed
 
 The xml2wbxmlFromContent references a huge XML file in /tmp which seems to
 contain all emails in this particular mailbox.
 
 xmllint says :
 
  parser error : xmlParseCharRef: invalid xmlChar value 57211
 #55356;#57224;#55356;#57224;#55356;#57224;#55356;#57211;#55356;#57211;
 
 So for now, ActiveSync doesn't seem to work.
 
 Is there any way to avoid this - prefiltering the XML file to remove invalid
 characters perhaps ?
 

Did you set SOGoMaximumSyncWindowSize ?

Also see bug #2972
http://www.sogo.nu/bugs/view.php?id=2972
Perhaps this is your problem too.


Kind regards,
Christian Mack

-- 
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416



smime.p7s
Description: S/MIME Cryptographic Signature


Re: [SOGo] Activesync errors

2014-11-06 Thread Sigurd Holter

Hi !

Thank you for your tips.

I have now set SOGoMaximumSyncWindowSize to 50 as suggested in the 
sogo.conf file.
Mails now seem to be arriving, albeit slowly since presumably 50 arrive 
at a time for each send/receive cycle.


I still have to wait and see if the xml2wbxmlFromContent error shows 
usp, buth the NSDataMappedFile error shows up several times for each sync.


I will gather more information and experiences from other users and 
report back if there's any news.


Regards,
Sigurd


Den 06.11.2014 13:47, skrev Christian Mack:

Hello Sigurd Holter

Am 2014-11-06 um 11:29 schrieb sig...@westaudio.no:

We have tried to get ActiveSync working since August for our Outlook users.
In the meantime, we have used IMAP/CalDav/ContactDav with varying results.

We now try to get ActiveSync working with the nightly build since there seems
to be a lot of bug fixes.
Unfortunately, we seem to get stuck at the same point as in August.

Using Outlook 2013 I get a lot of different errors in sogo.log for the nightly
build 141106.
The end result is that Outlook won't pick up any emails at all - it just hangs
waiting for server response.

I suspect one (or both) of the following errors might have something to do
with this :

File NSData.m: 3093. In -[NSDataMappedFile initWithContentsOfMappedFile:]
mapping failed for /tmp/OGo7BCD545B4AC148BA.tmp - Invalid argument

xml2wbxmlFromContent: failed: Parsing of XML Document Failed

The xml2wbxmlFromContent references a huge XML file in /tmp which seems to
contain all emails in this particular mailbox.

xmllint says :

  parser error : xmlParseCharRef: invalid xmlChar value 57211
#55356;#57224;#55356;#57224;#55356;#57224;#55356;#57211;#55356;#57211;

So for now, ActiveSync doesn't seem to work.

Is there any way to avoid this - prefiltering the XML file to remove invalid
characters perhaps ?


Did you set SOGoMaximumSyncWindowSize ?

Also see bug #2972
http://www.sogo.nu/bugs/view.php?id=2972
Perhaps this is your problem too.


Kind regards,
Christian Mack



--
MVH
Sigurd Holter
Bookingleder/prosjektleder
West Audio A/S
Consul Sigval Bergesens vei 41
4016 Stavanger
Telefon 51537030

--
users@sogo.nu
https://inverse.ca/sogo/lists


Re: [SOGo] Activesync errors

2014-11-06 Thread Ludovic Marcotte

On 06/11/2014 05:29, sig...@westaudio.no wrote:

xmllint says :

  parser error : xmlParseCharRef: invalid xmlChar value 57211
#55356;#57224;#55356;#57224;#55356;#57224;#55356;#57211;#55356;#57211;
Someone finally sent me a data set this morning and I was able to 
reproduce the issue.


The issue has just been fixed and pushed in master.

--
Ludovic Marcotte
lmarco...@inverse.ca  ::  +1.514.755.3630  ::  http://inverse.ca
Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence 
(http://packetfence.org)

--
users@sogo.nu
https://inverse.ca/sogo/lists