UnhandledPromiseRejectionWarning: EmptySitemap


  • Hello! I have this warn in my console, please help me how to fix this?

    node v14.15.5
    npm v6.14.11
    nodebb 1.16.2

    (node:1246) UnhandledPromiseRejectionWarning: EmptySitemap: You ended the stream without writing anything.
    (Use `node --trace-warnings ...` to show where the warning was created)
    (node:1246) 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:1246) [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.
    
  • GNU/Linux Admin

    @tom-sheward Hi, can you show the entire stack trace please?


  • @julian Hm this?

      started
    2021-02-11T15:11:43.005Z [4567/1180] - info: [build] Building in series mode
    2021-02-11T15:11:43.006Z [4567/1180] - info: [build]         plugin static dirs  build started
    2021-02-11T15:11:43.018Z [4567/1180] - info: [build]         plugin static dirs  build completed in 0.012sec
    2021-02-11T15:11:43.019Z [4567/1180] - info: [build]          requirejs modules  build started
    2021-02-11T15:11:50.533Z [4567/1180] - info: [build]          requirejs modules  build completed in 7.513sec
    2021-02-11T15:11:50.535Z [4567/1180] - info: [build]           client js bundle  build started
    2021-02-11T15:11:54.022Z [4567/1180] - info: [build]           client js bundle  build completed in 3.487sec
    2021-02-11T15:11:54.023Z [4567/1180] - info: [build]            admin js bundle  build started
    2021-02-11T15:11:56.634Z [4567/1180] - info: [build]            admin js bundle  build completed in 2.612sec
    2021-02-11T15:11:56.636Z [4567/1180] - info: [build]         client side styles  build started
    2021-02-11T15:12:03.892Z [4567/1180] - info: [build]         client side styles  build completed in 7.256sec
    2021-02-11T15:12:03.896Z [4567/1180] - info: [build] admin control panel styles  build started
    2021-02-11T15:12:08.781Z [4567/1180] - info: [build] admin control panel styles  build completed in 4.885sec
    2021-02-11T15:12:08.782Z [4567/1180] - info: [build]                  templates  build started
    2021-02-11T15:12:09.289Z [4567/1180] - info: [build]                  templates  build completed in 0.507sec
    2021-02-11T15:12:09.289Z [4567/1180] - info: [build]                  languages  build started
    2021-02-11T15:12:20.094Z [4567/1180] - info: [build]                  languages  build completed in 10.805sec
    2021-02-11T15:12:20.100Z [4567/1180] - info: [build] Asset compilation successful. Completed in 37.088sec.
    [cluster] Restarting...
    Clustering enabled: Spinning up 1 process(es).
    
    2021-02-11T15:12:20.126Z [4567/1180] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
    2021-02-11T15:12:20.131Z [4567/1180] - info: [app] Web server closed to connections.
    2021-02-11T15:12:20.133Z [4567/1180] - info: [app] Live analytics saved.
    2021-02-11T15:12:20.147Z [4567/1180] - info: [app] Database connection closed.
    2021-02-11T15:12:20.152Z [4567/1180] - info: [app] Shutdown complete.
    [cluster] Child Process (1180) has exited (code: 0, signal: null)
    2021-02-11T15:12:20.536Z [4567/1246] - info: Initializing NodeBB v1.16.2 https://MYFORUM
    2021-02-11T15:12:22.910Z [4567/1246] - info: [socket.io] Restricting access to origin: https://MYFORUM:*
    2021-02-11T15:12:23.387Z [4567/1246] - warn: [plugins/nodebb-plugin-2factor] Hook "filter:router.page" is deprecated, please use "response:router.page" instead.
    2021-02-11T15:12:23.390Z [4567/1246] - warn:    [plugins/nodebb-plugin-spam-be-gone] The plugin.json field "library" is deprecated. Please use the package.json field "main" instead.
    2021-02-11T15:12:23.589Z [4567/1246] - info: [plugins/spam-be-gone] Settings loaded
    2021-02-11T15:12:23.649Z [4567/1246] - info: [api] Adding 0 route(s) to `api/v3/plugins`
    2021-02-11T15:12:23.666Z [4567/1246] - info: Routes added
    2021-02-11T15:12:23.683Z [4567/1246] - info: NodeBB Ready
    2021-02-11T15:12:23.685Z [4567/1246] - info: Enabling 'trust proxy'
    2021-02-11T15:12:23.687Z [4567/1246] - info: NodeBB is now listening on: 0.0.0.0:4567
    (node:1246) UnhandledPromiseRejectionWarning: EmptySitemap: You ended the stream without writing anything.
    (Use `node --trace-warnings ...` to show where the warning was created)
    (node:1246) 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:1246) [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.
    (node:1246) UnhandledPromiseRejectionWarning: EmptySitemap: You ended the stream without writing anything.
    (node:1246) 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: 2)
    (node:1246) UnhandledPromiseRejectionWarning: EmptySitemap: You ended the stream without writing anything.
    (node:1246) 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: 3)
    2021-02-11T17:00:00.005Z [4567/1246] - 2021-02-11T17:00:00.005Z [4567/1246] - info: [user/jobs] Did not send digests (day) because subscription system is disabled.
    2021-02-11T18:47:29.631Z [4567/1246] - error: plugins.composer.renderHelp
    Error: help-hidden
        at Sockets.renderHelp (/var/www/MYFORUM/nodebb/node_modules/nodebb-plugin-composer-default/websockets.js:61:9)
        at onMessage (/var/www/MYFORUM/nodebb/src/socket.io/index.js:150:25)
        at runNextTicks (internal/process/task_queues.js:58:5)
        at processImmediate (internal/timers.js:434:9)
    

    Or you mean run node --trace-warnings ...?


  • I try new install Nodebb, it's not help...

  • NodeBB

    This error seems to be coming from the sitemap module https://github.com/ekalinin/sitemap.js/blob/965c4a77d9034d5e8aab8843aac76d8853a4a629/lib/errors.ts#L266

    Is your sitemap loading properly at /sitemap.xml?

  • NodeBB

    @Tom-Sheward https://github.com/NodeBB/NodeBB/issues/9301, thanks for reporting I was able to reproduce.

Suggested Topics

| |