Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Operator » Nginx error
  •  
Carconnex

Messages: 44
Karma: 0
Send a private message to this user
Hi,

since yesterday we are getting a lot of error messages on our Operator.
Could anybody explain what it means or what might be causing this?


[14/Jun/2017 14:30:33] nginx: 2017/06/14 14:30:33 [error] 3215#0: *78542 upstream prematurely closed connection while reading response header from upstream, client: 84.199.38.106, server: , request: "GET /ws HTTP/1.1", upstream: "http://127.0.0.1:5080/ws", host: "our hostname"
[14/Jun/2017 14:30:36] nginx: 2017/06/14 14:30:36 [error] 3215#0: *78544 upstream prematurely closed connection while reading response header from upstream, client: 84.199.38.106, server: , request: "GET /ws HTTP/1.1", upstream: "http://127.0.0.1:5080/ws", host: "our hostname"
[14/Jun/2017 14:30:41] nginx: 2017/06/14 14:30:41 [error] 3216#0: *78546 upstream prematurely closed connection while reading response header from upstream, client: 84.199.38.106, server: , request: "GET /ws HTTP/1.1", upstream: "http://127.0.0.1:5080/ws", host: "our hostname"
[14/Jun/2017 14:30:42] nginx: 2017/06/14 14:30:42 [error] 3216#0: *78548 upstream prematurely closed connection while reading response header from upstream, client: 89.172.181.95, server: , request: "GET /ws HTTP/1.1", upstream: "http://127.0.0.1:5080/ws", host: "our hostname"

[15/Jun/2017 10:20:54] nginx: 2017/06/15 10:20:54 [error] 3214#0: *141928 upstream prematurely closed connection while reading response header from upstream, client: 10.0.0.1, server: , request: "GET /ws HTTP/1.1", upstream: "http://127.0.0.1:5080/ws", host: "our hostname"
[15/Jun/2017 10:20:59] nginx: 2017/06/15 10:20:59 [error] 3214#0: *141930 upstream prematurely closed connection while reading response header from upstream, client: 10.0.0.1, server: , request: "GET /ws HTTP/1.1", upstream: "http://127.0.0.1:5080/ws", host: "our hostname"
[15/Jun/2017 10:21:21] nginx: 2017/06/15 10:21:21 [error] 3215#0: *141934 upstream prematurely closed connection while reading response header from upstream, client: 10.0.0.1, server: , request: "GET /ws HTTP/1.1", upstream: "http://127.0.0.1:5080/ws", host: "our hostname"
[15/Jun/2017 10:22:25] nginx: 2017/06/15 10:22:25 [error] 3216#0: *142006 upstream prematurely closed connection while reading response header from upstream, client: 10.0.0.1, server: , request: "GET /ws HTTP/1.1", upstream: "http://127.0.0.1:5080/ws", host: "our hostname"
[15/Jun/2017 10:23:12] nginx: 2017/06/15 10:23:12 [error] 3215#0: *142056 upstream prematurely closed connection while reading response header from upstream, client: 10.0.0.1, server: , request: "GET /ws HTTP/1.1", upstream: "http://127.0.0.1:5080/ws", host: "our hostname"


[14/Jun/2017 14:20:05] Connect Integration: Unknown message data: 49 FETCH
[14/Jun/2017 14:30:33] Asterisk: HTTP session count exceeded 100 sessions.
[14/Jun/2017 14:30:36] Asterisk: HTTP session count exceeded 100 sessions.
[14/Jun/2017 14:30:41] Asterisk: HTTP session count exceeded 100 sessions.
[14/Jun/2017 14:30:42] Asterisk: HTTP session count exceeded 100 sessions.
[14/Jun/2017 14:30:46] Asterisk: HTTP session count exceeded 100 sessions.
[14/Jun/2017 14:30:50] Asterisk: HTTP session count exceeded 100 sessions.
[14/Jun/2017 14:30:51] Asterisk: HTTP session count exceeded 100 sessions.
[14/Jun/2017 14:30:54] Asterisk: HTTP session count exceeded 100 sessions.
[14/Jun/2017 14:30:58] Connect Integration: Unknown message data: 3696 FETCH
[14/Jun/2017 14:30:59] Asterisk: HTTP session count exceeded 100 sessions.
  •  
Brian Carmichael (Kerio)

Messages: 725
Karma: 70
Send a private message to this user
There seems to be a bug in the web engine. Please contact technical support and provide them with this and other requested log data. Unfortunately the only solution is to restart the system.

Brian Carmichael
Senior Technical Marketing Engineer | Kerio
Stay Connected Anytime, Anywhere. Discover Kerio Cloud!
  •  
alainrussell

Messages: 75
Karma: 3
Send a private message to this user
I've just filed a similar request with support - did you ever hear back with a resolution? Thanks.
  •  
Carconnex

Messages: 44
Karma: 0
Send a private message to this user
Rebooting the server seemed to fix the problem. Haven't had any more of these entries in the logbook since that time.
  •  
alainrussell

Messages: 75
Karma: 3
Send a private message to this user
I've seen this 3 times now, restarting the server/services isn't really a long term option so will keep trying support (nothing from them yet .. )
  •  
PPG

Messages: 73
Karma: 4
Send a private message to this user
And it also affects the MyKerio functionality.
  •  
alainrussell

Messages: 75
Karma: 3
Send a private message to this user
I've had 2 replies from support on this now, one saying the issue is known, the second telling me there is no date for a fix and to submit a suggestion? That's taken 2 weeks - in the meantime we've replaced Operator with another server/app we're trying. A VOIP server that can't receive calls daily wasn't much use to us..
Previous Topic: Filemaker Pro
Next Topic: Dialing invalid number on grandstream GXP2130: No error tone, no message on display - just reset
Goto Forum:
  


Disclaimer:
Kerio discussion forums are intended for open communication between forum members and may contain information and material posted by members which may be useful in learning about Kerio products. The discussion forums are not intended to provide technical support for any specific product. Any information implied or expressed in the discussion forums is that of the posting member. Kerio is in no way responsible for the information posted in the forums, or its accuracy. Kerio employees may participate in the discussions, but their postings do not represent an offical position of the company on any issues raised or discussed. Kerio reserves the right to monitor and maintain the forums to promote free and accurate exchange of information.

Current Time: Thu Aug 17 15:44:01 CEST 2017

Total time taken to generate the page: 0.00440 seconds
.:: Contact :: Home ::.
Powered by: FUDforum 3.0.4.