Reply to thread

Message

It's a bit of ancient history I had to check to remind myself what it is. Years ago I used Firenet (ip over 1394) and so it (the 192.169.1.9 address) is a Firenet adapter that is still on the system, though I don't use it these days. Again, though perhaps a curiosity, I don't think it is the answer, because it's been there for years. However, having said that, there is a change I made a few weeks ago: I removed the FW PCI card and replaced it with a USB3 PCI card. As the Firenet adapter/connection didn't complain, I didn't even think about it. I don't suppose the mysql service was somehow entangled in the Firenet connection/FW card combo and now doesn't like it because there is a connection but no card? Seems rather unlikely?

So I have done the obvious, disabled the Firenet connection and the 1394 device (in device manager) - no change (slow mysql starts) though - again bizarrely - the boot immediately before doing that was a fast mysql start (I can tell whether it is a slow/fast start by how long the batch file window stays open).

I also tried adding --debug to the mysql service 'path to executable' (via the registry) - conks out with a not timely error. I also confirmed --verbose is only a sub switch for --help and checked the --verbose --help output. Sure is verbose, but couldn't see anything to switch on verbose logging.

<blockquote data-quote="CathodeRay" data-source="post: 1148517" data-attributes="member: 128074">It's a bit of ancient history I had to check to remind myself what it is. Years ago I used Firenet (ip over 1394) and so it (the 192.169.1.9 address) is a Firenet adapter that is still on the system, though I don't use it these days. Again, though perhaps a curiosity, I don't think it is the answer, because it's been there for years. However, having said that, there is a change I made a few weeks ago: I removed the FW PCI card and replaced it with a USB3 PCI card. As the Firenet adapter/connection didn't complain, I didn't even think about it. I don't suppose the mysql service was somehow entangled in the Firenet connection/FW card combo and now doesn't like it because there is a connection but no card? Seems rather unlikely?So I have done the obvious, disabled the Firenet connection and the 1394 device (in device manager) - no change (slow mysql starts) though - again bizarrely - the boot immediately before doing that was a fast mysql start (I can tell whether it is a slow/fast start by how long the batch file window stays open).I also tried adding --debug to the mysql service 'path to executable' (via the registry) - conks out with a not timely error. I also confirmed --verbose is only a sub switch for --help and checked the --verbose --help output. Sure is verbose, but couldn't see anything to switch on verbose logging.</blockquote>

[QUOTE="CathodeRay, post: 1148517, member: 128074"] It's a bit of ancient history I had to check to remind myself what it is. Years ago I used Firenet (ip over 1394) and so it (the 192.169.1.9 address) is a Firenet adapter that is still on the system, though I don't use it these days. Again, though perhaps a curiosity, I don't think it is the answer, because it's been there for years. However, having said that, there is a change I made a few weeks ago: I removed the FW PCI card and replaced it with a USB3 PCI card. As the Firenet adapter/connection didn't complain, I didn't even think about it. I don't suppose the mysql service was somehow entangled in the Firenet connection/FW card combo and now doesn't like it because there is a connection but no card? Seems rather unlikely? So I have done the obvious, disabled the Firenet connection and the 1394 device (in device manager) - no change (slow mysql starts) though - again bizarrely - the boot immediately before doing that was a fast mysql start (I can tell whether it is a slow/fast start by how long the batch file window stays open). I also tried adding --debug to the mysql service 'path to executable' (via the registry) - conks out with a not timely error. I also confirmed --verbose is only a sub switch for --help and checked the --verbose --help output. Sure is verbose, but couldn't see anything to switch on verbose logging. [/QUOTE]