Changes between Initial Version and Version 1 of Ticket #45434, comment 6


Ignore:
Timestamp:
Oct 30, 2014, 5:59:57 PM (10 years ago)
Author:
moderndeveloperllc (Mark Garrett)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #45434, comment 6

    initial v1  
    11I think I found the issue. It's not in the mongo port - it's somewhere else I think. The problem is that `/opt/local/var/log` is getting created by some port with a `0744` permission as opposed to the proper `0755`. This means that the _mongo user can't get down to the `/opt/local/var/log/mongodb` directory to store it's logs. This means that `mongod` does not launch.
    22
    3 As soon as I did `sudo chmod 755 /opt/local/var/log/` the `mongod` instance started and I was able to connect.
     3As soon as I did
     4
     5'''```sudo chmod 755 /opt/local/var/log/```'''
     6
     7the `mongod` instance started and I was able to connect.