The mongodb logs seem to be growing quite large. Even with logrotate, too many saved logs are being kept. This ran the EC2 RHUI's out of space on 2/19/2012. We only have 3-4 GB of space available on the root filesystem for the EC2 RHUI's. The reason for their growth seems to be the repeated logging of 2 messages. First, this log message is repeated several times per second in the log: Sun Feb 19 14:41:04 [conn10470] query pulp_database.packages ntoreturn:1 reslen:2730 nscanned:77430 { $query: { id: "8b3e8a74-e888-4a5d-abef-9cf6bb1f793b" } } nreturned:1 111ms Sun Feb 19 14:41:04 [conn10470] query pulp_database.packages ntoreturn:1 reslen:2195 nscanned:76979 { $query: { id: "d4e909d1-baab-4e9d-b175-b23d8ef35450" } } nreturned:1 152ms Sun Feb 19 14:41:05 [conn10470] query pulp_database.packages ntoreturn:1 reslen:2239 nscanned:76980 { $query: { id: "0141fa16-586f-4c91-b3e2-11f0c5982932" } } nreturned:1 110ms Sun Feb 19 14:41:05 [conn10470] query pulp_database.packages ntoreturn:1 reslen:1433 nscanned:76981 { $query: { id: "0e922213-ccfd-43b1-b381-8dff7854d62b" } } nreturned:1 144ms Sun Feb 19 14:41:05 [conn10472] query pulp_database.packages ntoreturn:1 reslen:856 nscanned:47339 { $query: { id: "34045c2a-78e0-4f31-9a12-0912f71f88b8" } } nreturned:1 103ms Sun Feb 19 14:41:05 [conn10470] query pulp_database.packages ntoreturn:1 reslen:1392 nscanned:76982 { $query: { id: "c2f26c45-3a64-4cbb-b4da-c82848891b6a" } } nreturned:1 150ms Sun Feb 19 14:41:05 [conn10472] query pulp_database.packages ntoreturn:1 reslen:804 nscanned:42253 { $query: { id: "8ce9b221-3567-426b-838d-1c8113e66360" } } nreturned:1 122ms Sun Feb 19 14:41:05 [conn10473] query pulp_database.packages ntoreturn:1 reslen:856 nscanned:47339 { $query: { id: "34045c2a-78e0-4f31-9a12-0912f71f88b8" } } nreturned:1 135ms Sun Feb 19 14:41:05 [conn10471] query pulp_database.packages ntoreturn:1 reslen:2738 nscanned:77429 { $query: { id: "e4eb2546-13c6-4cca-b0c9-f3ec2e3217a9" } } nreturned:1 212ms Sun Feb 19 14:41:05 [conn10473] query pulp_database.packages ntoreturn:1 reslen:804 nscanned:42253 { $query: { id: "8ce9b221-3567-426b-838d-1c8113e66360" } } nreturned:1 166ms Second, there are also lots of messages like this: Sun Feb 19 14:41:13 [conn10470] pulp_database.repos Btree::insert: key too large to index, skipping pulp_database.repos.$packagegroups_-1 2873 { : { mrg-grid: { mandatory_package_names: [ "condor", "mrg-release" ], description: "Red Hat Enterprise MRG Grid packages", repo_defined: true, default: true, display_order: 1024, immutable: true, user_visible: true, translated_name: {}, translated_description: {}, conditional_package_names: {}, default_package_names: {}, optional_package_names: [ "condor-aviary", "wallaby-utils", "python-boto", "wso2-wsf-cpp-devel", "wso2-rampart", "condor-vm-gahp", "ruby-wallaby", "condor-ec2-enhanced-hooks", "ruby-spqr", "spqr-gen", "condor-ec2-enhanced", "libyaml-devel", "wso2-rampart-devel", "condor-classads", "PyYAML", "condor-job-hooks", "wso2-axis2-devel", "condor-wallaby-client", "wso2-wsf-cpp", "wallaby", "python-condorec2e", "wso2-axis2", "condor-wallaby-base-db", "libyaml", "condor-kbdd", "condor-wallaby-tools", "python-condorutils", "python-wallabyclient", "ruby-rhubarb", "ruby-sqlite3", "condor-qmf", "condor-low-latency" ], langonly: null, _id: "mrg-grid", id: "mrg-grid", name: "MRG Grid" }, mrg-management: { mandatory_package_names: [ "cumin" ], description: "Red Hat Enterprise MRG Management packages", repo_defined: true, default: true, display_order: 1024, immutable: true, user_visible: true, translated_name: {}, translated_description: {}, conditional_package_names: {}, default_package_names: {}, optional_package_names: [ "python-psycopg2", "python-psycopg2-doc" ], langonly: null, _id: "mrg-management", id: "mrg-management", name: "MRG Management" }, mrg-messaging: { mandatory_package_names: [ "qpid-cpp-server-store", "qpid-tools", "saslwrapper", "python-saslwrapper", "qpid-cpp-server", "qpid-cpp-server-ssl", "mrg-release", "python-qpid" ], description: "Red Hat Enterprise MRG Messaging packages", repo_defined: true, default: true, display_order: 1024, immutable: true, user_visible: true, translated_name: {}, translated_description: {}, conditional_package_names: {}, default_package_names: [ "rhm-docs", "ruby-saslwrapper", "qpid-cpp-client-devel-docs", "xqilla-devel", "xerces-c-devel", "qpid-cpp-client-devel", "python-qpid-qmf", "qpid-java-common", "qpid-java-client", "xerces-c-doc", "qpid-cpp-server-xml", "xerces-c", "qpid-qmf", "qpid-qmf-devel", "qpid-cpp-client", "qpid-cpp-server-cluster", "sesame", "xqilla", "saslwrapper-devel", "qpid-java-example", "qpid-cpp-client-ssl", "qpid-cpp-server-devel" ], optional_package_names: [ "qpid-cpp-server-rdma", "qpid-dotnet", "qpid-cpp-client-rdma", "python-psycopg2", "qpid-java-jca", "qpid-tests", "ruby-qpid-qmf" ], langonly: null, _id: "mrg-messaging", id: "mrg-messaging", name: "MRG Messaging" } } }
File pulp bug #795435 for the 2nd error.
Is this bug going to be addressed by disabling those 2 kinds of logs?