[ RpcIpcMessagePortClosedError: Process 38 exited [SIGKILL].

[TheRealDarkCoder]

I cant docker-compose CTFNote on my VPS, here are the logs and files:

root@PubBuntu:~/CTFNote# docker-compose up -d --build
Building db
Step 1/2 : FROM postgres:14
 ---> e94a3bb61224
Step 2/2 : COPY create-multiple-postgresql-databases.sh /docker-entrypoint-initdb.d/create-multiple-postgresql-databases.sh
 ---> Using cache
 ---> aee0bfef7d1a

Successfully built aee0bfef7d1a
Successfully tagged ctfnote_db:latest
Building api
Step 1/27 : ARG NODE_ENV="production"
Step 2/27 : FROM node:16-alpine as builder
 ---> 710c8aa630d5
Step 3/27 : ARG NODE_ENV
 ---> Using cache
 ---> f9713ada2f4e
Step 4/27 : COPY package.json yarn.lock tsconfig.json start.sh /app/
 ---> Using cache
 ---> 9ce0ca6840a8
Step 5/27 : WORKDIR /app/
 ---> Using cache
 ---> 775f55525e2b
Step 6/27 : RUN yarn install --frozen-lockfile --production=false --no-progress
 ---> Using cache
 ---> 0c67b81de709
Step 7/27 : COPY src/ /app/src/
 ---> Using cache
 ---> e7c4d56244e5
Step 8/27 : COPY migrations/ /app/migrations/
 ---> Using cache
 ---> 932106bc3d9f
Step 9/27 : RUN yarn run build
 ---> Using cache
 ---> 0625bc5270aa

Step 10/27 : FROM node:16-alpine as clean
 ---> 710c8aa630d5
Step 11/27 : ARG NODE_ENV
 ---> Using cache
 ---> f9713ada2f4e
Step 12/27 : COPY --from=builder /app/package.json /app/yarn.lock /app/start.sh /app/
 ---> Using cache
 ---> 8eb318c725b2
Step 13/27 : COPY --from=builder /app/dist/ /app/dist/
 ---> Using cache
 ---> 07d67540af01
Step 14/27 : COPY --from=builder /app/migrations/ /app/migrations/
 ---> Using cache
 ---> 3787a522e2ae

Step 15/27 : FROM node:16-alpine
 ---> 710c8aa630d5
Step 16/27 : ARG NODE_ENV
 ---> Using cache
 ---> f9713ada2f4e
Step 17/27 : EXPOSE 3000
 ---> Using cache
 ---> c689b056f292
Step 18/27 : WORKDIR /app/
 ---> Using cache
 ---> b7612c97836e
Step 19/27 : COPY --from=clean /app/ /app/
 ---> Using cache
 ---> 42b27d846142
Step 20/27 : RUN yarn install --frozen-lockfile --production=true --no-progress
 ---> Using cache
 ---> 3fd1deac3937
Step 21/27 : RUN chmod -R 0555 .
 ---> Using cache
 ---> ad1b5e21749b
Step 22/27 : RUN mkdir /app/uploads
 ---> Using cache
 ---> ba8ed7170503
Step 23/27 : RUN chown node /app/uploads
 ---> Using cache
 ---> b97814ba9fca
Step 24/27 : ENV GRAPHILE_TURBO=1
 ---> Using cache
 ---> 5dc158df4aef
Step 25/27 : ENV NODE_ENV=$NODE_ENV
 ---> Using cache
 ---> f2b49be54b6b
Step 26/27 : USER node
 ---> Using cache
 ---> ebf8942720c9
Step 27/27 : CMD ./start.sh db 5432 yarn start
 ---> Using cache
 ---> 58672dd09a4c

Successfully built 58672dd09a4c
Successfully tagged ctfnote_api:latest
Building front
Step 1/12 : FROM node:16-alpine AS build-deps
 ---> 710c8aa630d5
Step 2/12 : RUN mkdir -p /usr/src/app
 ---> Using cache
 ---> 24cd8b5f5324
Step 3/12 : COPY package.json quasar.conf.js .eslintrc.js .eslintignore tsconfig.json .postcssrc.js yarn.lock babel.config.js quasar.extensions.json /usr/src/app/
 ---> Using cache
 ---> eeb3817307d4
Step 4/12 : RUN cd /usr/src/app && yarn install
 ---> Using cache
 ---> a7817dccba14
Step 5/12 : COPY src /usr/src/app/src
 ---> Using cache
 ---> 8f6724d17868
Step 6/12 : COPY public /usr/src/app/public
 ---> Using cache
 ---> 4562c8cd9267
Step 7/12 : WORKDIR /usr/src/app
 ---> Using cache
 ---> 235dd15200e9
Step 8/12 : RUN yarn build
 ---> Running in f05795e5e70d
yarn run v1.22.15
$ quasar build

 Build mode........ spa
 Pkg quasar........ v2.3.3
 Pkg @quasar/app... v3.2.3
 Pkg webpack....... v5
 Debugging......... no
 Publishing........ no

 Configured browser support (>= 89.37% of global marketshare):
 · Chrome for Android >= 96
 · Firefox for Android >= 94
 · Android >= 96
 · Chrome >= 87
 · Edge >= 93
 · Firefox >= 85
 · iOS >= 11.3-11.4
 · Opera >= 77
 · Safari >= 12.1

 App • Running "@quasar/apollo" Quasar App Extension...
 App • Running "@quasar/qmarkdown" Quasar App Extension... App • Extension(@quasar/apollo): Extending quasar.conf... App • Extension(@quasar/qmarkdown): Extending quasar.conf...
 App • Extension(@quasar/qmarkdown): Chaining "UI" Webpack config
 App Extension (qmarkdown) Info: 'Adding markdown loader to chainWebpack'
 App Extension (qmarkdown) Info: 'Adding .vmd (vue+markdown) loader to chainWebpack'
 App • Chaining "UI" Webpack config
 App • Cleaned build artifact: "/usr/src/app/dist/spa"
/usr/src/app/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:19
        closedError = new RpcIpcMessagePortClosedError_1.RpcIpcMessagePortClosedError(code
                      ^

[  RpcIpcMessagePortClosedError: Process 38 exited [SIGKILL].

  - RpcIpcMessagePort.js:19
    [app]/[fork-ts-checker-webpack-plugin]/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:    19:23

  - Generator.next

  - RpcIpcMessagePort.js:8

# Pad
    [app]/[fork-ts-checker-webpack-plugin]/lib/rpc/rpc-ipc/RpcIp
      POSTGRES_PASSWORD: ctfnote
cMessagePort.js:    8:71

  - new Promise

  - RpcIpcMessagePort.js:4 __awaiter
    [app]/[fork-ts-checker-webpack-plugin]/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:    4:12

  - RpcIpcMessagePort.js:18 ChildProcess.handleExit
    [app]/[fork-ts-checker-webpack-plugin]/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:    18:42

  - node:events:390 ChildProcess.emit
    node:events:390:28

  - child_process:290 Process.ChildProcess._handle.onexit
    node:internal/child_process:290:12

] {
  code: null,
  signal: 'SIGKILL'
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: Service 'front' failed to build: The command '/bin/sh -c yarn build' returned a non-zero code: 1

.env:

# Pad

# Secure: we're using HTTPS
CMD_PROTOCOL_USESSL=true

# Domain: you need to define this if you wish to enable any options
CMD_DOMAIN=ctf.[REDACED]:8080

# Content-Security Policy
# CMD_CSP_ENABLE=true

# Upload on filesystem (instead of imgur)
CMD_IMAGE_UPLOAD_TYPE=filesystem

*note, i got a few of these messages when building:

warning " > @apollo/client@3.5.5" has unmet peer dependency "graphql@^14.0.0 || ^15.0.0 || ^16.0.0".
warning "@apollo/client > @graphql-typed-document-node/core@3.1.1" has unmet peer dependency "graphql@^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0".
warning "@apollo/client > graphql-tag@2.12.6" has unmet peer dependency "graphql@^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0".
warning "@quasar/quasar-app-extension-apollo > @vue/apollo-composable@4.0.0-alpha.15" has unmet peer dependency "vue@^2.6.0 || ^3.1.0".

[XeR]

Hello, what commit hash are you using ?
Did you change any files besides .env ? (i.e. what is the output of git status ?)

*note, i got a few of these messages when building:
[...]

You can safely ignore these warnings.
We had to upgrade some packages partially to avoid vulnerabilities

[TheRealDarkCoder]

root@PubBuntu:~/CTFNote# git status
On branch main
Your branch is up to date with 'origin/main'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   .env
        modified:   docker-compose.yml

no changes added to commit (use "git add" and/or "git commit -a")

Im on the latest main branch. Pretty sure this is a system specific problem (Cause I can set it up on my home PC same branch easily). Just trying to figure out what might cause it like firewalls or anything (Since all I can infer from the error message is that some port is closed?)

[JJ-8]

@TheRealDarkCoder This issue seems to be very similar: TypeStrong/fork-ts-checker-webpack-plugin#674. Maybe it is useful to look into the solution that is provided there?

[TheRealDarkCoder]

I have just spun up a completely fresh VPS and the issue persists, so maybe it's not just system specific.

@JJ-8 I don't know how to patch a node module from inside a docker during build.

[XeR]

Is there any log message explaining why a process got SIGKILL'd ?
Try journalctl --boot if your distribution uses systemd and look for anything suspicious

[TheRealDarkCoder]

Looks like the kernel killed the process due to out of memory. Running htop while it builds confirms that the memory usage keeps getting higher until it crashes. There is no way this is a hardware issue, right? The droplet got 2 gigs of memory.

[TheRealDarkCoder]

It was indeed a Memory issue, builds just fine with a higher RAM on the VPS shrugs, who would have expected