search

vmware-archive / cfops

This is simply an automation that is based on the supported way to back up Pivotal Cloud Foundry
http://www.cfops.io
Apache License 2.0
35 stars 24 forks source link

cfops panic message #51

Closed awstaples closed 8 years ago

awstaples commented 8 years ago

Received panic message while using cfops to backup the elastic runtime tile. There was quite a bit of output from cfops after this. Is this a failure, or just informational? cfops version v2.0.49

---snip we have a cf product we have some psql we have some psql we have some psql 2016/01/28 10:37:31 I0128 10:37:31.22895 8786 elasticruntime.go:138] Exporting nfs_server ^[[B2016/01/28 10:41:05 I0128 10:41:05.337621 8786 elasticruntime.go:138] Exporting consoledb 2016/01/28 10:41:05 I0128 10:41:05.515441 8786 elasticruntime.go:138] Exporting ccdb 2016/01/28 10:41:05 I0128 10:41:05.75453 8786 elasticruntime.go:138] Exporting uaadb 2016/01/28 10:41:05 I0128 10:41:05.868943 8786 elasticruntime.go:138] Exporting mysql panic: you have to extend SystemInfo and implement GetPersistanceBackup method on the child ---snip

xchapter7x commented 8 years ago

what is the command you ran? can you confirm you set the ER_VERSION=1.6 env var

also, if you have set the LOG_LEVEL=debug this is normal output not a stack trace

awstaples commented 8 years ago

Here is the cmd I am running: ER_VERSION=1.6 ./cfops backup --omh ^ip of opsmgr^ --du ^cfadmin^ --dp ^passwd^ --omu ubuntu --omp ^passwd^ -d /opt/cfops/techlab -t elastic-runtime

awstaples commented 8 years ago

Output from the cmd is large without debug. With debug enabled it is, as expected, much larger! What specific sections are needed?.
The only item in the target folder when the cmd stops is mysql.backup

xchapter7x commented 8 years ago

If your elastic runtime is 1.6 and configured for MySQL persistence, then you should see a mysql.backup and a nfs.backup .

If you are not setting debug output then the output should be minimal, provided there are no errors.

Can you pull out any actual errors and paste them here. Likely something regarding NFS.

Also, how big is that mysql.backup? Is it a complete dump or is that where the error happened?

Let me know.

-John

On Wed, Feb 3, 2016, 8:56 AM awstaples notifications@github.com wrote:

Output from the cmd is large without debug. With debug enabled it is, as expected, much larger! What specific sections are needed?.

The only item in the target folder when the cmd stops is mysql.backup

— Reply to this email directly or view it on GitHub https://github.com/pivotalservices/cfops/issues/51#issuecomment-179247303 .