Discussion:
[SOGo] Updated to v3.0.2 / Centos 7.2.x / Web UI - Inbox doesn't open
f***@garbage-juice.com
2016-03-06 23:25:19 UTC
Permalink
Hello,

I switched my repo to that of v3 Sogo and updated my installation today.

I also use nginx and centos 7.2.x.

As of now, i can no longer open my inboxes in the web UI. Activesync
seems to work fine on my mobile devices. My sogo log reports:

Mar 06 17:59:10 sogod [10019]: <0x0x563aa66570d0[SOGoCache]> Using
host(s) '127.0.0.1' as server(s)
Mar 06 17:59:10 sogod [10019]: localhost "GET
/SOGo/so/***@garbage-juice.com/Mail/view HTTP/1.0" 200 14748/0
0.081 66066 77% 6M
Mar 06 17:59:12 sogod [10019]: [WARN]
<0x0x563aa6a10c40[SOGoWebDAVAclManager]> entry '{DAV:}write' already
exists in DAV permissions table
Mar 06 17:59:12 sogod [10019]: [WARN]
<0x0x563aa6a10c40[SOGoWebDAVAclManager]> entry '{DAV:}write-properties'
already exists in DAV permissions table
Mar 06 17:59:12 sogod [10019]: [WARN]
<0x0x563aa6a10c40[SOGoWebDAVAclManager]> entry '{DAV:}write-content'
already exists in DAV permissions table
Mar 06 17:59:12 sogod [10019]: localhost "GET
/SOGo/so/***@garbage-juice.com/Calendar/alarmslist?browserTime=1457305156
HTTP/1.0" 200 63/0 0.007 - - 256K
Mar 06 17:59:12 sogod [4127]: localhost "GET
/SOGo/so/***@garbage-juice.com/jsonSettings HTTP/1.0" 200 189/0
0.003 - - 0
Mar 06 17:59:12 sogod [10019]: localhost "GET
/SOGo/so/***@garbage-juice.com/jsonDefaults HTTP/1.0" 200 2125/0
0.009 - - 12K
EXCEPTION: <NSException: 0x563aa63dc030> NAME:NSInvalidArgumentException
REASON:NGImap4Connection(instance) does not recognize
allFoldersMetadataForURL:onlySubscribedFolders: INFO:(null)

In Chrome, I simply see 'OK' in a pop down message.

In firefox, I see "Bad gateway" in the same box.

My nginx error log reports:

2016/03/06 17:59:12 [error] 4354#4354: *2 upstream prematurely closed
connection while reading response header from upstream, client: x.x.x.x,
server: _, request: "GET
/SOGo/so/***@garbage-juice.com/Mail/0/view HTTP/2.0", upstream:
"http://127.0.0.1:20000/SOGo/so/***@garbage-juice.com/Mail/0/view",
host: "mail.garbage-juice.com", referrer:
"https://mail.garbage-juice.com/SOGo/so/***@garbage-juice.com/Mail/view"


What could be going on? This worked fine prior to my upgrade with v2.3.8
(latest).

Thanks.

- Fabian S.
--
***@sogo.nu
https://inverse.ca/sogo/lists
Purga
2016-03-08 07:30:29 UTC
Permalink
Have you updated the SQL tables as well?

https://github.com/inverse-inc/sogo/tree/master/Scripts
Post by f***@garbage-juice.com
Hello,
I switched my repo to that of v3 Sogo and updated my installation today.
I also use nginx and centos 7.2.x.
As of now, i can no longer open my inboxes in the web UI. Activesync
Mar 06 17:59:10 sogod [10019]: <0x0x563aa66570d0[SOGoCache]> Using host(s)
'127.0.0.1' as server(s)
Mar 06 17:59:10 sogod [10019]: localhost "GET /SOGo/so/
77% 6M
Mar 06 17:59:12 sogod [10019]: [WARN]
<0x0x563aa6a10c40[SOGoWebDAVAclManager]> entry '{DAV:}write' already exists
in DAV permissions table
Mar 06 17:59:12 sogod [10019]: [WARN]
<0x0x563aa6a10c40[SOGoWebDAVAclManager]> entry '{DAV:}write-properties'
already exists in DAV permissions table
Mar 06 17:59:12 sogod [10019]: [WARN]
<0x0x563aa6a10c40[SOGoWebDAVAclManager]> entry '{DAV:}write-content'
already exists in DAV permissions table
Mar 06 17:59:12 sogod [10019]: localhost "GET /SOGo/so/
HTTP/1.0" 200 63/0 0.007 - - 256K
Mar 06 17:59:12 sogod [4127]: localhost "GET /SOGo/so/
Mar 06 17:59:12 sogod [10019]: localhost "GET /SOGo/so/
12K
EXCEPTION: <NSException: 0x563aa63dc030> NAME:NSInvalidArgumentException
REASON:NGImap4Connection(instance) does not recognize
allFoldersMetadataForURL:onlySubscribedFolders: INFO:(null)
In Chrome, I simply see 'OK' in a pop down message.
In firefox, I see "Bad gateway" in the same box.
2016/03/06 17:59:12 [error] 4354#4354: *2 upstream prematurely closed
connection while reading response header from upstream, client: x.x.x.x,
HTTP/2.0", upstream: "
host: "mail.garbage-juice.com", referrer: "
"
What could be going on? This worked fine prior to my upgrade with v2.3.8
(latest).
Thanks.
- Fabian S.
--
https://inverse.ca/sogo/lists
--
***@sogo.nu
https://inverse.ca/sogo/lists
f***@garbage-juice.com
2016-03-08 15:59:06 UTC
Permalink
I looked at the scripts..judging by the file names, they don't seem to
apply to my case considering i updated from v2.3.8 to v3.0.2. am i
wrong?

- Fabe
Post by Purga
Have you updated the SQL tables as well?
https://github.com/inverse-inc/sogo/tree/master/Scripts
Post by f***@garbage-juice.com
Hello,
I switched my repo to that of v3 Sogo and updated my installation today.
I also use nginx and centos 7.2.x.
As of now, i can no longer open my inboxes in the web UI.
Activesync seems to work fine on my mobile devices. My sogo log
Mar 06 17:59:10 sogod [10019]: <0x0x563aa66570d0[SOGoCache]> Using
host(s) '127.0.0.1' as server(s)
Mar 06 17:59:10 sogod [10019]: localhost "GET
14748/0 0.081 66066 77% 6M
Mar 06 17:59:12 sogod [10019]: [WARN]
<0x0x563aa6a10c40[SOGoWebDAVAclManager]> entry '{DAV:}write' already
exists in DAV permissions table
Mar 06 17:59:12 sogod [10019]: [WARN]
<0x0x563aa6a10c40[SOGoWebDAVAclManager]> entry
'{DAV:}write-properties' already exists in DAV permissions table
Mar 06 17:59:12 sogod [10019]: [WARN]
<0x0x563aa6a10c40[SOGoWebDAVAclManager]> entry '{DAV:}write-content'
already exists in DAV permissions table
Mar 06 17:59:12 sogod [10019]: localhost "GET
[2] HTTP/1.0" 200 63/0 0.007 - - 256K
Mar 06 17:59:12 sogod [4127]: localhost "GET
189/0 0.003 - - 0
Mar 06 17:59:12 sogod [10019]: localhost "GET
2125/0 0.009 - - 12K
EXCEPTION: <NSException: 0x563aa63dc030>
NAME:NSInvalidArgumentException REASON:NGImap4Connection(instance)
INFO:(null)
In Chrome, I simply see 'OK' in a pop down message.
In firefox, I see "Bad gateway" in the same box.
2016/03/06 17:59:12 [error] 4354#4354: *2 upstream prematurely
closed connection while reading response header from upstream,
client: x.x.x.x, server: _, request: "GET
What could be going on? This worked fine prior to my upgrade with
v2.3.8 (latest).
Thanks.
- Fabian S.
--
https://inverse.ca/sogo/lists
--
https://inverse.ca/sogo/lists
------
[2]
[6] http://mail.garbage-juice.com
--
***@sogo.nu
https://inverse.ca/sogo/lists
f***@garbage-juice.com
2016-03-08 15:57:28 UTC
Permalink
Does upgrading via YUM not accomplish this automatically? Should there
not be a warning to do so otherwise? I will look into this now...

- Fabe
Post by Purga
Have you updated the SQL tables as well?
https://github.com/inverse-inc/sogo/tree/master/Scripts
Post by f***@garbage-juice.com
Hello,
I switched my repo to that of v3 Sogo and updated my installation today.
I also use nginx and centos 7.2.x.
As of now, i can no longer open my inboxes in the web UI.
Activesync seems to work fine on my mobile devices. My sogo log
Mar 06 17:59:10 sogod [10019]: <0x0x563aa66570d0[SOGoCache]> Using
host(s) '127.0.0.1' as server(s)
Mar 06 17:59:10 sogod [10019]: localhost "GET
14748/0 0.081 66066 77% 6M
Mar 06 17:59:12 sogod [10019]: [WARN]
<0x0x563aa6a10c40[SOGoWebDAVAclManager]> entry '{DAV:}write' already
exists in DAV permissions table
Mar 06 17:59:12 sogod [10019]: [WARN]
<0x0x563aa6a10c40[SOGoWebDAVAclManager]> entry
'{DAV:}write-properties' already exists in DAV permissions table
Mar 06 17:59:12 sogod [10019]: [WARN]
<0x0x563aa6a10c40[SOGoWebDAVAclManager]> entry '{DAV:}write-content'
already exists in DAV permissions table
Mar 06 17:59:12 sogod [10019]: localhost "GET
[2] HTTP/1.0" 200 63/0 0.007 - - 256K
Mar 06 17:59:12 sogod [4127]: localhost "GET
189/0 0.003 - - 0
Mar 06 17:59:12 sogod [10019]: localhost "GET
2125/0 0.009 - - 12K
EXCEPTION: <NSException: 0x563aa63dc030>
NAME:NSInvalidArgumentException REASON:NGImap4Connection(instance)
INFO:(null)
In Chrome, I simply see 'OK' in a pop down message.
In firefox, I see "Bad gateway" in the same box.
2016/03/06 17:59:12 [error] 4354#4354: *2 upstream prematurely
closed connection while reading response header from upstream,
client: x.x.x.x, server: _, request: "GET
What could be going on? This worked fine prior to my upgrade with
v2.3.8 (latest).
Thanks.
- Fabian S.
--
https://inverse.ca/sogo/lists
--
https://inverse.ca/sogo/lists
------
[2]
[6] http://mail.garbage-juice.com
--
***@sogo.nu
https://inverse.ca/sogo/lists
Fabian Santiago
2016-03-13 13:59:09 UTC
Permalink
Sorry my mobile device didn't reply to the list. Here it is ; see below.

Sincerely,

Fabian Santiago

Sent from my iPhone
Date: March 13, 2016 at 9:31:46 AM EDT
Subject: Re: [SOGo] Updated to v3.0.2 / Centos 7.2.x / Web UI - Inbox doesn't open
Hi Jim,
Yum reinstall sope49-*
Was my command line.
Restarted sogod afterwards and was good to go.
Since then I've also switched my yum repo definition for sogo to the nightly builds repo because you'll also discover after going to v3.0.2 that mime parts are broken in email viewing via EAS / mobile devices. The fix is slated for v3.0.3 I believe but it is in the nightly build repo for now.
I also updated my nginx configs for sogo based on the lists recommendations. Only minor tweaks. I have those too if need be. Let me know.
Hope this helps.
Sincerely,
Fabian Santiago
Sent from my iPhone
Hi Fabian. I saw your post regarding SOGo issue. I did a google search and stumbled across your article. Unfortunately, I made the same error doing a "yum update". I am using CentOS 6.7 with iRedMail and I am seeing the same problem you’re seeing. It started to work at first. The users were commenting on the new SOGo look which they liked, but then we’re seeing Proxy Error message on our browser. We have not been able to use SOGo for a week now. I am having my users use RoundCube instead.
I was not aware that this was a major update. This seems kind of bad, but I guess I get what I paid for
 If you were able to fix the problem, can you please share your fix? Thanks in advance.
—
Jim
http://article.gmane.org/gmane.comp.groupware.sogo.user/23871
--
***@sogo.nu
https://inverse.ca/sogo/lists
Fabian Santiago
2016-03-14 03:16:15 UTC
Permalink
I don't know what that file is for. The list may know...?

I am glad I could help but the real help is this list. That's where I've found my answers. I'm really just a sogo newb and have only recently started using it more often as I previously used roundcube and imap almost exclusively.

Sincerely,

Fabian Santiago

Sent from my iPhone
Hi Fabian. I tried what you suggested. I reinstalled sope49-\* packages and restarted SOGo. I still got the same Proxy Error from the web browser.
I also noticed the attachments not working properly. A few of our users are using iOS and we could no longer see attachments after the 3.0.2 update. The work around was to remove the account from iOS and re-add it as Other (IMAP) instead of Microsoft Exchange account. That seems to work, but we lose some functionality.
So, I just went ahead and changed my repo to point to nightly. I did a ‘yum check-update’ and it showed that sope49 packages were out of date. So, I went ahead and updated it from nightly. This seemed to fix my login problem! I can login on SOGo again from the web. Will try again to see if MS Exchange attachments is working again.
btw, do you know what this file is for, /usr/share/doc/sogo-3.0.2/SOGo-apple-ab.conf? Is this to give better integration for OS X and iOS?
Thanks so much for your help!
—
Jim
Hi Jim,
Yum reinstall sope49-*
Was my command line.
Restarted sogod afterwards and was good to go.
Since then I've also switched my yum repo definition for sogo to the nightly builds repo because you'll also discover after going to v3.0.2 that mime parts are broken in email viewing via EAS / mobile devices. The fix is slated for v3.0.3 I believe but it is in the nightly build repo for now.
I also updated my nginx configs for sogo based on the lists recommendations. Only minor tweaks. I have those too if need be. Let me know.
Hope this helps.
Sincerely,
Fabian Santiago
Sent from my iPhone
Hi Fabian. I saw your post regarding SOGo issue. I did a google search and stumbled across your article. Unfortunately, I made the same error doing a "yum update". I am using CentOS 6.7 with iRedMail and I am seeing the same problem you’re seeing. It started to work at first. The users were commenting on the new SOGo look which they liked, but then we’re seeing Proxy Error message on our browser. We have not been able to use SOGo for a week now. I am having my users use RoundCube instead.
I was not aware that this was a major update. This seems kind of bad, but I guess I get what I paid for
 If you were able to fix the problem, can you please share your fix? Thanks in advance.
—
Jim
http://article.gmane.org/gmane.comp.groupware.sogo.user/23871
--
***@sogo.nu
https://inverse.ca/sogo/lists

Loading...