Vince, I didn't stop and start mysql after making changes, I'll try that along with the other points you mentioned. I'll probably revisit this after a calming adult beverage...or two.
Dave-KB1PVH Sent from my Galaxy S9 On Fri, Feb 22, 2019, 7:55 PM vince <[email protected]> wrote: > On Friday, February 22, 2019 at 4:40:02 PM UTC-8, Dave Webb wrote: >> >> Doing #2 didn't fix it, still getting same error. I'm going to abort >> mission until tomorrow or Sunday. >> >> > A few thoughts: > > - after you change the mysql config to listen to non-localhost > traffic, you probably need to start+stop mysql on the database server to > have it take effect > - you might be blocking incoming traffic with a packet filter on your > database server (ok, that one's more of a stretch) > - it could be DNS resolution on the weewx system as well. Can the > weewx system resolve the hostname 'sdr-pi' that you defined for the db > server ? > - and Tom's item3 is the acid test - can you connect from the weewx > system via the shell directly, using the hostname/db/user/pass you defined > in weewx.conf ? > > > -- > You received this message because you are subscribed to the Google Groups > "weewx-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
