View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003384SOGoWeb Calendarpublic2015-11-11 18:132015-11-17 18:55
Reporterukovataga Assigned Tofrancis  
PrioritynormalSeverityblockReproducibilityalways
Status resolvedResolutionno change required 
PlatformLinux x86_64 (amd64)OSDebianOS Version8.0 (Jessie)
Product Version2.2.9 
Summary0003384: Can't subscribe remote calendar via http_proxy, leading to blocking behaviour for login
Description

<b>I am using SOGo in the following conditions:</b>

  • SOGo was installed as Debian package via debian default repository from the current stable release (apt-get install sogo) on machine A.
  • The machine A sits behind a firewall on machine F.
  • Outgoing http(s) traffic through that firewall on machine F is only possible using another machine P, a webproxy (Squid).

<b>Outgoing http(s) traffic is working by accomplishing these steps:</b>

  • Gateway is set.
  • Modified /etc/environment to export http_proxy variable
  • Modified visudo to make also possible to use by sudoers.
  • Verfied with: wget www.google.com -O /dev/null AND sudo -u sogo wget www.google.com -O /dev/null

<b>Problem:</b>
When I try to subscribe to any web calendar with public access in the calendar tab, nothing happens for a long time (approx. 2 minutes). After that a message is raised with the text "An error occurred while loading remote calendar: the url in use is invalid or the host is currently unreachable.".

But now let me explain the blocking behaviour. If I don't delete the failing subscription, the WOWatchDog will prevent me from logging in! I assume it's because the default tab is the calendar view and the after logging in instantiated child is trying to fetch the subscribed calendar. But I can't prove that.

<b>Log-Output:</b>
This piece of Log is not cut inbetween. It shows the login, the polling on the WOWatchDog and the final POST of the SOGo GUI if a child becomes available again.

Nov 11 00:09:23 sogod [1693]: SOGoRootPage successful login from '93.92.91.90' for user 'blableblu' - expire = -1 grace = -1
Nov 11 00:09:48 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:09:49 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:09:51 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:09:52 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:09:53 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:09:55 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:09:56 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:09:58 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:09:59 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:01 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:02 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:03 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:05 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:06 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:08 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:09 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:10 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:12 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:13 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:15 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:16 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:17 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:19 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:20 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:22 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:23 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:23 sogod [1692]: [WARN] <0x0x7fb024aea320[WOWatchDogChild]> pid 1693 has been hanging in the same request for 1 minutes
Nov 11 00:10:25 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:26 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:27 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:29 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:30 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:32 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:33 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:34 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:36 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:37 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:39 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:40 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:42 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:43 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:44 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:46 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:47 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:49 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:50 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:51 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:53 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:54 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:56 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:57 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:10:59 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:00 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:01 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:03 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:04 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:06 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:07 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:08 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:10 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:11 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:13 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:14 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:16 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:17 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:18 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:20 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:21 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:23 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:23 sogod [1692]: [WARN] <0x0x7fb024aea320[WOWatchDogChild]> pid 1693 has been hanging in the same request for 2 minutes
Nov 11 00:11:24 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:26 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:27 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:28 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
Nov 11 00:11:30 sogod [1692]: [ERROR] <0x0x7fb024874400[WOWatchDog]> No child available to handle incoming request!
93.92.91.90 - - [11/Nov/2015:00:11:31 GMT] "POST /SOGo/connect HTTP/1.1" 200 27/48 127.371 - - 284K

<b>Additional notes:</b>
Increasing workers, RAM, CPU and so on doesn't help. More detailed logs are not given.

Steps To Reproduce

Another similar bug report:
http://www.sogo.nu/bugs/view.php?id=1491

But that doesn't help me.

Additional Information

<b>uname -srmv</b>
Linux 3.16.0-4-amd64 0000001 SMP Debian 3.16.7-ckt4-3 (2015-02-03) x86_64

<b>lsb_release -a</b>
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie

<b>dpkg -s sogo</b>
Package: sogo
Status: install ok installed
Priority: optional
Section: mail
Installed-Size: 6020
Maintainer: Jeroen Dekkers <jeroen@dekkers.ch>
Architecture: amd64
Version: 2.2.9+git20141017-1
Depends: gnustep-base-runtime (>= 1.24.6), libc6 (>= 2.14), libcurl3-gnutls (>= 7.16.2), libgcc1 (>= 1:4.1.1), libglib2.0-0 (>= 2.14.0), libgnustep-base1.24 (>= 1.24.6), libgnutls-deb0-28 (>= 3.3.0), liblasso3 (>= 2.4.1), libmemcached11, libobjc4 (>= 4.6), libsbjson2.3, libsope1 (>= 2.2.9), tmpreaper | systemd, sogo-common (= 2.2.9+git20141017-1), adduser, zip

TagsNo tags attached.

Activities

ukovataga

ukovataga

2015-11-11 18:17

reporter   ~0009088

Oh, I have to add something. If i delete the (failing) subscription then the problems don't show up anymore:
a) Login is not error prone (no blocking).
b) No error msg in calendar tab.

If I add the subscription, then the problems return.
ukovataga

ukovataga

2015-11-11 18:18

reporter   ~0009089

I am using SOGo alone just for evaluation purposes. So no other user might infer with that problem.
ukovataga

ukovataga

2015-11-11 18:20

reporter   ~0009090

Sorry for that much messaging.

I was searching on your mailing lists, on google and within this bugtracker. I couldn't find any similar description with a diagnosis.
ukovataga

ukovataga

2015-11-13 23:21

reporter   ~0009097

Hello again, I added the inverse.ca sogo-repository for jessie, did a reinstall of sogo (now 2.3.3), performed the db-update with sql-update-2.2.17_to_2.3.0.sh and hoped that the problem will disappear.

It doesn't, so it's still present.

Additionally I wsa skimming your github-repos. But i cannot find something related to http_proxy.
tfu

tfu

2015-11-16 12:41

reporter   ~0009098

Have you tried to set "export http_proxy=..." in /etc/default/sogo?
ukovataga

ukovataga

2015-11-17 15:03

reporter   ~0009101

Last edited: 2015-11-17 15:03

No. From my understanding an export of that variable in /etc/environment would set the proxy globally. So I would only overwrite it by setting it in /etc/default/sogo locally.

Despite this I tried to set it locally (after your comment), but <u>without</u> success. Same result.
tfu

tfu

2015-11-17 17:11

reporter   ~0009102

How do you start sogod? Via a service?
/etc/environment is not read by debians' service infrastructure.
You can check /proc/<pid of sogod>/environ to make sure that http_proxy is set.
ukovataga

ukovataga

2015-11-17 18:04

reporter   ~0009103

Yes, I'm starting it as a service.

Obviously I did something wrong when I was following your instructions (in 0009101).

Setting the proxy worked with the following (as you mentioned):
<b>sudo nano -w /etc/default/sogo</b>

The amount of processes that should be spawned (Default: 3)

PREFORK=3

The name of the account under which SOGo will be running (Default: sogo)

USER=sogo

export http_proxy=http://my.url:port

As noted in your last comment I can see the variable being set in /proc/<pid of sogod>/environ.

Thank you very much. I'm sorry that I didn't get that on my own. But I really appreciate your help.

May others benefit from this bug report.

Issue History

Date Modified Username Field Change
2015-11-11 18:13 ukovataga New Issue
2015-11-11 18:17 ukovataga Note Added: 0009088
2015-11-11 18:18 ukovataga Note Added: 0009089
2015-11-11 18:20 ukovataga Note Added: 0009090
2015-11-13 23:21 ukovataga Note Added: 0009097
2015-11-16 12:41 tfu Note Added: 0009098
2015-11-17 15:03 ukovataga Note Added: 0009101
2015-11-17 15:03 ukovataga Note Edited: 0009101
2015-11-17 17:11 tfu Note Added: 0009102
2015-11-17 18:04 ukovataga Note Added: 0009103
2015-11-17 18:55 francis Status new => resolved
2015-11-17 18:55 francis Resolution open => no change required
2015-11-17 18:55 francis Assigned To => francis