• Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 1.8.2
    • Component/s: Sharding, Stability
    • Labels:
    • Environment:
      Linux 2.6.18-238.19.1.el5 #1 SMP Fri Jul 15 07:31:24 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
      CentOS 5
    • Linux

      The mongos crashed with a signal 11 after a lot of "killing old cursor".

      I can see a
      MessagingPort say send() errno:104 Connection reset by peer CLIENT:52821
      Tue Jul 26 10:51:10 [conn177] DBException in process: socket exception
      Tue Jul 26 10:51:10 [conn177] MessagingPort say send() errno:32 Broken pipe CLIENT:52821
      Tue Jul 26 10:51:10 [conn177] unclean socket shutdown from: CLIENT:52821

      just before the crash (see attachment)

        1. issue.log
          63 kB
        2. mongos_crash_last10min.log.gz
          27.56 MB

            Assignee:
            eliot Eliot Horowitz (Inactive)
            Reporter:
            kamaradclimber Grégoire Seux
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: