Majic Projects
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Closed Bug report MAR-48 Directories created by roles in /run do not survive reboot
Go to the next issue (open or closed)
Go to the next open issue
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue basics
  • Type of issue
    Bug report
  • Category
    Not determined
  • Targetted for
  • Status
  • Progress
  • Priority
    Must fix before next release
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
  • Estimated time
    2 hours
  • Time spent
    No time spent
    Click here to see time logged against this issue
Issue details
  • Resolution
  • Reproducability
    Not determined
  • Severity
    Not determined
Attachments (0)
There is nothing attached to this issue
Duplicate issues (0)
This issue does not have any duplicates
Currently there is a bunch of roles that are creating role-specific sub-directories under '''/run''' or '''/var/run'''. Unfortunately, '''/run''' is mounted as a tmpfs, while '''/var/run''' is just a symlink to '''/run'''. The end result of this is that certain services (web ones for example) are unable to output their pid files to dedicated directories under '''/run''', and will fail to start after reboot.

The behaviour is well described under - and should be easy to fix using the solution outlined in the article.

At least the following roles need updates:

* web_server
* php_website
* wsgi_website
Steps to reproduce this issue
# Deploy testsite.
# Access and
# Verify all works ok.
# Reboot server ''''''.
# Access and
# Both websites are now inaccessible.
Comments ()