Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Permission Denied" when reloading #32

Open
michael-t-dukes opened this issue Feb 6, 2017 · 0 comments
Open

"Permission Denied" when reloading #32

michael-t-dukes opened this issue Feb 6, 2017 · 0 comments

Comments

@michael-t-dukes
Copy link

On two different occasions I have seen a strange issue when some Jenkins jobs executes into nginx and adds some configuration.

Occasion 1: Java cartridge

  • Post loading in the Java cartridge the environment job is loaded
  • Once the environment is created it copies in the configuration and loads it over:
    + docker exec proxy /usr/sbin/nginx -s reload nginx: [alert] kill(125, 1) failed (13: Permission denied) Build step 'Execute shell' marked build as failure [ssh-agent] Stopped. Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered Finished: FAILURE
  • When doing some manual activity the following was found:
    root@ADOP-Product-Demo:/home/ubuntu# docker exec proxy /usr/sbin/nginx -s reload nginx: [alert] kill(125, 1) failed (13: Permission denied) root@ADOP-Product-Demo:/home/ubuntu# docker exec proxy sh root@1c43656726b7:/# ls -ltr /usr/sbin/nginx -rwxr-xr-x 1 root root 5479619 Apr 20 2016 /usr/sbin/nginx root@1c43656726b7:/#

Occasion 2: Hybris cartridge

  • Hybris cartridge does the same thing, once environment is created generate the proxy files and then copy in/load it
    root@DEMO-Mike-ADOP-Hybris:/var/lib/docker/volumes/nginx_config/_data/sites-enabled# docker exec -ti proxy bash root@fd9d37ac520a:/# nginx -s reload nginx: [alert] kill(140, 1) failed (13: Permission denied)

Only happens on some occasions, and the fix is: to simply restart the proxy container. Then the config runs correctly as it was intended to be created without any further action.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant