Op dinsdag 27 augustus 2019 22:28:49 UTC+2 schreef Jos Bredek: > > > > Op maandag 26 augustus 2019 22:39:18 UTC+2 schreef mwall: >> >> it looks like debug is not enabled - there are no debug messages in the >> log postings that you made. it would help to see the debug messages. >> >> what do you see in the shell in which you invoked weewxd? >> >> did weewx run properly with some other driver, such as simulator, before >> you installed the weewx-interceptor driver? >> >> m >> > > Sorry... seems like i pasted from the wrong log file.. Here is the syslog > output.... and it turns out the connection to my sql db is not properly > working. I guess this is the reason van the tcp-server thread quitting? > > Anyhow .. i will try to fix it. Keep you posted. > > Ciao, > Jbr >
Yes, that did the trick! The portnumber that weewx uses as a default (3306) differed from my port my mariadb was listering on (3307). I see loop data coming in on the console, and a first row in my db! I wil continue the rest of the setup and tuning. Thank you so much for helping me out! Ciao, Jbr -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/db3d725b-dd7a-44bd-a198-2c61e208f768%40googlegroups.com.
