Re: [weewx-user] weewx failure after power loos

[valken...@gmail.com]

Allright, I managed to get someone on the spot and push the right buttons 
on the ultimeter to get it in logger mode. The weewxd output immediately 
started to make sense.  It appeared the power outage had reset the 
ultimeter to its defaults. Pressure had to be recalibrated as well. The 
backup battery in the ultimeter had died over time, and will be replaced. 
But at least everything is running fine again. Sorry to bother you for 
this, but thanks for your effort. It just helped me to search in the right 
direction! Weewx is great!

Op vrijdag 28 mei 2021 om 17:18:15 UTC+2 schreef tke...@gmail.com:

> I think you're right. The '&CR&' header you are seeing is typical of 
> "Complete Record Mode". You want data logger mode.
>
> On Fri, May 28, 2021 at 8:12 AM valken...@gmail.com  
> wrote:
>
>> I meant both the ultimeter and the server are both at a remote loaction, 
>> and conected by a classical serial cable. They are on Island where in 
>> summer sailing regattas are held. There is a wireless internet link to the 
>> location. So I don't have the setup right here under my hands, but I'm able 
>> to log in by VPN. But off course it's not impossible to get there. I think 
>> the Ultimeter is talking in the wrong mode.
>>
>> Op vrijdag 28 mei 2021 om 17:05:51 UTC+2 schreef tke...@gmail.com:
>>
>>> Looking at the Peet Bros protocol 
>>> , they say the baud 
>>> rate is 2,400, so you got that right. Make sure it's 8 data bits, 1 stop 
>>> bit, no parity.
>>>
>>> Something I'm not understanding: you are using port /dev/ttyS0, which is 
>>> a typical serial port. However, the Ultimeter is at a remote location. How 
>>> does it connect to the port? Perhaps the problem is somewhere in that link?
>>>
>>> On Fri, May 28, 2021 at 7:51 AM valken...@gmail.com  
>>> wrote:
>>>
 Thnx again. I think it must be the right port since there is only 1 
 serial device connected. If you say the output of ttyS0 is not normal 
 ultimeter output, i assume we found the cause of the disfunctioning.  I 
 used baud rate 2400 for the screen command. The output is not readable 
 indeed, but it is a flow of data. Maybe the unit is not in logger mode 
 since teh power outage. Unfornately the station is at a remote location. 
 I'll see if i can get someone up there to check the Ultimeter and the 
 setup. I'll let you know.

 Op vrijdag 28 mei 2021 om 16:15:07 UTC+2 schreef tke...@gmail.com:

> That does not look like the Ultimeter protocol, which typically has 
> double exclamation points ('!!') every 42, 46, or 50 bytes. Are you sure 
> you have the baud rate correct? Have the right port?
>
> On Fri, May 28, 2021 at 6:31 AM valken...@gmail.com <
> valken...@gmail.com> wrote:
>
>> screen /dev/ttyS0 2400 shows me:
>>
>> &CR&004900D9008400EB026E026E026A056901B7021701B7021701CD030601CD03062BA7004300DA2BA7022C022C03F203F203F203F2013900200139002002E503ED004300DA02E503ED13D313D3026A0559026A05590001DC00DC2D
>> &CR&004500D2008400EB026E026E02690569 
>> etcetera
>>
>> Op vrijdag 28 mei 2021 om 15:08:56 UTC+2 schreef valken...@gmail.com:
>>
>>> Exactly nothing happens:
>>>
>>> @kwsweerstation:/etc/weewx# weewxd
>>>
>>> And then the screen stays completely blank..
>>>
>>> Op vrijdag 28 mei 2021 om 15:00:08 UTC+2 schreef tke...@gmail.com:
>>>
 What happens when you run weewxd directly from the console?

 On Fri, May 28, 2021 at 5:54 AM valken...@gmail.com <
 valken...@gmail.com> wrote:

> Dear Tom,
>
> Thank you for your answer. You are right. This is a very short 
> interval. I let it run much longer earlier, and nothing else showed 
> up in 
> the logs. Indeed, I quit weewx by systemctl stop weewx. Then I 
> noticed this 
> error, an I assumed it might yield an answer. To get a clean piece of 
> logs,  did a start and stop in a short time. (But that's not helpful 
> I 
> understand now.) I did run weewxd (after stopping weewx), but it show 
> no 
> output whatsoever. Just nothing. Blank. So now data received from 
> ttyS0? 
> When i start weewx by systemctl. The log gives me the same output. 
> The last log entry is: 
> kwsweerstation weewx[12255] DEBUG weewx.manager: Daily summary 
> version is 4.0
>
> After that no further entries appear. The rest of the log above 
> this entry is exactly similar to the log shown in the openig post. I 
> thi

Re: [weewx-user] weewx failure after power loos

[Tom Keffer]

I think you're right. The '&CR&' header you are seeing is typical of
"Complete Record Mode". You want data logger mode.

On Fri, May 28, 2021 at 8:12 AM valken...@gmail.com 
wrote:

> I meant both the ultimeter and the server are both at a remote loaction,
> and conected by a classical serial cable. They are on Island where in
> summer sailing regattas are held. There is a wireless internet link to the
> location. So I don't have the setup right here under my hands, but I'm able
> to log in by VPN. But off course it's not impossible to get there. I think
> the Ultimeter is talking in the wrong mode.
>
> Op vrijdag 28 mei 2021 om 17:05:51 UTC+2 schreef tke...@gmail.com:
>
>> Looking at the Peet Bros protocol
>> , they say the baud
>> rate is 2,400, so you got that right. Make sure it's 8 data bits, 1 stop
>> bit, no parity.
>>
>> Something I'm not understanding: you are using port /dev/ttyS0, which is
>> a typical serial port. However, the Ultimeter is at a remote location. How
>> does it connect to the port? Perhaps the problem is somewhere in that link?
>>
>> On Fri, May 28, 2021 at 7:51 AM valken...@gmail.com 
>> wrote:
>>
>>> Thnx again. I think it must be the right port since there is only 1
>>> serial device connected. If you say the output of ttyS0 is not normal
>>> ultimeter output, i assume we found the cause of the disfunctioning.  I
>>> used baud rate 2400 for the screen command. The output is not readable
>>> indeed, but it is a flow of data. Maybe the unit is not in logger mode
>>> since teh power outage. Unfornately the station is at a remote location.
>>> I'll see if i can get someone up there to check the Ultimeter and the
>>> setup. I'll let you know.
>>>
>>> Op vrijdag 28 mei 2021 om 16:15:07 UTC+2 schreef tke...@gmail.com:
>>>
 That does not look like the Ultimeter protocol, which typically has
 double exclamation points ('!!') every 42, 46, or 50 bytes. Are you sure
 you have the baud rate correct? Have the right port?

 On Fri, May 28, 2021 at 6:31 AM valken...@gmail.com <
 valken...@gmail.com> wrote:

> screen /dev/ttyS0 2400 shows me:
>
> &CR&004900D9008400EB026E026E026A056901B7021701B7021701CD030601CD03062BA7004300DA2BA7022C022C03F203F203F203F2013900200139002002E503ED004300DA02E503ED13D313D3026A0559026A05590001DC00DC2D
> &CR&004500D2008400EB026E026E02690569
> etcetera
>
> Op vrijdag 28 mei 2021 om 15:08:56 UTC+2 schreef valken...@gmail.com:
>
>> Exactly nothing happens:
>>
>> @kwsweerstation:/etc/weewx# weewxd
>>
>> And then the screen stays completely blank..
>>
>> Op vrijdag 28 mei 2021 om 15:00:08 UTC+2 schreef tke...@gmail.com:
>>
>>> What happens when you run weewxd directly from the console?
>>>
>>> On Fri, May 28, 2021 at 5:54 AM valken...@gmail.com <
>>> valken...@gmail.com> wrote:
>>>
 Dear Tom,

 Thank you for your answer. You are right. This is a very short
 interval. I let it run much longer earlier, and nothing else showed up 
 in
 the logs. Indeed, I quit weewx by systemctl stop weewx. Then I noticed 
 this
 error, an I assumed it might yield an answer. To get a clean piece of
 logs,  did a start and stop in a short time. (But that's not helpful I
 understand now.) I did run weewxd (after stopping weewx), but it show 
 no
 output whatsoever. Just nothing. Blank. So now data received from 
 ttyS0?
 When i start weewx by systemctl. The log gives me the same output.
 The last log entry is:
 kwsweerstation weewx[12255] DEBUG weewx.manager: Daily summary
 version is 4.0

 After that no further entries appear. The rest of the log above
 this entry is exactly similar to the log shown in the openig post. I 
 think
 there is some  issue with the serial connection, although screen gives 
 me
 some encoded output.
 Op vrijdag 28 mei 2021 om 14:30:26 UTC+2 schreef tke...@gmail.com:

> In this log sample, I assume you stopped weewx by doing something
> like "systemctl stop weewx". If so, the "error in the log" is just the
> normal shutdown chatter and doesn't mean anything.
>
> In this sample, there is only 3 seconds between when weewx had
> finished initializing, and when the shutdown sequence started. That's 
> not
> enough time to judge whether weewx was doing anything.
>
> Suggestions:
> 1. Let it run longer. At least

Re: [weewx-user] weewx failure after power loos

[valken...@gmail.com]

I meant both the ultimeter and the server are both at a remote loaction, 
and conected by a classical serial cable. They are on Island where in 
summer sailing regattas are held. There is a wireless internet link to the 
location. So I don't have the setup right here under my hands, but I'm able 
to log in by VPN. But off course it's not impossible to get there. I think 
the Ultimeter is talking in the wrong mode.

Op vrijdag 28 mei 2021 om 17:05:51 UTC+2 schreef tke...@gmail.com:

> Looking at the Peet Bros protocol 
> , they say the baud 
> rate is 2,400, so you got that right. Make sure it's 8 data bits, 1 stop 
> bit, no parity.
>
> Something I'm not understanding: you are using port /dev/ttyS0, which is a 
> typical serial port. However, the Ultimeter is at a remote location. How 
> does it connect to the port? Perhaps the problem is somewhere in that link?
>
> On Fri, May 28, 2021 at 7:51 AM valken...@gmail.com  
> wrote:
>
>> Thnx again. I think it must be the right port since there is only 1 
>> serial device connected. If you say the output of ttyS0 is not normal 
>> ultimeter output, i assume we found the cause of the disfunctioning.  I 
>> used baud rate 2400 for the screen command. The output is not readable 
>> indeed, but it is a flow of data. Maybe the unit is not in logger mode 
>> since teh power outage. Unfornately the station is at a remote location. 
>> I'll see if i can get someone up there to check the Ultimeter and the 
>> setup. I'll let you know.
>>
>> Op vrijdag 28 mei 2021 om 16:15:07 UTC+2 schreef tke...@gmail.com:
>>
>>> That does not look like the Ultimeter protocol, which typically has 
>>> double exclamation points ('!!') every 42, 46, or 50 bytes. Are you sure 
>>> you have the baud rate correct? Have the right port?
>>>
>>> On Fri, May 28, 2021 at 6:31 AM valken...@gmail.com  
>>> wrote:
>>>
 screen /dev/ttyS0 2400 shows me:

 &CR&004900D9008400EB026E026E026A056901B7021701B7021701CD030601CD03062BA7004300DA2BA7022C022C03F203F203F203F2013900200139002002E503ED004300DA02E503ED13D313D3026A0559026A05590001DC00DC2D
 &CR&004500D2008400EB026E026E02690569 
 etcetera

 Op vrijdag 28 mei 2021 om 15:08:56 UTC+2 schreef valken...@gmail.com:

> Exactly nothing happens:
>
> @kwsweerstation:/etc/weewx# weewxd
>
> And then the screen stays completely blank..
>
> Op vrijdag 28 mei 2021 om 15:00:08 UTC+2 schreef tke...@gmail.com:
>
>> What happens when you run weewxd directly from the console?
>>
>> On Fri, May 28, 2021 at 5:54 AM valken...@gmail.com <
>> valken...@gmail.com> wrote:
>>
>>> Dear Tom,
>>>
>>> Thank you for your answer. You are right. This is a very short 
>>> interval. I let it run much longer earlier, and nothing else showed up 
>>> in 
>>> the logs. Indeed, I quit weewx by systemctl stop weewx. Then I noticed 
>>> this 
>>> error, an I assumed it might yield an answer. To get a clean piece of 
>>> logs,  did a start and stop in a short time. (But that's not helpful I 
>>> understand now.) I did run weewxd (after stopping weewx), but it show 
>>> no 
>>> output whatsoever. Just nothing. Blank. So now data received from 
>>> ttyS0? 
>>> When i start weewx by systemctl. The log gives me the same output. 
>>> The last log entry is: 
>>> kwsweerstation weewx[12255] DEBUG weewx.manager: Daily summary 
>>> version is 4.0
>>>
>>> After that no further entries appear. The rest of the log above this 
>>> entry is exactly similar to the log shown in the openig post. I think 
>>> there 
>>> is some  issue with the serial connection, although screen gives me 
>>> some 
>>> encoded output. 
>>> Op vrijdag 28 mei 2021 om 14:30:26 UTC+2 schreef tke...@gmail.com:
>>>
 In this log sample, I assume you stopped weewx by doing something 
 like "systemctl stop weewx". If so, the "error in the log" is just the 
 normal shutdown chatter and doesn't mean anything.

 In this sample, there is only 3 seconds between when weewx had 
 finished initializing, and when the shutdown sequence started. That's 
 not 
 enough time to judge whether weewx was doing anything.

 Suggestions:
 1. Let it run longer. At least an archive period.
 2. Alternatively, run weewxd directly from the console 
  for a 
 while. It will print out LOOP packets as they arrive, allowing you to 
 check 
 wh

Re: [weewx-user] weewx failure after power loos

[Tom Keffer]

Looking at the Peet Bros protocol
, they say the baud
rate is 2,400, so you got that right. Make sure it's 8 data bits, 1 stop
bit, no parity.

Something I'm not understanding: you are using port /dev/ttyS0, which is a
typical serial port. However, the Ultimeter is at a remote location. How
does it connect to the port? Perhaps the problem is somewhere in that link?

On Fri, May 28, 2021 at 7:51 AM valken...@gmail.com 
wrote:

> Thnx again. I think it must be the right port since there is only 1 serial
> device connected. If you say the output of ttyS0 is not normal ultimeter
> output, i assume we found the cause of the disfunctioning.  I used baud
> rate 2400 for the screen command. The output is not readable indeed, but it
> is a flow of data. Maybe the unit is not in logger mode since teh power
> outage. Unfornately the station is at a remote location. I'll see if i can
> get someone up there to check the Ultimeter and the setup. I'll let you
> know.
>
> Op vrijdag 28 mei 2021 om 16:15:07 UTC+2 schreef tke...@gmail.com:
>
>> That does not look like the Ultimeter protocol, which typically has
>> double exclamation points ('!!') every 42, 46, or 50 bytes. Are you sure
>> you have the baud rate correct? Have the right port?
>>
>> On Fri, May 28, 2021 at 6:31 AM valken...@gmail.com 
>> wrote:
>>
>>> screen /dev/ttyS0 2400 shows me:
>>>
>>> &CR&004900D9008400EB026E026E026A056901B7021701B7021701CD030601CD03062BA7004300DA2BA7022C022C03F203F203F203F2013900200139002002E503ED004300DA02E503ED13D313D3026A0559026A05590001DC00DC2D
>>> &CR&004500D2008400EB026E026E02690569
>>> etcetera
>>>
>>> Op vrijdag 28 mei 2021 om 15:08:56 UTC+2 schreef valken...@gmail.com:
>>>
 Exactly nothing happens:

 @kwsweerstation:/etc/weewx# weewxd

 And then the screen stays completely blank..

 Op vrijdag 28 mei 2021 om 15:00:08 UTC+2 schreef tke...@gmail.com:

> What happens when you run weewxd directly from the console?
>
> On Fri, May 28, 2021 at 5:54 AM valken...@gmail.com <
> valken...@gmail.com> wrote:
>
>> Dear Tom,
>>
>> Thank you for your answer. You are right. This is a very short
>> interval. I let it run much longer earlier, and nothing else showed up in
>> the logs. Indeed, I quit weewx by systemctl stop weewx. Then I noticed 
>> this
>> error, an I assumed it might yield an answer. To get a clean piece of
>> logs,  did a start and stop in a short time. (But that's not helpful I
>> understand now.) I did run weewxd (after stopping weewx), but it show no
>> output whatsoever. Just nothing. Blank. So now data received from ttyS0?
>> When i start weewx by systemctl. The log gives me the same output.
>> The last log entry is:
>> kwsweerstation weewx[12255] DEBUG weewx.manager: Daily summary
>> version is 4.0
>>
>> After that no further entries appear. The rest of the log above this
>> entry is exactly similar to the log shown in the openig post. I think 
>> there
>> is some  issue with the serial connection, although screen gives me some
>> encoded output.
>> Op vrijdag 28 mei 2021 om 14:30:26 UTC+2 schreef tke...@gmail.com:
>>
>>> In this log sample, I assume you stopped weewx by doing something
>>> like "systemctl stop weewx". If so, the "error in the log" is just the
>>> normal shutdown chatter and doesn't mean anything.
>>>
>>> In this sample, there is only 3 seconds between when weewx had
>>> finished initializing, and when the shutdown sequence started. That's 
>>> not
>>> enough time to judge whether weewx was doing anything.
>>>
>>> Suggestions:
>>> 1. Let it run longer. At least an archive period.
>>> 2. Alternatively, run weewxd directly from the console
>>>  for a
>>> while. It will print out LOOP packets as they arrive, allowing you to 
>>> check
>>> whether weewx is properly receiving data.
>>>
>>> -tk
>>>
>>> On Fri, May 28, 2021 at 5:03 AM valken...@gmail.com <
>>> valken...@gmail.com> wrote:
>>>
 Hi,
 Iḿ having troubles with a weewx inatance running on ubuntu 20.
 After an unforseen power outage, the system came back up, but weewx 
 stopped
 processing data. The system is connected to an ulitmeter 2100 via 
 ttyS0.
 With screen I do see data on that port. However weewx starts, and does
 nothing. No errors in the log, no activity at actually after starting
 weewx. If I manually stop weewx, it results i

Re: [weewx-user] weewx failure after power loos

[valken...@gmail.com]

Thnx again. I think it must be the right port since there is only 1 serial 
device connected. If you say the output of ttyS0 is not normal ultimeter 
output, i assume we found the cause of the disfunctioning.  I used baud 
rate 2400 for the screen command. The output is not readable indeed, but it 
is a flow of data. Maybe the unit is not in logger mode since teh power 
outage. Unfornately the station is at a remote location. I'll see if i can 
get someone up there to check the Ultimeter and the setup. I'll let you 
know.

Op vrijdag 28 mei 2021 om 16:15:07 UTC+2 schreef tke...@gmail.com:

> That does not look like the Ultimeter protocol, which typically has double 
> exclamation points ('!!') every 42, 46, or 50 bytes. Are you sure you have 
> the baud rate correct? Have the right port?
>
> On Fri, May 28, 2021 at 6:31 AM valken...@gmail.com  
> wrote:
>
>> screen /dev/ttyS0 2400 shows me:
>>
>> &CR&004900D9008400EB026E026E026A056901B7021701B7021701CD030601CD03062BA7004300DA2BA7022C022C03F203F203F203F2013900200139002002E503ED004300DA02E503ED13D313D3026A0559026A05590001DC00DC2D
>> &CR&004500D2008400EB026E026E02690569 
>> etcetera
>>
>> Op vrijdag 28 mei 2021 om 15:08:56 UTC+2 schreef valken...@gmail.com:
>>
>>> Exactly nothing happens:
>>>
>>> @kwsweerstation:/etc/weewx# weewxd
>>>
>>> And then the screen stays completely blank..
>>>
>>> Op vrijdag 28 mei 2021 om 15:00:08 UTC+2 schreef tke...@gmail.com:
>>>
 What happens when you run weewxd directly from the console?

 On Fri, May 28, 2021 at 5:54 AM valken...@gmail.com <
 valken...@gmail.com> wrote:

> Dear Tom,
>
> Thank you for your answer. You are right. This is a very short 
> interval. I let it run much longer earlier, and nothing else showed up in 
> the logs. Indeed, I quit weewx by systemctl stop weewx. Then I noticed 
> this 
> error, an I assumed it might yield an answer. To get a clean piece of 
> logs,  did a start and stop in a short time. (But that's not helpful I 
> understand now.) I did run weewxd (after stopping weewx), but it show no 
> output whatsoever. Just nothing. Blank. So now data received from ttyS0? 
> When i start weewx by systemctl. The log gives me the same output. The 
> last log entry is: 
> kwsweerstation weewx[12255] DEBUG weewx.manager: Daily summary version 
> is 4.0
>
> After that no further entries appear. The rest of the log above this 
> entry is exactly similar to the log shown in the openig post. I think 
> there 
> is some  issue with the serial connection, although screen gives me some 
> encoded output. 
> Op vrijdag 28 mei 2021 om 14:30:26 UTC+2 schreef tke...@gmail.com:
>
>> In this log sample, I assume you stopped weewx by doing something 
>> like "systemctl stop weewx". If so, the "error in the log" is just the 
>> normal shutdown chatter and doesn't mean anything.
>>
>> In this sample, there is only 3 seconds between when weewx had 
>> finished initializing, and when the shutdown sequence started. That's 
>> not 
>> enough time to judge whether weewx was doing anything.
>>
>> Suggestions:
>> 1. Let it run longer. At least an archive period.
>> 2. Alternatively, run weewxd directly from the console 
>>  for a 
>> while. It will print out LOOP packets as they arrive, allowing you to 
>> check 
>> whether weewx is properly receiving data. 
>>
>> -tk
>>
>> On Fri, May 28, 2021 at 5:03 AM valken...@gmail.com <
>> valken...@gmail.com> wrote:
>>
>>> Hi,
>>> Iḿ having troubles with a weewx inatance running on ubuntu 20. After 
>>> an unforseen power outage, the system came back up, but weewx stopped 
>>> processing data. The system is connected to an ulitmeter 2100 via 
>>> ttyS0. 
>>> With screen I do see data on that port. However weewx starts, and does 
>>> nothing. No errors in the log, no activity at actually after starting 
>>> weewx. If I manually stop weewx, it results in an error in the log, 
>>> before 
>>> stopping. I reinstalled weewx, emptied the database but no effect. I 
>>> just 
>>> doesn´t process data. Debug level=1. Maybe someone can help me out?
>>>
>>> Log entries:
>>>
>>> May 28 14:00:18 kwsweerstation systemd[1]: Starting LSB: weewx 
>>> weather system...
>>> May 28 14:00:18 kwsweerstation weewx[11973]:  * Starting weewx 
>>> weather system weewx
>>> May 28 14:00:18 kwsweerstation weewx[11991] INFO __main__: 
>>> Initializing weewx version 4.5.1
>

Re: [weewx-user] weewx failure after power loos

[Tom Keffer]

That does not look like the Ultimeter protocol, which typically has double
exclamation points ('!!') every 42, 46, or 50 bytes. Are you sure you have
the baud rate correct? Have the right port?

On Fri, May 28, 2021 at 6:31 AM valken...@gmail.com 
wrote:

> screen /dev/ttyS0 2400 shows me:
>
> &CR&004900D9008400EB026E026E026A056901B7021701B7021701CD030601CD03062BA7004300DA2BA7022C022C03F203F203F203F2013900200139002002E503ED004300DA02E503ED13D313D3026A0559026A05590001DC00DC2D
> &CR&004500D2008400EB026E026E02690569
> etcetera
>
> Op vrijdag 28 mei 2021 om 15:08:56 UTC+2 schreef valken...@gmail.com:
>
>> Exactly nothing happens:
>>
>> @kwsweerstation:/etc/weewx# weewxd
>>
>> And then the screen stays completely blank..
>>
>> Op vrijdag 28 mei 2021 om 15:00:08 UTC+2 schreef tke...@gmail.com:
>>
>>> What happens when you run weewxd directly from the console?
>>>
>>> On Fri, May 28, 2021 at 5:54 AM valken...@gmail.com 
>>> wrote:
>>>
 Dear Tom,

 Thank you for your answer. You are right. This is a very short
 interval. I let it run much longer earlier, and nothing else showed up in
 the logs. Indeed, I quit weewx by systemctl stop weewx. Then I noticed this
 error, an I assumed it might yield an answer. To get a clean piece of
 logs,  did a start and stop in a short time. (But that's not helpful I
 understand now.) I did run weewxd (after stopping weewx), but it show no
 output whatsoever. Just nothing. Blank. So now data received from ttyS0?
 When i start weewx by systemctl. The log gives me the same output. The
 last log entry is:
 kwsweerstation weewx[12255] DEBUG weewx.manager: Daily summary version
 is 4.0

 After that no further entries appear. The rest of the log above this
 entry is exactly similar to the log shown in the openig post. I think there
 is some  issue with the serial connection, although screen gives me some
 encoded output.
 Op vrijdag 28 mei 2021 om 14:30:26 UTC+2 schreef tke...@gmail.com:

> In this log sample, I assume you stopped weewx by doing something like
> "systemctl stop weewx". If so, the "error in the log" is just the normal
> shutdown chatter and doesn't mean anything.
>
> In this sample, there is only 3 seconds between when weewx had
> finished initializing, and when the shutdown sequence started. That's not
> enough time to judge whether weewx was doing anything.
>
> Suggestions:
> 1. Let it run longer. At least an archive period.
> 2. Alternatively, run weewxd directly from the console
>  for a
> while. It will print out LOOP packets as they arrive, allowing you to 
> check
> whether weewx is properly receiving data.
>
> -tk
>
> On Fri, May 28, 2021 at 5:03 AM valken...@gmail.com <
> valken...@gmail.com> wrote:
>
>> Hi,
>> Iḿ having troubles with a weewx inatance running on ubuntu 20. After
>> an unforseen power outage, the system came back up, but weewx stopped
>> processing data. The system is connected to an ulitmeter 2100 via ttyS0.
>> With screen I do see data on that port. However weewx starts, and does
>> nothing. No errors in the log, no activity at actually after starting
>> weewx. If I manually stop weewx, it results in an error in the log, 
>> before
>> stopping. I reinstalled weewx, emptied the database but no effect. I just
>> doesn´t process data. Debug level=1. Maybe someone can help me out?
>>
>> Log entries:
>>
>> May 28 14:00:18 kwsweerstation systemd[1]: Starting LSB: weewx
>> weather system...
>> May 28 14:00:18 kwsweerstation weewx[11973]:  * Starting weewx
>> weather system weewx
>> May 28 14:00:18 kwsweerstation weewx[11991] INFO __main__:
>> Initializing weewx version 4.5.1
>> May 28 14:00:18 kwsweerstation weewx[11991] INFO __main__: Using
>> Python 3.8.5 (default, Jan 27 2021, 15:41:15) #012[GCC 9.3.0]
>> May 28 14:00:19 kwsweerstation weewx[11991] INFO __main__: Platform
>> Linux-5.4.0-73-generic-x86_64-with-glibc2.29
>> May 28 14:00:19 kwsweerstation weewx[11991] INFO __main__: Locale is
>> 'nl_NL.UTF-8'
>> May 28 14:00:19 kwsweerstation weewx[11991] INFO __main__: PID file
>> is /var/run/weewx.pid
>> May 28 14:00:19 kwsweerstation weewx[11994] INFO __main__: Using
>> configuration file /etc/weewx/weewx.conf
>> May 28 14:00:19 kwsweerstation weewx[11994] INFO __main__: Debug is 1
>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG __main__:
>> Initializing engine
>> May 28 14:00:19 kwswee

Re: [weewx-user] weewx failure after power loos

[valken...@gmail.com]

screen /dev/ttyS0 2400 shows me:
&CR&004900D9008400EB026E026E026A056901B7021701B7021701CD030601CD03062BA7004300DA2BA7022C022C03F203F203F203F2013900200139002002E503ED004300DA02E503ED13D313D3026A0559026A05590001DC00DC2D
&CR&004500D2008400EB026E026E02690569 
etcetera

Op vrijdag 28 mei 2021 om 15:08:56 UTC+2 schreef valken...@gmail.com:

> Exactly nothing happens:
>
> @kwsweerstation:/etc/weewx# weewxd
>
> And then the screen stays completely blank..
>
> Op vrijdag 28 mei 2021 om 15:00:08 UTC+2 schreef tke...@gmail.com:
>
>> What happens when you run weewxd directly from the console?
>>
>> On Fri, May 28, 2021 at 5:54 AM valken...@gmail.com  
>> wrote:
>>
>>> Dear Tom,
>>>
>>> Thank you for your answer. You are right. This is a very short interval. 
>>> I let it run much longer earlier, and nothing else showed up in the logs. 
>>> Indeed, I quit weewx by systemctl stop weewx. Then I noticed this error, an 
>>> I assumed it might yield an answer. To get a clean piece of logs,  did a 
>>> start and stop in a short time. (But that's not helpful I understand now.) 
>>> I did run weewxd (after stopping weewx), but it show no output whatsoever. 
>>> Just nothing. Blank. So now data received from ttyS0? 
>>> When i start weewx by systemctl. The log gives me the same output. The 
>>> last log entry is: 
>>> kwsweerstation weewx[12255] DEBUG weewx.manager: Daily summary version 
>>> is 4.0
>>>
>>> After that no further entries appear. The rest of the log above this 
>>> entry is exactly similar to the log shown in the openig post. I think there 
>>> is some  issue with the serial connection, although screen gives me some 
>>> encoded output. 
>>> Op vrijdag 28 mei 2021 om 14:30:26 UTC+2 schreef tke...@gmail.com:
>>>
 In this log sample, I assume you stopped weewx by doing something like 
 "systemctl stop weewx". If so, the "error in the log" is just the normal 
 shutdown chatter and doesn't mean anything.

 In this sample, there is only 3 seconds between when weewx had finished 
 initializing, and when the shutdown sequence started. That's not enough 
 time to judge whether weewx was doing anything.

 Suggestions:
 1. Let it run longer. At least an archive period.
 2. Alternatively, run weewxd directly from the console 
  for a 
 while. It will print out LOOP packets as they arrive, allowing you to 
 check 
 whether weewx is properly receiving data. 

 -tk

 On Fri, May 28, 2021 at 5:03 AM valken...@gmail.com <
 valken...@gmail.com> wrote:

> Hi,
> Iḿ having troubles with a weewx inatance running on ubuntu 20. After 
> an unforseen power outage, the system came back up, but weewx stopped 
> processing data. The system is connected to an ulitmeter 2100 via ttyS0. 
> With screen I do see data on that port. However weewx starts, and does 
> nothing. No errors in the log, no activity at actually after starting 
> weewx. If I manually stop weewx, it results in an error in the log, 
> before 
> stopping. I reinstalled weewx, emptied the database but no effect. I just 
> doesn´t process data. Debug level=1. Maybe someone can help me out?
>
> Log entries:
>
> May 28 14:00:18 kwsweerstation systemd[1]: Starting LSB: weewx weather 
> system...
> May 28 14:00:18 kwsweerstation weewx[11973]:  * Starting weewx weather 
> system weewx
> May 28 14:00:18 kwsweerstation weewx[11991] INFO __main__: 
> Initializing weewx version 4.5.1
> May 28 14:00:18 kwsweerstation weewx[11991] INFO __main__: Using 
> Python 3.8.5 (default, Jan 27 2021, 15:41:15) #012[GCC 9.3.0]
> May 28 14:00:19 kwsweerstation weewx[11991] INFO __main__: Platform 
> Linux-5.4.0-73-generic-x86_64-with-glibc2.29
> May 28 14:00:19 kwsweerstation weewx[11991] INFO __main__: Locale is 
> 'nl_NL.UTF-8'
> May 28 14:00:19 kwsweerstation weewx[11991] INFO __main__: PID file is 
> /var/run/weewx.pid
> May 28 14:00:19 kwsweerstation weewx[11994] INFO __main__: Using 
> configuration file /etc/weewx/weewx.conf
> May 28 14:00:19 kwsweerstation weewx[11994] INFO __main__: Debug is 1
> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG __main__: 
> Initializing engine
> May 28 14:00:19 kwsweerstation weewx[11994] INFO weewx.engine: Loading 
> station type Ultimeter (weewx.drivers.ultimeter)
> May 28 14:00:19 kwsweerstation weewx[11994] INFO 
> weewx.drivers.ultimeter: Driver version is 0.41
> May 28 14:00:19 kwsweerstation weewx[11994] INFO 
> weewx.drivers.ultimeter: Using serial po

Re: [weewx-user] weewx failure after power loos

[valken...@gmail.com]

Exactly nothing happens:

@kwsweerstation:/etc/weewx# weewxd

And then the screen stays completely blank..

Op vrijdag 28 mei 2021 om 15:00:08 UTC+2 schreef tke...@gmail.com:

> What happens when you run weewxd directly from the console?
>
> On Fri, May 28, 2021 at 5:54 AM valken...@gmail.com  
> wrote:
>
>> Dear Tom,
>>
>> Thank you for your answer. You are right. This is a very short interval. 
>> I let it run much longer earlier, and nothing else showed up in the logs. 
>> Indeed, I quit weewx by systemctl stop weewx. Then I noticed this error, an 
>> I assumed it might yield an answer. To get a clean piece of logs,  did a 
>> start and stop in a short time. (But that's not helpful I understand now.) 
>> I did run weewxd (after stopping weewx), but it show no output whatsoever. 
>> Just nothing. Blank. So now data received from ttyS0? 
>> When i start weewx by systemctl. The log gives me the same output. The 
>> last log entry is: 
>> kwsweerstation weewx[12255] DEBUG weewx.manager: Daily summary version is 
>> 4.0
>>
>> After that no further entries appear. The rest of the log above this 
>> entry is exactly similar to the log shown in the openig post. I think there 
>> is some  issue with the serial connection, although screen gives me some 
>> encoded output. 
>> Op vrijdag 28 mei 2021 om 14:30:26 UTC+2 schreef tke...@gmail.com:
>>
>>> In this log sample, I assume you stopped weewx by doing something like 
>>> "systemctl stop weewx". If so, the "error in the log" is just the normal 
>>> shutdown chatter and doesn't mean anything.
>>>
>>> In this sample, there is only 3 seconds between when weewx had finished 
>>> initializing, and when the shutdown sequence started. That's not enough 
>>> time to judge whether weewx was doing anything.
>>>
>>> Suggestions:
>>> 1. Let it run longer. At least an archive period.
>>> 2. Alternatively, run weewxd directly from the console 
>>>  for a 
>>> while. It will print out LOOP packets as they arrive, allowing you to check 
>>> whether weewx is properly receiving data. 
>>>
>>> -tk
>>>
>>> On Fri, May 28, 2021 at 5:03 AM valken...@gmail.com  
>>> wrote:
>>>
 Hi,
 Iḿ having troubles with a weewx inatance running on ubuntu 20. After an 
 unforseen power outage, the system came back up, but weewx stopped 
 processing data. The system is connected to an ulitmeter 2100 via ttyS0. 
 With screen I do see data on that port. However weewx starts, and does 
 nothing. No errors in the log, no activity at actually after starting 
 weewx. If I manually stop weewx, it results in an error in the log, before 
 stopping. I reinstalled weewx, emptied the database but no effect. I just 
 doesn´t process data. Debug level=1. Maybe someone can help me out?

 Log entries:

 May 28 14:00:18 kwsweerstation systemd[1]: Starting LSB: weewx weather 
 system...
 May 28 14:00:18 kwsweerstation weewx[11973]:  * Starting weewx weather 
 system weewx
 May 28 14:00:18 kwsweerstation weewx[11991] INFO __main__: Initializing 
 weewx version 4.5.1
 May 28 14:00:18 kwsweerstation weewx[11991] INFO __main__: Using Python 
 3.8.5 (default, Jan 27 2021, 15:41:15) #012[GCC 9.3.0]
 May 28 14:00:19 kwsweerstation weewx[11991] INFO __main__: Platform 
 Linux-5.4.0-73-generic-x86_64-with-glibc2.29
 May 28 14:00:19 kwsweerstation weewx[11991] INFO __main__: Locale is 
 'nl_NL.UTF-8'
 May 28 14:00:19 kwsweerstation weewx[11991] INFO __main__: PID file is 
 /var/run/weewx.pid
 May 28 14:00:19 kwsweerstation weewx[11994] INFO __main__: Using 
 configuration file /etc/weewx/weewx.conf
 May 28 14:00:19 kwsweerstation weewx[11994] INFO __main__: Debug is 1
 May 28 14:00:19 kwsweerstation weewx[11994] DEBUG __main__: 
 Initializing engine
 May 28 14:00:19 kwsweerstation weewx[11994] INFO weewx.engine: Loading 
 station type Ultimeter (weewx.drivers.ultimeter)
 May 28 14:00:19 kwsweerstation weewx[11994] INFO 
 weewx.drivers.ultimeter: Driver version is 0.41
 May 28 14:00:19 kwsweerstation weewx[11994] INFO 
 weewx.drivers.ultimeter: Using serial port /dev/ttyS0
 May 28 14:00:19 kwsweerstation weewx[11994] DEBUG 
 weewx.drivers.ultimeter: Open serial port /dev/ttyS0
 May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Loading 
 service weewx.engine.StdTimeSynch
 May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: 
 Finished loading service weewx.engine.StdTimeSynch
 May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Loading 
 service weewx.engine.StdConvert
 May 28 14:00:19 kwsweerstation weewx[11994] INFO weewx.engine: 
 StdConvert target unit is 0x1
 May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: 
 Finished loading service weewx.engine.StdConvert
 May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weew

Re: [weewx-user] weewx failure after power loos

[Tom Keffer]

What happens when you run weewxd directly from the console?

On Fri, May 28, 2021 at 5:54 AM valken...@gmail.com 
wrote:

> Dear Tom,
>
> Thank you for your answer. You are right. This is a very short interval. I
> let it run much longer earlier, and nothing else showed up in the logs.
> Indeed, I quit weewx by systemctl stop weewx. Then I noticed this error, an
> I assumed it might yield an answer. To get a clean piece of logs,  did a
> start and stop in a short time. (But that's not helpful I understand now.)
> I did run weewxd (after stopping weewx), but it show no output whatsoever.
> Just nothing. Blank. So now data received from ttyS0?
> When i start weewx by systemctl. The log gives me the same output. The
> last log entry is:
> kwsweerstation weewx[12255] DEBUG weewx.manager: Daily summary version is
> 4.0
>
> After that no further entries appear. The rest of the log above this entry
> is exactly similar to the log shown in the openig post. I think there is
> some  issue with the serial connection, although screen gives me some
> encoded output.
> Op vrijdag 28 mei 2021 om 14:30:26 UTC+2 schreef tke...@gmail.com:
>
>> In this log sample, I assume you stopped weewx by doing something like
>> "systemctl stop weewx". If so, the "error in the log" is just the normal
>> shutdown chatter and doesn't mean anything.
>>
>> In this sample, there is only 3 seconds between when weewx had finished
>> initializing, and when the shutdown sequence started. That's not enough
>> time to judge whether weewx was doing anything.
>>
>> Suggestions:
>> 1. Let it run longer. At least an archive period.
>> 2. Alternatively, run weewxd directly from the console
>>  for a while.
>> It will print out LOOP packets as they arrive, allowing you to check
>> whether weewx is properly receiving data.
>>
>> -tk
>>
>> On Fri, May 28, 2021 at 5:03 AM valken...@gmail.com 
>> wrote:
>>
>>> Hi,
>>> Iḿ having troubles with a weewx inatance running on ubuntu 20. After an
>>> unforseen power outage, the system came back up, but weewx stopped
>>> processing data. The system is connected to an ulitmeter 2100 via ttyS0.
>>> With screen I do see data on that port. However weewx starts, and does
>>> nothing. No errors in the log, no activity at actually after starting
>>> weewx. If I manually stop weewx, it results in an error in the log, before
>>> stopping. I reinstalled weewx, emptied the database but no effect. I just
>>> doesn´t process data. Debug level=1. Maybe someone can help me out?
>>>
>>> Log entries:
>>>
>>> May 28 14:00:18 kwsweerstation systemd[1]: Starting LSB: weewx weather
>>> system...
>>> May 28 14:00:18 kwsweerstation weewx[11973]:  * Starting weewx weather
>>> system weewx
>>> May 28 14:00:18 kwsweerstation weewx[11991] INFO __main__: Initializing
>>> weewx version 4.5.1
>>> May 28 14:00:18 kwsweerstation weewx[11991] INFO __main__: Using Python
>>> 3.8.5 (default, Jan 27 2021, 15:41:15) #012[GCC 9.3.0]
>>> May 28 14:00:19 kwsweerstation weewx[11991] INFO __main__: Platform
>>> Linux-5.4.0-73-generic-x86_64-with-glibc2.29
>>> May 28 14:00:19 kwsweerstation weewx[11991] INFO __main__: Locale is
>>> 'nl_NL.UTF-8'
>>> May 28 14:00:19 kwsweerstation weewx[11991] INFO __main__: PID file is
>>> /var/run/weewx.pid
>>> May 28 14:00:19 kwsweerstation weewx[11994] INFO __main__: Using
>>> configuration file /etc/weewx/weewx.conf
>>> May 28 14:00:19 kwsweerstation weewx[11994] INFO __main__: Debug is 1
>>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG __main__: Initializing
>>> engine
>>> May 28 14:00:19 kwsweerstation weewx[11994] INFO weewx.engine: Loading
>>> station type Ultimeter (weewx.drivers.ultimeter)
>>> May 28 14:00:19 kwsweerstation weewx[11994] INFO
>>> weewx.drivers.ultimeter: Driver version is 0.41
>>> May 28 14:00:19 kwsweerstation weewx[11994] INFO
>>> weewx.drivers.ultimeter: Using serial port /dev/ttyS0
>>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG
>>> weewx.drivers.ultimeter: Open serial port /dev/ttyS0
>>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Loading
>>> service weewx.engine.StdTimeSynch
>>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Finished
>>> loading service weewx.engine.StdTimeSynch
>>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Loading
>>> service weewx.engine.StdConvert
>>> May 28 14:00:19 kwsweerstation weewx[11994] INFO weewx.engine:
>>> StdConvert target unit is 0x1
>>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Finished
>>> loading service weewx.engine.StdConvert
>>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Loading
>>> service weewx.engine.StdCalibrate
>>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Finished
>>> loading service weewx.engine.StdCalibrate
>>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Loading
>>> service weewx.engine.StdQC
>>> May 28 14:00:19 kwsweerstation weewx[1199

Re: [weewx-user] weewx failure after power loos

[valken...@gmail.com]

Dear Tom,

Thank you for your answer. You are right. This is a very short interval. I 
let it run much longer earlier, and nothing else showed up in the logs. 
Indeed, I quit weewx by systemctl stop weewx. Then I noticed this error, an 
I assumed it might yield an answer. To get a clean piece of logs,  did a 
start and stop in a short time. (But that's not helpful I understand now.) 
I did run weewxd (after stopping weewx), but it show no output whatsoever. 
Just nothing. Blank. So now data received from ttyS0? 
When i start weewx by systemctl. The log gives me the same output. The last 
log entry is: 
kwsweerstation weewx[12255] DEBUG weewx.manager: Daily summary version is 
4.0

After that no further entries appear. The rest of the log above this entry 
is exactly similar to the log shown in the openig post. I think there is 
some  issue with the serial connection, although screen gives me some 
encoded output. 
Op vrijdag 28 mei 2021 om 14:30:26 UTC+2 schreef tke...@gmail.com:

> In this log sample, I assume you stopped weewx by doing something like 
> "systemctl stop weewx". If so, the "error in the log" is just the normal 
> shutdown chatter and doesn't mean anything.
>
> In this sample, there is only 3 seconds between when weewx had finished 
> initializing, and when the shutdown sequence started. That's not enough 
> time to judge whether weewx was doing anything.
>
> Suggestions:
> 1. Let it run longer. At least an archive period.
> 2. Alternatively, run weewxd directly from the console 
>  for a while. 
> It will print out LOOP packets as they arrive, allowing you to check 
> whether weewx is properly receiving data. 
>
> -tk
>
> On Fri, May 28, 2021 at 5:03 AM valken...@gmail.com  
> wrote:
>
>> Hi,
>> Iḿ having troubles with a weewx inatance running on ubuntu 20. After an 
>> unforseen power outage, the system came back up, but weewx stopped 
>> processing data. The system is connected to an ulitmeter 2100 via ttyS0. 
>> With screen I do see data on that port. However weewx starts, and does 
>> nothing. No errors in the log, no activity at actually after starting 
>> weewx. If I manually stop weewx, it results in an error in the log, before 
>> stopping. I reinstalled weewx, emptied the database but no effect. I just 
>> doesn´t process data. Debug level=1. Maybe someone can help me out?
>>
>> Log entries:
>>
>> May 28 14:00:18 kwsweerstation systemd[1]: Starting LSB: weewx weather 
>> system...
>> May 28 14:00:18 kwsweerstation weewx[11973]:  * Starting weewx weather 
>> system weewx
>> May 28 14:00:18 kwsweerstation weewx[11991] INFO __main__: Initializing 
>> weewx version 4.5.1
>> May 28 14:00:18 kwsweerstation weewx[11991] INFO __main__: Using Python 
>> 3.8.5 (default, Jan 27 2021, 15:41:15) #012[GCC 9.3.0]
>> May 28 14:00:19 kwsweerstation weewx[11991] INFO __main__: Platform 
>> Linux-5.4.0-73-generic-x86_64-with-glibc2.29
>> May 28 14:00:19 kwsweerstation weewx[11991] INFO __main__: Locale is 
>> 'nl_NL.UTF-8'
>> May 28 14:00:19 kwsweerstation weewx[11991] INFO __main__: PID file is 
>> /var/run/weewx.pid
>> May 28 14:00:19 kwsweerstation weewx[11994] INFO __main__: Using 
>> configuration file /etc/weewx/weewx.conf
>> May 28 14:00:19 kwsweerstation weewx[11994] INFO __main__: Debug is 1
>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG __main__: Initializing 
>> engine
>> May 28 14:00:19 kwsweerstation weewx[11994] INFO weewx.engine: Loading 
>> station type Ultimeter (weewx.drivers.ultimeter)
>> May 28 14:00:19 kwsweerstation weewx[11994] INFO weewx.drivers.ultimeter: 
>> Driver version is 0.41
>> May 28 14:00:19 kwsweerstation weewx[11994] INFO weewx.drivers.ultimeter: 
>> Using serial port /dev/ttyS0
>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG 
>> weewx.drivers.ultimeter: Open serial port /dev/ttyS0
>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Loading 
>> service weewx.engine.StdTimeSynch
>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Finished 
>> loading service weewx.engine.StdTimeSynch
>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Loading 
>> service weewx.engine.StdConvert
>> May 28 14:00:19 kwsweerstation weewx[11994] INFO weewx.engine: StdConvert 
>> target unit is 0x1
>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Finished 
>> loading service weewx.engine.StdConvert
>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Loading 
>> service weewx.engine.StdCalibrate
>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Finished 
>> loading service weewx.engine.StdCalibrate
>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Loading 
>> service weewx.engine.StdQC
>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Finished 
>> loading service weewx.engine.StdQC
>> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Loading 
>> service weewx.wxservices.StdWXCalc

Re: [weewx-user] weewx failure after power loos

[Tom Keffer]

In this log sample, I assume you stopped weewx by doing something like
"systemctl stop weewx". If so, the "error in the log" is just the normal
shutdown chatter and doesn't mean anything.

In this sample, there is only 3 seconds between when weewx had finished
initializing, and when the shutdown sequence started. That's not enough
time to judge whether weewx was doing anything.

Suggestions:
1. Let it run longer. At least an archive period.
2. Alternatively, run weewxd directly from the console
 for a while. It
will print out LOOP packets as they arrive, allowing you to check whether
weewx is properly receiving data.

-tk

On Fri, May 28, 2021 at 5:03 AM valken...@gmail.com 
wrote:

> Hi,
> Iḿ having troubles with a weewx inatance running on ubuntu 20. After an
> unforseen power outage, the system came back up, but weewx stopped
> processing data. The system is connected to an ulitmeter 2100 via ttyS0.
> With screen I do see data on that port. However weewx starts, and does
> nothing. No errors in the log, no activity at actually after starting
> weewx. If I manually stop weewx, it results in an error in the log, before
> stopping. I reinstalled weewx, emptied the database but no effect. I just
> doesn´t process data. Debug level=1. Maybe someone can help me out?
>
> Log entries:
>
> May 28 14:00:18 kwsweerstation systemd[1]: Starting LSB: weewx weather
> system...
> May 28 14:00:18 kwsweerstation weewx[11973]:  * Starting weewx weather
> system weewx
> May 28 14:00:18 kwsweerstation weewx[11991] INFO __main__: Initializing
> weewx version 4.5.1
> May 28 14:00:18 kwsweerstation weewx[11991] INFO __main__: Using Python
> 3.8.5 (default, Jan 27 2021, 15:41:15) #012[GCC 9.3.0]
> May 28 14:00:19 kwsweerstation weewx[11991] INFO __main__: Platform
> Linux-5.4.0-73-generic-x86_64-with-glibc2.29
> May 28 14:00:19 kwsweerstation weewx[11991] INFO __main__: Locale is
> 'nl_NL.UTF-8'
> May 28 14:00:19 kwsweerstation weewx[11991] INFO __main__: PID file is
> /var/run/weewx.pid
> May 28 14:00:19 kwsweerstation weewx[11994] INFO __main__: Using
> configuration file /etc/weewx/weewx.conf
> May 28 14:00:19 kwsweerstation weewx[11994] INFO __main__: Debug is 1
> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG __main__: Initializing
> engine
> May 28 14:00:19 kwsweerstation weewx[11994] INFO weewx.engine: Loading
> station type Ultimeter (weewx.drivers.ultimeter)
> May 28 14:00:19 kwsweerstation weewx[11994] INFO weewx.drivers.ultimeter:
> Driver version is 0.41
> May 28 14:00:19 kwsweerstation weewx[11994] INFO weewx.drivers.ultimeter:
> Using serial port /dev/ttyS0
> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.drivers.ultimeter:
> Open serial port /dev/ttyS0
> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Loading
> service weewx.engine.StdTimeSynch
> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Finished
> loading service weewx.engine.StdTimeSynch
> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Loading
> service weewx.engine.StdConvert
> May 28 14:00:19 kwsweerstation weewx[11994] INFO weewx.engine: StdConvert
> target unit is 0x1
> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Finished
> loading service weewx.engine.StdConvert
> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Loading
> service weewx.engine.StdCalibrate
> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Finished
> loading service weewx.engine.StdCalibrate
> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Loading
> service weewx.engine.StdQC
> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Finished
> loading service weewx.engine.StdQC
> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Loading
> service weewx.wxservices.StdWXCalculate
> May 28 14:00:19 kwsweerstation weewx[11973]:...done.
> May 28 14:00:19 kwsweerstation systemd[1]: Started LSB: weewx weather
> system.
> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.manager: Daily
> summary version is 4.0
> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Finished
> loading service weewx.wxservices.StdWXCalculate
> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.engine: Loading
> service user.cmon.ComputerMonitor
> May 28 14:00:19 kwsweerstation weewx[11994] INFO user.cmon: service
> version is 0.20
> May 28 14:00:19 kwsweerstation weewx[11994] DEBUG weewx.manager: Daily
> summary version is 4.0
> May 28 14:00:19 kwsweerstation weewx[11994] INFO user.cmon: sysinfo: Linux
> kwsweerstation 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:39:42 UTC 2021
> x86_64
> May 28 14:00:19 kwsweerstation weewx[11994] INFO user.cmon: cpuinfo:
> processor: 3
> May 28 14:00:19 kwsweerstation weewx[11994] INFO user.cmon: cpuinfo:
> vendor_id: GenuineIntel
> May 28 14:00:19 kwsweerstation weewx[11994] INFO user.cmon: cpuinfo: cpu
> family: 6
> May 28 14:00:19 kwsweerstat