<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 03:12:24 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-6682] Can&apos;t write to ANY collection in the MongoDB instance</title>
                <link>https://jira.mongodb.org/browse/SERVER-6682</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;We are trying to write to any collection in our database and are unable to do so. Log file shows no entries. Even trying to change log level to 2 does not work. The query just continues to run (active, but no result). &lt;/p&gt;

&lt;p&gt;We&apos;ve been using this database for a long time and have never encountered this issue.&lt;/p&gt;</description>
                <environment></environment>
        <key id="46013">SERVER-6682</key>
            <summary>Can&apos;t write to ANY collection in the MongoDB instance</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</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="benjamin.becker">Ben Becker</assignee>
                                    <reporter username="eugene@magazineradar.com">Eugene Shustef</reporter>
                        <labels>
                    </labels>
                <created>Wed, 1 Aug 2012 18:22:27 +0000</created>
                <updated>Fri, 8 Mar 2013 15:55:57 +0000</updated>
                            <resolved>Fri, 28 Sep 2012 03:21:48 +0000</resolved>
                                    <version>2.0.6</version>
                                                                        <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="161868" author="benjamin.becker" created="Sat, 8 Sep 2012 01:01:19 +0000"  >&lt;p&gt;Hi Eugene,&lt;/p&gt;

&lt;p&gt;I just wanted to follow up to see if you have encountered any similar issues since upgrading to v2.0.7-rc1.  Also, were you able to determine if any system events were logged when this was encountered (e.g. due to low disk space)?&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Ben&lt;/p&gt;</comment>
                            <comment id="150084" author="benjamin.becker" created="Thu, 2 Aug 2012 22:00:33 +0000"  >&lt;p&gt;Thanks, that makes sense and seems to line up with &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-5663&quot; title=&quot;Private pages accumulate in Windows RAM and page file when journaling&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-5663&quot;&gt;&lt;del&gt;SERVER-5663&lt;/del&gt;&lt;/a&gt;.  We&apos;ve seen VirtualProtect fail under similar circumstances &amp;#8211; usually a system warning message similar to the following will be present in the event viewer:&lt;/p&gt;

&lt;p&gt;&lt;tt&gt;&quot;Your system is low on virtual memory. Windows is increasing the size of your virtual memory paging file. During this process, memory requests for some applications may be denied&quot;&lt;/tt&gt;&lt;/p&gt;

&lt;p&gt;I believe that in most cases the mongod.exe process will start responding again once there is more room in the commit pool, so I&apos;m curious if there were any other related messages from the OS at the time of the VirtualProtect failure.&lt;/p&gt;</comment>
                            <comment id="150077" author="eugene@magazineradar.com" created="Thu, 2 Aug 2012 21:47:16 +0000"  >&lt;p&gt;I think we figured out that the drive where the service resides had less than 1 GB left (actual mongo files are on a different drive). The page file size is the standard Windows Server size (just over 8 GB). &lt;/p&gt;

&lt;p&gt;BTW, even if you run --nojournal (sp?) option, repair won&apos;t work. I don&apos;t remember the exact message. &lt;/p&gt;</comment>
                            <comment id="150076" author="benjamin.becker" created="Thu, 2 Aug 2012 21:41:59 +0000"  >&lt;p&gt;Hi Eugene,&lt;/p&gt;

&lt;p&gt;If you&apos;re referring to &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-4266&quot; title=&quot;Need to support --repairpath outside of --dbpath with journaling on&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-4266&quot;&gt;&lt;del&gt;SERVER-4266&lt;/del&gt;&lt;/a&gt;, --repairpath should work if disable journaling (which is ok since the journal files were already removed.  If importing to a new replica set is already in progress, then no need to worry about it (sorry I missed you&apos;re previous comment).&lt;/p&gt;

&lt;p&gt;The system events around the time VirtualProtect failed would be very helpful to confirm the root cause.  Any additional details about system settings (e.g. custom page file size, network attached storage, virtualization, etc.) would also be very helpful.&lt;/p&gt;</comment>
                            <comment id="150063" author="eugene@magazineradar.com" created="Thu, 2 Aug 2012 21:18:52 +0000"  >&lt;p&gt;I didn&apos;t have enough space for the repair option on the same drive. Couldn&apos;t use --repairpath because we are using journaling and apparently you can&apos;t repair using a different drive when journaling is turned on. There was a jira case from Nov. 2011 talking about this.&lt;/p&gt;</comment>
                            <comment id="149917" author="benjamin.becker" created="Thu, 2 Aug 2012 16:38:10 +0000"  >&lt;p&gt;Hi Eugene,&lt;/p&gt;

&lt;p&gt;To get back up and running, I would recommend &lt;a href=&quot;http://www.mongodb.org/display/DOCS/Durability+and+Repair&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;repairing the database&lt;/a&gt;.  For future reference, it would be best not to manually remove the journal files.&lt;/p&gt;

&lt;p&gt;If time permits, before running the repair, could you run the &apos;db.foo.validate(&lt;/p&gt;
{full:true}
&lt;p&gt;)&apos; command on each collection and paste the output here?  Also, could you check in the event viewer for any system events that may have occurred around the time of this failure?&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Ben&lt;/p&gt;</comment>
                            <comment id="149911" author="eugene@magazineradar.com" created="Thu, 2 Aug 2012 16:26:04 +0000"  >&lt;p&gt;FYI... we had to take the old db offline. Created a new replica set (all members running 2.0.7 rc1) with a brand new database. Just going to migrate the data out of the old database since we can still read. Would still love to find out what happened.&lt;/p&gt;</comment>
                            <comment id="149594" author="eugene@magazineradar.com" created="Wed, 1 Aug 2012 19:30:36 +0000"  >&lt;p&gt;So, the question is how to get our current database back up.&lt;/p&gt;</comment>
                            <comment id="149593" author="tad" created="Wed, 1 Aug 2012 19:27:34 +0000"  >&lt;p&gt;The first problem you hit is that in version 2.0.6, mongod.exe consumes page file space when journaling is enabled (as it is by default for 64-bit version).  A second problem is that when mongod.exe runs out of page file space it really should just shut down, since it can&apos;t safely maintain the journal any more, but version 2.0.6 keeps running anyway.&lt;/p&gt;

&lt;p&gt;Both of these problems are fixed in 2.0.7, which is currently in release candidate state (2.0.7-rc1 is the current one a this moment).  The first problem is documented in &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-5663&quot; title=&quot;Private pages accumulate in Windows RAM and page file when journaling&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-5663&quot;&gt;&lt;del&gt;SERVER-5663&lt;/del&gt;&lt;/a&gt; as Andy said; the second problem (shut down if we run out of page file space) is documented in &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-6132&quot; title=&quot;a failure inside MakeChunkWritable should call abort/fassert instead of assert&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-6132&quot;&gt;&lt;del&gt;SERVER-6132&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="149592" author="eugene@magazineradar.com" created="Wed, 1 Aug 2012 19:24:20 +0000"  >&lt;p&gt;We have upgraded to 2.0.7.  We believe the problem is writing to new records, because are able to update existing old records.  This is most likely caused by corruption in the db file that was created earlier today by the database.  &lt;br/&gt;
We have two 2-gig files that were created at the exact same time, right around the time that this issue began.&lt;br/&gt;
Is there a way to repair a file?  Can we just delete the latest 2-gig files?&lt;/p&gt;</comment>
                            <comment id="149585" author="schwerin" created="Wed, 1 Aug 2012 19:03:53 +0000"  >&lt;p&gt;This looks like an instance of &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-5663&quot; title=&quot;Private pages accumulate in Windows RAM and page file when journaling&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-5663&quot;&gt;&lt;del&gt;SERVER-5663&lt;/del&gt;&lt;/a&gt;, which is resolved in Mongo version 2.0.7.&lt;/p&gt;</comment>
                            <comment id="149583" author="eugene@magazineradar.com" created="Wed, 1 Aug 2012 18:53:53 +0000"  >&lt;p&gt;It&apos;s version 2.0.6. &lt;/p&gt;

&lt;p&gt;Here is the latest log content since restart:&lt;/p&gt;


&lt;p&gt;Wed Aug 01 19:49:53 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; MongoDB starting : pid=1632 port=27017 dbpath=d:\mongo 64-bit host=ip-0A32EB4B&lt;br/&gt;
Wed Aug 01 19:49:53 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; db version v2.0.6, pdfile version 4.5&lt;br/&gt;
Wed Aug 01 19:49:53 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; git version: e1c0cbc25863f6356aa4e31375add7bb49fb05bc&lt;br/&gt;
Wed Aug 01 19:49:53 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; build info: windows sys.getwindowsversion(major=6, minor=1, build=7601, platform=2, service_pack=&apos;Service Pack 1&apos;) BOOST_LIB_VERSION=1_42&lt;br/&gt;
Wed Aug 01 19:49:53 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; options: &lt;/p&gt;
{ dbpath: &quot;d:\mongo&quot;, logpath: &quot;d:\mongo\log\mongodb.log&quot;, service: true }
&lt;p&gt;Wed Aug 01 19:49:53 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; journal dir=d:/mongo/journal&lt;br/&gt;
Wed Aug 01 19:49:53 &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;
Wed Aug 01 19:49:53 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; waiting for connections on port 27017&lt;br/&gt;
Wed Aug 01 19:49:53 &lt;span class=&quot;error&quot;&gt;&amp;#91;websvr&amp;#93;&lt;/span&gt; admin web console waiting for connections on port 28017&lt;br/&gt;
Wed Aug 01 19:49:58 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 98.113.167.34:62402 #1&lt;br/&gt;
Wed Aug 01 19:50:01 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 127.0.0.1:49177 #2&lt;br/&gt;
Wed Aug 01 19:50:01 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from 98.113.167.34:42947 #3&lt;br/&gt;
Wed Aug 01 19:50:02 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1&amp;#93;&lt;/span&gt; end connection 98.113.167.34:62402&lt;br/&gt;
Wed Aug 01 19:50:02 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn3&amp;#93;&lt;/span&gt; end connection 98.113.167.34:42947&lt;/p&gt;


&lt;p&gt;We also tried to delete the journal folder and re-install the MongoDB service. We are running on Windows Server 2008.&lt;/p&gt;</comment>
                            <comment id="149580" author="schwerin" created="Wed, 1 Aug 2012 18:48:03 +0000"  >&lt;p&gt;@Eugene, can you supply version information about the version of Mongo you&apos;re using?  Attach mongo.log files?&lt;/p&gt;</comment>
                            <comment id="149575" author="eugene@magazineradar.com" created="Wed, 1 Aug 2012 18:43:05 +0000"  >&lt;p&gt;Just noticed that 10-20 minutes prior to when we noticed the issue, we saw this in the log: VirtualProtect failed (mcw) D:/mongo/troidb.136 849284b09a0000 3660000 errno:1455 The paging file is too small for this operation to complete.&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>14.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 1 Aug 2012 18:48:03 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        11 years, 23 weeks, 5 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>ian@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            11 years, 23 weeks, 5 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_10032" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Operating System</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10026"><![CDATA[ALL]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>schwerin@mongodb.com</customfieldvalue>
            <customfieldvalue>benjamin.becker</customfieldvalue>
            <customfieldvalue>eugene@magazineradar.com</customfieldvalue>
            <customfieldvalue>tad</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrnsx3:</customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>8317</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|hrlkz3:</customfieldvalue>

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