Date: Wed, 06 Jan 2010 17:59:35 +0100 From: =?ISO-8859-1?Q?D=E1rio?= "P." <fbsd.questions.list@gmail.com> To: Matthew Seaman <m.seaman@infracaninophile.co.uk> Cc: freebsd-questions@freebsd.org Subject: Re: mysql not starting on boot Message-ID: <1262797175.5561.9.camel@dasp-laptop> In-Reply-To: <4B44B776.9050300@infracaninophile.co.uk> References: <4B44B376.2010005@midsummerdream.org> <4B44B776.9050300@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Qua, 2010-01-06 às 16:16 +0000, Matthew Seaman escreveu: > Rob wrote: > > Since I upgraded to FreBSD 8.0, I'm noticing that mysql isn't starting > > on boot anymore. It starts fine once the system has booted, and looking > > at the mysql log I see: > > > > 100105 17:46:56 mysqld_safe Starting mysqld daemon with databases from > > /var/db/m > > ysql > > 100105 17:46:56 [ERROR] Can't start server: cannot resolve hostname!: > > Unknown er > > ror: 0 > > 100105 17:46:56 [ERROR] Aborting > > > > I use dhcp and ddns in my network, so I'm guessing that mysql is > > attempting to start before the networking has stabilized. Is there a > > way to make mysql be the last thing started at boot? > > MySQL will be happy if it can work out what the hostname of the machine > is. You say you're using ddns? If that means your machines are pushing > a hostname up to the DHCP server while they ask it for an IP number, then > there should be no problem. > > You can simply set the hostname in /etc/rc.conf -- it doesn't really > matter if the machine thinks its name is one thing, and the IPs on its > network interfaces resolve to something else (at least, not for the > purposes of running mysql.). The thing you'ld have to look out for are > the host part of usernames in grants of permissions to users. I have exactly the same problem, but with apache. It seems that the apache try to start before the network. > > I tried adding: > > > > # REQUIRE: NETWORKING > > > > To the init script, but that didn't seem to have any effect. Is there a > > tool that will run through all the init scripts and tell you the order > > of startup? > > rcorder(8) > > You might also find it beneficial to use 'SYNCDHCP' instead of plain 'DHCP' > in ifconfig_XXY lines in /etc/rc.conf -- this will cause the boot process to > block on getting an IP for the interface, rather than the default action of > backgrounding that process and trying to start everything else up. This will be useful for me too. Thank you.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1262797175.5561.9.camel>