Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-28934

Mongo systemd service does not define nofiles

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 3.4.3
    • Component/s: Packaging
    • None
    • Linux

      The issue started after installing the latest mongo server, where the service of mongo has changed from mongod to mongodb, and the service was installed via /usr/lib/systemd and not under /etc/init.

      The problem is that the systemd service does not use the limits defined in /etc/security/limits.conf, and mongo starts with 1024 max open files, and easily crashes as it runs out of open files.

      Also generally systemd does not check /etc/security/limits.conf and you need to add LimitNOFILES to the service.

            Assignee:
            mark.agarunov Mark Agarunov
            Reporter:
            uri.harduf Uri Harduf
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: