I have never used the interceptor driver but I would expect the interceptor driver should be emitting loop packets which would be printed on the console. I think the fact that you are seeing a blank screen means we have hit on the problem. You are going to need some input from Matthew or an interceptor driver user, as I said I have not used that driver. One thing you could do is have a read of the comments at the start of the driver file (/usr/share/weewx/user/interceptor.py), there are often additional instructions there for configuring/fault finding etc
Gary On Tuesday, 16 April 2019 23:17:57 UTC+10, Damjan Hajsek wrote: > > > I have manualls started interceptor, what can I expect from it, because > nothing changes? > PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/interceptor.py > --device=observer --mode=listen --port=9999 > > Dne torek, 16. april 2019 11.16.05 UTC+2 je oseba gjr80 napisala: >> >> There have been no changes to the database since 3.8.1, but this is not a >> database problem. WeeWX is event driven and it relies on loop packets >> and/or archive records from the driver triggering events which then cause >> archive records to be created and saved to the database, reports to be >> generated etc. None of that is happening which makes me think there may be >> a driver issue given we have ruled out any other obvious issue. You are >> using the interceptor driver which, due to its nature, is susceptible to >> changes in your network. Perhaps something has changed on your network? >> Perhaps you should try running the interceptor driver directly to take >> WeeWX out of the equation and ensure you can get data from the interceptor >> driver. Running the driver directly is covered in the interceptor driver >> wiki entry. <https://github.com/matthewwall/weewx-interceptor> >> >> I would not be re-installing, as someone else here once said 'this is >> Linux not Windows'. >> >> Gary >> >> On Tuesday, 16 April 2019 17:56:56 UTC+10, Damjan Hajsek wrote: >>> >>> Thank you I did this and no luck. >>> Can you tell me are there any changes in databasebetween version 3.8.1 >>> and the latest version?? >>> If not I will install new weewx with rpm and than use old database. >>> regards >>> >>> Dne petek, 12. april 2019 15.34.53 UTC+2 je oseba Leon Shaner napisala: >>>> >>>> Damian, >>>> >>>> The symptoms I mentioned where it seems like weewxd is waiting for >>>> input could be due to an issue parsing your conf file. The wee_debug info >>>> you posted has these lines: >>>> >>>> # This section can adjust data using calibration expressions. >>>> >>>> [1] >>>> >>>> >>>> That looks like garbage. >>>> And yet way before that you have the typical section: >>>> >>>> # This section can adjust data using calibration expressions. >>>> >>>> [StdCalibrate] >>>> >>>> [[Corrections]] >>>> # For each type, an arbitrary calibration expression can be >>>> given. >>>> # It should be in the units defined in the StdConvert section. >>>> # Example: >>>> foo = foo + 0.2 >>>> >>>> >>>> ############################################################################## >>>> >>>> >>>> I suggest you try commenting out that extraneous "[1]" by preceding it >>>> with # a la: >>>> >>>> #[1] >>>> >>>> Other than that you may need to make a backup of your weewx.conf and >>>> run wee_config. It may be confused by your current conf file, just as >>>> weewxd appears to be. >>>> If all else fails, remove your conf file, run wee_config, and use diff >>>> against the backup to see what else you need to add back, but with care to >>>> only put the important parameters and to not reintroduce corruption. >>>> >>>> Regards, >>>> Leon >>>> -- >>>> Leon Shaner :: Dearborn, Michigan (iPhone) >>>> >>>> https://twitter.com/AEtherZcythe >>>> >>>> On Apr 12, 2019, at 4:12 AM, Damjan Hajsek <[email protected]> wrote: >>>> >>>> hi >>>> here is my debug log. >>>> >>>> http://zerobin.povej.net/?6a7fc01d0616ffa9#Zj15RUTw5bxNGfoVlibcKTgn5D2oPqPX0Dg+rkHOeR4= >>>> don't know what happend here all what I do on server latelly was to >>>> uninstall gnome desktop and reinstall it. >>>> Maybe is some part of python deleted or something like that? >>>> >>>> Damian >>>> >>>> Dne petek, 12. april 2019 01.14.27 UTC+2 je oseba gjr80 napisala: >>>>> >>>>> Let's be very clear here, you have logs they are not missing, that is >>>>> what you have been posting over the last 12 hours. It would seem that >>>>> once >>>>> WeeWX has completed its loading/initialisation something is causing it to >>>>> die or otherwise not do anything. You say that the last log extract >>>>> posted >>>>> was with debug = 1, I don't doubt you but the log extract you >>>>> provided is not with debug = 1. A log with debug = 1 will include >>>>> somethign like this: >>>>> >>>>> Apr 5 22:54:29 stretch7 weewx[1012]: Starting weewx weather system: >>>>> weewx. >>>>> Apr 5 22:54:29 stretch7 weewx[1024]: engine: Locale is 'en_AU.UTF-8' >>>>> Apr 5 22:54:29 stretch7 weewx[1024]: engine: pid file is /var/run/ >>>>> weewx.pid >>>>> Apr 5 22:54:29 stretch7 weewx[1028]: engine: Using configuration >>>>> file /home/weewx/weewx.conf >>>>> Apr 5 22:54:29 stretch7 weewx[1028]: engine: debug is 1 >>>>> Apr 5 22:54:29 stretch7 weewx[1028]: engine: Initializing engine >>>>> Apr 5 22:54:29 stretch7 weewx[1028]: engine: Loading station type >>>>> Simulator (weewx.drivers.simulator) >>>>> Apr 5 22:54:29 stretch7 weewx[1028]: engine: Loading service weewx. >>>>> engine.StdTimeSynch >>>>> Apr 5 22:54:29 stretch7 weewx[1028]: engine: Finished loading >>>>> service weewx.engine.StdTimeSynch >>>>> >>>>> which shows debug is 1 and there is more detail about services being >>>>> loaded/initialised. >>>>> >>>>> I think it might be a good time to have a look at your weewx.conf. >>>>> Can you run the wee_debug utility >>>>> <http://weewx.com/docs/utilities.htm#wee_debug_utility> and post its >>>>> output. The advantage of running wee_debug is that it will locate the >>>>> weewx.conf that WeeWX is using which is handy if you have more than >>>>> one weewx.conf on your system. Before you post the wee_debug output >>>>> just check the output for sensitive info like usernames, passwords, api >>>>> keys etc. wee_debug does a good job at obfuscating such info but it's >>>>> not perfect. >>>>> >>>>> Gary >>>>> >>>>> On Friday, 12 April 2019 02:37:20 UTC+10, Damjan Hajsek wrote: >>>>>> >>>>>> Hi >>>>>> >>>>>> [image: 2019-04-11 18_34_45-_etc_weewx_weewx.conf - >>>>>> [email protected] - Editor - WinSCP.png] >>>>>> Yes I really changed debug to 1 in conf file. I am from GMT +2 >>>>>> And I tested, date shows real date and time as it should be >>>>>> Why there is no logs I don't know, that is all what I get for fev >>>>>> hours after starting it manually. >>>>>> >>>>>> Dne četrtek, 11. april 2019 18.27.31 UTC+2 je oseba Leon Shaner >>>>>> napisala: >>>>>>> >>>>>>> Hi, Damjan, >>>>>>> >>>>>>> I do not see debug output. Did you change debug = 0 to debug = 1 in >>>>>>> the conf file? >>>>>>> >>>>>>> Other than that, there is a thread where folks mentioned issues when >>>>>>> the date is off by too much... >>>>>>> I can't tell what time zone your host is set to, but I would guess >>>>>>> UTC or GMT, no? >>>>>>> In my case I have the host time zone set to my local time zone and >>>>>>> when I type "date" it shows the current local time. Mine works, so it >>>>>>> could be a factor. >>>>>>> >>>>>>> Other than that, I posted just yesterday about an issue with >>>>>>> Wunderground-RF (rapid fire) not working unless I also explicitly >>>>>>> forced >>>>>>> Wunderground-PWS on. The setting to do that is in the Wunderground >>>>>>> section >>>>>>> and you can try adding it right under the rapidfire = True a la: >>>>>>> >>>>>>> archive_post = True >>>>>>> >>>>>>> I'm on 1.3.9-1 and you're on 1.3.8, so while it is worth a shot, it >>>>>>> might not be the issue in your case. >>>>>>> >>>>>>> Regards, >>>>>>> Leon >>>>>>> -- >>>>>>> Leon Shaner :: Dearborn, Michigan (iPad Pro) >>>>>>> >>>>>>> On Apr 11, 2019, at 11:35 AM, Damjan Hajsek <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>> Here is log with debug enabled. >>>>>>> >>>>>>> >>>>>>> http://zerobin.povej.net/?18327ca6959d12c6#NusymzsEuAoTuXNt9tVsZL1+VG4jZO28VhSVYjJxwC0= >>>>>>> >>>>>>> >>>>>>> Dne četrtek, 11. april 2019 15.17.35 UTC+2 je oseba gjr80 napisala: >>>>>>>> >>>>>>>> Ok, so you do have logs. The startup log extract you posted looks >>>>>>>> fine to me. What's happens next in the log? Need to see at least the >>>>>>>> next 5 >>>>>>>> minutes of log. >>>>>>>> >>>>>>>> Not that it seems to be required but your attempt at running WeeWX >>>>>>>> directly failed because WeeWX could not find weewx.conf, you need to >>>>>>>> provide the path to weewx.conf in full eg: >>>>>>>> >>>>>>>> $ sudo weewxd /etc/weewx/weewx.conf >>>>>>>> >>>>>>>> Gary >>>>>>>> >>>>>>>> -- >>>>>>> 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. >>>> >>>> -- 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.
