[BUG] - error using statistics command

Question

[BUG] - error using statistics command

mr190e opened this issue a year ago · 14 comments

When using the statistics command (with a steam64) the following happens:

In discord the bot is stuck "Name-of-Bot is thinkig..."

And in log files I find this error:


[19:37:27] [SYSERR] : An error has occurred while executing the /statistics command

Error: Failed to launch the browser process! spawn /root/.cache/puppeteer/chrome/linux-113.0.5672.63/chrome-linux64/chrome ENOENT

TROUBLESHOOTING: https://pptr.dev/troubleshooting

    at ChildProcess.onClose (/app/node_modules/@puppeteer/browsers/lib/cjs/launch.js:262:24)

    at ChildProcess.emit (node:events:513:28)

    at ChildProcess._handle.onexit (node:internal/child_process:291:12)

    at onErrorNT (node:internal/child_process:483:16)

    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

[19:37:27] [DEBUG]  : statistics executed in 729.84 ms

The error appears no matter what steamID i put in or BohemiaID

Answer 1 · 2023-05-24T19:56:40.000Z

This happens because we're trying to launch a headless chromium browser, the dependencies might not be installed.

What OS are you on, some Linux distro I'm guessing - but which one specifically?

Answer 2 · 2023-05-25T10:02:41.000Z

I have added STATISTICS_INCLUDE_ZONES_HEATMAP as a server config setting - you can disable this (false) to temporarily avoid trying to initialze the headless chromium instance

Answer 3 · 2023-05-25T10:03:50.000Z

Please install the Chromium dependency using sudo apt-get install chromium-browser

Answer 4 · 2023-05-25T10:04:27.000Z

Not technically a bug, I have to document this and add user customization for the Chromium executable path

Answer 5 · 2023-05-25T10:14:50.000Z

I have updated the documentation accordingly, please refer to: https://github.com/Mirasaki/cftools-discord-bot#prerequisites

Feel free to re-open this issue if you're still encountering issues after installing the dependency

Answer 6 · 2023-06-04T11:00:35.000Z

I use the bot running from a Docker container on Ubuntu 22.04 LTS

How I get Chromium in the container installed?

Answer 7 · 2023-06-04T11:55:05.000Z

Pretty quick and simple with Docker Compose, let me send you an example

Answer 8 · 2023-06-04T12:27:56.000Z

@mr190e I've updated the production and development Dockerfiles to include direct support for Chromium/Puppeteer:

https://github.com/Mirasaki/cftools-discord-bot/pull/43/files

Answer 9 · 2023-06-04T12:28:43.000Z

Let me know how it goes, I'll re-open this issue for now. Please download the latest bundle from the main branch, or update your Dockerfiles manually by comparing (not recommended)

Answer 10 · 2023-06-06T14:17:22.000Z

@mr190e Bump, please let me know if this works for you

Answer 11 · 2023-06-06T16:06:17.000Z

Hey mate, I am travelling atm. Can test it Friday Gesendet mit der mobilen Mail AppAm 06.06.23 um 16:17 schrieb Richard Hillebrand Von: "Richard Hillebrand" ***@***.***>Datum: 6. Juni 2023An: "Mirasaki/cftools-discord-bot" ***@***.***>Cc: "Mention" ***@***.***>,"mr190e" ***@***.***>Betreff: Re: [Mirasaki/cftools-discord-bot] [BUG] - error using statistics command (Issue #11) @mr190e Bump, please let me know if this works for you —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

Answer 12 · 2023-06-07T16:47:56.000Z

Sure thing, let me know - good luck in your travels!

Answer 13 · 2023-06-07T20:56:34.000Z

Build the new image and now the statistics work, but still get this error:

[20:59:33] [SYSERR] : An error has occurred while executing the /statistics command

Error: Failed to launch the browser process! spawn /root/.cache/puppeteer/chrome/linux-113.0.5672.63/chrome-linux64/chrome ENOENT

TROUBLESHOOTING: https://pptr.dev/troubleshooting

    at ChildProcess.onClose (/app/node_modules/@puppeteer/browsers/lib/cjs/launch.js:262:24)

    at ChildProcess.emit (node:events:513:28)

    at ChildProcess._handle.onexit (node:internal/child_process:291:12)

    at onErrorNT (node:internal/child_process:483:16)

    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

[20:59:33] [DEBUG]  : statistics executed in 766.36 ms

[21:03:12] [DEBUG]  : <spawn-item> | Auto Complete | Queried "" in 1257.93 ms

[21:03:13] [DEBUG]  : <spawn-item> | Auto Complete | Queried "c" in 0.53 ms

[21:03:14] [DEBUG]  : <spawn-item> | Auto Complete | Queried "chew" in 0.34 ms

npm ERR! path /app

npm ERR! command failed

npm ERR! signal SIGTERM

npm ERR! command sh -c node .

npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2023-06-07T20_59_11_267Z-debug-0.log

Answer 14 · 2023-06-08T09:39:00.000Z

We're probably going to have to add an option to overwrite the path pointing to the Chromium executable if this doesn't work