[SERVER-8413] max_message_size.js fails in auth passthrough suite Created: 30/Jan/13  Updated: 11/Jul/16  Resolved: 30/Jan/13

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 2.3.2
Fix Version/s: 2.4.0-rc0

Type: Bug Priority: Major - P3
Reporter: Andy Schwerin Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-8410 max_message_size.js failing on 32-bit... Closed
Related
related to SERVER-8414 DBClientConnection::auth should suppo... Closed
Operating System: ALL
Participants:

 Description   

The first failing test case causes the connection to the database to close. The shell automatically reopens a new one, but because it does not cache authentication credentials, it cannot (and does not try to) reauthenticate. This stems from the shell not faithfully implementing the driver spec (the C++ driver doesn't, either).

      Test : max_message_size.js ...
      Command : /data/buildslaves/Linux_64bit_Subscription_Amazon_AMI_Nightly/mongo/mongo --port 27999 --authenticationMechanism CRAM-MD5 /data/buildslaves/Linux_64bit_Subscription_Amazon_AMI_Nightly/mongo/jstests/max_message_size.js --eval TestData = new Object();TestData.testPath = "/data/buildslaves/Linux_64bit_Subscription_Amazon_AMI_Nightly/mongo/jstests/max_message_size.js";TestData.testFile = "max_message_size.js";TestData.testName = "max_message_size";TestData.noJournal = false;TestData.noJournalPrealloc = false;TestData.auth = true;TestData.keyFile = "/data/buildslaves/Linux_64bit_Subscription_Amazon_AMI_Nightly/mongo/jstests/libs/authTestsKey";TestData.keyFileData = "Thiskeyisonlyforrunningthesuitewithauthenticationdontuseitinanytestsdirectly";jsTest.authenticate(db.getMongo());
         Date : Wed Jan 30 07:37:50 2013
MongoDB shell version: 2.3.3-pre-
connecting to: 127.0.0.1:27999/test
Wed Jan 30 07:37:50.895 [initandlisten] connection accepted from 127.0.0.1:38012 #34 (1 connection now open)
Authenticating to admin database as admin with mechanism CRAM-MD5 on connection: connection to 127.0.0.1:27999
Wed Jan 30 07:37:50.898 [conn34] SASL: Successfully authenticated as principal: admin
1
Wed Jan 30 07:37:50.915 [conn34] CMD: drop test.max_message_size
Wed Jan 30 07:37:51.754 [FileAllocator] allocating new datafile /data/db/sconsTests/test.2, filling with zeroes...
Wed Jan 30 07:37:51.760 [FileAllocator] done allocating datafile /data/db/sconsTests/test.2, size: 256MB,  took 0.005 secs
Wed Jan 30 07:37:51.760 [FileAllocator] allocating new datafile /data/db/sconsTests/test.3, filling with zeroes...
Wed Jan 30 07:37:51.767 [FileAllocator] done allocating datafile /data/db/sconsTests/test.3, size: 512MB,  took 0.006 secs
Wed Jan 30 07:37:51.767 [FileAllocator] allocating new datafile /data/db/sconsTests/test.4, filling with zeroes...
Wed Jan 30 07:37:51.767 [conn34] build index test.max_message_size { _id: 1 }
Wed Jan 30 07:37:51.768 [conn34] build index done.  scanned 0 total records. 0.001 secs
Wed Jan 30 07:37:51.788 [FileAllocator] done allocating datafile /data/db/sconsTests/test.4, size: 1024MB,  took 0.021 secs
Wed Jan 30 07:37:51.871 [conn34] insert test.max_message_size ninserted:3 keyUpdates:0 locks(micros) w:116953 116ms
Wed Jan 30 07:37:51.968 [conn34] CMD: drop test.max_message_size
Wed Jan 30 07:37:52.125 [conn34] command test.$cmd command: { drop: "max_message_size" } ntoreturn:1 keyUpdates:0 locks(micros) w:156561 reslen:128 156ms
Wed Jan 30 07:37:52.575 [conn34] build index test.max_message_size { _id: 1 }
Wed Jan 30 07:37:52.576 [conn34] build index done.  scanned 0 total records. 0 secs
Wed Jan 30 07:37:52.723 [conn34] insert test.max_message_size ninserted:3 keyUpdates:0 locks(micros) w:147974 148ms
Wed Jan 30 07:37:52.747 [conn34] CMD: drop test.max_message_size
Wed Jan 30 07:37:53.130 [conn34] build index test.max_message_size { _id: 1 }
Wed Jan 30 07:37:53.131 [conn34] build index done.  scanned 0 total records. 0 secs
Wed Jan 30 07:37:53.154 [conn34] CMD: drop test.max_message_size
Wed Jan 30 07:37:53.420 [conn34] recv(): message len 48000001 is too large. Max is 48000000
Wed Jan 30 07:37:53.421 [conn34] end connection 127.0.0.1:38012 (0 connections now open)
Wed Jan 30 07:37:53.421 Socket say send() errno:104 Connection reset by peer 127.0.0.1:27999
Wed Jan 30 07:37:56.438 trying reconnect to 127.0.0.1:27999
Wed Jan 30 07:37:56.439 [initandlisten] connection accepted from 127.0.0.1:38013 #35 (1 connection now open)
Wed Jan 30 07:37:56.439 reconnect 127.0.0.1:27999 ok
Wed Jan 30 07:37:56.439 [conn35] command denied: { count: "max_message_size", query: {}, fields: {} }
Wed Jan 30 07:37:56.441 count failed: { "ok" : 0, "errmsg" : "unauthorized" } src/mongo/shell/query.js:180
failed to load: /data/buildslaves/Linux_64bit_Subscription_Amazon_AMI_Nightly/mongo/jstests/max_message_size.js
Wed Jan 30 07:37:56.482 [conn35] end connection 127.0.0.1:38013 (0 connections now open)
                 5648.1149 ms
Wed Jan 30 07:37:56.483 got signal 15 (Terminated), will terminate after current cmd ends
Wed Jan 30 07:37:56.483 [interruptThread] now exiting
Wed Jan 30 07:37:56.483 dbexit: 
Wed Jan 30 07:37:56.483 [interruptThread] shutdown: going to close listening sockets...
Wed Jan 30 07:37:56.483 [interruptThread] closing listening socket: 9
Wed Jan 30 07:37:56.483 [interruptThread] closing listening socket: 10
Wed Jan 30 07:37:56.483 [interruptThread] closing listening socket: 11
Wed Jan 30 07:37:56.483 [interruptThread] removing socket file: /tmp/mongodb-27999.sock
Wed Jan 30 07:37:56.483 [interruptThread] shutdown: going to flush diaglog...
Wed Jan 30 07:37:56.483 [interruptThread] shutdown: going to close sockets...
Wed Jan 30 07:37:56.483 [interruptThread] shutdown: waiting for fs preallocator...
Wed Jan 30 07:37:56.483 [interruptThread] shutdown: lock for final commit...
Wed Jan 30 07:37:56.483 [interruptThread] shutdown: final commit...
Wed Jan 30 07:37:57.557 [interruptThread] shutdown: closing all files...
Wed Jan 30 07:37:57.572 [interruptThread] closeAllFiles() finished
Wed Jan 30 07:37:57.572 [interruptThread] journalCleanup...
Wed Jan 30 07:37:57.572 [interruptThread] removeJournalFiles
Wed Jan 30 07:37:57.577 [interruptThread] shutdown: removing fs lock...
Wed Jan 30 07:37:57.577 dbexit: really exiting now
test /data/buildslaves/Linux_64bit_Subscription_Amazon_AMI_Nightly/mongo/jstests/max_message_size.js exited with status 253



 Comments   
Comment by auto [ 30/Jan/13 ]

Author:

{u'date': u'2013-01-30T21:24:08Z', u'email': u'spencer@10gen.com', u'name': u'Spencer T Brody'}

Message: SERVER-8414 SERVER-8413 Skip jstests/max_message_size.js when running with auth
Branch: master
https://github.com/mongodb/mongo/commit/ba257276295142403329d885a1702e30756a76f7

Comment by Spencer Brody (Inactive) [ 30/Jan/13 ]

This is failing because of SERVER-8414. MONGO-CR style auth credentials get cached and used to re-authenticate connections when the socket is broken, the same thing doesn't happen for sasl authentication.

Generated at Thu Feb 08 03:17:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.