MySQL 3 needed but how?
Laszlo Nagy
Hi,
I have an old backup from a MySQL data directory. It was created with
MySQL version 3. If I install MySQL 4 then I get this message telling
that the table was created with a different MySQL version.
So I try to install mysql 3. Here is the problem:
gw# pwd
/usr/ports/databases/mysql323-server
gw# make
===> mysql-server-3.23.59.n.20050301_3 obsolete and does not build with
gcc4.2; use mysql 5 or later.
*** Error code 1
Stop in /usr/ports/databases/mysql323-server.
gw#
But I really need mysql 3. I usually install everything from the ports
tree, but in this case this won't work. I need a quick solution. Maybe I
can install a different OS in a virtual machine. But do you know where
can I download a BSD OS version that has a binary package of MySQL
server 3? (I don't know how to search for a BSD OS that has binary
packages for mysql3...)
Thanks,
Laszlo
_______________________________________________
freebsd-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"
Kristaps Kūlis
/usr/ports/databases/mysql323-server/
65 .if ${OSVERSION} >= 700000
66 IGNORE= obsolete and does not build with gcc4.2; use mysql 5 or later
67 .endif
Get FreeBSD-6x installed somewhere and mysql port SHOULD compile and run.
Laszlo Nagy
> In article<4D8E1E4A...@shopzeus.com> you write:
>> Hi,
>>
>> I have an old backup from a MySQL data directory. It was created with
>> MySQL version 3. If I install MySQL 4 then I get this message telling
>> that the table was created with a different MySQL version.
> under mysql 4 and use ALTER TABLE to upgrade the file formats. You'll
> lose the user access stuff, but that's usually easy enough to
> reconstruct.
>
> In MySQL, each database is self-describing. That is, for database
> foo, the files in the foo/ directory are both the description of
> the tables and the data in them.
>
> http://dev.mysql.com/doc/refman/4.1/en/upgrading-from-3-23.html
Okay, I tried to follow the instruction. So instead of installing 4.1, I
have installed 4.0. After replacing /var/db/mysql with my archived
directory:
gw# /usr/local/etc/rc.d/mysql-server start
Starting mysql.
gw# /usr/local/etc/rc.d/mysql-server status
mysql is not running.
gw#
There is nothing in /var/log/messages.
It was working with 4.1 server, but I just uninstalled that (because the
upgrading faq told me to install 4.0 instead.)
So what now?
L
John R. Levine
> gw# /usr/local/etc/rc.d/mysql-server status
> mysql is not running.
> gw#
>
>
> There is nothing in /var/log/messages.
Sounds like you'll have to do some debugging. Try adding --verbose to
mysql_args in /etc/rc.conf, and see the other advice in
http://dev.mysql.com/doc/refman/4.1/en/starting-server.html
It may be something really simple, like the mysql data directory not being
where the server expects it to be.
Regards,
John Levine, jo...@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly
Jerry
Laszlo Nagy <gan...@shopzeus.com> articulated:
Do you have the following in your "/etc/rc.conf" file:
mysql_enable="YES"
--
Jerry ✌
FreeBS...@seibercom.net
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________
Microbiology Lab: Staph Only!
Laszlo Nagy
>> There is nothing in /var/log/messages.
>>
>> It was working with 4.1 server, but I just uninstalled that (because
>> the upgrading faq told me to install 4.0 instead.)
> Do you have the following in your "/etc/rc.conf" file:
>
> mysql_enable="YES"
Hopefully I'll be able to compile mysql 3.23 and make a backup from there.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Laszlo Nagy
> Sounds like you'll have to do some debugging. Try adding --verbose to
> mysql_args in /etc/rc.conf, and see the other advice in
> http://dev.mysql.com/doc/refman/4.1/en/starting-server.html
gw# /usr/local/bin/mysqld_safe --verbose
Starting mysqld daemon with databases from /var/db/mysql
STOPPING server from pid file /var/db/mysql/gw.sznet.pid
110326 16:44:14 mysqld ended
The data directory is correct. I don't understand why it is stopping
immediatelly after startup.
Trying the other way around (FreeBSD 6.4 on a virtual machine)
>
> It may be something really simple, like the mysql data directory not
> being where the server expects it to be.
>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
Fbsd8
>
>> Sounds like you'll have to do some debugging. Try adding --verbose to
>> mysql_args in /etc/rc.conf, and see the other advice in
>> http://dev.mysql.com/doc/refman/4.1/en/starting-server.html
>
> gw# /usr/local/bin/mysqld_safe --verbose
> Starting mysqld daemon with databases from /var/db/mysql
> STOPPING server from pid file /var/db/mysql/gw.sznet.pid
> 110326 16:44:14 mysqld ended
>
> The data directory is correct. I don't understand why it is stopping
> immediatelly after startup.
>
> Trying the other way around (FreeBSD 6.4 on a virtual machine)
>>
>> It may be something really simple, like the mysql data directory not
>> being where the server expects it to be.
>>
>
>
you have to run this command
mysql_install_db --user=mysql
on the command line to create mysql's
control databases first.
Then restart the mysql service.
To verify mysql is operational issue this command.
mysqladmin version
Them run your restore DB job pointing at your old bkup file.
That should recreate your db definition and populate the db
with your data in sync with the version of mysql your running.
Jerry
Fbsd8 <fb...@a1poweruser.com> articulated:
> Laszlo Nagy wrote:
> >
> >> Sounds like you'll have to do some debugging. Try adding
> >> --verbose to mysql_args in /etc/rc.conf, and see the other advice
> >> in http://dev.mysql.com/doc/refman/4.1/en/starting-server.html
> >
> > gw# /usr/local/bin/mysqld_safe --verbose
> > Starting mysqld daemon with databases from /var/db/mysql
> > STOPPING server from pid file /var/db/mysql/gw.sznet.pid
> > 110326 16:44:14 mysqld ended
> >
> > The data directory is correct. I don't understand why it is
> > stopping immediatelly after startup.
> >
> > Trying the other way around (FreeBSD 6.4 on a virtual machine)
> >>
> >> It may be something really simple, like the mysql data directory
> >> not being where the server expects it to be.
> >>
> >
> >
> No matter which version of mysql you install,
> you have to run this command
> mysql_install_db --user=mysql
> on the command line to create mysql's
> control databases first.
I believe that all of that is done by the mysql-server start-up file.
--
Jerry ✌
FreeBS...@seibercom.net
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________
_______________________________________________
krad
Why not get the binary packages off the freebsd archive servers from an
earlier release and run those with the relevant compatibility layer
Laszlo Nagy
and run mysqldump from there.
Thank you for your help!
L
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________