Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-4727

init script doesn't check for corefile limits when starting

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Fix
    • Critical
    • 2.0
    • 2.0
    • installer
    • Security Level: Public
    • CentOS 5.6

    Description

      Customer installed DP3 on a system with /etc/security/limits.conf originally set to:

      • soft core 0
      • hard core 0

      The Couchbase service started properly, but memcached refused to start with message:
      'ns_1@.....' exited with status 71. Restarting. Messages: failed to ensure corefile creation

      After setting /etc/security/limits.conf to:
      couchbase hard nofile 10240
      couchbase hard core unlimited

      The server was able to start properly.

      We need to check this before service start so that memcached doesn't continuously restart itself.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            steve Steve Yen
            perry Perry Krug
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty