All,
If you have 4.6 installed from RPMs / ISO and yum upgrade please mind
that it will upgrade MongoDB as well (from 2.0.2 within sipxecs repo
to 2.0.7 published in epel-release). While mongo 2.0.2 stores data in
/var/lib/mongod the new one will store it in /var/lib/mongodb.
So if you want to
I did that, in my case I moved the files, not copied them which if the DB
resides in mongodb directory we shouldn't have to leave a trail of files
all over I would assume. I get mongo dead but subsys locked now when
restarting mongo. What gives?
On Wed, Sep 12, 2012 at 7:34 AM, George Niculae
On Wed, Sep 12, 2012 at 3:05 PM, Tony Graziano tgrazi...@myitdepartment.net
wrote:
I did that, in my case I moved the files, not copied them which if the DB
resides in mongodb directory we shouldn't have to leave a trail of files
all over I would assume. I get mongo dead but subsys locked now
On Wed, Sep 12, 2012 at 8:05 AM, Tony Graziano tgrazi...@myitdepartment.net
wrote:
I did that, in my case I moved the files, not copied them which if the DB
resides in mongodb directory we shouldn't have to leave a trail of files
all over I would assume.
move is fine
I get mongo dead but
I did a move. I made sure the folder and file were set for mongodb:mongodb
and the files were 0600 while the directory was 0755. The issue I had was
not having js installed which is a lately introduced dependency.
Would be nice if the directory were auto renamed/ownership before mongo
updates
On Wed, Sep 12, 2012 at 9:25 AM, Tony Graziano tgrazi...@myitdepartment.net
wrote:
I did a move. I made sure the folder and file were set for mongodb:mongodb
and the files were 0600 while the directory was 0755. The issue I had was
not having js installed which is a lately introduced
