You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if config file being pushed contains Windows style line endings (\r\n), then \r will be treated as part of the value, which will result in error when trying to parse HEALTHCHECK_INITIAL_DELAY from uploaded config:
Creating config... Error:
503 SERVICE UNAVAILABLE
detail: aborting, app containers failed to respond to health check
Which does not give any idea what was actual problem (bad delay value).
Changing file line endings to UNIX style fixes the problem, but shouldn't all line endings be ignored? This will require developers using Windows to careful work with configs, and in case of the error it is hard to diagnose. The \r problem is not obvious as when config is pushed the operation will fail saying that containers failed health-check without any details of actual problem (that Publisher was not able to parse value).
From @NickAb on September 3, 2016 2:9
When using
if config file being pushed contains Windows style line endings (
\r\n
), then\r
will be treated as part of the value, which will result in error when trying to parseHEALTHCHECK_INITIAL_DELAY
from uploaded config:which results in config push failing with
Which does not give any idea what was actual problem (bad delay value).
Changing file line endings to UNIX style fixes the problem, but shouldn't all line endings be ignored? This will require developers using Windows to careful work with configs, and in case of the error it is hard to diagnose. The
\r
problem is not obvious as when config is pushed the operation will fail saying that containers failed health-check without any details of actual problem (that Publisher was not able to parse value).Copied from original issue: deis/deis#5091
The text was updated successfully, but these errors were encountered: