Subscribe for automatic updates: RSS icon RSS

Login icon Sign in for full access | Help icon Help
Advanced search

Pages: [1]
  Reply  |  Print  
Author Topic: fastcgidispatch stopping  (Read 1069 times)
Gary C.
Posts: 74


« on: December 03, 2019, 12:43:28 pm »

Hi

Just wondering if any other user has had similar experiences they can share. We run Apache and GAS on the same server and use fastcgidispatch. The server does not appear to be stressed. On two occasions over the past week we have had a situation were all sessions have been terminated.

On looking, I can see that the fastcgidispatch -s process is not running, but restarting it does not seem to solve the problem. I have to date restarted the server and the services to restore normal operations.

Looking in the apache error log I can see the following entries:

Code
  1. [Mon Dec 02 09:40:41.036717 2019] [proxy:error] [pid 1608:tid 140488589903616] AH00940: FCGI: disabled connection for (localhost)
  2. [Mon Dec 02 09:40:43.043685 2019] [proxy:error] [pid 1608:tid 140488823146240] AH00940: FCGI: disabled connection for (localhost)
  3. [Mon Dec 02 09:40:45.058024 2019] [proxy:error] [pid 1608:tid 140488573118208] AH00940: FCGI: disabled connection for (localhost)
  4. [Mon Dec 02 09:40:47.064385 2019] [proxy:error] [pid 1609:tid 140488707401472] AH00940: FCGI: disabled connection for (localhost)
  5.  

Many thanks
Gary
Reuben B.
Four Js
Posts: 625


« Reply #1 on: December 03, 2019, 09:17:08 pm »

Have you looked in our logs?
Gary C.
Posts: 74


« Reply #2 on: December 04, 2019, 12:31:30 pm »

Hello

It has literally just happened again.

I have looked in the fastcgidispatch log file but this gave no insight into the cause. Are there other logs I can look at? There are many, many proxy and dvm logs.

For reference, to restore services I am require to restart Apache and then start fastcgidispatch in standalone mode.

Gary
Neil M.
Four Js
Posts: 18


« Reply #3 on: December 17, 2019, 02:17:36 pm »

Just to update on the state of this case.
The problem looks like it was a combination of a known and fixed issue ( https://4js.com/support/issue/?id=FGL-05258?id=FGL-05258 ) and not setting the ulimit correctly.

The GAS dispatcher shows the ulimit settings on a server as a 'heads up' to limits that might cause an issue to the GAS.
The OS 'open files' default of 1024 is rarely going to be enough for the GAS Dispatcher + GAS Proxy  + FGL ( which will access all the .42m / .42f / .4st / .4ad )
This 'open files' limit is per OS user, since the GAS and all the fglrun's will be normally running as the same OS user, so you need to set this limit accordingly.
Candy M.
Posts: 128


« Reply #4 on: December 17, 2019, 03:41:16 pm »

Does Fourjs have a guideline as to how that ulimit should be set, that is some sort of formula how we should estimate this value for the ulimit?

Thanks,
Candy
Frank G.
Four Js
Posts: 40


« Reply #5 on: February 03, 2020, 10:27:49 am »

Hi Candy,

 There is no guideline about the ulimit values. The default system values should be ok, but if you know the GAS will have a lot of simultaneous users connected to, it is recommanded to increase the open file ulimit value.

Do you have error in your log files ?

Regards,
Frank
Pages: [1]
  Reply  |  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines