I do get JavaScript/angularjs errors in my browser:
Error: [$rootScope:infdig]
http://errors.angularjs.org/1.4.10/$rootScope/infdig?p0=10=%5B%5D
at n.prototype.$digest
(https://coda.pw/SOGo.woa/WebServerResources/js/vendor/angular.min.js:133:304)
at n.prototype.$apply
I just tried an upgrade to the latest nightly version. Nothing changed,
so I guess that it is in my configuration.
Could this be related to the upgrade scripts that need to be run after
installation? I ran:
"sql-update-3.0.0-to-combined-mysql.sh" which finished fine.
I also tried
Hi all,
I wanted to say that I also experience a somewhat slow web interface:
my config:
http://pastebin.com/hsAAfzja
Memcached runs and sogo successfully connects to it
[root@mail ~]# netstat -anptul | grep 11211 | grep sogo
tcp0 0 127.0.0.1:44389 127.0.0.1:11211
Hello!
I think so, yes:
● memcached.service - memcached daemon
Loaded: loaded (/lib/systemd/system/memcached.service; enabled)
Active: active (running) since Mon 2016-04-18 22:13:26 CEST; 13h ago
Main PID: 458 (memcached)
CGroup: /system.slice/memcached.service
└─458
Is there anything wrong with my configuration? I did not change it
between updates anyway, so I do not think that it is the cause of the
problem. I came from SOGo 3.0 and there were no issues.
Am 14.04.2016 um 21:52 schrieb Adrian Figueroa (adr...@figueroa.cc):
I installed SOGo as part of the
I installed SOGo as part of the iRedMail package. I think that a sieve
server is running but I do not know any details. The logs of both apache
and SOGo do not show any errors by the way.
Here is my sogo.conf:
https://s.coda.pw/?2c92588d72036759#1Gpf7sI7DS6bZtBptctyaZmGLmp3RpDG8JGao7gfkJM=
Can you paste your sogo.conf ?
Did you setup a sieve server and if so, is it really working ?
On Thu, Apr 14, 2016 at 02:29 PM, Adrian Figueroa wrote:
Hello,
I am having issues with the SOGo web interface. It is very slow to load
and react anything.
It was running well before upgrading to
Hello,
I am having issues with the SOGo web interface. It is very slow to load
and react anything.
It was running well before upgrading to 3.0.2. I have a worker count of
40 and all other requests (Thunderbird, Exchange on phones etc.) run
fast and fine.
What could be the problem?
Kind