max-mapper / max-mapper/nginx-vhosts
Permission issues
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 72
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
When running nginx-vhosts I run into permission issues:
{ [Error: Command failed: /bin/sh -c nginx -s reload
nginx: [alert] could not open error log file: open() "/var/log/nginx/error.log" failed (13: Permission denied)
2015/06/18 20:49:20 [notice] 20500#0: signal process started
2015/06/18 20:49:20 [alert] 20500#0: kill(11831, 1) failed (1: Operation not permitted)
]
killed: false,
code: 1,
signal: null,
cmd: '/bin/sh -c nginx -s reload' } '' 'nginx: [alert] could not open error log file: open() "/var/log/nginx/error.log" failed (13: Permission denied)\n2015/06/18 20:49:20 [notice] 20500#0: signal process started\n2015/06/18 20:49:20 [alert] 20500#0: kill(11831, 1) failed (1: Operation not permitted)\n'
I had the same problem writing to the conf.d folder
first problem: write access to /etc/nginx/conf.d/
{ [Error: EACCES, open '/etc/nginx/conf.d/test.conf']
errno: -13,
code: 'EACCES',
path: '/etc/nginx/conf.d/test.conf' } undefined undefined
but I temporarily solved this by chmodding it to 777. This could also be my lack of knowledge on how to provide Nodejs with sudo capabilities, but how can I run nginx-vhost without running into these issues?
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the reported failures from the nginx-vhosts command, including nginx -s reload and writing to /etc/nginx/conf.d/. Inspect how the tool invokes nginx and writes configuration files, then define completion as handling the reported permission failures without relying on chmod 777.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nginx
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100