[Linux] Chat resource not starting, I think due to Webpack

FiveM Server Development Server Discussion
,
1

I’m having issues with my Linux FXServer. As seen below the chat is unable to start due to Webpack, this should be normal but then after Webpack is done initializing it should start the chat resource again, but there it’s not the case.

Terminal:

[    c-resources-core] Could not start dependency webpack for resource chat.
[ citizen-server-impl] Couldn't start resource chat.
...
warning webpack > node-libs-browser > url > querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
warning webpack > watchpack > watchpack-chokidar2 > chokidar > fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
warning webpack > micromatch > snapdragon > source-map-resolve > resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
warning webpack > micromatch > snapdragon > source-map-resolve > urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
[2/4] Fetching packages...
info fsevents@2.3.2: The platform "linux" is incompatible with this module.
info "fsevents@2.3.2" is an optional dependency and failed compatibility check. Excluding it from installation.
info fsevents@1.2.13: The platform "linux" is incompatible with this module.
info "fsevents@1.2.13" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
error An unexpected error occurred: "Internal error. Icu error.".
info If you think this is a bug, please open a bug report with the information provided in "/home/FXServer/server-data/resources/[cfx-default]/[system]/[builders]/webpack/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

yarn-error.log

Arguments: 
  /home/FXServer/server/alpine/opt/cfx-server/ld-musl-x86_64.so.1 /home/FXServer/server-data/resources/[cfx-default]/[system]/[builders]/yarn/yarn_cli.js install --ignore-scripts --cache-folder /home/FXServer/server-data/cache/yarn-cache --mutex file:/home/FXServer/server-data/cache/yarn-mutex

PATH: 
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

Yarn version: 
  1.22.5

Node version: 
  16.9.1

Platform: 
  linux x64

Trace: 
  RangeError: Internal error. Icu error.
      at String.localeCompare (<anonymous>)
      at /home/FXServer/server-data/resources/[cfx-default]/[system]/[builders]/yarn/yarn_cli.js:49386:24
      at Array.sort (<anonymous>)
      at /home/FXServer/server-data/resources/[cfx-default]/[system]/[builders]/yarn/yarn_cli.js:49385:27
      at Generator.next (<anonymous>)
      at step (/home/FXServer/server-data/resources/[cfx-default]/[system]/[builders]/yarn/yarn_cli.js:310:30)
      at /home/FXServer/server-data/resources/[cfx-default]/[system]/[builders]/yarn/yarn_cli.js:328:14
      at new Promise (<anonymous>)
      at new F (/home/FXServer/server-data/resources/[cfx-default]/[system]/[builders]/yarn/yarn_cli.js:25783:28)
      at /home/FXServer/server-data/resources/[cfx-default]/[system]/[builders]/yarn/yarn_cli.js:307:12

npm manifest: 
  {
    "name": "webpack-builder",
    "version": "1.0.1",
    "description": "",
    "main": "index.js",
    "scripts": {
      "test": "echo \"Error: no test specified\" && exit 1"
    },
    "author": "",
    "license": "ISC",
    "dependencies": {
      "async": "^3.1.0",
      "webpack": "^4.41.2",
      "worker-farm": "^1.7.0"
    }
  }

yarn manifest: 
  No manifest

Lockfile: 
  No lockfile
2

This should be fixed since fix(scripting/v8): bundle icudtl for linux (hotfix) · citizenfx/fivem@98e9c7b · GitHub.

3

Still getting this error it seems on my end with the build Versions: v4.5.0 / 4593. Server is again on a Linux box.

terminal

[ citizen-server-impl] Running build tasks on resource cad - it'll restart once completed.
[ citizen-server-impl] Couldn't start resource cad.
yarn install v1.22.5
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
error An unexpected error occurred: "Internal error. Icu error.".
info If you think this is a bug, please open a bug report with the information provided in "/home/kirsty/lc/lc-server/resources/[IN DEVELOPMENT]/cad/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
[ citizen-server-impl] Building resource cad failed.
[ citizen-server-impl] Error data: yarn failed!

yarn-error.log

Arguments:
/home/kirsty/lc/FXServer/alpine/opt/cfx-server/ld-musl-x86_64.so.1 /home/kirsty/lc/lc-server/resources/[system]/[builders]/yarn/yarn_cli.js install --ignore-scripts --cache-folder /home/kirsty/lc/lc-server/cache/yarn-cache --mutex file:/home/kirsty/lc/lc-server/cache/yarn-mutex

PATH:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

Yarn version:
1.22.5

Node version:
16.9.1

Platform:
linux x64

Trace:
RangeError: Internal error. Icu error.
at String.localeCompare ()
at /home/kirsty/lc/lc-server/resources/[system]/[builders]/yarn/yarn_cli.js:49386:24
at Array.sort ()
at /home/kirsty/lc/lc-server/resources/[system]/[builders]/yarn/yarn_cli.js:49385:27
at Generator.next ()
at step (/home/kirsty/lc/lc-server/resources/[system]/[builders]/yarn/yarn_cli.js:310:30)
at /home/kirsty/lc/lc-server/resources/[system]/[builders]/yarn/yarn_cli.js:328:14
at new Promise ()
at new F (/home/kirsty/lc/lc-server/resources/[system]/[builders]/yarn/yarn_cli.js:25783:28)
at /home/kirsty/lc/lc-server/resources/[system]/[builders]/yarn/yarn_cli.js:307:12

npm manifest:
{
“name”: “CAD”,
“version”: “1.0.0”,
“description”: “JS runtime to link with CAD.”,
“main”: “index.js”,
“author”: “Kirsty Wright”,
“license”: “MIT”,
“private”: true,
“dependencies”: {
“autobahn”: “^20.9.2”
}
}

yarn manifest:
No manifest

Lockfile:

# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.

# yarn lockfile v1

autobahn@^20.9.2:
version “20.9.2”
resolved “https://registry.yarnpkg.com/autobahn/-/autobahn-20.9.2.tgz#244029f0829b23b465dfdbe83cb597b6d4e212ed”
integrity sha512-Xas7mHujzRJe1p9RWPS3QTrwcXF5S9B9oT26cbzQKnE7qsvMOvmNnRZ6SWYpMdgDgJDCQ+kvpvQE8pRA/kWTPw==
dependencies:
cbor “>= 3.0.0”
crypto-js “>=3.1.8”
msgpack5 “>= 3.6.0”
tweetnacl “>= 0.14.3”
ws “>= 1.1.4”
optionalDependencies:
bufferutil “>= 1.2.1”
utf-8-validate “>= 1.2.1”
when “>= 3.7.7”

base64-js@^1.3.1:
version “1.5.1”
resolved “https://registry.yarnpkg.com/base64-js/-/base64-js-1.5.1.tgz#1b1b440160a5bf7ad40b650f095963481903930a”
integrity sha512-AKpaYlHn8t4SVbOHCy+b5+KKgvR4vrsD8vbvrbiQJps7fKDTkjkDry6ji0rUJjC0kzbNePLwzxq8iypo41qeWA==

bl@^4.0.0:
version “4.1.0”
resolved “https://registry.yarnpkg.com/bl/-/bl-4.1.0.tgz#451535264182bec2fbbc83a62ab98cf11d9f7b3a”
integrity sha512-1W07cM9gS6DcLperZfFSj+bWLtaPGSOHWhPiGzXmvVJbRLdG82sH/Kn8EtW1VqWVA54AKf2h5k5BbnIbwF3h6w==
dependencies:
buffer “^5.5.0”
inherits “^2.0.4”
readable-stream “^3.4.0”

buffer@^5.5.0:
version “5.7.1”
resolved “https://registry.yarnpkg.com/buffer/-/buffer-5.7.1.tgz#ba62e7c13133053582197160851a8f648e99eed0”
integrity sha512-EHcyIPBQ4BSGlvjB16k5KgAJ27CIsHY/2JBmCRReo48y9rQ3MaUzWX3KVlBa4U7MyX02HdVj0K7C3WaB3ju7FQ==
dependencies:
base64-js “^1.3.1”
ieee754 “^1.1.13”

“bufferutil@>= 1.2.1”:
version “4.0.3”
resolved “https://registry.yarnpkg.com/bufferutil/-/bufferutil-4.0.3.tgz#66724b756bed23cd7c28c4d306d7994f9943cc6b”
integrity sha512-yEYTwGndELGvfXsImMBLop58eaGW+YdONi1fNjTINSY98tmMmFijBG6WXgdkfuLNt4imzQNtIE+eBp1PVpMCSw==
dependencies:
node-gyp-build “^4.2.0”

“cbor@>= 3.0.0”:
version “8.0.0”
resolved “https://registry.yarnpkg.com/cbor/-/cbor-8.0.0.tgz#51657d26a99a6a1866f8c3258e948576eb17d709”
integrity sha512-nMmaLWbj7+bC6MsApKRIig8h+yjgNLhPLXaCelq5+C7mpWsHgIcseZSdvgexSY5uE1Q3m2uPvIDZwSdxdo7qig==
dependencies:
nofilter “^3.0.2”

crypto-js@>=3.1.8:
version “4.1.1”
resolved “https://registry.yarnpkg.com/crypto-js/-/crypto-js-4.1.1.tgz#9e485bcf03521041bd85844786b83fb7619736cf”
integrity sha512-o2JlM7ydqd3Qk9CA0L4NL6mTzU2sdx96a+oOfPu8Mkl/PK51vSyoi8/rQ8NknZtk44vq15lmhAj9CIAGwgeWKw==

ieee754@^1.1.13:
version “1.2.1”
resolved “https://registry.yarnpkg.com/ieee754/-/ieee754-1.2.1.tgz#8eb7a10a63fff25d15a57b001586d177d1b0d352”
integrity sha512-dcyqhDvX1C46lXZcVqCpK+FtMRQVdIMN6/Df5js2zouUsqG7I6sFxitIC+7KYK29KdXOLHdu9zL4sFnoVQnqaA==

inherits@^2.0.3, inherits@^2.0.4:
version “2.0.4”
resolved “https://registry.yarnpkg.com/inherits/-/inherits-2.0.4.tgz#0fa2c64f932917c3433a0ded55363aae37416b7c”
integrity sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==

“msgpack5@>= 3.6.0”:
version “5.3.2”
resolved “https://registry.yarnpkg.com/msgpack5/-/msgpack5-5.3.2.tgz#679a1f197465f2d446a1d467cf678e3e83bb56dc”
integrity sha512-e9jz+6InQIUb2cGzZ/Mi+rQBs1KFLby+gNi+22VwQ1pnC9ieZjysKGmRMjdlf6IyjsltbgY4tGoHwHmyS7l94A==
dependencies:
bl “^4.0.0”
inherits “^2.0.3”
readable-stream “^3.0.0”
safe-buffer “^5.1.2”

node-gyp-build@^4.2.0:
version “4.3.0”
resolved “https://registry.yarnpkg.com/node-gyp-build/-/node-gyp-build-4.3.0.tgz#9f256b03e5826150be39c764bf51e993946d71a3”
integrity sha512-iWjXZvmboq0ja1pUGULQBexmxq8CV4xBhX7VDOTbL7ZR4FOowwY/VOtRxBN/yKxmdGoIp4j5ysNT4u3S2pDQ3Q==

nofilter@^3.0.2:
version “3.0.3”
resolved “https://registry.yarnpkg.com/nofilter/-/nofilter-3.0.3.tgz#3ff3b142efdccb403434ccae4a0c2c835cb9b522”
integrity sha512-TN/MCrQmXQk5DyUJ8TGUq1Il8rv4fTsjddLmMopV006QP8DMkglmGgYfQKD5620vXLRXfr8iGI6ZZ4/ZWld2cQ==

readable-stream@^3.0.0, readable-stream@^3.4.0:
version “3.6.0”
resolved “https://registry.yarnpkg.com/readable-stream/-/readable-stream-3.6.0.tgz#337bbda3adc0706bd3e024426a286d4b4b2c9198”
integrity sha512-BViHy7LKeTz4oNnkcLJ+lVSL6vpiFeX6/d3oSH8zCW7UxP2onchk+vTGB143xuFjHS3deTgkKoXXymXqymiIdA==
dependencies:
inherits “^2.0.3”
string_decoder “^1.1.1”
util-deprecate “^1.0.1”

safe-buffer@^5.1.2, safe-buffer@~5.2.0:
version “5.2.1”
resolved “https://registry.yarnpkg.com/safe-buffer/-/safe-buffer-5.2.1.tgz#1eaf9fa9bdb1fdd4ec75f58f9cdb4e6b7827eec6”
integrity sha512-rp3So07KcdmmKbGvgaNxQSJr7bGVSVk5S9Eq1F+ppbRo70+YeaDxkw5Dd8NPN+GD6bjnYm2VuPuCXmpuYvmCXQ==

string_decoder@^1.1.1:
version “1.3.0”
resolved “https://registry.yarnpkg.com/string_decoder/-/string_decoder-1.3.0.tgz#42f114594a46cf1a8e30b0a84f56c78c3edac21e”
integrity sha512-hkRX8U1WjJFd8LsDJ2yQ/wWWxaopEsABU1XfkM8A+j0+85JAGppt16cr1Whg6KIbb4okU6Mql6BOj+uup/wKeA==
dependencies:
safe-buffer “~5.2.0”

“tweetnacl@>= 0.14.3”:
version “1.0.3”
resolved “https://registry.yarnpkg.com/tweetnacl/-/tweetnacl-1.0.3.tgz#ac0af71680458d8a6378d0d0d050ab1407d35596”
integrity sha512-6rt+RN7aOi1nGMyC4Xa5DdYiukl2UWCbcJft7YhxReBGQD7OAM8Pbxw6YMo4r2diNEA8FEmu32YOn9rhaiE5yw==

“utf-8-validate@>= 1.2.1”:
version “5.0.5”
resolved “https://registry.yarnpkg.com/utf-8-validate/-/utf-8-validate-5.0.5.tgz#dd32c2e82c72002dc9f02eb67ba6761f43456ca1”
integrity sha512-+pnxRYsS/axEpkrrEpzYfNZGXp0IjC/9RIxwM5gntY4Koi8SHmUGSfxfWqxZdRxrtaoVstuOzUp/rbs3JSPELQ==
dependencies:
node-gyp-build “^4.2.0”

util-deprecate@^1.0.1:
version “1.0.2”
resolved “https://registry.yarnpkg.com/util-deprecate/-/util-deprecate-1.0.2.tgz#450d4dc9fa70de732762fbd2d4a28981419a0ccf”
integrity sha1-RQ1Nyfpw3nMnYvvS1KKJgUGaDM8=

“when@>= 3.7.7”:
version “3.7.8”
resolved “https://registry.yarnpkg.com/when/-/when-3.7.8.tgz#c7130b6a7ea04693e842cdc9e7a1f2aa39a39f82”
integrity sha1-xxMLan6gRpPoQs3J56Hyqjmjn4I=

“ws@>= 1.1.4”:
version “8.2.2”
resolved “https://registry.yarnpkg.com/ws/-/ws-8.2.2.tgz#ca684330c6dd6076a737250ed81ac1606cb0a63e”
integrity sha512-Q6B6H2oc8QY3llc3cB8kVmQ6pnJWVQbP7Q5algTcIxx7YEpc0oU4NBVHlztA7Ekzfhw2r0rPducMUiCGWKQRzw==```
4

Subprocesses on Linux weren’t using icudtl paths until… uh, forgot to add that to the earlier fix commits.

1 Like
5

Will be fixed once fix(scripting/v8): use icudtl path for linux fxnode too by blattersturm · Pull Request #1031 · citizenfx/fivem · GitHub is in.

1 Like
6

Awesome, thank you for the quick response!