RocketChat / RocketChat/Rocket.Chat
problem with fresh install to 5
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
When installing the latest version of rocket chat, there is an error.
Oct 28 17:10:54 localhost systemd[1]: Started The Rocket.Chat server.
Oct 28 17:10:59 localhost rocketchat[28286]: strict mode: use allowUnionTypes to allow union type keyword at "#/properties/value" (strictTypes)
Oct 28 17:11:00 localhost systemd[1]: rocketchat.service: main process exited, code=killed, status=11/SEGV
Oct 28 17:11:00 localhost systemd[1]: Unit rocketchat.service entered failed state.
Oct 28 17:11:00 localhost systemd[1]: rocketchat.service failed.
Server Setup Information:
Operating System: Centos 7.9.2009
Deployment Method:
Number of Running Instances: 1
DB Replicaset Oplog:
NodeJS Version: v4.19.3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the fresh-install logs and the reported CentOS 7.9.2009, Node.js v4.19.3, and single-instance setup. Reproduce the startup failure, then investigate the strict-mode warning alongside the status 11/SEGV; the issue is done when the Rocket.Chat service starts successfully after installation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100