RTC Forums
November 30, 2021, 06:06:51 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
 
   Home   Help Login Register  
Pages: [1]
  Print  
Author Topic: RTC server stops responding  (Read 896 times)
thomh
RTC License+
****
Posts: 15


« on: September 24, 2020, 11:22:10 AM »

Hi Danijel,

I have a web server running with RTC v930 and StreamSec4 that have crashed a couple of times at one of our customer sites.

I found these ERR! entries in the log file:

2020-09-08 16:44:00.879; ERR! 172.20.100.167 > paperless:9900 "GET /pllogin.html" -178866 REF "https://paperless:9900/pldocportal.html" AGENT "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36" 64240/243106 bytes in 58500 ms =1 kbits

2020-09-08 16:44:56.127; ERR! 172.20.100.167 > paperless:9900 "GET /" -178866 REF "" AGENT "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36" 64240/243106 bytes in 15 ms =4282 kbits

2020-09-22 10:51:10.784; ERR! 193.117.200.65 > paperless.theivy-collection.com:9900 "GET /pldocportal.js" -47855 REF "https://paperless.theivy-collection.com:9900/pldocportal.html" AGENT "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" 770880/818735 bytes in 2297 ms =335 kbits

This one caused to server to stop working:

2020-09-22 14:43:45.763; ERR! 82.152.32.135 > paperless.theivy-collection.com:9900 "GET /" -178866 REF "" AGENT "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" 64240/243106 bytes in 346781 ms =0 kbits
2020-09-22 14:43:45.763; ---- 40.94.100.58: 49672 [0 open]
2020-09-22 14:43:45.779; ---- 40.94.100.86: 49673 [0 open]
2020-09-22 14:43:45.779; ++++ 10.0.1.92: 59979 [0 open]
2020-09-22 14:43:45.998; ++++ 82.152.32.135: 57939 [0 open]
2020-09-22 14:43:46.013; ---- 10.0.1.92: 59979 [0 open]
2020-09-22 14:43:46.201; ++++ 82.152.32.135: 57940 [0 open]
2020-09-22 21:40:44.846; ServiceTimer created at 2020-09-22 21:40:44 Interval = 8295154
2020-09-22 21:40:44.846; ServiceTimer set to run at 2020-09-22 23:59:00
2020-09-22 21:40:45.517; SERVER STARTED on Port 9900 ...

In the TFileProvider.FileProviderDisconnect method I see the code which produces these log entries:

// did not send a complete result
XLog('BRK! '+PeerAddr+' > '+Request.Host+
  ' "'+Request.Method+' '+Request.URI+'"'+
  ' -'+Int2Str(Response.DataSize-Response.DataOut)+
  ' REF "'+Request.Referer+'"'+
  ' AGENT "'+Request.Agent+'" '+
  Int2Str(Response.DataOut)+' bytes in '+
  Int2Str(GetTickTime-Request.Info.asLargeInt['$time'])+' ms ='+
  Int2Str(Response.DataOut div tim)+' kbits');

What causes the server not to send complete results?

// Thom
Logged
D.Tkalcec (RTC)
Administrator
*****
Posts: 1861


« Reply #1 on: September 24, 2020, 12:13:41 PM »

The entries you've found only contain some general request/response information, which don't help much when it comes to debugging. Anything can cause the Server to stop sending complete responses, from something as simple as a disconnect (which could be caused by the Client, or by the Server, or by anything in-between) to all kinds of bugs in code.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.023 seconds with 16 queries.