mandatoryprogrammer / mandatoryprogrammer/xsshunter-express

docker-compose fails on step 25

Open
#30 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
2.4k
Forks
428
PR merge metrics
No merged PRs in 30d

Description

See error message below.
`uname -a` yields `Linux xsshunter 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) x86_64 GNU/Linux`

```
xsshunterexpress_1 | renewAt: 1
xsshunterexpress_1 | defaults:
xsshunterexpress_1 | store:{"module":"greenlock-store-fs"}
xsshunterexpress_1 | challenges:{"http-01":{"module":"acme-http-01-standalone"}}
xsshunterexpress_1 | Starting server...
xsshunterexpress_1 | (node:29) [SEQUELIZE0002] DeprecationWarning: The logging-option should be either a function or false. Default: console.log
xsshunterexpress_1 | (node:29) UnhandledPromiseRejectionWarning: SequelizeConnectionError: could not open file "global/pg_filenode.map": Permission denied
xsshunterexpress_1 | at Client._connectionCallback (/app/node_modules/sequelize/lib/dialects/postgres/connection-manager.js:184:24)
xsshunterexpress_1 | at Client._handleErrorWhileConnecting (/app/node_modules/pg/lib/client.js:305:19)
xsshunterexpress_1 | at Client._handleErrorMessage (/app/node_modules/pg/lib/client.js:325:19)
xsshunterexpress_1 | at Connection.emit (events.js:314:20)
xsshunterexpress_1 | at /app/node_modules/pg/lib/connection.js:115:12
xsshunterexpress_1 | at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:40:17)
xsshunterexpress_1 | at Socket. (/app/node_modules/pg-protocol/dist/index.js:10:42)
xsshunterexpress_1 | at Socket.emit (events.js:314:20)
xsshunterexpress_1 | at addChunk (_stream_readable.js:297:12)
xsshunterexpress_1 | at readableAddChunk (_stream_readable.js:272:9)
xsshunterexpress_1 | (node:29) 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)
xsshunterexpress_1 | (node:29) [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.
xsshunter-express_xsshunterexpress_1 exited with code 0
```

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing step 25 with docker-compose on the reported Debian environment and inspect the PostgreSQL setup behind the Sequelize connection failure. Done means the compose startup completes and the XSS Hunter Express service remains running without the pg_filenode.map permission error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose, javascript, node.js, postgresql
Domain
backend, databases, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.