Error 502 on initial sync on FMS 18 - How to increase XML timeout?

[DataCruncher]

Mirrorsync 4.0027

I have dealt with many an error 502 during initial sync with earlier versions of FMS - 12,14,15. 

The easy fix was to simply increase the PoxyPass timeout in /Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/mod_proxy.conf. 

 

The problem now is that FMS18 does not have /Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/mod_proxy.conf. 

 

Any guidance here, please? I remain very confused why a mirror copy of the same database file needs to sync well over 5000 records on initial sync, BTW. 

 

Thank you!!!

 

 

Edited November 30, 2019 by DataCruncher

[ryan360Works]

Hello,

The ProxyPass timeout can be set in the file located at 

Quote

/Library/FileMaker Server/HTTPServer/conf/httpd.conf

I recommend that you stop the HTTP server, make then change to the file, and then start the HTTPserver. 

[DataCruncher]

I did that - thank you. 

It does not time out any more. However, with FMS 18 - and I have not had this issue before, not I get random 'the server appears to be hung' drops. I can't figure out why it's doing that. I am using Mirrorsync 4.0027 and FMS 18 on a Mac. 

 

This is what I get: 

 

Dec 16, 2019 7:29:11 PM com.prosc.mirror.config.server.SyncServer$3 call
SEVERE: Sync between test.com / PXC (FileMaker Server) and 2.test.com / PXC (FileMaker Server), 3.test.com / PXC (FileMaker Server), 3.test.com / PXC (FileMaker Server), 5.test.com / PXC (FileMaker Server)
Last sync failed: com.prosc.sync.AbortException: Database server at FileMaker Server test.com/sync_CASES appears to be hung; sync is automatically being aborted. Please try the sync again.

 

I looked at topcallstats, but there is nothing out of the ordinary. Where should I look next? It is important to note that the exact same FMS18 version is running at 3.test.com and never appears to be hung? 

This is the topcallstats log (an excerpt of it):

 

8933    Query    PXC::table(129)::field definitions(448)    939    33    8933    0    0    user (172.16.0.94) [172.16.0.94]
2019-12-16 19:38:00.337 -0800    4579.601252    4579.610122    8869    Commit Records (Commit)    PXC::table(129)    811    23    8869    0    0    user (172.16.0.94) [172.16.0.94]
2019-12-16 19:38:00.337 -0800    4573.62564    4573.63438    8740    Commit Records (Commit)    PXC::table(129)    811    23    8740    0    0    user (172.16.0.94) [172.16.0.94]
2019-12-16 19:38:00.337 -0800    4561.352677    4561.361323    8646    Commit Records (Commit)    PXC::table(129)    811    23    8646    0    0    user (172.16.0.94) [172.16.0.94]
2019-12-16 19:38:00.337 -0800    4580.899823    4580.908464    8641    Commit Records (Commit)    PXC::table(129)    811    23    8641    0    0    user (172.16.0.94) [172.16.0.94]
2019-12-16 19:38:00.337 -0800    4581.486836    4581.495399    8562    Commit Records (Commit)    PXC::table(129)    811

 

Edited December 18, 2019 by DataCruncher
added log

[DataCruncher]

On 12/3/2019 at 7:35 AM, ryan360Works said:

Hello,

The ProxyPass timeout can be set in the file located at 

I recommend that you stop the HTTP server, make then change to the file, and then start the HTTPserver. 

Hello Ryan, 

 

I had to re-install FMS 18 on a Mac yesterday. I added the timeout to 

/Library/FileMaker Server/HTTPServer/conf/httpd.conf

 

Yet I still get 502 Errors with mirrorsync. In earlier FMS versions, there was another file to set a timeout parameter in, mod_proxy.conf. That file seems to no longer exist in FMS 18 - is there any other way I could increase the FMS18 timeout? 

 

Thank you!

 

[ryan360Works]

You may need to also modify the httpd-proxy-fmiwebd.conf file. See instructions here

[DataCruncher]

Thank you! That was the missing file location I have been looking for...