RockMongo fails open any further collections after a while

[GoogleCodeExporter]

Shortly after opening the first couple of collections rock runs into problems 
and fails to open any further collections with the message:
There is something wrong:invoke failed: JS Error: Error: can't use sharded 
collection from db.eval shell/db.js:30, please refresh the page to try again.
Reloading the page doesnt really help. There are also now error log messages.
Php memory limit and max. execution time has been increased without any effect.

MongoDB 1.8.1
RockMongo v1.1.0

Web server  Apache/2.2.14
PHP version PHP 5.3.2-1ubuntu4.9
PHP extension   mongo/1.2.1

Linux bs-linux64.10gen.cc 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_41

Original issue reported on code.google.com by s.podkow...@gmail.com on 12 Jul 2011 at 7:51

[GoogleCodeExporter]

Having the same issue since we sharded.   Pretty much can't use Rockmongo 
anymore, and we miss it terribly!

Original comment by eana...@gmail.com on 1 Aug 2011 at 5:12

[GoogleCodeExporter]

I am having the same problem, does this mean you cant use rockmongo in sharded 
environment?

Original comment by jbon...@gmail.com on 12 Aug 2011 at 1:23

[GoogleCodeExporter]

I am having the same problem, when I switched from mongodb 1.8.3 to mongo 
2.0.0.rc0

Original comment by webmast...@gmail.com on 31 Aug 2011 at 7:39

[GoogleCodeExporter]

This is caused by the extensive use of $db->execute. Basically, nearly every 
call to $db->execute needs to be replaced with non-eval code.

Original comment by JohnCren...@gmail.com on 12 Sep 2011 at 4:10

[GoogleCodeExporter]

You can workaround the immediate problem here by changing 
app/models/MCollection.php line 54 (first line of info() method) to:

$ret = $db->command(array( 'collStats' => $collection ));

This will ONLY allow you to read the collection (updates and such will still 
fail.) Also, none of the advanced operations will work (like repair, copy, 
import, export, etc.) Similar changes will be needed throughout to fully 
support sharded collections.

Given the scope and severity of the problem, I think that "medium" priority is 
wrong. Rockmongo is completely non-functional outside of the simplest 
configurations.

Original comment by JohnCren...@gmail.com on 12 Sep 2011 at 4:41

[GoogleCodeExporter]

Agreed with the above, it's now pretty much useless to us.

Original comment by k...@layer7.be on 19 Oct 2011 at 10:27

[GoogleCodeExporter]

this should probably be the no.1 issue to fix upon return. It makes rockMongo a 
non-competitor for any use case worth having mongo for...

Original comment by ar...@scene53.com on 3 May 2012 at 8:21

[GoogleCodeExporter]

Hi, everyone, we will fix the issue ASAP, and will release new version in this 
week. Thank you.

Original comment by iwind....@gmail.com on 4 May 2012 at 12:42

[GoogleCodeExporter]

Same problem :/ still not fixed

Original comment by Sp1n3.t...@gmail.com on 1 Jul 2012 at 4:50

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

got the same problem and i fixed it, by using an older version of the 
collection php file.

See the following:

http://www.rockmongo.com/svn/filedetails.php?repname=RockMongo&path=%2Fsrc%2Fapp
%2Fmodels%2FMCollection.php&rev=59&peg=59

Works for me, replace the file with the existing one.

PS. don't forget to make a backup, before applying ;)

Original comment by reape...@gmail.com on 26 Mar 2013 at 3:02