==================================================================
Please DO NOT REPLY to this mail or send email to the developers
about this bug. Please follow-up to Bugzilla using this link:
https://bugs.contribs.org/show_bug.cgi?id=9720
Have you checked the Frequently Asked Questions (FAQ)?
http://wiki.contribs.org/SME_Server:Documentation:FAQ
Please also take the time to read the following useful guide:
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
==================================================================
Bug ID: 9720
Summary: wrong output during update or install of
smeserver-automysqlbackup
Classification: Contribs
Product: SME Contribs
Version: 9.0
Hardware: ---
OS: ---
Status: CONFIRMED
Severity: normal
Priority: P3
Component: smeserver-automysqlbackup
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
when running yum you can see:
Mise à jour : 2:smeserver-automysqlbackup-3.0.RC6-6.el6.sme.noarch
11/39
Migrating existing database hosts
Migrating existing database yum_installed
Migrating existing database yum_updates
Migrating existing database spamassassin
Migrating existing database configuration
Migrating existing database yum_available
Migrating existing database yum_repositories
Migrating existing database domains
Migrating existing database mailpatterns
Migrating existing database backups
Migrating existing database networks
Migrating existing database accounts
=========================================================================================
Your Databases are saved in /root/backup/db
only Root can access to these folders
a mail is send to Admin for all logs
Configuration file is /etc/automysqlbackup/myserver.conf
For a manual play you can use directly
automysqlbackup /etc/automysqlbackup/myserver.conf
else backups are done every night at 04H00 AM with
/etc/cron.daily/runmysqlbackup
=========================================================================================
RESTORING
In a root terminal
cd /root/backup/db/ and choose your backup
gunzip file-name.sql.gz
Next you will need to use the mysql client to restore the DB from the
sql file.
mysql database < /path/file.sql
NOTE: Make sure you use < and not > in the above command because you
are piping the file.sql
to mysql and not the other way around
=========================================================================================
Some db configuration for handle this contrib
Mailcontent (stdout/log/files/quiet)
# What would you like to be mailed to you?
# - log : send only log file (default)
# - files : send log file and sql files as attachments (see docs)
#- stdout : will simply output the log to the screen if run manually.
#- quiet : Only send logs if an error occurs to the MAILADDR.
Sizemail=8000 (bytes)
Mailto=root (or any other [email protected])
Backupdir=path to the folder where mysql files are saved
ex: config setprop automysqlbackup Mailcontent files
=========================================================================================
Mise à jour : smeserver-vacation-1.1-22.el6.sme.noarch
the triggering of initializing default db should not be done there, if every
rpm does this you will see a real mess in the update.
Yum already does this at the end of transaction!!!
all the rest of the output has nothing to do there :
- either it will be lost in the long output of yum in cli
- either it will not been seen with an update from manager, or confuse user.
this should be in the wiki
--
You are receiving this mail because:
You are the QA Contact for the bug._______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/
