heroku node amqplib app errors starting Oct 1

oct 1 incident makes me suspicious , long running node / amqplib app just started throwing heroku init type errors as of oct 1

heroku restart is failing to start the server (amqplib in express server )

procfile ( web & server )

web: node --optimize_for_size --max_old_space_size=460 --gc_interval=100 lib/server.js worker: node lib/worker.js

Error on normal procfile start

detl:
2020-10-02T17:41:22.251154+00:00 heroku[web.1]: Starting process with command `node --optimize_for_size --max_old_space_size=460 --gc_interval=100 lib/server.js`
2020-10-02T17:41:22.449521+00:00 app[worker.1]: type=info msg="ParseSdk on" port=443
2020-10-02T17:41:22.449774+00:00 app[worker.1]: type=info msg="starting worker" concurrency=1 parseurl=warm-earth-97740.herokuapp.com
2020-10-02T17:41:25.274043+00:00 app[web.1]: type=info msg="ParseSdk on" port=443
2020-10-02T17:41:25.730789+00:00 app[web.1]: type=info msg="ParseSdk on" port=443
2020-10-02T17:41:25.887162+00:00 app[web.1]: type=info msg="starting server" concurrency=1 thrifty=true timeout=60000 busy_ms=40000
2020-10-02T17:42:18.524852+00:00 app[worker.1]: type=error msg=disconnected service=rabbitmq
2020-10-02T17:42:18.525021+00:00 app[worker.1]: type=info msg=app.lost
2020-10-02T17:42:18.525199+00:00 app[worker.1]: type=error msg="Error: read ECONNRESET" service=rabbitmq
2020-10-02T17:42:20.888712+00:00 app[web.1]: type=error msg=disconnected service=rabbitmq
2020-10-02T17:42:20.888955+00:00 app[web.1]: type=info msg=app.lost
2020-10-02T17:42:20.889217+00:00 app[web.1]: type=info msg="shutting down" abort=true
2020-10-02T17:42:20.978181+00:00 heroku[web.1]: Process exited with status 0
2020-10-02T17:42:21.021340+00:00 heroku[web.1]: State changed from starting to crashed

if i use heroku to get a bash shell on the remote and then run "npm run start" the app ( server / client ) start fine as in stdout below:

$ npm run start <-- this starts up the server OK

node-ffmpeg-heroku@0.0.2 start /app nf start

[WARN] No ENV file found [OKAY] Trimming display Output to 128 Columns 19:40:52 web.1 | type=info msg="ParseSdk on" port=443 19:40:52 worker.1 | type=info msg="ParseSdk on" port=443 19:40:52 worker.1 | type=info msg="ParseSdk on" port=443 19:40:52 worker.1 | type=info msg="starting worker" concurrency=1 parseurl=warm-earth-97740.herokuapp.com 19:40:52 worker.1 | type=info msg=connected service=rabbitmq 19:40:52 worker.1 | type=info msg=app.ready 19:40:53 web.1 | type=info msg="ParseSdk on" port=443 19:40:53 web.1 | type=info msg="starting server" concurrency=1 thrifty=true timeout=60000 busy_ms=40000 19:40:53 web.1 | type=info msg=connected service=rabbitmq 19:40:53 web.1 | type=info msg=app.ready 19:40:53 web.1 | type=info msg=app.purgePendingVotes 19:40:53 web.1 | type=info msg=app.purgePendingUsers 19:40:53 web.1 | type=info msg=listening port=5000

but "heroku restart " fails

server.js

var logger = require('logfmt');
var cpus = require('os').cpus().length;
var http = require('http');
var throng = require('throng');

var config = require('./config');
var app = require('./app');
var web = require('./web');

http.globalAgent.maxSockets = Infinity;
throng(start, { workers: config.concurrency,  grace: config.worker_grace  });

function start() {
  logger.log({
    type: 'info',
    msg: 'starting server',
    concurrency: config.concurrency,
    thrifty: config.thrifty,
    timeout: config.timeout,
    busy_ms: config.busy_ms
  });

  var instance = app(config);
  instance.on('ready', createServer);
  instance.on('lost', abort);

  function createServer() {
    //if (config.thrifty) instance.startScraping();
    if (config.thrifty){
      instance.purgePendingVotes();
      instance.purgePendingUsers();
      instance.startScraping();
    }
    var server = http.createServer(web(instance, config));

    process.on('SIGTERM', shutdown);
    instance
      .removeListener('lost', abort)
      .on('lost', shutdown);

    server.listen(config.port, onListen);

    function onListen() {
      logger.log({ type: 'info', msg: 'listening', port: server.address().port });
    }

    function shutdown() {
      logger.log({ type: 'info', msg: 'shutting down' });
      server.close(function() {
        logger.log({ type: 'info', msg: 'exiting' });
        process.exit();
      });
    }
  }

  function abort() {
    logger.log({ type: 'info', msg: 'shutting down', abort: true });
    process.exit();
  }
}

above , the "http.createServer" is failing . Normally stdout , on init includes following:

2017-09-13T18:53:45.798524+00:00 app[web.1]: type=info msg="ParseSdk on" port=443
2017-09-13T18:53:45.900704+00:00 app[web.1]: type=info msg="starting server" concurrency=1 thrifty=true timeout=60000 busy_ms=40000
2017-09-13T18:53:46.012264+00:00 app[web.1]: type=info msg=connected service=rabbitmq
2017-09-13T18:53:46.016532+00:00 app[web.1]: type=info msg=app.ready
2017-09-13T18:53:46.016764+00:00 app[web.1]: type=info msg=app.purgePendingVotes
2017-09-13T18:53:46.040622+00:00 app[web.1]: type=info msg=listening port=59575

so , how do i debug the server not running in node/amqplib ? ill go over to that node module and see what i can dig up.