Post v1.0.6 to v2.0.1 Update -- existing delivery logs are inaccessible

[Scott MacDonald]

After upgrading from v1.0.6 to v2.0.1 I have noted a few "issues"

1. After upgrading to 2.0.1 none of the previous 30 days of delivery logs are inaccessible -- attempting to select any date pre-update results in a "500 Internal Server Error" -- However, delivery logs created post update were accessible without issue. On clicking or selecting any pre-update day of delivery logs the following error is received:

Oops! An Error Occurred The server returned a "500 Internal Server Error". Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.

2. After starting the 2.0.1 container for the first time -- it seems that some of the services failed to start -- as none of the email related ports (25, 587) were listening -- however, a simple restart of the container (docker restart "image_name") corrected the issue.

[Scott MacDonald]

Here is a little more on the post update delivery logs not accessible.. I snipped the following excerpts from the prod.log in /var/log/admin-app

[2018-04-28 01:35:32] request.INFO: Matched route "log_show". {"route":"log_show
","route_parameters":{"page":1,"_controller":"ProBundle\\Controller\\LogControll
er::showAction","date":"2018-04-27","_route":"log_show"},"request_uri":"https://
<erased_for_privacy>/admin/log/2018-04-27","method":"GET"} []
[2018-04-28 01:35:32] security.DEBUG: Read existing security token from the sess
ion. {"key":"_security_secured_area","token_class":"Symfony\\Component\\Security
\\Core\\Authentication\\Token\\UsernamePasswordToken"} []
[2018-04-28 01:35:32] security.DEBUG: User was reloaded from a user provider. {"
provider":"AppBundle\\Entity\\BoxRepository","username":"<erased_for_privacy>"} []
[2018-04-28 01:35:32] request.CRITICAL: Uncaught PHP Exception Exception: "Can't
 parse row "2018-04-27 00:00:57 bb7da9a0-02a0-4d70-9c20-f635d34cee16@ind1s06mta1
264.xt.local delivery 11454: success: did_0+0+1/ "" at /opt/admin/src/ProBundle/
Logs/TransactionLogs.php line 109 {"exception":"[object] (Exception(code: 0): Ca
n't parse row \"2018-04-27 00:00:57 bb7da9a0-02a0-4d70-9c20-f635d34cee16@ind1s06
mta1264.xt.local delivery 11454: success: did_0+0+1/\n\" at /opt/admin/src/ProBu
ndle/Logs/TransactionLogs.php:109)"} []

[SH]

Logs are sadly one think which was intentionaly made incompatible (1 vs 2.0). Whole logging works differently (and better) and we were not able to process two different formats at log viewer. But still, older logs are available at log folder