[weewx-user] RAM is running full. Apparently it's due to the weectl import
Hello everyone, I currently have the problem that my RAM is regularly full and I have to restart the server. I have now seen that the weectl import service is not stopped. I'm attaching the output. Does anyone have an idea what this Area 31 30 means? That's where it seems to hang. Thank you root@weewx5:~# weectl import --import-config=/etc/weewx/import/wu-example.conf --no-prompt --verbose Using configuration file /etc/weewx/weewx.conf Starting weectl import... Observation history for Weather Underground station 'I*' will be imported. The following options will be used: config=/etc/weewx/weewx.conf, import-config=/etc/weewx/import/wu-example.conf station=I**, from=None, to=None apiKey=** dry-run=False, calc_missing=True, ignore_invalid_data=True tranche=250, interval=5, wind_direction=[0.0, 360.0] Using database binding 'wx_binding', which is bound to database 'weewx.sdb' Destination table 'archive' unit system is '0x10' (METRIC). The following imported field-to-WeeWX field map will be used: source field 'epoch' in units 'unix_epoch' --> WeeWX field 'dateTime' source field 'tempAvg' in units 'degree_F' --> WeeWX field 'outTemp' source field 'humidityAvg' in units 'percent' --> WeeWX field 'outHumidity' source field 'dewptAvg' in units 'degree_F' --> WeeWX field 'dewpoint' source field 'heatindexAvg' in units 'degree_F' --> WeeWX field 'heatindex' source field 'windchillAvg' in units 'degree_F' --> WeeWX field 'windchill' source field 'pressureAvg' in units 'inHg' --> WeeWX field 'barometer' source field 'precipTotal' in units 'inch' --> WeeWX field 'rain' (source field 'precipTotal' will be treated as a cumulative value) source field 'precipRate' in units 'inch_per_hour' --> WeeWX field 'rainRate' source field 'windspeedAvg' in units 'mile_per_hour' --> WeeWX field 'windSpeed' source field 'winddirAvg' in units 'degree_compass' --> WeeWX field 'windDir' source field 'windgustHigh' in units 'mile_per_hour' --> WeeWX field 'windGust' source field 'solarRadiationHigh' in units 'watt_per_meter_squared' --> WeeWX field 'radiation' source field 'uvHigh' in units 'uv_index' --> WeeWX field 'UV' Missing derived observations will be calculated. Starting import ... Records covering multiple periods have been identified for import. Obtaining raw import data for period 1 ... Raw import data read successfully for period 1. Mapping raw import data for period 1 ... Mapped 139 records. Raw import data mapped successfully for period 1. Saving mapped data to archive for period 1 ... 139 records identified for import. Unique records processed: 139; Last timestamp: 2024-07-22 11:34:52 CEST (1721640892) Mapped data saved to archive successfully for period 1. Calculating missing derived observations ... Processing record: 140; Last record: 2024-07-23 00:00:00 CEST (1721685600) Recalculating daily summaries... Finished recalculating daily summaries Finished calculating missing derived observations Finished import 139 records were processed and 139 unique records imported in 0.28 seconds. Those records with a timestamp already in the archive will not have been imported. Confirm successful import in the weectl log file. area 30 31 -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/159cf095-8c4f-43a5-a5c6-f9ab5fd2a803n%40googlegroups.com.
[weewx-user] Re: RAM is running full. Apparently it's due to the weectl import
One more note The message appears after cancellation Finished calculating missing derived observations Finished import 248 records were processed and 248 unique records imported in 0.42 seconds. Those records with a timestamp already in the archive will not have been imported. Confirm successful import in the weectl log file. ^CException ignored in: Traceback (most recent call last): File "/usr/lib/python3.11/threading.py", line 1590, in _shutdown lock.acquire() KeyboardInterrupt: root@weewx5:~# Sebastian E schrieb am Montag, 22. Juli 2024 um 13:56:45 UTC+2: > Hello everyone, I currently have the problem that my RAM is regularly full > and I have to restart the server. > > I have now seen that the weectl import service is not stopped. I'm > attaching the output. Does anyone have an idea what this Area 31 30 means? > That's where it seems to hang. Thank you > > > root@weewx5:~# weectl import > --import-config=/etc/weewx/import/wu-example.conf --no-prompt --verbose > Using configuration file /etc/weewx/weewx.conf > Starting weectl import... > Observation history for Weather Underground station 'I*' will be > imported. > The following options will be used: > config=/etc/weewx/weewx.conf, > import-config=/etc/weewx/import/wu-example.conf > station=I**, from=None, to=None > apiKey=** > dry-run=False, calc_missing=True, ignore_invalid_data=True > tranche=250, interval=5, wind_direction=[0.0, 360.0] > Using database binding 'wx_binding', which is bound to database 'weewx.sdb' > Destination table 'archive' unit system is '0x10' (METRIC). > The following imported field-to-WeeWX field map will be used: > source field 'epoch' in units 'unix_epoch' --> WeeWX field 'dateTime' > source field 'tempAvg' in units 'degree_F' --> WeeWX field 'outTemp' > source field 'humidityAvg' in units 'percent' --> WeeWX field 'outHumidity' > source field 'dewptAvg' in units 'degree_F' --> WeeWX field 'dewpoint' > source field 'heatindexAvg' in units 'degree_F' --> WeeWX field 'heatindex' > source field 'windchillAvg' in units 'degree_F' --> WeeWX field 'windchill' > source field 'pressureAvg' in units 'inHg' --> WeeWX field 'barometer' > source field 'precipTotal' in units 'inch' --> WeeWX field 'rain' > (source field 'precipTotal' will be treated as a cumulative value) > source field 'precipRate' in units 'inch_per_hour' --> WeeWX field > 'rainRate' > source field 'windspeedAvg' in units 'mile_per_hour' --> WeeWX field > 'windSpeed' > source field 'winddirAvg' in units 'degree_compass' --> WeeWX field > 'windDir' > source field 'windgustHigh' in units 'mile_per_hour' --> WeeWX field > 'windGust' > source field 'solarRadiationHigh' in units 'watt_per_meter_squared' --> > WeeWX field 'radiation' > source field 'uvHigh' in units 'uv_index' --> WeeWX field 'UV' > Missing derived observations will be calculated. > Starting import ... > Records covering multiple periods have been identified for import. > Obtaining raw import data for period 1 ... > Raw import data read successfully for period 1. > Mapping raw import data for period 1 ... > Mapped 139 records. > Raw import data mapped successfully for period 1. > Saving mapped data to archive for period 1 ... > 139 records identified for import. > Unique records processed: 139; Last timestamp: 2024-07-22 11:34:52 CEST > (1721640892) > Mapped data saved to archive successfully for period 1. > Calculating missing derived observations ... > Processing record: 140; Last record: 2024-07-23 00:00:00 CEST (1721685600) > Recalculating daily summaries... > Finished recalculating daily summaries > Finished calculating missing derived observations > Finished import > 139 records were processed and 139 unique records imported in 0.28 seconds. > Those records with a timestamp already in the archive will not have been > imported. Confirm successful import in the weectl log file. > area 30 31 > > -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/7b7c650d-ad66-4e00-af2d-1da83d2fd4dcn%40googlegroups.com.
[weewx-user] What do I need?
You suggested the the 'Davis Instruments 6510USB WeatherLink USB Data Logger and Software for Windows'. I don't use Windows, I have Ubuntu 22.04. Are you saying that I need something that communicates via USB not WiFi? I had a Davis Vanage Vue in Colorado from 2006 to 2014 and I had to buy that product to convert from my console to USB to my computer. Is the WetherLink-Live model 6100 not compatible with WeeWx? How would I connect from the new console using the data logger? I was not going to get the console but rather just the WetherLink-Live 6100. -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/b268b16b-32fa-4cb8-9be5-c89dbfdfb9dcn%40googlegroups.com.
[weewx-user] Re: What do I need?
Uncertain what exactly you're asking there. Are you replying to a post that isn't visible or an email or something perhaps ? If you have the old original 1970s-LCD-looking ugly console, you can use the absurdly overpriced Davis USB or serial datalogger to connect it to your weewx computer (and throw the unnecessary Windows software in the trash). I have a serial version and use a serial2usb converter to connect it to my raspi. There are a variety of third-party variants that do basically the same thing for less cost. Meteopi is one of those. https://www.scaledinstruments.com/product-category/shop-by-category/data-loggers/ has some others. If you have the new tablet-like color console, you can not connect that directly to your weewx computer because Davis provides no way to do so at all. There's also no programming interface. Ugh. The WLL 6100 is on sale at scientificsales.com currently it seems if that's what you're wanting to buy, but I can't speak to how to connect that to weewx. If you have a rtl-sdr antenna and dongle you 'can' sniff the RF from the ISS sensor directly with the rtldavis driver but that's a little painful to get working. Once you do so, it seems pretty stable, although you do miss data if your weewx computer goes down. There's no data logger in that setup, just an antenna that can hear the RF. On Monday, July 22, 2024 at 1:38:48 PM UTC-7 Barton Phillips wrote: > You suggested the the 'Davis Instruments 6510USB WeatherLink USB Data > Logger and Software for Windows'. I don't use Windows, I have Ubuntu > 22.04. Are you saying that I need something that communicates via USB not > WiFi? I had a Davis Vanage Vue in Colorado from 2006 to 2014 and I had to > buy that product to convert from my console to USB to my computer. Is the > WetherLink-Live model 6100 not compatible with WeeWx? How would I connect > from the new console using the data logger? I was not going to get the > console but rather just the WetherLink-Live 6100. > -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/61c542cb-19af-46a3-bc74-a03ab336fbf8n%40googlegroups.com.
[weewx-user] Re: RAM is running full. Apparently it's due to the weectl import
A few questions for you: - why do you believe weectl import is the cause of your memory leak problem? - what does the WeeWX log say? - what do you mean by "I have now seen that the weectl import service is not stopped". weectl import is a plain ordinary python utility that is run from the command line, it is not a WeeWX (or system) service. - regards your second post, I'm not seeing anything unusual there: weectl import was run and appears to have completed execution normal, then ctl-C seems to have been pressed. Exactly what did you do (ie commands entered, keys pressed)? Gary On Tuesday 23 July 2024 at 05:15:49 UTC+10 sebastian...@googlemail.com wrote: > > One more note > The message appears after cancellation > > > Finished calculating missing derived observations > Finished import > 248 records were processed and 248 unique records imported in 0.42 seconds. > > Those records with a timestamp already in the archive will not have been > imported. Confirm successful import in the weectl log file. > ^CException ignored in: '/usr/lib/python3.11/threading.py'> > Traceback (most recent call last): > File "/usr/lib/python3.11/threading.py", line 1590, in _shutdown > lock.acquire() > KeyboardInterrupt: > root@weewx5:~# > > Sebastian E schrieb am Montag, 22. Juli 2024 um 13:56:45 UTC+2: > >> Hello everyone, I currently have the problem that my RAM is regularly >> full and I have to restart the server. >> >> I have now seen that the weectl import service is not stopped. I'm >> attaching the output. Does anyone have an idea what this Area 31 30 means? >> That's where it seems to hang. Thank you >> >> >> root@weewx5:~# weectl import >> --import-config=/etc/weewx/import/wu-example.conf --no-prompt --verbose >> Using configuration file /etc/weewx/weewx.conf >> Starting weectl import... >> Observation history for Weather Underground station 'I*' will be >> imported. >> The following options will be used: >> config=/etc/weewx/weewx.conf, >> import-config=/etc/weewx/import/wu-example.conf >> station=I**, from=None, to=None >> apiKey=** >> dry-run=False, calc_missing=True, ignore_invalid_data=True >> tranche=250, interval=5, wind_direction=[0.0, 360.0] >> Using database binding 'wx_binding', which is bound to database >> 'weewx.sdb' >> Destination table 'archive' unit system is '0x10' (METRIC). >> The following imported field-to-WeeWX field map will be used: >> source field 'epoch' in units 'unix_epoch' --> WeeWX field 'dateTime' >> source field 'tempAvg' in units 'degree_F' --> WeeWX field 'outTemp' >> source field 'humidityAvg' in units 'percent' --> WeeWX field >> 'outHumidity' >> source field 'dewptAvg' in units 'degree_F' --> WeeWX field 'dewpoint' >> source field 'heatindexAvg' in units 'degree_F' --> WeeWX field >> 'heatindex' >> source field 'windchillAvg' in units 'degree_F' --> WeeWX field >> 'windchill' >> source field 'pressureAvg' in units 'inHg' --> WeeWX field 'barometer' >> source field 'precipTotal' in units 'inch' --> WeeWX field 'rain' >> (source field 'precipTotal' will be treated as a cumulative value) >> source field 'precipRate' in units 'inch_per_hour' --> WeeWX field >> 'rainRate' >> source field 'windspeedAvg' in units 'mile_per_hour' --> WeeWX field >> 'windSpeed' >> source field 'winddirAvg' in units 'degree_compass' --> WeeWX field >> 'windDir' >> source field 'windgustHigh' in units 'mile_per_hour' --> WeeWX field >> 'windGust' >> source field 'solarRadiationHigh' in units 'watt_per_meter_squared' --> >> WeeWX field 'radiation' >> source field 'uvHigh' in units 'uv_index' --> WeeWX field 'UV' >> Missing derived observations will be calculated. >> Starting import ... >> Records covering multiple periods have been identified for import. >> Obtaining raw import data for period 1 ... >> Raw import data read successfully for period 1. >> Mapping raw import data for period 1 ... >> Mapped 139 records. >> Raw import data mapped successfully for period 1. >> Saving mapped data to archive for period 1 ... >> 139 records identified for import. >> Unique records processed: 139; Last timestamp: 2024-07-22 11:34:52 CEST >> (1721640892) >> Mapped data saved to archive successfully for period 1. >> Calculating missing derived observations ... >> Processing record: 140; Last record: 2024-07-23 00:00:00 CEST (1721685600) >> Recalculating daily summaries... >> Finished recalculating daily summaries >> Finished calculating missing derived observations >> Finished import >> 139 records were processed and 139 unique records imported in 0.28 >> seconds. >> Those records with a timestamp already in the archive will not have been >> imported. Confirm successful import in the weectl log file. >> area 30 31 >> >> -- 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 weewx-user+unsubscr...@googlegroups.com. To view this
[weewx-user] Re: What do I need?
I am sorry for the confusion. I had emailed Tom Keffer with some questions about the WLL model 6100 and he answered me saying I should use the Windows Data Logger. I replied that I do not use Windows; I use Ubuntu 22.04 Linux. I asked if the Vantage Vue plus the WLL would work. He replied that I should post on the weewx-user group. I have not purchased either the Vantage Vue or the WLL yet as I want to make sure that they will work with weewx. I had a AcuRite Isis 5 in 1 that I sent back to Amazon because I could not figure out how to capture the WiFi that is sent to Weather Underground. So that is the rest of the story. Now I want to know if the weewx program can be used with the Vantage Vue and the WLL before I purchase them from Amazon. The WLL has both WiFi and an Eithernet port. It does not have USB. Can the Eithernet be run into my desktop computer (it does not have WiFi) and can I somehow capture the data and route it to weewx? Does weewx only work with serial or USB? Thanks. On Monday, July 22, 2024 at 6:09:24 PM UTC-4 vince wrote: > Uncertain what exactly you're asking there. Are you replying to a post > that isn't visible or an email or something perhaps ? > > If you have the old original 1970s-LCD-looking ugly console, you can use > the absurdly overpriced Davis USB or serial datalogger to connect it to > your weewx computer (and throw the unnecessary Windows software in the > trash). I have a serial version and use a serial2usb converter to connect > it to my raspi. There are a variety of third-party variants that do > basically the same thing for less cost. Meteopi is one of those. > https://www.scaledinstruments.com/product-category/shop-by-category/data-loggers/ > > has some others. > > If you have the new tablet-like color console, you can not connect that > directly to your weewx computer because Davis provides no way to do so at > all. There's also no programming interface. Ugh. > > The WLL 6100 is on sale at scientificsales.com currently it seems if > that's what you're wanting to buy, but I can't speak to how to connect that > to weewx. > > If you have a rtl-sdr antenna and dongle you 'can' sniff the RF from the > ISS sensor directly with the rtldavis driver but that's a little painful to > get working. Once you do so, it seems pretty stable, although you do miss > data if your weewx computer goes down. There's no data logger in that > setup, just an antenna that can hear the RF. > > On Monday, July 22, 2024 at 1:38:48 PM UTC-7 Barton Phillips wrote: > >> You suggested the the 'Davis Instruments 6510USB WeatherLink USB Data >> Logger and Software for Windows'. I don't use Windows, I have Ubuntu >> 22.04. Are you saying that I need something that communicates via USB not >> WiFi? I had a Davis Vanage Vue in Colorado from 2006 to 2014 and I had to >> buy that product to convert from my console to USB to my computer. Is the >> WetherLink-Live model 6100 not compatible with WeeWx? How would I connect >> from the new console using the data logger? I was not going to get the >> console but rather just the WetherLink-Live 6100. >> > -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e3807b02-172d-40bc-8e3a-205dd4f07eban%40googlegroups.com.
[weewx-user] Re: What do I need?
No, weewx supports all kinds of interfaces including network depending on which gear you have. Tom was likely suggesting the hardware datalogger because it 'is' pretty nice if you have the old console and can direct connect to the weewx system because of the logging and backfill functionality, but there are a lot of ways of connecting stuff up end to end. There are a bunch of old WLL drivers if you google search for "weewx WLL" and poke around a bit. (wow - I wrote one too ages ago according to https://www.wxforum.net/index.php?topic=41328.0 that I again forgot. Back then in 2020 a bunch of folks did initial versions.) https://github.com/michael-slx/weewx-weatherlink-live seems most current and maintained. A quick search of the weewx map shows over 35 registered WLL systems so there have to be a lot more actual users. A quick look at the driver's installation web page seems to say you need to configure the ip address of the WLL device so weewx can talk to it over the network, so you probably are looking pretty good for a Vue plus WLL unless I'm reading it wrong. I can't speak to whether there are lower cost options, but if it was 'me' considering I have the gear, I'd just do a Vue sensor suite and rtldavis using a rtl-sdr dongle and antenna (which I already have) so that gets it into the $100 plus Vue sensor suite kind of price range. WLL adds more stuff of course and is more turnkey at some large additional price. Really comes down to the time-value of your labor and blood pressure to integrate and support it all. On Monday, July 22, 2024 at 5:20:14 PM UTC-7 Barton Phillips wrote: > I am sorry for the confusion. I had emailed Tom Keffer with some questions > about the WLL model 6100 and he answered me saying I should use the Windows > Data Logger. I replied that I do not use Windows; I use Ubuntu 22.04 Linux. > I asked if the Vantage Vue plus the WLL would work. He replied that I > should post on the weewx-user group. I have not purchased either the > Vantage Vue or the WLL yet as I want to make sure that they will work with > weewx. I had a AcuRite Isis 5 in 1 that I sent back to Amazon because I > could not figure out how to capture the WiFi that is sent to Weather > Underground. So that is the rest of the story. > > Now I want to know if the weewx program can be used with the Vantage Vue > and the WLL before I purchase them from Amazon. The WLL has both WiFi and > an Eithernet port. It does not have USB. Can the Eithernet be run into my > desktop computer (it does not have WiFi) and can I somehow capture the data > and route it to weewx? Does weewx only work with serial or USB? > > Thanks. > > On Monday, July 22, 2024 at 6:09:24 PM UTC-4 vince wrote: > >> Uncertain what exactly you're asking there. Are you replying to a post >> that isn't visible or an email or something perhaps ? >> >> If you have the old original 1970s-LCD-looking ugly console, you can use >> the absurdly overpriced Davis USB or serial datalogger to connect it to >> your weewx computer (and throw the unnecessary Windows software in the >> trash). I have a serial version and use a serial2usb converter to connect >> it to my raspi. There are a variety of third-party variants that do >> basically the same thing for less cost. Meteopi is one of those. >> https://www.scaledinstruments.com/product-category/shop-by-category/data-loggers/ >> >> has some others. >> >> If you have the new tablet-like color console, you can not connect that >> directly to your weewx computer because Davis provides no way to do so at >> all. There's also no programming interface. Ugh. >> >> The WLL 6100 is on sale at scientificsales.com currently it seems if >> that's what you're wanting to buy, but I can't speak to how to connect that >> to weewx. >> >> If you have a rtl-sdr antenna and dongle you 'can' sniff the RF from the >> ISS sensor directly with the rtldavis driver but that's a little painful to >> get working. Once you do so, it seems pretty stable, although you do miss >> data if your weewx computer goes down. There's no data logger in that >> setup, just an antenna that can hear the RF. >> >> On Monday, July 22, 2024 at 1:38:48 PM UTC-7 Barton Phillips wrote: >> >>> You suggested the the 'Davis Instruments 6510USB WeatherLink USB Data >>> Logger and Software for Windows'. I don't use Windows, I have Ubuntu >>> 22.04. Are you saying that I need something that communicates via USB not >>> WiFi? I had a Davis Vanage Vue in Colorado from 2006 to 2014 and I had to >>> buy that product to convert from my console to USB to my computer. Is the >>> WetherLink-Live model 6100 not compatible with WeeWx? How would I connect >>> from the new console using the data logger? I was not going to get the >>> console but rather just the WetherLink-Live 6100. >>> >> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group an
[weewx-user] Re: RAM is running full. Apparently it's due to the weectl import
Gary, may be, it is a little bit of a language problem. I heard of this case before, so I may add some explanation, but I cannot explain all. The user seems to call weectl import from the command line or from crontab to retrieve data from Wunderground. The command first runs as expected. Data is imported and saved to the database. But then, the command does not end. It hangs. So I suggested to the user to press CTRL-C several times. This resulted in an error message saying that the command hang in the threading module while waiting for a lock. First question: Where does weectl import use threading? Or does this point to the problem that threading is involved at all? I had a short glance at the sources, but I did not see it. Then, there are some hints that third party extensions are involved in the problem. Does weectl import load WeeWX extensions? I do not see a reason to do so. But the output "area 30 31" at the end of the first post is from an extension, not from the command itself. Karen -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/d5c8d2e7-aa8c-4ac1-8352-ce12ac0db156n%40googlegroups.com.
Re: [weewx-user] RAM is running full. Apparently it's due to the weectl import
is the transaction buffer over-running avail memory? can the tranche of updates be reduced per transaction? ⊣GE⊢ > On 23 Jul 2024, at 3:08 PM, Karen K wrote: > > The user seems to call weectl import from the command line or from crontab to > retrieve data from Wunderground. The command first runs as expected. Data is > imported and saved to the database. But then, the command does not end. It > hangs. So I suggested to the user to press CTRL-C several times -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/C2C0D52E-ED0F-4F20-A171-8119F533EA2D%40geddy.au.
[weewx-user] Re: RAM is running full. Apparently it's due to the weectl import
So if ctl-C is being used to interrupt a script, the script must be being run from the command line; ctl-C will have no effect on scripts executed by cron. weectl import does not directly use threading, however, weectl import uses a number of WeeWX 'API' calls to do things (save data to database and calculate missing/derived obs are the two main ones). I would suggest this use of threading is possibly due to an xtype call when calculating missing/derived obs. weectl import does not 'load' any extensions per se; however, that is not to say that some other parts of WeeWX called by weectl import do not. Again an xtype being used to calculate missing/derived obs is an obvious candidate. I don't see the 'area 30 31' output being direct weectl import output, quite possibly it is output from some other extension. To start tracking this down we need to go back to basics with log and config. What does the WeeWX log shown when weectl import is run? And what is in weewx.conf (and to a lesser extent) the import config file /etc/weewx/import/wu-example.conf. Gary On Tuesday 23 July 2024 at 15:08:09 UTC+10 kk44...@gmail.com wrote: > Gary, > > may be, it is a little bit of a language problem. I heard of this case > before, so I may add some explanation, but I cannot explain all. > > The user seems to call weectl import from the command line or from > crontab to retrieve data from Wunderground. The command first runs as > expected. Data is imported and saved to the database. But then, the command > does not end. It hangs. So I suggested to the user to press CTRL-C several > times. This resulted in an error message saying that the command hang in > the threading module while waiting for a lock. > > First question: Where does weectl import use threading? Or does this > point to the problem that threading is involved at all? > > I had a short glance at the sources, but I did not see it. > > Then, there are some hints that third party extensions are involved in the > problem. Does weectl import load WeeWX extensions? I do not see a reason > to do so. But the output "area 30 31" at the end of the first post is > from an extension, not from the command itself. > > Karen > > -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/055517ed-93d0-4cc6-9b70-a26d949445b0n%40googlegroups.com.
