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
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
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
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
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 comm
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
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,
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 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 r
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
10 matches
Mail list logo
