iisnode 上的 NestJs 安装和未处理的承诺拒绝

当我尝试在 IIS 服务器上安装 NestJs 应用程序（安装了 iisnode）时，我总是遇到问题“...错误：听 EADDRINUSE：地址已在使用 :::3450 ..”（见下文）并且，作为您可以从 console.log（见下文）中看到，NestJs 应用程序首先完全初始化并启动，但随后总是出现端口已在使用的问题。无论我尝试多少个不同的端口，它都会持续存在。我还尝试重新启动 iisnode.exe 并终止进程和端口，但它没有帮助。任何人都有这方面的经验并找到解决方案？

节点分布/主要

[32m[Nest] 36096   - [39m09/01/2020, 1:43:54 PM   [33m[NestFactory] [39m[32mStarting Nest application...[39m
[32m[Nest] 36096   - [39m09/01/2020, 1:43:54 PM   [33m[InstanceLoader] [39m[32mConfigHostModule dependencies initialized[39m[33m +34ms[39m
[32m[Nest] 36096   - [39m09/01/2020, 1:43:54 PM   [33m[InstanceLoader] [39m[32mAppModule dependencies initialized[39m[33m +0ms[39m
[32m[Nest] 36096   - [39m09/01/2020, 1:43:54 PM   [33m[InstanceLoader] [39m[32mConfigModule dependencies initialized[39m[33m +1ms[39m
hello from NestJs app
[32m[Nest] 36096   - [39m09/01/2020, 1:43:54 PM   [33m[RoutesResolver] [39m[32mAppController {}:[39m[33m +13ms[39m
[32m[Nest] 36096   - [39m09/01/2020, 1:43:54 PM   [33m[RouterExplorer] [39m[32mMapped {, GET} route[39m[33m +4ms[39m
[32m[Nest] 36096   - [39m09/01/2020, 1:43:54 PM   [33m[RoutesResolver] [39m[32mItemsController {/items}:[39m[33m +0ms[39m
[32m[Nest] 36096   - [39m09/01/2020, 1:43:54 PM   [33m[RouterExplorer] [39m[32mMapped {/items, GET} route[39m[33m +1ms[39m
[32m[Nest] 36096   - [39m09/01/2020, 1:43:54 PM   [33m[RouterExplorer] [39m[32mMapped {/items/:id, GET} route[39m[33m +2ms[39m
[32m[Nest] 36096   - [39m09/01/2020, 1:43:54 PM   [33m[RouterExplorer] [39m[32mMapped {/items, POST} route[39m[33m +1ms[39m
[32m[Nest] 36096   - [39m09/01/2020, 1:43:54 PM   [33m[RoutesResolver] [39m[32mShoppingCartController {/shopping-cart}:[39m[33m +1ms[39m
[32m[Nest] 36096   - [39m09/01/2020, 1:43:54 PM   [33m[RouterExplorer] [39m[32mMapped {/shopping-cart, POST} route[39m[33m +0ms[39m
[32m[Nest] 36096   - [39m09/01/2020, 1:43:54 PM   [33m[NestApplication] [39m[32mNest application successfully started[39m[33m +4ms[39m
App is running in port: 61302
events.js:292
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE: address already in use :::61302
    at Server.setupListenHandle [as _listen2] (net.js:1313:16)
    at listenInCluster (net.js:1361:12)
    at Server.listen (net.js:1447:7)
    at ExpressAdapter.listen (C:\...\node_modules\@nestjs\platform-express\adapters\express-adapter.js:45:32)
    at NestApplication.listen (C:\...\node_modules\@nestjs\core\nest-application.js:146:26)
    at async bootstrap (C:\...\dist\main.js:8:9)
Emitted 'error' event on Server instance at:
    at emitErrorNT (net.js:1340:8)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  code: 'EADDRINUSE',
  errno: 'EADDRINUSE',
  syscall: 'listen',
  address: '::',
  port: 61302
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start:prod: `node dist/main`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start:prod script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\...\AppData\Roaming\npm-cache\_logs\2020-09-01T12_43_54_285Z-debug.log

在 iisnode 服务器错误日志中，我还可以找到以下内容：（这证明是在前一天记录的 - 并且不再在日志中看到。因此，此 iisnode 日志消息可能与问题根本无关）

(node:45472) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(node:45472) UnhandledPromiseRejectionWarning: RangeError [ERR_SOCKET_BAD_PORT]: options.port should be >= 0 and < 65536. Received NaN.
    at validatePort (internal/validators.js:182:11)
    at Server.listen (net.js:1439:5)
    at ExpressAdapter.listen (C:\...\node_modules\@nestjs\platform-express\adapters\express-adapter.js:45:32)
    at NestApplication.listen (C:\...\node_modules\@nestjs\core\nest-application.js:146:26)
    at async bootstrap (C:\...\dist\main.js:7:5)
(node:45472) 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:45472) [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.

此外，这里还有当前形式的 /dist/main.js 文件（我已经添加了那些 try / catch 语句）。

"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
const core_1 = require("@nestjs/core");
const app_module_1 = require("./app.module");
async function bootstrap() {
    try {
        const app = await core_1.NestFactory.create(app_module_1.AppModule);
        await app.listen(parseInt(process.env.PORT) || 8080)
        .catch((e) => {
            console.error(e);
            process.exit(1);
        });
        console.log('App is running in port: ' + process.env.PORT);
    }
    catch (error) {
        console.log("Error message: " + error);
    }
}
bootstrap().catch(e => { 
    console.error(e);
});
//# sourceMappingURL=main.js.map