<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 03:22:10 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[SERVER-10064] How does MMS know the version number of my mongod server?</title>
                <link>https://jira.mongodb.org/browse/SERVER-10064</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;I have 5 mongo servers in a replica set: zuemongo1, 2, 5, 6, and 7.&lt;/p&gt;

&lt;p&gt;MMS currently shows their versions as 2.2.1, 2.2.5, 2.2.1, 2.2.5, 2.2.5 (respectively).&lt;/p&gt;

&lt;p&gt;The active daemon running on all five servers is 2.2.1.&lt;/p&gt;

&lt;p&gt;Last night, I did some maintenance on this replicaset, and so knowing (a) I was going to bounce the dameon on each server and (b) we need to upgrade to 2.2.5 soon, I took last night as an opportunity to get the 2.2.5 binaries on the servers, but set them aside (details below) so i can upgrade and downgrade at will (details below) when we&apos;re ready for the upgrade. &lt;/p&gt;

&lt;p&gt;What&apos;s odd is that MMS thinks we&apos;re running 2.2.5 on 3 servers and 2.2.1 on 2 servers ... when in reality i executed the exact same commands on all five servers.&lt;/p&gt;


&lt;p&gt;Yesterday, I stopped mongod:&lt;br/&gt;
  $ /etc/init.d/mongod stop&lt;/p&gt;

&lt;p&gt;Yum upgraded to 2.2.5:&lt;br/&gt;
  $ yum update mongo-10gen-2.2.5 mongo-10gen-server-2.2.5&lt;/p&gt;

&lt;p&gt;But then mv&apos;d all of the 2.2.5 binaries aside, e.g.:&lt;br/&gt;
  $ cd /usr/bin&lt;br/&gt;
  $ mv mongo         mongo.2.2.5&lt;br/&gt;
  $ mv mongod        mongod.2.2.5&lt;br/&gt;
  $ mv mongodump     mongodump.2.2.5&lt;br/&gt;
  $ mv mongoexport   mongoexport.2.2.5&lt;br/&gt;
  $ mv mongofiles    mongofiles.2.2.5&lt;br/&gt;
  $ mv mongoimport   mongoimport.2.2.5&lt;br/&gt;
  $ mv mongooplog    mongooplog.2.2.5&lt;br/&gt;
  $ mv mongoperf     mongoperf.2.2.5&lt;br/&gt;
  $ mv mongorestore  mongorestore.2.2.5&lt;br/&gt;
  $ mv mongos        mongos.2.2.5&lt;br/&gt;
  $ mv mongostat     mongostat.2.2.5&lt;br/&gt;
  $ mv mongotop      mongotop.2.2.5&lt;br/&gt;
  $ mv bsondump      bsondump.2.2.5&lt;/p&gt;

&lt;p&gt;And sym linkd the 2.2.1 binaries (which is what we&apos;ve been running on):&lt;br/&gt;
  $ ln -sf mongo.2.2.1          mongo&lt;br/&gt;
  $ ln -sf mongod.2.2.1         mongod&lt;br/&gt;
  $ ln -sf mongodump.2.2.1      mongodump&lt;br/&gt;
  $ ln -sf mongoexport.2.2.1    mongoexport&lt;br/&gt;
  $ ln -sf mongofiles.2.2.1     mongofiles&lt;br/&gt;
  $ ln -sf mongoimport.2.2.1    mongoimport&lt;br/&gt;
  $ ln -sf mongooplog.2.2.1     mongoimport&lt;br/&gt;
  $ ln -sf mongoperf.2.2.1      mongoperf&lt;br/&gt;
  $ ln -sf mongorestore.2.2.1   mongorestore&lt;br/&gt;
  $ ln -sf mongos.2.2.1         mongos&lt;br/&gt;
  $ ln -sf mongostat.2.2.1      mongostat &lt;br/&gt;
  $ ln -sf mongotop.2.2.1       mongotop&lt;br/&gt;
  $ ln -sf bsondump.2.2.1       bsondump&lt;/p&gt;

&lt;p&gt;Then started mongod back up:&lt;br/&gt;
  $ /etc/init.d/mongod start&lt;/p&gt;



&lt;p&gt;So my incredibly trivial question is: how does MMS get it&apos;s version info? I&apos;m guessing it&apos;s not from the running daemon but possibly via a YUM post-install hook or some YUM meta-data somewhere. &lt;/p&gt;

&lt;p&gt;Thanks&lt;br/&gt;
--tom&lt;/p&gt;





</description>
                <environment>CentOS x86_64, mongod 2.2.1.</environment>
        <key id="80787">SERVER-10064</key>
            <summary>How does MMS know the version number of my mongod server?</summary>
                <type id="6" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14720&amp;avatarType=issuetype">Question</type>
                                            <priority id="5" iconUrl="https://jira.mongodb.org/images/icons/priorities/trivial.svg">Trivial - P5</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="9">Done</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="tlaramee">Tom Laramee</reporter>
                        <labels>
                    </labels>
                <created>Sat, 29 Jun 2013 18:17:05 +0000</created>
                <updated>Wed, 10 Dec 2014 23:11:40 +0000</updated>
                            <resolved>Sun, 30 Jun 2013 02:43:45 +0000</resolved>
                                                                                        <votes>0</votes>
                                    <watches>6</watches>
                                                                                                                <comments>
                            <comment id="372073" author="tlaramee" created="Mon, 1 Jul 2013 22:42:21 +0000"  >&lt;p&gt;Johan: (cont)&lt;/p&gt;

&lt;p&gt;The fact that the conditional restarts STDOUT &amp;amp; STDERR goes to /dev/null is bad idea. I have seen this before it&apos;s a bad idea in the other places too. (i&apos;ve seen it in some /etc/init.d scripts) &lt;/p&gt;

&lt;p&gt;The down side here is that I might miss the fact that the conditional restart failed.&lt;/p&gt;

&lt;p&gt;The upside is none. &lt;/p&gt;

&lt;p&gt;If you guys insist on a restart, it would be better to note the result of that signal going to the daemon and display an error when it fails.&lt;/p&gt;

&lt;p&gt;Also, a:&lt;/p&gt;

&lt;p&gt;echo &quot;*** HEAD&apos;S UP - RESTARING THE DAMEON ****&quot;&lt;/p&gt;

&lt;p&gt;would be wickedly helpful.&lt;/p&gt;
</comment>
                            <comment id="372066" author="tlaramee" created="Mon, 1 Jul 2013 22:38:54 +0000"  >&lt;p&gt;Johan:&lt;/p&gt;

&lt;p&gt;Whether this is a &quot;standard&quot; or not (it isn&apos;t), is a moot point.&lt;/p&gt;

&lt;p&gt;The salient question here is: is this the right behavior for mongodb?&lt;/p&gt;

&lt;p&gt;I&apos;d like to make the case that it&apos;s not.&lt;/p&gt;

&lt;p&gt;The problem is, the yum script is conflating two things:&lt;br/&gt;
(1) when i upgrade&lt;br/&gt;
(2) when i have a service-related outage due to a bounced daemon&lt;/p&gt;

&lt;p&gt;This means that the time yum takes to go out and update it&apos;s repo meta-data, copy the rpm to my server, unpack it, and run all of the pre/post-install instructions (step 1) becomes automatically part of (2) my service interruption.&lt;/p&gt;

&lt;p&gt;My goal is always to minimize the duration of (2), and this makes it impossible to do so.&lt;/p&gt;

&lt;p&gt;I have two possible ways to update:&lt;br/&gt;
(1a) stop mongod&lt;br/&gt;
(1b) run a yum update&lt;br/&gt;
(1c) start mongod manually&lt;/p&gt;

&lt;p&gt;vs:&lt;br/&gt;
(2a) run a yum update&lt;br/&gt;
(2b) have mongod restarted via a conditional restart compliments of yum&lt;/p&gt;


&lt;p&gt;In both of those cases, the time of the &quot;yum update&quot; is part of my outage, and that is the core problem.&lt;/p&gt;

&lt;p&gt;It would be &lt;b&gt;much&lt;/b&gt; better if the yum update simply echo&apos;d to STDOUT:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;
		&lt;ul&gt;
			&lt;li&gt;
			&lt;ul&gt;
				&lt;li&gt;RUN A SERVICE RESTART TO BEGIN RUNNING THE NEW BINARY ****&lt;/li&gt;
			&lt;/ul&gt;
			&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;That way, I could get the binaries on my machine, check out my configs, run a mongodump, and &lt;b&gt;then&lt;/b&gt; bounce the daemon.&lt;/p&gt;















</comment>
                            <comment id="371209" author="jhn" created="Sun, 30 Jun 2013 20:10:21 +0000"  >&lt;p&gt;Tom, restarting running deamons after an &lt;tt&gt;yum update&lt;/tt&gt; is very common (I would say standard) on RedHat based distributions and mongodb is no different in that aspect.&lt;/p&gt;

&lt;p&gt;Whats not considered good practice is to start a deamon that is stopped when you &lt;tt&gt;yum update&lt;/tt&gt;.&lt;/p&gt;</comment>
                            <comment id="371203" author="tlaramee" created="Sun, 30 Jun 2013 19:48:55 +0000"  >&lt;p&gt;thanks Johan... at least i understand what happened.&lt;/p&gt;

&lt;p&gt;so a couple of things:&lt;/p&gt;

&lt;p&gt;(1) never have i encountered a software package in which a &quot;yum update&quot; causes &lt;br/&gt;
an active daemon to restart. i&apos;ve installed hundreds of software packages &lt;br/&gt;
using yum and have never encountered this before. &lt;/p&gt;

&lt;p&gt;(2) in reading various tutorials on upgrading mongo in yum (found using google), &lt;br/&gt;
i think everyone else is not expecting this either. everyone seems to indicate &lt;br/&gt;
that the last step is always a &quot;service mongod start&quot; or an &quot;/etc/init.d/mongod start&quot;. &lt;/p&gt;

&lt;p&gt;E.g.: &lt;br/&gt;
&lt;a href=&quot;http://ivanfioravanti.wordpress.com/2013/03/19/upgrade-a-standalone-mongodb-2-2-to-2-4-on-linux-centos-in-azure/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://ivanfioravanti.wordpress.com/2013/03/19/upgrade-a-standalone-mongodb-2-2-to-2-4-on-linux-centos-in-azure/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;(3) why does the postun section redirect stdout &amp;amp; stderr to /dev/null?  what &lt;br/&gt;
makes this so confusing is that there are 2 lines of stdout when you run &lt;br/&gt;
an &quot;/etc/init.d/mongod start&quot; indicating that the daemon has started and &lt;br/&gt;
where the log can be found... these are buried in update script. &lt;/p&gt;

&lt;p&gt;here&apos;s the 5 lines of the postun command i&apos;m referencing:&lt;/p&gt;

&lt;p&gt;%postun server&lt;br/&gt;
if test $1 -ge 1&lt;br/&gt;
then&lt;br/&gt;
  /sbin/service mongod condrestart &amp;gt;/dev/null 2&amp;gt;&amp;amp;1 || :&lt;br/&gt;
fi&lt;/p&gt;



</comment>
                            <comment id="371131" author="jhn" created="Sun, 30 Jun 2013 15:12:23 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=tlaramee&quot; class=&quot;user-hover&quot; rel=&quot;tlaramee&quot;&gt;tlaramee&lt;/a&gt;, when looking at the spec-file in the git repository for 2.2 it does a condrestart of mongod after an upgrade: &lt;a href=&quot;https://github.com/mongodb/mongo/blob/v2.2/rpm/mongo.spec&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/blob/v2.2/rpm/mongo.spec&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The check for a running mongod in condrestart is a little bit simple: &lt;a href=&quot;https://github.com/mongodb/mongo/blob/v2.2/rpm/init.d-mongod&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/blob/v2.2/rpm/init.d-mongod&lt;/a&gt; so if you for example have a stale &lt;tt&gt;/var/lock/subsys/mongod&lt;/tt&gt; an &lt;tt&gt;yum update&lt;/tt&gt; will start up a mongod directly after the update even if you don&apos;t have any mongod running.&lt;/p&gt;</comment>
                            <comment id="371124" author="tlaramee" created="Sun, 30 Jun 2013 14:49:18 +0000"  >
&lt;p&gt;One possible explanation for this could be if this command:&lt;/p&gt;

&lt;p&gt;$ yum update mongo-10gen-2.2.5 mongo-10gen-server-2.2.5&lt;/p&gt;

&lt;p&gt;..caused the new binaries to be pulled down and a new daemon started in the background.&lt;/p&gt;

&lt;p&gt;Is it possible that this was what happened?&lt;/p&gt;

&lt;p&gt;That would explain the spawning of three 2.2.5 daemons. Then, when I manually tried to start them after the yum update via:&lt;/p&gt;

&lt;p&gt;$ /etc/init.d/mongod start&lt;/p&gt;

&lt;p&gt;These likely would have errored out due to an already-running daemon.&lt;/p&gt;

&lt;p&gt;This would explain a lot if it&apos;s true.&lt;/p&gt;





</comment>
                            <comment id="370983" author="tlaramee" created="Sun, 30 Jun 2013 05:16:34 +0000"  >&lt;p&gt;While we&apos;re at it: if the installer could not overwrite the existing binaries: THAT WOULD BE AMAZING! &lt;img class=&quot;emoticon&quot; src=&quot;https://jira.mongodb.org/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;

&lt;p&gt;Check out my initial comments - i&apos;m maintaining multiple versions of your binaries so i can upgrade and downgrade at will - mostly to mitigate any risk w/ upgrading and running into a major production issue and having to roll back.&lt;/p&gt;
</comment>
                            <comment id="370981" author="tlaramee" created="Sun, 30 Jun 2013 05:14:24 +0000"  >&lt;p&gt;The bug is that MMS seems to never downgrade a version.&lt;/p&gt;

&lt;p&gt;I&apos;m relatively confident that the daemons for all of these machines were started using v2.2.1.&lt;/p&gt;

&lt;p&gt;Two things I don&apos;t understand are:&lt;/p&gt;

&lt;p&gt;(1) this bug&lt;br/&gt;
(2) why the daemon seems to auto-restart following a yum upgrade.&lt;/p&gt;

&lt;p&gt;w/r/t (2): I didn&apos;t manually restart the daemon during the yum upgrade &amp;#8211; this was something the yum post-install script must have done on my behalf.&lt;/p&gt;

&lt;p&gt;This is a HUGE problem for me ...and likely for others.&lt;/p&gt;

&lt;p&gt;When I upgraded the server, the daemon was STOPPED. If yum is going to restart it on my behalf: this is bad ... it&apos;s really bad.&lt;/p&gt;

&lt;p&gt;Said another way: at no point did I explicitly start a 2.2.5 daemon &amp;#8211; i only started 2.2.1 daemons ... and there is no scenario in which I wanted a 2.2.5 daemon started.&lt;/p&gt;

&lt;p&gt;I want to retain the choice to upgrade and downgrade at will - and so I &quot;yum installed&quot; the new binaries knowing i would set them aside (via a &quot;mv&quot;).. then sym link the active binary. &lt;/p&gt;

&lt;p&gt;Should the case arise that I need to roll-back, it&apos;s as simple as re-sym-linking and bouncing daemons.&lt;/p&gt;

















</comment>
                            <comment id="370979" author="tlaramee" created="Sun, 30 Jun 2013 05:07:48 +0000"  >&lt;p&gt;Here&apos;s mongo7 .. same deal - a restart on 2.2.5 followed by a downgrade to 2.2.1.  MMS has the wrong version info.&lt;/p&gt;


&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;root@zuemongo7 mongo&amp;#93;&lt;/span&gt;#  grep -A 20 &quot;SERVER RESTARTED&quot; 29 &lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;
		&lt;ul&gt;
			&lt;li&gt;
			&lt;ul&gt;
				&lt;li&gt;
				&lt;ul&gt;
					&lt;li&gt;SERVER RESTARTED *****&lt;/li&gt;
				&lt;/ul&gt;
				&lt;/li&gt;
			&lt;/ul&gt;
			&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;Fri Jun 28 19:59:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; MongoDB starting : pid=32512 port=27022 dbpath=/var/lib/mongo 64-bit host=zuemongo7.zulily.com&lt;br/&gt;
Fri Jun 28 19:59:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; db version v2.2.5, pdfile version 4.5&lt;br/&gt;
Fri Jun 28 19:59:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; git version: 14d8c4d1eb320ab10c6956f6e4b52263249bc0b4&lt;br/&gt;
Fri Jun 28 19:59:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; build info: Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49&lt;br/&gt;
Fri Jun 28 19:59:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; options: &lt;/p&gt;
{ config: &quot;/etc/mongod.conf&quot;, dbpath: &quot;/var/lib/mongo&quot;, fork: &quot;true&quot;, logappend: &quot;true&quot;, logpath: &quot;/var/log/mongo/mongod.log&quot;, oplogSize: 5000, port: 27022, replSet: &quot;zumongous&quot;, rest: &quot;true&quot; }
&lt;p&gt;Fri Jun 28 19:59:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; journal dir=/var/lib/mongo/journal&lt;br/&gt;
Fri Jun 28 19:59:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; recover : no journal files present, no recovery needed&lt;br/&gt;
Fri Jun 28 19:59:46 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster=true 11.62&lt;br/&gt;
Fri Jun 28 19:59:47 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster=true 10.46&lt;br/&gt;
Fri Jun 28 19:59:48 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster=true 10.68&lt;br/&gt;
Fri Jun 28 19:59:48 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocating a journal file /var/lib/mongo/journal/prealloc.0&lt;br/&gt;
Fri Jun 28 19:59:58 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocating a journal file /var/lib/mongo/journal/prealloc.1&lt;br/&gt;
Fri Jun 28 20:00:08 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocating a journal file /var/lib/mongo/journal/prealloc.2&lt;br/&gt;
Fri Jun 28 20:00:17 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; waiting for connections on port 27022&lt;br/&gt;
Fri Jun 28 20:00:17 &lt;span class=&quot;error&quot;&gt;&amp;#91;websvr&amp;#93;&lt;/span&gt; admin web console waiting for connections on port 28022&lt;br/&gt;
Fri Jun 28 20:00:17 &lt;span class=&quot;error&quot;&gt;&amp;#91;rsStart&amp;#93;&lt;/span&gt; replSet can&apos;t get local.system.replset config from self or any seed (EMPTYCONFIG)&lt;br/&gt;
Fri Jun 28 20:00:17 &lt;span class=&quot;error&quot;&gt;&amp;#91;rsStart&amp;#93;&lt;/span&gt; replSet info you may need to run replSetInitiate &amp;#8211; rs.initiate() in the shell &amp;#8211; if that is not already done&lt;br/&gt;
Fri Jun 28 20:00:17 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.187:48315 #1 (1 connection now open)&lt;br/&gt;
&amp;#8211;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;
		&lt;ul&gt;
			&lt;li&gt;
			&lt;ul&gt;
				&lt;li&gt;
				&lt;ul&gt;
					&lt;li&gt;SERVER RESTARTED *****&lt;/li&gt;
				&lt;/ul&gt;
				&lt;/li&gt;
			&lt;/ul&gt;
			&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;Fri Jun 28 20:00:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; MongoDB starting : pid=8520 port=27022 dbpath=/var/lib/mongo 64-bit host=zuemongo7.zulily.com&lt;br/&gt;
Fri Jun 28 20:00:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; db version v2.2.1, pdfile version 4.5&lt;br/&gt;
Fri Jun 28 20:00:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; git version: d6764bf8dfe0685521b8bc7b98fd1fab8cfeb5ae&lt;br/&gt;
Fri Jun 28 20:00:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; build info: Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49&lt;br/&gt;
Fri Jun 28 20:00:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; options: &lt;/p&gt;
{ config: &quot;/etc/mongod.conf&quot;, dbpath: &quot;/var/lib/mongo&quot;, fork: &quot;true&quot;, logappend: &quot;true&quot;, logpath: &quot;/var/log/mongo/mongod.log&quot;, oplogSize: 5000, port: 27022, replSet: &quot;zumongous&quot;, rest: &quot;true&quot; }
&lt;p&gt;Fri Jun 28 20:00:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.186:15324 #8027 (429 connections now open)&lt;br/&gt;
Fri Jun 28 20:00:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn7828&amp;#93;&lt;/span&gt; end connection 172.16.0.186:12697 (428 connections now open)&lt;br/&gt;
Fri Jun 28 20:00:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.186:15396 #8028 (429 connections now open)&lt;br/&gt;
Fri Jun 28 20:00:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.136:51656 #8029 (430 connections now open)&lt;br/&gt;
Fri Jun 28 20:00:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.187:12492 #8030 (431 connections now open)&lt;br/&gt;
Fri Jun 28 20:00:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.182:51631 #8031 (432 connections now open)&lt;br/&gt;
Fri Jun 28 20:00:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.187:12510 #8032 (433 connections now open)&lt;br/&gt;
Fri Jun 28 20:00:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.136:51708 #8033 (434 connections now open)&lt;br/&gt;
Fri Jun 28 20:00:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.136:51730 #8034 (435 connections now open)&lt;br/&gt;
Fri Jun 28 20:00:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.136:51737 #8035 (436 connections now open)&lt;br/&gt;
Fri Jun 28 20:00:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.137:32510 #8036 (437 connections now open)&lt;br/&gt;
Fri Jun 28 20:00:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.186:15498 #8037 (438 connections now open)&lt;br/&gt;
Fri Jun 28 20:00:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.182:51678 #8038 (439 connections now open)&lt;/p&gt;</comment>
                            <comment id="370977" author="tlaramee" created="Sun, 30 Jun 2013 05:05:53 +0000"  >&lt;p&gt;Here&apos;s mongo6.&lt;/p&gt;

&lt;p&gt;I reports it&apos;s on v2.2.5 ... even though the last restart is on v.2.2.1. I think the version info on MMS is wrong:&lt;/p&gt;


&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;root@zuemongo6 mongo&amp;#93;&lt;/span&gt;#  grep -A 20 &quot;ERVER RESTARTE&quot; 29 &lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;
		&lt;ul&gt;
			&lt;li&gt;
			&lt;ul&gt;
				&lt;li&gt;
				&lt;ul&gt;
					&lt;li&gt;SERVER RESTARTED *****&lt;/li&gt;
				&lt;/ul&gt;
				&lt;/li&gt;
			&lt;/ul&gt;
			&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;Fri Jun 28 20:23:25 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; MongoDB starting : pid=4677 port=27021 dbpath=/var/lib/mongo 64-bit host=zuemongo6.zulily.com&lt;br/&gt;
Fri Jun 28 20:23:25 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; db version v2.2.5, pdfile version 4.5&lt;br/&gt;
Fri Jun 28 20:23:25 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; git version: 14d8c4d1eb320ab10c6956f6e4b52263249bc0b4&lt;br/&gt;
Fri Jun 28 20:23:25 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; build info: Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49&lt;br/&gt;
Fri Jun 28 20:23:25 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; options: &lt;/p&gt;
{ config: &quot;/etc/mongod.conf&quot;, dbpath: &quot;/var/lib/mongo&quot;, fork: &quot;true&quot;, logappend: &quot;true&quot;, logpath: &quot;/var/log/mongo/mongod.log&quot;, oplogSize: 5000, port: 27021, replSet: &quot;zumongous&quot;, rest: &quot;true&quot; }
&lt;p&gt;Fri Jun 28 20:23:25 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; journal dir=/var/lib/mongo/journal&lt;br/&gt;
Fri Jun 28 20:23:25 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; recover : no journal files present, no recovery needed&lt;br/&gt;
Fri Jun 28 20:23:26 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster=true 13.72&lt;br/&gt;
Fri Jun 28 20:23:27 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster=true 13.28&lt;br/&gt;
Fri Jun 28 20:23:29 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster=true 13.6&lt;br/&gt;
Fri Jun 28 20:23:29 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster check took 3.367 secs&lt;br/&gt;
Fri Jun 28 20:23:29 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocating a journal file /var/lib/mongo/journal/prealloc.0&lt;br/&gt;
Fri Jun 28 20:23:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocating a journal file /var/lib/mongo/journal/prealloc.1&lt;br/&gt;
Fri Jun 28 20:23:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocating a journal file /var/lib/mongo/journal/prealloc.2&lt;br/&gt;
Fri Jun 28 20:23:58 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; waiting for connections on port 27021&lt;br/&gt;
Fri Jun 28 20:23:58 &lt;span class=&quot;error&quot;&gt;&amp;#91;websvr&amp;#93;&lt;/span&gt; admin web console waiting for connections on port 28021&lt;br/&gt;
Fri Jun 28 20:23:58 &lt;span class=&quot;error&quot;&gt;&amp;#91;rsStart&amp;#93;&lt;/span&gt; replSet can&apos;t get local.system.replset config from self or any seed (EMPTYCONFIG)&lt;br/&gt;
Fri Jun 28 20:23:58 &lt;span class=&quot;error&quot;&gt;&amp;#91;rsStart&amp;#93;&lt;/span&gt; replSet info you may need to run replSetInitiate &amp;#8211; rs.initiate() in the shell &amp;#8211; if that is not already done&lt;br/&gt;
&amp;#8211;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;
		&lt;ul&gt;
			&lt;li&gt;
			&lt;ul&gt;
				&lt;li&gt;
				&lt;ul&gt;
					&lt;li&gt;SERVER RESTARTED *****&lt;/li&gt;
				&lt;/ul&gt;
				&lt;/li&gt;
			&lt;/ul&gt;
			&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;Fri Jun 28 20:24:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; MongoDB starting : pid=12277 port=27021 dbpath=/var/lib/mongo 64-bit host=zuemongo6.zulily.com&lt;br/&gt;
Fri Jun 28 20:24:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; db version v2.2.1, pdfile version 4.5&lt;br/&gt;
Fri Jun 28 20:24:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; git version: d6764bf8dfe0685521b8bc7b98fd1fab8cfeb5ae&lt;br/&gt;
Fri Jun 28 20:24:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; build info: Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49&lt;br/&gt;
Fri Jun 28 20:24:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; options: &lt;/p&gt;
{ config: &quot;/etc/mongod.conf&quot;, dbpath: &quot;/var/lib/mongo&quot;, fork: &quot;true&quot;, logappend: &quot;true&quot;, logpath: &quot;/var/log/mongo/mongod.log&quot;, oplogSize: 5000, port: 27021, replSet: &quot;zumongous&quot;, rest: &quot;true&quot; }
&lt;p&gt;Fri Jun 28 20:24:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.187:57117 #7369 (176 connections now open)&lt;br/&gt;
Fri Jun 28 20:24:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.181:54047 #7370 (177 connections now open)&lt;br/&gt;
Fri Jun 28 20:24:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.137:31161 #7371 (178 connections now open)&lt;br/&gt;
Fri Jun 28 20:24:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.137:31174 #7372 (179 connections now open)&lt;br/&gt;
Fri Jun 28 20:24:15 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.181:54088 #7373 (180 connections now open)&lt;br/&gt;
Fri Jun 28 20:24:15 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.137:31221 #7374 (181 connections now open)&lt;br/&gt;
Fri Jun 28 20:24:15 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.136:54817 #7375 (182 connections now open)&lt;br/&gt;
Fri Jun 28 20:24:15 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.182:12872 #7376 (183 connections now open)&lt;br/&gt;
Fri Jun 28 20:24:15 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.181:54112 #7377 (184 connections now open)&lt;br/&gt;
Fri Jun 28 20:24:15 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.186:31406 #7378 (185 connections now open)&lt;br/&gt;
Fri Jun 28 20:24:15 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.186:31424 #7379 (186 connections now open)&lt;br/&gt;
Fri Jun 28 20:24:15 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.186:31433 #7380 (187 connections now open)&lt;br/&gt;
Fri Jun 28 20:24:15 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.187:57330 #7381 (188 connections now open)&lt;br/&gt;
&lt;span class=&quot;error&quot;&gt;&amp;#91;root@zuemongo6 mongo&amp;#93;&lt;/span&gt;# &lt;/p&gt;


</comment>
                            <comment id="370976" author="tlaramee" created="Sun, 30 Jun 2013 05:04:47 +0000"  >&lt;p&gt;Here&apos;s mongo5 .. this one had some serious problems connecting to the replica set ... so i ended up killing the active daemons manually and restarting. I can open a separate ticket for that bug if you&apos;d like. &lt;/p&gt;

&lt;p&gt;The salient restart is the last one &amp;#8211; it&apos;s 2.2.1.&lt;/p&gt;

&lt;p&gt;MMS reports this as 2.2.1 ... which makes sense to me, the last time the daemon was restarted was on v2.2.1 .. even though it had a previous restart on v2.2.5.&lt;/p&gt;




&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;root@zuemongo5 mongo&amp;#93;&lt;/span&gt;#  grep -A 20 &quot;SERVER RESTARTED&quot; 29 &lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;
		&lt;ul&gt;
			&lt;li&gt;
			&lt;ul&gt;
				&lt;li&gt;
				&lt;ul&gt;
					&lt;li&gt;SERVER RESTARTED *****&lt;/li&gt;
				&lt;/ul&gt;
				&lt;/li&gt;
			&lt;/ul&gt;
			&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;Fri Jun 28 20:31:24 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; MongoDB starting : pid=11329 port=27020 dbpath=/var/lib/mongo 64-bit host=zuemongo5.zulily.com&lt;br/&gt;
Fri Jun 28 20:31:24 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; db version v2.2.5, pdfile version 4.5&lt;br/&gt;
Fri Jun 28 20:31:24 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; git version: 14d8c4d1eb320ab10c6956f6e4b52263249bc0b4&lt;br/&gt;
Fri Jun 28 20:31:24 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; build info: Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49&lt;br/&gt;
Fri Jun 28 20:31:24 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; options: &lt;/p&gt;
{ config: &quot;/etc/mongod.conf&quot;, dbpath: &quot;/var/lib/mongo&quot;, fork: &quot;true&quot;, logappend: &quot;true&quot;, logpath: &quot;/var/log/mongo/mongod.log&quot;, oplogSize: 5000, port: 27020, replSet: &quot;zumongous&quot;, rest: &quot;true&quot; }
&lt;p&gt;Fri Jun 28 20:31:24 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; journal dir=/var/lib/mongo/journal&lt;br/&gt;
Fri Jun 28 20:31:24 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; recover : no journal files present, no recovery needed&lt;br/&gt;
Fri Jun 28 20:31:24 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster=true 7.68&lt;br/&gt;
Fri Jun 28 20:31:25 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster=true 8.04&lt;br/&gt;
Fri Jun 28 20:31:26 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster=true 8.2&lt;br/&gt;
Fri Jun 28 20:31:26 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocating a journal file /var/lib/mongo/journal/prealloc.0&lt;br/&gt;
Fri Jun 28 20:31:32 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocating a journal file /var/lib/mongo/journal/prealloc.1&lt;br/&gt;
Fri Jun 28 20:31:38 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocating a journal file /var/lib/mongo/journal/prealloc.2&lt;br/&gt;
Fri Jun 28 20:31:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; waiting for connections on port 27020&lt;br/&gt;
Fri Jun 28 20:31:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;websvr&amp;#93;&lt;/span&gt; admin web console waiting for connections on port 28020&lt;br/&gt;
Fri Jun 28 20:31:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;rsStart&amp;#93;&lt;/span&gt; replSet can&apos;t get local.system.replset config from self or any seed (EMPTYCONFIG)&lt;br/&gt;
Fri Jun 28 20:31:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;rsStart&amp;#93;&lt;/span&gt; replSet info you may need to run replSetInitiate &amp;#8211; rs.initiate() in the shell &amp;#8211; if that is not already done&lt;br/&gt;
Fri Jun 28 20:31:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.187:46702 #1 (1 connection now open)&lt;br/&gt;
&amp;#8211;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;
		&lt;ul&gt;
			&lt;li&gt;
			&lt;ul&gt;
				&lt;li&gt;
				&lt;ul&gt;
					&lt;li&gt;SERVER RESTARTED *****&lt;/li&gt;
				&lt;/ul&gt;
				&lt;/li&gt;
			&lt;/ul&gt;
			&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;Fri Jun 28 20:32:10 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.181:44536 #23773 (774 connections now open)&lt;br/&gt;
Fri Jun 28 20:32:10 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn23634&amp;#93;&lt;/span&gt; end connection 172.16.0.20:45439 (773 connections now open)&lt;br/&gt;
Fri Jun 28 20:32:11 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.182:26782 #23774 (774 connections now open)&lt;br/&gt;
Fri Jun 28 20:32:11 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn23608&amp;#93;&lt;/span&gt; end connection 172.16.0.18:34977 (773 connections now open)&lt;br/&gt;
Fri Jun 28 20:32:12 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.181:44937 #23775 (774 connections now open)&lt;br/&gt;
Fri Jun 28 20:32:13 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.137:19675 #23776 (775 connections now open)&lt;br/&gt;
Fri Jun 28 20:32:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.4:28651 #23777 (776 connections now open)&lt;br/&gt;
Fri Jun 28 20:32:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.181:45455 #23778 (777 connections now open)&lt;br/&gt;
Fri Jun 28 20:32:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.181:45458 #23779 (778 connections now open)&lt;br/&gt;
Fri Jun 28 20:32:15 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.182:27549 #23780 (779 connections now open)&lt;br/&gt;
Fri Jun 28 20:32:15 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.181:45641 #23781 (780 connections now open)&lt;br/&gt;
Fri Jun 28 20:32:16 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.182:27841 #23782 (781 connections now open)&lt;br/&gt;
Fri Jun 28 20:32:16 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 127.0.0.1:54645 #23783 (782 connections now open)&lt;br/&gt;
Fri Jun 28 20:32:16 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.181:45788 #23784 (783 connections now open)&lt;br/&gt;
Fri Jun 28 20:32:17 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1491&amp;#93;&lt;/span&gt; end connection 172.16.0.242:51718 (782 connections now open)&lt;br/&gt;
Fri Jun 28 20:32:17 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.242:51725 #23785 (783 connections now open)&lt;br/&gt;
Fri Jun 28 20:32:19 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.32:15833 #23786 (784 connections now open)&lt;br/&gt;
Fri Jun 28 20:32:19 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.181:46297 #23787 (785 connections now open)&lt;br/&gt;
&amp;#8211;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;
		&lt;ul&gt;
			&lt;li&gt;
			&lt;ul&gt;
				&lt;li&gt;
				&lt;ul&gt;
					&lt;li&gt;SERVER RESTARTED *****&lt;/li&gt;
				&lt;/ul&gt;
				&lt;/li&gt;
			&lt;/ul&gt;
			&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;Fri Jun 28 20:52:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; MongoDB starting : pid=9517 port=27020 dbpath=/var/lib/mongo 64-bit host=zuemongo5.zulily.com&lt;br/&gt;
Fri Jun 28 20:52:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; db version v2.2.1, pdfile version 4.5&lt;br/&gt;
Fri Jun 28 20:52:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; git version: d6764bf8dfe0685521b8bc7b98fd1fab8cfeb5ae&lt;br/&gt;
Fri Jun 28 20:52:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; build info: Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49&lt;br/&gt;
Fri Jun 28 20:52:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; options: &lt;/p&gt;
{ config: &quot;/etc/mongod.conf&quot;, dbpath: &quot;/var/lib/mongo&quot;, fork: &quot;true&quot;, logappend: &quot;true&quot;, logpath: &quot;/var/log/mongo/mongod.log&quot;, oplogSize: 5000, port: 27020, replSet: &quot;zumongous&quot;, rest: &quot;true&quot; }
&lt;p&gt;Fri Jun 28 20:52:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; journal dir=/var/lib/mongo/journal&lt;br/&gt;
Fri Jun 28 20:52:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; recover begin&lt;br/&gt;
Fri Jun 28 20:52:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; recover lsn: 1006869&lt;br/&gt;
Fri Jun 28 20:52:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; recover /var/lib/mongo/journal/j._3&lt;br/&gt;
Fri Jun 28 20:52:45 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; recover skipping application of section seq:408618 &amp;lt; lsn:1006869&lt;br/&gt;
Fri Jun 28 20:52:46 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; recover skipping application of section seq:468234 &amp;lt; lsn:1006869&lt;br/&gt;
Fri Jun 28 20:52:46 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; recover skipping application of section seq:587600 &amp;lt; lsn:1006869&lt;br/&gt;
Fri Jun 28 20:52:46 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; recover /var/lib/mongo/journal/j._4&lt;br/&gt;
Fri Jun 28 20:52:46 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; recover skipping application of section seq:647542 &amp;lt; lsn:1006869&lt;br/&gt;
Fri Jun 28 20:52:46 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; recover skipping application of section seq:707486 &amp;lt; lsn:1006869&lt;br/&gt;
Fri Jun 28 20:52:46 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; recover skipping application of section seq:767346 &amp;lt; lsn:1006869&lt;br/&gt;
Fri Jun 28 20:52:46 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; recover skipping application of section seq:827234 &amp;lt; lsn:1006869&lt;br/&gt;
Fri Jun 28 20:52:46 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; recover skipping application of section seq:887019 &amp;lt; lsn:1006869&lt;br/&gt;
&lt;span class=&quot;error&quot;&gt;&amp;#91;root@zuemongo5 mongo&amp;#93;&lt;/span&gt;# &lt;/p&gt;


</comment>
                            <comment id="370975" author="tlaramee" created="Sun, 30 Jun 2013 05:01:33 +0000"  >&lt;p&gt;This is zuemongo2 ... it&apos;s currently running 2.2.5 and i think it should be running 2.2.1.  Note that there are two restarts in the log .. I only initiated one of them (I suspect the latter).&lt;/p&gt;

&lt;p&gt;Restart #1: 2.2.5&lt;br/&gt;
Restart #2: 2.2.1&lt;/p&gt;

&lt;p&gt;Question: Why is the final version info 2.2.5? The active daemon is 2.2.1. I&apos;m pretty sure that the active daemon is 2.2.1 and that the reporting of the version # is wrong.&lt;/p&gt;




&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;root@zuemongo2 mongo&amp;#93;&lt;/span&gt;#  grep -A 20 &quot;SERVER RESTARTED&quot; 29 &lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;
		&lt;ul&gt;
			&lt;li&gt;
			&lt;ul&gt;
				&lt;li&gt;
				&lt;ul&gt;
					&lt;li&gt;SERVER RESTARTED *****&lt;/li&gt;
				&lt;/ul&gt;
				&lt;/li&gt;
			&lt;/ul&gt;
			&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;Fri Jun 28 20:49:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; MongoDB starting : pid=3303 port=27019 dbpath=/var/lib/mongo 64-bit host=zuemongo2.pubip.peer1.net&lt;br/&gt;
Fri Jun 28 20:49:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; db version v2.2.5, pdfile version 4.5&lt;br/&gt;
Fri Jun 28 20:49:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; git version: 14d8c4d1eb320ab10c6956f6e4b52263249bc0b4&lt;br/&gt;
Fri Jun 28 20:49:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; build info: Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49&lt;br/&gt;
Fri Jun 28 20:49:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; options: &lt;/p&gt;
{ config: &quot;/etc/mongod.conf&quot;, dbpath: &quot;/var/lib/mongo&quot;, fork: &quot;true&quot;, logappend: &quot;true&quot;, logpath: &quot;/var/log/mongo/mongod.log&quot;, oplogSize: 5000, port: 27019, replSet: &quot;zumongous&quot;, rest: &quot;true&quot; }
&lt;p&gt;Fri Jun 28 20:49:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; journal dir=/var/lib/mongo/journal&lt;br/&gt;
Fri Jun 28 20:49:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; recover : no journal files present, no recovery needed&lt;br/&gt;
Fri Jun 28 20:49:04 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster=true 10.64&lt;br/&gt;
Fri Jun 28 20:49:05 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster=true 9.54&lt;br/&gt;
Fri Jun 28 20:49:06 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster=true 11.2&lt;br/&gt;
Fri Jun 28 20:49:06 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster check took 3.757 secs&lt;br/&gt;
Fri Jun 28 20:49:06 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocating a journal file /var/lib/mongo/journal/prealloc.0&lt;br/&gt;
Fri Jun 28 20:49:16 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocating a journal file /var/lib/mongo/journal/prealloc.1&lt;br/&gt;
Fri Jun 28 20:49:26 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocating a journal file /var/lib/mongo/journal/prealloc.2&lt;br/&gt;
Fri Jun 28 20:49:36 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; waiting for connections on port 27019&lt;br/&gt;
Fri Jun 28 20:49:36 &lt;span class=&quot;error&quot;&gt;&amp;#91;websvr&amp;#93;&lt;/span&gt; admin web console waiting for connections on port 28019&lt;br/&gt;
Fri Jun 28 20:49:36 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.137:49116 #1 (1 connection now open)&lt;br/&gt;
Fri Jun 28 20:49:36 &lt;span class=&quot;error&quot;&gt;&amp;#91;rsStart&amp;#93;&lt;/span&gt; replSet can&apos;t get local.system.replset config from self or any seed (EMPTYCONFIG)&lt;br/&gt;
&amp;#8211;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;
		&lt;ul&gt;
			&lt;li&gt;
			&lt;ul&gt;
				&lt;li&gt;
				&lt;ul&gt;
					&lt;li&gt;SERVER RESTARTED *****&lt;/li&gt;
				&lt;/ul&gt;
				&lt;/li&gt;
			&lt;/ul&gt;
			&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;Fri Jun 28 20:49:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; MongoDB starting : pid=17229 port=27019 dbpath=/var/lib/mongo 64-bit host=zuemongo2.pubip.peer1.net&lt;br/&gt;
Fri Jun 28 20:49:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; db version v2.2.1, pdfile version 4.5&lt;br/&gt;
Fri Jun 28 20:49:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; git version: d6764bf8dfe0685521b8bc7b98fd1fab8cfeb5ae&lt;br/&gt;
Fri Jun 28 20:49:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; build info: Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49&lt;br/&gt;
Fri Jun 28 20:49:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; options: &lt;/p&gt;
{ config: &quot;/etc/mongod.conf&quot;, dbpath: &quot;/var/lib/mongo&quot;, fork: &quot;true&quot;, logappend: &quot;true&quot;, logpath: &quot;/var/log/mongo/mongod.log&quot;, oplogSize: 5000, port: 27019, replSet: &quot;zumongous&quot;, rest: &quot;true&quot; }
&lt;p&gt;Fri Jun 28 20:49:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.137:58435 #13596 (208 connections now open)&lt;br/&gt;
Fri Jun 28 20:49:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; exception in initAndListen: 10310 Unable to lock file: /var/lib/mongo/mongod.lock. Is a mongod instance already running?, terminating&lt;br/&gt;
Fri Jun 28 20:49:49 dbexit: &lt;br/&gt;
Fri Jun 28 20:49:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; shutdown: going to close listening sockets...&lt;br/&gt;
Fri Jun 28 20:49:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; shutdown: going to flush diaglog...&lt;br/&gt;
Fri Jun 28 20:49:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; shutdown: going to close sockets...&lt;br/&gt;
Fri Jun 28 20:49:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; shutdown: waiting for fs preallocator...&lt;br/&gt;
Fri Jun 28 20:49:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; shutdown: lock for final commit...&lt;br/&gt;
Fri Jun 28 20:49:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; shutdown: final commit...&lt;br/&gt;
Fri Jun 28 20:49:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; shutdown: closing all files...&lt;br/&gt;
Fri Jun 28 20:49:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; closeAllFiles() finished&lt;br/&gt;
Fri Jun 28 20:49:49 dbexit: really exiting now&lt;br/&gt;
Fri Jun 28 20:49:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.137:58438 #13597 (209 connections now open)&lt;/p&gt;

</comment>
                            <comment id="370973" author="tlaramee" created="Sun, 30 Jun 2013 04:57:27 +0000"  >&lt;p&gt;The maintenance I did was on 6/28 at approx 8pm pacific time:&lt;/p&gt;

&lt;p&gt;This is zuemongo1 .. which is v2.2.1, which is what I expect: &lt;/p&gt;



&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;root@zuemongo1 mongo&amp;#93;&lt;/span&gt;# grep -A 20 &quot;SERVER RESTARTED&quot; 29 &lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;
		&lt;ul&gt;
			&lt;li&gt;
			&lt;ul&gt;
				&lt;li&gt;
				&lt;ul&gt;
					&lt;li&gt;SERVER RESTARTED *****&lt;/li&gt;
				&lt;/ul&gt;
				&lt;/li&gt;
			&lt;/ul&gt;
			&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;Fri Jun 28 21:22:58 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; MongoDB starting : pid=12341 port=27017 dbpath=/var/lib/mongo 64-bit host=zuemongo1.pubip.peer1.net&lt;br/&gt;
Fri Jun 28 21:22:58 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; &lt;br/&gt;
Fri Jun 28 21:22:58 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; ** WARNING: /proc/sys/vm/zone_reclaim_mode is 1&lt;br/&gt;
Fri Jun 28 21:22:58 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; **          We suggest setting it to 0&lt;br/&gt;
Fri Jun 28 21:22:58 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; **          &lt;a href=&quot;http://www.kernel.org/doc/Documentation/sysctl/vm.txt&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://www.kernel.org/doc/Documentation/sysctl/vm.txt&lt;/a&gt;&lt;br/&gt;
Fri Jun 28 21:22:58 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; db version v2.2.1, pdfile version 4.5&lt;br/&gt;
Fri Jun 28 21:22:58 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; git version: d6764bf8dfe0685521b8bc7b98fd1fab8cfeb5ae&lt;br/&gt;
Fri Jun 28 21:22:58 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; build info: Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49&lt;br/&gt;
Fri Jun 28 21:22:58 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; options: &lt;/p&gt;
{ config: &quot;/etc/mongod.conf&quot;, dbpath: &quot;/var/lib/mongo&quot;, fork: &quot;true&quot;, logappend: &quot;true&quot;, logpath: &quot;/var/log/mongo/mongod.log&quot;, oplogSize: 5000, replSet: &quot;zumongous&quot;, rest: &quot;true&quot; }
&lt;p&gt;Fri Jun 28 21:22:58 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; journal dir=/var/lib/mongo/journal&lt;br/&gt;
Fri Jun 28 21:22:58 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; recover : no journal files present, no recovery needed&lt;br/&gt;
Fri Jun 28 21:22:59 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster=true 8.42&lt;br/&gt;
Fri Jun 28 21:22:59 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster=true 8.2&lt;br/&gt;
Fri Jun 28 21:23:01 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster=true 7.6&lt;br/&gt;
Fri Jun 28 21:23:01 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster check took 3.107 secs&lt;br/&gt;
Fri Jun 28 21:23:01 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocating a journal file /var/lib/mongo/journal/prealloc.0&lt;br/&gt;
Fri Jun 28 21:23:12 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocating a journal file /var/lib/mongo/journal/prealloc.1&lt;br/&gt;
Fri Jun 28 21:23:21 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocating a journal file /var/lib/mongo/journal/prealloc.2&lt;/p&gt;
</comment>
                            <comment id="370971" author="tlaramee" created="Sun, 30 Jun 2013 04:55:54 +0000"  >&lt;p&gt;Please re-open this ticket.&lt;/p&gt;</comment>
                            <comment id="370970" author="tlaramee" created="Sun, 30 Jun 2013 04:55:34 +0000"  >&lt;p&gt;I take it all back ... the plot thickens / this is unresolved.&lt;/p&gt;

&lt;p&gt;Please re-open this ticket.&lt;/p&gt;

&lt;p&gt;Here are the &quot;SERVER RESTARTS&quot; from the logs for all 5 servers in this replica set.&lt;/p&gt;

&lt;p&gt;Before I continue, I think I found a bug in the server &amp;#8211; you&apos;ll see this on mongo5 in the log. It took several restarts to get this server to connect back to the replica set... it had a very odd error in the logs - it couldn&apos;t determine who the PRI was, not the SEC, and so it got stuck - all i saw in the logs was an error every ~10 seconds telling me that it couldn&apos;t connect to the replica set... so i ended up doing a &quot;kill -kill&quot; on it and restarting. &lt;/p&gt;

&lt;p&gt;There were ~3 daemons spawned at that point - the only one i explicitly spawned was via a single &quot;/etc/init.d/mongod start&quot; ... the addt&apos;l daemons came via mongod itself (meaning I did not start them).&lt;/p&gt;

&lt;p&gt;In the next comment, I will post the server logs indicting that I explicitly started the daemons w/ v 2.2.1 for all servers - and that this is the last server restart for all servers.&lt;/p&gt;





</comment>
                            <comment id="370933" author="tlaramee" created="Sun, 30 Jun 2013 02:29:12 +0000"  >&lt;p&gt;PS: feel free to close this ticket - thanks everyone for your assistance.&lt;/p&gt;</comment>
                            <comment id="370930" author="tlaramee" created="Sun, 30 Jun 2013 02:19:22 +0000"  >&lt;p&gt;hi Eliot:&lt;/p&gt;

&lt;p&gt;great idea. the log shows that this is my error. this is zuemongo2, which is reporting &lt;br/&gt;
that it&apos;s running 2.2.5. here&apos;s the 1st ~20 lines of the log following the daemon bounce.&lt;br/&gt;
i&apos;m not sure where i went wrong, but it&apos;s clear that i need to get mongo1 &amp;amp; 5 upgraded &lt;br/&gt;
to 2.2.5 ASAP.&lt;/p&gt;

&lt;p&gt;--tom&lt;/p&gt;




&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;
		&lt;ul&gt;
			&lt;li&gt;
			&lt;ul&gt;
				&lt;li&gt;
				&lt;ul&gt;
					&lt;li&gt;SERVER RESTARTED *****&lt;/li&gt;
				&lt;/ul&gt;
				&lt;/li&gt;
			&lt;/ul&gt;
			&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;Fri Jun 28 20:49:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; MongoDB starting : pid=3303 port=27019 dbpath=/var/lib/mongo 64-bit host=zuemongo2.pubip.peer1.net&lt;br/&gt;
Fri Jun 28 20:49:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; db version v2.2.5, pdfile version 4.5&lt;br/&gt;
Fri Jun 28 20:49:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; git version: 14d8c4d1eb320ab10c6956f6e4b52263249bc0b4&lt;br/&gt;
Fri Jun 28 20:49:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; build info: Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49&lt;br/&gt;
Fri Jun 28 20:49:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; options: &lt;/p&gt;
{ config: &quot;/etc/mongod.conf&quot;, dbpath: &quot;/var/lib/mongo&quot;, fork: &quot;true&quot;, logappend: &quot;true&quot;, logpath: &quot;/var/log/mongo/mongod.log&quot;, oplogSize: 5000, port: 27019, replSet: &quot;zumongous&quot;, rest: &quot;true&quot; }
&lt;p&gt;Fri Jun 28 20:49:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; journal dir=/var/lib/mongo/journal&lt;br/&gt;
Fri Jun 28 20:49:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; recover : no journal files present, no recovery needed&lt;br/&gt;
Fri Jun 28 20:49:04 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster=true 10.64&lt;br/&gt;
Fri Jun 28 20:49:05 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster=true 9.54&lt;br/&gt;
Fri Jun 28 20:49:06 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster=true 11.2&lt;br/&gt;
Fri Jun 28 20:49:06 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocateIsFaster check took 3.757 secs&lt;br/&gt;
Fri Jun 28 20:49:06 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocating a journal file /var/lib/mongo/journal/prealloc.0&lt;br/&gt;
Fri Jun 28 20:49:16 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocating a journal file /var/lib/mongo/journal/prealloc.1&lt;br/&gt;
Fri Jun 28 20:49:26 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; preallocating a journal file /var/lib/mongo/journal/prealloc.2&lt;br/&gt;
Fri Jun 28 20:49:36 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; waiting for connections on port 27019&lt;br/&gt;
Fri Jun 28 20:49:36 &lt;span class=&quot;error&quot;&gt;&amp;#91;websvr&amp;#93;&lt;/span&gt; admin web console waiting for connections on port 28019&lt;br/&gt;
Fri Jun 28 20:49:36 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.137:49116 #1 (1 connection now open)&lt;br/&gt;
Fri Jun 28 20:49:36 &lt;span class=&quot;error&quot;&gt;&amp;#91;rsStart&amp;#93;&lt;/span&gt; replSet can&apos;t get local.system.replset config from self or any seed (EMPTYCONFIG)&lt;br/&gt;
Fri Jun 28 20:49:36 &lt;span class=&quot;error&quot;&gt;&amp;#91;rsStart&amp;#93;&lt;/span&gt; replSet info you may need to run replSetInitiate &amp;#8211; rs.initiate() in the shell &amp;#8211; if that is not already done&lt;br/&gt;
Fri Jun 28 20:49:36 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1&amp;#93;&lt;/span&gt; end connection 172.16.0.137:49116 (0 connections now open)&lt;br/&gt;
Fri Jun 28 20:49:36 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.137:49117 #2 (1 connection now open)&lt;br/&gt;
Fri Jun 28 20:49:36 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn2&amp;#93;&lt;/span&gt; end connection 172.16.0.137:49117 (0 connections now open)&lt;br/&gt;
Fri Jun 28 20:49:36 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.137:49121 #3 (1 connection now open)&lt;br/&gt;
Fri Jun 28 20:49:36 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn3&amp;#93;&lt;/span&gt; end connection 172.16.0.137:49121 (0 connections now open)&lt;br/&gt;
Fri Jun 28 20:49:36 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 172.16.0.137:49129 #4 (1 connection now open)&lt;/p&gt;

</comment>
                            <comment id="370926" author="eliot" created="Sun, 30 Jun 2013 02:06:36 +0000"  >&lt;p&gt;It can&apos;t report itself wrong, its built into the binary itself.&lt;br/&gt;
So however that binary was started, it was with 2.2.5.&lt;br/&gt;
I would look at:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;ps&lt;/li&gt;
	&lt;li&gt;/proc/&amp;lt;mongo pid&amp;gt;/exe&lt;br/&gt;
For some hints.&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="370839" author="tlaramee" created="Sat, 29 Jun 2013 20:29:35 +0000"  >&lt;p&gt;Looking at just mongo2, which indicates it&apos;s running 2.2.5 via the buildInfo command:&lt;/p&gt;

&lt;p&gt;$ cd /usr/bin&lt;/p&gt;

&lt;p&gt;$ ls -la mongod*&lt;br/&gt;
lrwxrwxrwx 1 root root       12 Jun 28 20:49 mongod -&amp;gt; mongod.2.2.1&lt;br/&gt;
-rwxr-xr-x 1 root root  9322480 Apr 11  2012 mongod.2.0.2&lt;br/&gt;
-rwxr-xr-x 1 root root 11348288 Oct 30  2012 mongod.2.2.1&lt;br/&gt;
-rwxr-xr-x 1 root root 11454224 Jun 28 11:54 mongod.2.2.5&lt;/p&gt;

&lt;p&gt;$ ./mongod --version&lt;br/&gt;
db version v2.2.1, pdfile version 4.5&lt;br/&gt;
Sat Jun 29 13:26:32 git version: d6764bf8dfe0685521b8bc7b98fd1fab8cfeb5ae&lt;/p&gt;



&lt;p&gt;My question is: how is it possible for this server to be reporting that it&apos;s running 2.2.5 when the binary is clearly 2.2.1? At no point when mongod was running was the 2.2.5 binary the one that was sym linked. &lt;/p&gt;

&lt;p&gt;Also note that the mongo shell for each server is 2.2.1, which is what i&apos;d expect.&lt;/p&gt;

&lt;p&gt;Note that the mongod.2.2.1 binary is a different size than the mongo2.2.5 binary - so they are different.&lt;/p&gt;

&lt;p&gt;$ ./mongod.2.2.1 --version&lt;br/&gt;
db version v2.2.1, pdfile version 4.5&lt;br/&gt;
Sat Jun 29 13:29:16 git version: d6764bf8dfe0685521b8bc7b98fd1fab8cfeb5ae&lt;/p&gt;

&lt;p&gt;$ ./mongod.2.2.5 --version&lt;br/&gt;
db version v2.2.5, pdfile version 4.5&lt;br/&gt;
Sat Jun 29 13:29:19 git version: 14d8c4d1eb320ab10c6956f6e4b52263249bc0b4&lt;/p&gt;




&lt;p&gt;$ ls -la mongo*&lt;br/&gt;
lrwxrwxrwx 1 root root       11 Jun 28 20:49 mongo -&amp;gt; mongo.2.2.1&lt;br/&gt;
-rwxr-xr-x 1 root root  3077272 Apr 11  2012 mongo.2.0.2&lt;br/&gt;
-rwxr-xr-x 1 root root  4712840 Oct 30  2012 mongo.2.2.1&lt;br/&gt;
-rwxr-xr-x 1 root root  4730616 Jun 28 11:54 mongo.2.2.5&lt;/p&gt;


</comment>
                            <comment id="370837" author="tlaramee" created="Sat, 29 Jun 2013 20:25:15 +0000"  >&lt;p&gt;Here is the buildinfo for each server ... my question will follow in the next comment:&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;t@zuemongo1 ~&amp;#93;&lt;/span&gt;$ mongo&lt;br/&gt;
MongoDB shell version: 2.2.1&lt;br/&gt;
connecting to: test&lt;br/&gt;
zumongous:PRIMARY&amp;gt; db.serverBuildInfo()&lt;br/&gt;
{&lt;br/&gt;
	&quot;version&quot; : &quot;2.2.1&quot;,&lt;br/&gt;
	&quot;gitVersion&quot; : &quot;d6764bf8dfe0685521b8bc7b98fd1fab8cfeb5ae&quot;,&lt;br/&gt;
	&quot;sysInfo&quot; : &quot;Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49&quot;,&lt;br/&gt;
	&quot;versionArray&quot; : [&lt;br/&gt;
		2,&lt;br/&gt;
		2,&lt;br/&gt;
		1,&lt;br/&gt;
		0&lt;br/&gt;
	],&lt;br/&gt;
	&quot;bits&quot; : 64,&lt;br/&gt;
	&quot;debug&quot; : false,&lt;br/&gt;
	&quot;maxBsonObjectSize&quot; : 16777216,&lt;br/&gt;
	&quot;ok&quot; : 1&lt;br/&gt;
}&lt;/p&gt;


&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;t@zuemongo2 ~&amp;#93;&lt;/span&gt;$ mongo&lt;br/&gt;
MongoDB shell version: 2.2.1&lt;br/&gt;
connecting to: 127.0.0.1:27019/test&lt;br/&gt;
zumongous:SECONDARY&amp;gt; db.serverBuildInfo()&lt;br/&gt;
{&lt;br/&gt;
	&quot;version&quot; : &quot;2.2.5&quot;,&lt;br/&gt;
	&quot;gitVersion&quot; : &quot;14d8c4d1eb320ab10c6956f6e4b52263249bc0b4&quot;,&lt;br/&gt;
	&quot;sysInfo&quot; : &quot;Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49&quot;,&lt;br/&gt;
	&quot;versionArray&quot; : [&lt;br/&gt;
		2,&lt;br/&gt;
		2,&lt;br/&gt;
		5,&lt;br/&gt;
		0&lt;br/&gt;
	],&lt;br/&gt;
	&quot;bits&quot; : 64,&lt;br/&gt;
	&quot;debug&quot; : false,&lt;br/&gt;
	&quot;maxBsonObjectSize&quot; : 16777216,&lt;br/&gt;
	&quot;ok&quot; : 1&lt;br/&gt;
}&lt;/p&gt;


&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;t@zuemongo5 ~&amp;#93;&lt;/span&gt;$ mongo 127.0.0.1:27020&lt;br/&gt;
MongoDB shell version: 2.2.1&lt;br/&gt;
connecting to: 127.0.0.1:27020/test&lt;br/&gt;
zumongous:SECONDARY&amp;gt; db.serverBuildInfo()&lt;br/&gt;
{&lt;br/&gt;
	&quot;version&quot; : &quot;2.2.1&quot;,&lt;br/&gt;
	&quot;gitVersion&quot; : &quot;d6764bf8dfe0685521b8bc7b98fd1fab8cfeb5ae&quot;,&lt;br/&gt;
	&quot;sysInfo&quot; : &quot;Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49&quot;,&lt;br/&gt;
	&quot;versionArray&quot; : [&lt;br/&gt;
		2,&lt;br/&gt;
		2,&lt;br/&gt;
		1,&lt;br/&gt;
		0&lt;br/&gt;
	],&lt;br/&gt;
	&quot;bits&quot; : 64,&lt;br/&gt;
	&quot;debug&quot; : false,&lt;br/&gt;
	&quot;maxBsonObjectSize&quot; : 16777216,&lt;br/&gt;
	&quot;ok&quot; : 1&lt;br/&gt;
}&lt;/p&gt;


&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;t@zuemongo6 ~&amp;#93;&lt;/span&gt;$ mongo 127.0.0.1:27021&lt;br/&gt;
MongoDB shell version: 2.2.1&lt;br/&gt;
connecting to: 127.0.0.1:27021/test&lt;br/&gt;
zumongous:SECONDARY&amp;gt; db.serverBuildInfo()&lt;br/&gt;
{&lt;br/&gt;
	&quot;version&quot; : &quot;2.2.5&quot;,&lt;br/&gt;
	&quot;gitVersion&quot; : &quot;14d8c4d1eb320ab10c6956f6e4b52263249bc0b4&quot;,&lt;br/&gt;
	&quot;sysInfo&quot; : &quot;Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49&quot;,&lt;br/&gt;
	&quot;versionArray&quot; : [&lt;br/&gt;
		2,&lt;br/&gt;
		2,&lt;br/&gt;
		5,&lt;br/&gt;
		0&lt;br/&gt;
	],&lt;br/&gt;
	&quot;bits&quot; : 64,&lt;br/&gt;
	&quot;debug&quot; : false,&lt;br/&gt;
	&quot;maxBsonObjectSize&quot; : 16777216,&lt;br/&gt;
	&quot;ok&quot; : 1&lt;br/&gt;
}&lt;/p&gt;


&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;t@zuemongo7 ~&amp;#93;&lt;/span&gt;$ mongo 127.0.0.1:27022&lt;br/&gt;
MongoDB shell version: 2.2.1&lt;br/&gt;
connecting to: 127.0.0.1:27022/test&lt;br/&gt;
zumongous:SECONDARY&amp;gt; db.serverBuildInfo()&lt;br/&gt;
{&lt;br/&gt;
	&quot;version&quot; : &quot;2.2.5&quot;,&lt;br/&gt;
	&quot;gitVersion&quot; : &quot;14d8c4d1eb320ab10c6956f6e4b52263249bc0b4&quot;,&lt;br/&gt;
	&quot;sysInfo&quot; : &quot;Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49&quot;,&lt;br/&gt;
	&quot;versionArray&quot; : [&lt;br/&gt;
		2,&lt;br/&gt;
		2,&lt;br/&gt;
		5,&lt;br/&gt;
		0&lt;br/&gt;
	],&lt;br/&gt;
	&quot;bits&quot; : 64,&lt;br/&gt;
	&quot;debug&quot; : false,&lt;br/&gt;
	&quot;maxBsonObjectSize&quot; : 16777216,&lt;br/&gt;
	&quot;ok&quot; : 1&lt;br/&gt;
}&lt;/p&gt;</comment>
                            <comment id="370814" author="dan@10gen.com" created="Sat, 29 Jun 2013 19:12:18 +0000"  >&lt;p&gt;The mms agent gets the build info by running the &quot;buildinfo&quot; command on the host.  You can login to the host in question and run:&lt;/p&gt;
&lt;p/&gt;
&lt;div id=&quot;syntaxplugin&quot; class=&quot;syntaxplugin&quot; style=&quot;border: 1px dashed #bbb; border-radius: 5px !important; overflow: auto; max-height: 30em;&quot;&gt;
&lt;table cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; width=&quot;100%&quot; style=&quot;font-size: 1em; line-height: 1.4em !important; font-weight: normal; font-style: normal; color: black;&quot;&gt;
		&lt;tbody &gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;  margin-top: 10px;   margin-bottom: 10px;  width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;db.serverBuildInfo()&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
			&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;p/&gt;

&lt;p&gt;You should see the same information there as you do in the &quot;Last Ping&quot; tab in the MMS host details.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>21.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Sat, 29 Jun 2013 19:12:18 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        10 years, 33 weeks, 2 days ago
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18254" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Dependencies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[]]></customfieldvalue>


                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10057" key="com.atlassian.jira.toolkit:lastusercommented">
                        <customfieldname>Last comment by Customer</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>true</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10056" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last commenter</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>ramon.fernandez@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            10 years, 33 weeks, 2 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10000" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Old_Backport</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10000"><![CDATA[No]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>dan@mongodb.com</customfieldvalue>
            <customfieldvalue>eliot</customfieldvalue>
            <customfieldvalue>jhn</customfieldvalue>
            <customfieldvalue>tlaramee</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrmonb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hrrf6v:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>73845</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_23361" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Requested By</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10053" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>Time In Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_22870" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Triagers</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_14350" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>serverRank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrlm3r:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>