This is a known issue in 1.14.0-1.14.3. I have not personally experienced it, but I remember reading about it while researching my own problems with the current build. If I recall correctly, there are 2 current workarounds.
One is, to remove the logger from your yaml. The other is to roll back to 1.13.6.