Re: [webmin-l] New to MySQL

[Jamie C. <jca...@we...>]

Hi Dan,=20
When you edit a database in Webmin, you should see a Backup Database butt=
on at the bottom of the page for creating a .sql format backup.=20
To restore on, you need to use the Execute SQL page, and just execute the=
 backup .sql file. Unlike some other databases, MySQL doesn't have a spec=
ial restore program or backup file format.

 - Jamie

-----Original Message-----

From:  da...@so...
Subj:  Re: [webmin-l] New to MySQL
Date:  Fri 24 Feb 2006 7:49 am
Size:  3K
To:  John Hinton <web...@ew...>,web...@li...

Okay, now with a lot of fighting and fussing we have takeoff Houston=20
AKA mysql version 5.0. Next question how do we upload or import a=20
user database without using another third party administration. I=20
know in the configuration there is an import script setup, but nothing=20
shows up in the module.

thanks,
Dan


From:           	John Hinton <web...@ew...>
To:             	web...@li...
Subject:        	Re: [webmin-l] New to MySQL
Send reply to:  	web...@li...
	<mailto:web...@li...?subject=3Dunsubscrib=
e>
	<mailto:web...@li...?subject=3Dsubscribe>
Date sent:      	Thu, 23 Feb 2006 11:07:57 -0500

[ Double-click this line for list subscription options ]=20

da...@so... wrote:
> Hi Jamie,
> Actually MySQL isn't running, it shuts down even on system reboot.=20
> Below are the last two error log entries. The second is after I=20
> deleted the databases as in a new start. This is a new install so=20
> MySQL hasn't run yet.
You have deleted or not created the master 'mysql' database which=20
contains all the connection information for any other existing=20
databases. The line, 'mysql.host' would be the host table in the=20
mysql=20
database. This one contains info about what host are allowed to=20
connect=20
to mysql. So there's no method for mysql to connect to itself. This=20
database holds host, user, db, and most of the time columns_priv,=20
func,=20
tables_priv. Each of these instruct mysql as to what databases exist=20
and=20
what who can do from where with them. The basic addressing and=20
permission system.

I don't think there are any direct methods within Webmin to create=20
this=20
database. I'm thinking you're going to need to go back through your=20
installation of mysql and find out where/how this database gets=20
created=20
based on your particular installation method (packaged, compiled,=20
etc.).=20
Sounds like a mysql question instead of a Webmin question at this=20
point=20
as this would be a botched install of mysql or at least an incomplete=20
install.

Best,
John Hinton
>
> ***********************************************************************=
*******
> 060223 08:36:00  mysqld started
> 060223  8:36:01  InnoDB: Database was not shut down normally!
> InnoDB: Starting crash recovery.
> InnoDB: Reading tablespace information from the .ibd files...
> InnoDB: Restoring possible half-written data pages from the doublewrite
> InnoDB: buffer...
> 060223  8:36:01  InnoDB: Starting log scan based on checkpoint at
> InnoDB: log sequence number 0 43634.
> InnoDB: Doing recovery: scanned up to log sequence number 0 43634
> 060223  8:36:02  InnoDB: Flushing modified pages from the buffer pool..=
.
> 060223  8:36:02  InnoDB: Started; log sequence number 0 43634
> 060223  8:36:02 [ERROR] Fatal error: Can't open privilege tables:=20
> Table 'mysql.host' doesn't exist
> 060223 08:36:02  mysqld ended
>
> 060223 08:59:38  mysqld started
> InnoDB: The first specified data file ./ibdata1 did not exist:
> InnoDB: a new database to be created!
> 060223  8:59:39  InnoDB: Setting file ./ibdata1 size to 10 MB
> InnoDB: Database physically writes the file full: wait...
> 060223  8:59:39  InnoDB: Log file ./ib_logfile0 did not exist: new to=20
> be created
> InnoDB: Setting log file ./ib_logfile0 size to 5 MB
> InnoDB: Database physically writes the file full: wait...
> 060223  8:59:39  InnoDB: Log file ./ib_logfile1 did not exist: new to=20
> be created
> InnoDB: Setting log file ./ib_logfile1 size to 5 MB
> InnoDB: Database physically writes the file full: wait...
> InnoDB: Doublewrite buffer not found: creating new

--- message truncated ---