Exception not shown when logging an error

It's not convenient when an error log is shown not to have the exception printed with the stack.

Example of logs I get:

Feb 06 11:28:50 peertube-search-index[9124]: [11:28:50.194] INFO (9124): Server listening on port 8095
Feb 06 11:28:50 peertube-search-index[9124]: [11:28:50.196] INFO (9124): Initialize peertube-search-index-channels Elastic Search index.
Feb 06 11:28:50 peertube-search-index[9124]: [11:28:50.228] INFO (9124): Initialize peertube-search-index-videos Elastic Search index.
Feb 06 11:28:50 peertube-search-index[9124]: [11:28:50.229] INFO (9124): Initialize peertube-search-index-playlists Elastic Search index.
Feb 06 11:28:50 peertube-search-index[9124]: [11:28:50.313] ERROR (9124): Cannot init videos index.
Feb 06 11:28:50 systemd[1]: peertube-search-index.service: Main process exited, code=exited, status=255/EXCEPTION
Feb 06 11:28:50 systemd[1]: peertube-search-index.service: Failed with result 'exit-code'.

And it seems like the error is passed to the logger: https://framagit.org/framasoft/peertube/search-index/-/blob/adfe422cc1450ba1f94d0771de59e734137e88cf/server.ts#L151