Mailing List Archive: make clone error

make clone error - wrong db

Sep 24, 2009, 2:50 PM

Post #1 of 8 (3178 views)

Hello,

I'm trying "make clone" on a 10.1.2 installation.

When I type "make clone" all of the questions are pre-populated with the correct answers. Notably, it shows the correct value for the conf file:
Bricolage Config Directory [/usr/local/bricolage/conf]
I just press [Enter] since it's correct, that is where bricolage.conf lives.

However, when it comes to connecting to the database, which is on a remote server, it fails. Here are the settings for my database in bricolage.conf
DB_NAME = et_bric
DB_HOST = db.etonline.com
DB_PORT = 5432

But here is the error during make clone:
==> Cloning Bricolage Database <==

Becoming postgres...
pg_dump: [archiver (db)] connection to database "bric" failed: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

My database is named "et_bric", so why is "make clone" trying to connect to a db named "bric"? Also, I assume "Becoming postgres..." means that it's su'ing to the user "postgres". Why doesn't it use the DB_USER and DB_PASS from the conf file?

Thank you,
Mike

Re: make clone error - wrong db [ In reply to ]

david at kineticode

Sep 24, 2009, 3:05 PM

Post #2 of 8 (3097 views)

Permalink

On Sep 24, 2009, at 2:50 PM, Fletcher, Michael wrote:

> I'm trying "make clone" on a 10.1.2 installation.

Try cloning your 1.10.2 install from a 1.10.7 download.

HTH,

David

RE: make clone error - wrong db [ In reply to ]

mike.fletcher at cbs

Sep 28, 2009, 10:34 AM

Post #3 of 8 (3073 views)

Permalink

On Thursday, September 24, 2009 3:06 PM David E. Wheeler wrote:

>> Try cloning your 1.10.2 install from a 1.10.7 download.

That sounds like a great way to upgrade at the same time. I'm running out of space even if I use devclone. Is there a way to calculate how much space I will need for a devclone?

Thanks,
Mike

Re: make clone error - wrong db [ In reply to ]

david at kineticode

Sep 28, 2009, 5:40 PM

Post #4 of 8 (3075 views)

Permalink

On Sep 28, 2009, at 10:34 AM, Fletcher, Michael wrote:

>>> Try cloning your 1.10.2 install from a 1.10.7 download.
>
> That sounds like a great way to upgrade at the same time. I'm
> running out of space even if I use devclone. Is there a way to
> calculate how much space I will need for a devclone?

It's about 1/6th of your database size + the full size of all of your
media files.

Best,

David

Re: make clone error - wrong db [ In reply to ]

paulo at digitalcraftsmen

Sep 29, 2009, 1:43 AM

Post #5 of 8 (3086 views)

Permalink

David E. Wheeler wrote:
> It's about 1/6th of your database size + the full size of all of your
> media files.

However, you should note that the devclone creates a full clone first, and
then removes all of the previews and cached objects, (anything that can be
regenerated basically), to create the smaller file for you to move.

If you're running out of disk space you could always delete previews and
mason cached objects within your live directories older than a certain
point. Your users can regenerate them if they need to. data/burn/stage and
data/burn/preview are the two places you should start. Stage in particular,
since it used to generate the files to before distributing to the live
servers so will always get overwritten anyway.

regards,

Paul

Re: make clone error - wrong db [ In reply to ]

david at kineticode

Sep 29, 2009, 9:31 AM

Post #6 of 8 (3075 views)

Permalink

On Sep 29, 2009, at 1:43 AM, Paul Orrock wrote:

> If you're running out of disk space you could always delete previews
> and mason cached objects within your live directories older than a
> certain point. Your users can regenerate them if they need to. data/
> burn/stage and data/burn/preview are the two places you should
> start. Stage in particular, since it used to generate the files to
> before distributing to the live servers so will always get
> overwritten anyway.

I also usually move the media root out of the way, leaving it out of
the clone, and rsync it to the new box manually. This keeps the size
of the clone much more manageable, but does create an extra couple of
steps in the upgrade process.

Best,

David

RE: make clone error - wrong db [ In reply to ]

mike.fletcher at cbs

Sep 29, 2009, 10:21 AM

Post #7 of 8 (3079 views)

Permalink

On Tuesday, September 29, 2009 9:32 AM David E. Wheeler wrote:

> I also usually move the media root out of the way,
> leaving it out of the clone, and rsync it to the
> new box manually. This keeps the size of the clone
> much more manageable, but does create an extra couple
> of steps in the upgrade process.

I was thinking of installing 1.10.2 on the new server and pointing to the existing database. The new server would be using the same db as the existing server. Then putting the 1.10.7 download on the same "new" server and doing make clone there. That way, it's cloning from the old db, but no media is present. Then I can move the media over when I'm done.

Sound doable?

Thanks,
Mike

Re: make clone error - wrong db [ In reply to ]

david at kineticode

Sep 29, 2009, 12:42 PM

Post #8 of 8 (3073 views)

Permalink

On Sep 29, 2009, at 10:21 AM, Fletcher, Michael wrote:

> I was thinking of installing 1.10.2 on the new server and pointing
> to the existing database. The new server would be using the same db
> as the existing server. Then putting the 1.10.7 download on the
> same "new" server and doing make clone there. That way, it's
> cloning from the old db, but no media is present. Then I can move
> the media over when I'm done.
>
> Sound doable

I think you need to copy everything in $BRICOLAGE_ROOT over to the new
server, not just install there. There's a lot more than just media:
esp templates. The safest way to do this is to clone it all.

Best,

David