<    March 2017    >
Su Mo Tu We Th Fr Sa  
          1  2  3  4  
 5  6  7  8  9 10 11  
12 13 14 15 16 17 18  
19 20 21 22 23 24 25  
26 27 28 29 30 31
00:05 s2013 joined
00:24 skot joined
00:36 Gwayne joined
00:38 shackra joined
00:40 Sasazuka_ joined
00:45 timg__ joined
01:00 sftp joined
01:02 orbyt_ joined
01:04 svm_invictvs joined
01:38 philipballew joined
01:42 PerpetualWar joined
01:51 Sasazuka joined
02:00 s2013 joined
02:03 PerpetualWar joined
02:12 PerpetualWar joined
02:26 raspado joined
02:35 gentunian joined
03:15 s2013 joined
03:16 raspado joined
03:17 raspado joined
03:18 gentunian joined
03:32 philipballew joined
03:54 smokeysea joined
03:56 gamespttr joined
04:37 qmr joined
04:41 dustinm` joined
04:47 ayogi joined
05:06 arussel` joined
05:13 dafuel__ joined
05:14 joshua joined
05:15 jandrews joined
05:16 hfp_work joined
05:16 chen joined
05:16 JohnsonAskot joined
05:20 Liara- joined
05:29 YoY joined
05:30 timg__ joined
05:34 jaitaiwan joined
05:35 AlgorithmWizard joined
05:35 xrated joined
05:45 gregor3005 joined
05:47 coudenysj joined
05:48 lpin joined
06:03 <KekSi> is there any way that i can force a replica primary to stay primary even when its alone?
06:03 KingGregoryXVIII joined
06:04 <KekSi> pretty much master-slave replication but with a replica-set?
06:07 <joannac> Have a single node replica set
06:11 philipballew joined
06:13 swiftkey joined
06:26 rendar joined
06:29 kyuwonchoi joined
06:30 <KekSi> no i want replication but apparently priority 0 and hidden true aren't enough to make that happen
06:30 jwd joined
06:30 <KekSi> the primary steps down when that secondary loses connection
06:43 <KekSi> would a priority 1000 on the primary help? or setting up an arbiter on exactly that node?
06:43 smokeysea joined
06:44 <KekSi> the secondary (and it is only one) is sort-of a backup (networking related since there's no direct access possible between the software pieces that use mongodb and the secondary - only the primary can access it)
06:47 emil_k joined
06:58 <neodarz> Hello, I would like to install doctrine/mongodb in symfony 2.8 but I have this error : "doctrine/mongodb 1.4.0 requires ext-mongo ^1.5 -> the requested PHP extension mongo is missing from your system." I have the last version of ext-mongo : 1.2.8 (https://pecl.php.net/package/mongodb)
06:58 <neodarz> Somebody can help me please ?
07:16 wowz joined
07:23 Folkol joined
07:26 <wowz> Hi, I ran into https://pastebin.com/rBkmWXdg when importing a previously exported collection.
07:27 <wowz> I used mongoexport /host 192.168.0.57 --db dpp_Demo --collection workPeriodData --out workPeriodData.json to export and mongoimport --db=dpp_Demo --collection=workPeriodData /tmp/dpp_Demo/workPeriodData.json to import
07:27 <wowz> the file is 40Mb with about 300 document and the biggest document is 3MB
07:27 <wowz> anyone any idea?
07:42 kyuwonchoi joined
07:57 emil_k joined
08:09 KingGregoryXVIII joined
08:11 <wowz> no-one?
08:20 SkyRocknRoll joined
08:23 SkyRocknRoll joined
08:26 kexmex joined
08:29 emil_k joined
08:39 KingGregoryXVIII joined
08:50 gfidente joined
08:55 kyuwonchoi joined
09:03 okapi joined
09:11 okapi joined
09:45 tiwest joined
10:06 kyuwonchoi joined
10:14 kexmex joined
10:15 yeitijem joined
10:17 emil_k joined
10:31 klics joined
10:33 okapi joined
10:50 okapi joined
11:18 kyuwonchoi joined
11:20 oka joined
11:21 oka left
11:22 okasakii joined
11:24 okasakii joined
11:24 <okasakii> Hey
11:56 undertuga joined
12:07 arussel`` joined
12:08 Folkol joined
12:17 StephenLynx joined
12:30 okapi joined
12:31 kyuwonchoi joined
12:37 <chris|> I am currently planing an uprade of our 3.2 cluster to 3.4. What is eluding me this far is the migration path from the old tag based sharding to the new zone based sharding. From what I can see, this is basically compatible, right? if not, what does the migration path look like?
12:38 kyuwonchoi joined
12:43 <Derick> chris|: afaik, it's just a rename of the feature
12:46 <chris|> Derick: that is what I figured, thanks
12:49 kyuwonchoi joined
12:52 Guest11008 left
12:56 dsardari joined
12:57 basiclaser joined
12:58 jeffreylevesque joined
13:00 geoffb joined
13:04 edrocks joined
13:10 kyuwonchoi joined
13:11 kyuwonchoi joined
13:12 kyuwonchoi joined
13:13 kyuwonchoi joined
13:13 kyuwonchoi joined
13:14 kyuwonchoi joined
13:21 raspado joined
13:27 ramortegui joined
13:31 gentunian joined
14:08 culthero joined
14:14 apetresc joined
14:15 Diggsey joined
14:15 edrocks joined
14:16 kyuwonchoi joined
14:20 <chris|> can I pin the featureCompatibilityVersion to 3.2 before upgrading the mongo (meaning: on 3.2)?
14:23 <Derick> yes, I believe so
14:23 <Derick> but I am not sure whether there is a shell helper for it
14:23 <Derick> let me see
14:24 <chris|> actually, I would prefere to not use a shell helper :)
14:24 <chris|> it looks like the compatibility version is set in admin.system.version on each member, however that collection does not seem to exist on 3.2
14:24 <Derick> chris|: you don't need to
14:25 <Derick> For deployments upgraded from 3.2 "3.2" until you setFeatureCompatibilityVersion to "3.4".
14:25 <Derick> under https://docs.mongodb.com/manual/reference/command/setFeatureCompatibilityVersion/#default-values
14:26 <Derick> > use admin
14:26 <Derick> switched to db admin
14:26 <Derick> > db.system.version.update( { "_id" : "featureCompatibilityVersion" }, { $set: { "version" : "3.2" } }, { upsert: true } );
14:26 <Derick> WriteResult({ "nMatched" : 1, "nUpserted" : 0, "nModified" : 0 })
14:29 gentunian joined
14:29 <chris|> yeah, I think I'll want to make it explicit
14:37 KingGregoryXVIII joined
14:39 Folkol joined
14:57 emil_k joined
14:59 timg__ joined
15:10 s2013 joined
15:14 itaipu joined
15:25 Folkol joined
15:30 timg___ joined
15:30 sz0 joined
15:33 tharkun joined
15:35 gentunian joined
15:44 okapi joined
15:45 raspado joined
15:46 synchroack joined
15:54 Lujeni joined
15:55 smokeysea joined
15:58 svm_invictvs joined
16:05 timg__ joined
16:11 timg___ joined
16:22 philipballew joined
16:31 orbyt_ joined
16:37 orbyt_ joined
16:38 synchroack_ joined
16:39 synchroack_ joined
16:41 kexmex joined
16:41 synchroack_ joined
16:58 FrozenSolid joined
17:07 kyuwonchoi joined
17:11 point joined
17:29 silenced joined
17:34 fels joined
17:40 roger_rabbit joined
17:41 fullerja joined
17:43 coudenysj joined
17:51 synchroack__ joined
17:56 skoude_ joined
17:57 mobiledeath joined
17:57 seprob_ joined
17:57 alnewkir1 joined
17:58 Ratler_ joined
18:00 redondos joined
18:00 ace joined
18:01 JoWie joined
18:04 Sasazuka joined
18:21 silenced joined
18:41 n0arch joined
18:42 Sasazuka joined
18:45 artok joined
18:49 synchroack_ joined
18:57 rendar joined
18:57 rendar joined
19:04 culthero_ joined
19:06 culther__ joined
19:22 jwd joined
19:22 kexmex joined
19:24 silenced joined
19:29 FrozenSolid joined
19:33 KingGregoryXVIII joined
19:36 okapi joined
19:39 coudenysj joined
19:46 gentunian joined
19:49 culthero joined
19:55 KingGregoryXVIII joined
20:02 culthero joined
20:07 FrozenSolid joined
20:11 kyuwonchoi joined
20:14 PerpetualWar joined
20:16 teprrr joined
20:31 itaipu joined
20:42 svm_invictvs joined
20:44 itaipu_ joined
20:45 okapi joined
20:48 orbyt_ joined
21:23 KingGregoryXVIII joined
21:31 StephenLynx joined
21:36 <ironpig> I have a production mongoDB server running that supports a CRM... and for some odd reason, weird collection names are appearing in the primary database. What is this? Could it be an exploit attempt? There is nothing actually in the collection, no documents. Has anyone seen this before?
21:40 itaipu joined
21:40 castlelore joined
21:40 castlelore joined
21:41 <joannac> itaipu: what kind of collection names?
21:42 <joannac> oops, wrong person. ironpig ^^
21:43 <ironpig> weird ones, like a bunch of foreign charater & black dimond question mark strings.
21:45 KingGregoryXVIII joined
21:45 <ironpig> here'e a pastebin of the odd names.
21:45 <ironpig> https://pastebin.com/jXw7Pnqs
21:47 <joannac> o.O
21:47 <ironpig> ??
21:47 <ironpig> bad?
21:48 <joannac> bad parsing on your app side?
21:49 <joannac> what driver are you using?
21:51 <ironpig> php mongo.so 1.6.13
21:52 <ironpig> there's a java driver in use as well, but I think this part the CRM is 100% PHP.
22:27 druonysus joined
22:49 culthero joined
23:03 Sasazuka_ joined
23:11 kyuwonchoi joined
23:34 SkyRocknRoll joined
23:45 silenced joined
23:49 jaequery joined