1 |
On Thu, Jan 24, 2013 at 7:03 AM, Stroller |
2 |
<stroller@××××××××××××××××××.uk> wrote: |
3 |
> I think, to be rigorous, I would want to test this system (I'm not saying you should keep it this way) by setting the IP address statically for eth1. |
4 |
> |
5 |
> From what I'm understanding, this doesn't sound like a MySQL problem, but a DHCP problem. |
6 |
|
7 |
You're correct. When I set the interface statically, MySQL starts up |
8 |
like a champ. |
9 |
|
10 |
> You're checking the IP address with ifconfig - I believe that is deprecated. I guess at some point you might replace that in your `echo > test.log` scripts with the newer tools, just to make sure they say the same thing. Maybe this is paranoia, but you know what they say about that. |
11 |
> |
12 |
> http://blog.timheckman.net/2011/12/22/why-you-should-replace-ifconfig/ |
13 |
|
14 |
Thanks for the link. I'll definitely check that out. |
15 |
|
16 |
>> ... |
17 |
>> eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 |
18 |
>> inet6 NNNN:NNNN:NNNN:NNNN:NNNN:NNNN:NNNN:NNNN prefixlen 64 |
19 |
>> scopeid 0x0<global> |
20 |
>> inet6 NNNN::NNNN:NNNN:NNNN:NNNN prefixlen 64 scopeid 0x20<link> |
21 |
> |
22 |
> I don't think these are valid IPv6 addresses. If you're not using IPv6 then I would recommend removing the IPv6 USE flag globally and remerging everything --newuse. This will ensure nothing is depending upon IPv6 or expecting it or waiting for it. |
23 |
|
24 |
The real addresses are valid, I just didn't want to put them in a |
25 |
public mailing list message so I edited them. IPv6 on my network |
26 |
(through a Hurricane Electric tunnel) is working fine. |
27 |
|
28 |
>> The entries for eth1 in /etc/conf.d/net are: |
29 |
>> |
30 |
>> config_eth1="dhcp" |
31 |
>> routes_eth1="239.0.0.0/8" |
32 |
> |
33 |
> Is this right? |
34 |
|
35 |
Yes. The extra route is so that DLNA/uPnP works correctly on my network. |
36 |
|
37 |
>> I could add a delay to the mysql script to ensure startup, but I'd |
38 |
>> rather figure out why the IP address is not yet available even though |
39 |
>> the net.eth1 script has completed. Does anyone have any hints on what |
40 |
>> could be going wrong? |
41 |
> |
42 |
> There are several DHCP clients available in Portage. |
43 |
> |
44 |
> You need to tell us which one you're using. |
45 |
|
46 |
I did, although it was sort of hidden in the list of upgraded |
47 |
packages: "dhcpcd was upgraded from 5.2.12 to 5.6.4". |
48 |
|
49 |
> It wouldn't do any harm to experiment with one or two others. |
50 |
> |
51 |
> I think that a busybox version may be installed on some systems, and that this may interfere or misbehave. I don't know if a bug report has been filed for this.6 |
52 |
|
53 |
In any case, I did some more debugging and found that the problem |
54 |
seems to be an interaction between dhcpcd and IPv6 configuration. The |
55 |
latest version of dhcpcd now attempts by default to take over IPv6 |
56 |
stateless configuration instead of letting the kernel take care of it |
57 |
as happened before. dhcpcd appears to be getting an IPv6 address set |
58 |
up before the IPv4 configuration is complete, and considers this "good |
59 |
enough" to background itself instead of waiting for the IPv4 |
60 |
configuration to be complete. The workaround was to add "noipv6rs" |
61 |
(Disable solicition of IPv6 Router Advertisements) to the |
62 |
/etc/dhcpcd.conf file so that dhcpcd ignores IPv6 configuration. The |
63 |
kernel still configures IPv6 correctly, and dhcpcd now waits for the |
64 |
IPv4 configuration to be complete before backgrounding itself. |
65 |
|
66 |
-- |
67 |
Manuel A. McLure WW1FA <manuel@××××××.org> <http://www.mclure.org> |
68 |
...for in Ulthar, according to an ancient and significant law, |
69 |
no man may kill a cat. -- H.P. Lovecraft |