Sync error on remote site - 'EOF while parsing'

[regotaina]

What went wrong? 😲

After doing any transaction on a remote site(android), I press 'sync now' and get the following error message:

the problem is resolved if I press the sync button for the 2nd time.

Expected behaviour 🤔

No need to press sync twice to get it to work.

How to Reproduce 🔨

Steps to reproduce the behaviour:

1. Go to 'remote site (android)
2. Do any transactions (internal order, outbound shipment, etc..)
3. Go to sync and press the button 'sync now'
4. See error

Your environment 🌱

• Open mSupply Version: V2.0 RC3
• Legacy mSupply Central Server Version: V7.14.0

• Platform: android

[DhanyaHerath]

Triage: needs checking to reproduce

[roxy-dao]

Update: Doesn't seem to be happening anymore and could have been something to do with set up. Have tested with problematic data and seems to be working fine in development

[jmbrunskill]

Seems to happen more often straight after login, then gets better after 10min?

[marthakeezy]

Reopening since the issue is happening again for me and @regotaina (going to look at this with @kahn-msupply ). The problem is no longer resolved when you press Sync twice, I have to wait for about 10-15 minutes befor sync eventually works. Right not I've been waiting for 26 minutes. Tainá and I are on different datafiles too

I am on V2.3.0-RC8

Also changing severity to High since it's a major testing blocker, I cannot sync anything between my remote site and Central Server

[regotaina]

just clarifying, sync still works here - the error occurs sporadically, not following a pattern. It's not blocking
Like James mentioned, sync issues might be or not connected to this one.

[kahn-msupply]

I haven't been able to pin-point this issue. I will be doing some testing to rule out data file issues. I'll make sure to update here with my findings.

[jmbrunskill]

@kahn-msupply have you confirmed it does or doesn't still happen with Caddy?

[kahn-msupply]

@kahn-msupply have you confirmed it does or doesn't still happen with Caddy?

Tests show this issue is occurring only with Caddy - I'll be doing some more testing to see if I can replicate this on another test server, and if there is an effect on remote sites.

[jmbrunskill]

@triage team, adding this for triage again.

Reasoning is...

1. We're rolling out Caddy to clients, which already have challenging internet connections. If this introduces additional issues with sync that won't help matters!
2. This is causing significant interruption to QA testing as tests have to try to sync multiple times, I've seen it require 4-5 sync attempts to work.

Maybe needs some more refinement and time boxing but I think probably worth spending some time to investigate further.

Obviously one option is to just remove Caddy from the workflow?
#5080 might help with QA issues

[kahn-msupply]

One interesting thing I have noticed (from Desktop application, installed next to Oepn mSupply Central Server)... I have 3 options available. Server is running on Port 443. AppData was cleared and options persist. Netstat -ano shows no PID attached to ports 8000 (SSL Certs / Manual) and 7000 (Caddy Reverse Proxy). I'll keep providing updates.

[marthakeezy]

I always have 2 options shown - 7000 and 8000. Only one of them works though

[marthakeezy]

Happening again in V2.5.0-reports2