[BUG] Strange log entries #90
Description
My running DCM log is full of
BadRequestError: request aborted
at IncomingMessage.onAborted (/app/node_modules/raw-body/index.js:231:10)
at IncomingMessage.emit (events.js:314:20)
at abortIncoming (_http_server.js:535:9)
at socketOnClose (_http_server.js:528:3)
at Socket.emit (events.js:326:22)
at TCP.<anonymous> (net.js:673:12)
Somethimes also
(node:19) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'match' of undefined
at /app/src/routes/api.js:413:143
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:19) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:19) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Is it something I should worry about? Can this exception be handled?
More, it seems that it can't recover from a lost MySQL connection, I'm having some minor problems with MySQL reachability and DCM is the only software I have to force-restart.