[weewx-user] Re: Temp showing N/A
Thank you Garyyour analysis was spot onas usual! On Sunday, 16 June 2019 14:10:21 UTC+12, gjr80 wrote: > > Hi, > > Mirabile Dictu! > > > Sort of guessed what that meant but had to look that one up to be sure! > > A few comments. Pressure comes from a sensor in the console as does inside > temperature so it is possible that if your ISS cannot be contacted by the > console WeeWX may still have communications with the console and pressure > and inside temperature may well still be recorded and posted to WU - > everything else will likely be None or N/A (or a WU default in the case of > WU). Since you mention a solar panel I presume you are referring to the > solar panel on your ISS meaning you have the wireless version. I don't have > one myself but I understand there was a super cap (high capacity capacitor) > in the ISS that stores solar energy to keep the ISS running overnight. If > that fails the ISS falls back to a non-rechargeable lithium battery. Could > be lack of sun or the super cap failing has meant it did not have enough > energy to keep your ISS running overnight and if your lithium battery > happens to be dead your ISS would die. It would then take until there was > enough solar power to get the ISS running (and maybe charging the super cap > to a certain extent) before things came back again. Given it's winter and > depending on your solar panel orientation/location/shielding, it could take > until around 11:30am before it had sufficient power to get the ISS running > again. Super caps do fail (Google replace Davis super cap) as do lithium > batteries. It could be a case of the super cap (largely) failing some time > ago and the lithium battery has been carrying the ISS overnight for a while > and now it is finally flat. > > If WeeWX was posting pressure data to WU overnight then WeeWX must have > had good comms with the console (which you would expect even if the ISS > failed). In the log extract you post there is a repeated and seemingly > continuous failure to obtain loop packets from the console: > > Jun 16 10:25:59 WeatherPi weewx[583]: vantage: Gentle wake up of console > successful > Jun 16 10:25:59 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets > . > Jun 16 10:25:59 WeatherPi weewx[583]: vantage: Gentle wake up of console > successful > Jun 16 10:26:03 WeatherPi weewx[583]: vantage: LOOP try #1; error: > Expected to read 99 chars; got 0 instead > Jun 16 10:26:03 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets > . > Jun 16 10:26:04 WeatherPi weewx[583]: vantage: Retry #0 failed > Jun 16 10:26:04 WeatherPi weewx[583]: vantage: Rude wake up of console > successful > Jun 16 10:26:08 WeatherPi weewx[583]: vantage: LOOP try #2; error: > Expected to read 99 chars; got 0 instead > Jun 16 10:26:08 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets > . > Jun 16 10:26:10 WeatherPi weewx[583]: vantage: Retry #0 failed > Jun 16 10:26:10 WeatherPi weewx[583]: vantage: Rude wake up of console > successful > Jun 16 10:26:14 WeatherPi weewx[583]: vantage: LOOP try #3; error: > Expected to read 99 chars; got 0 instead > Jun 16 10:26:14 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets > . > Jun 16 10:26:15 WeatherPi weewx[583]: vantage: Retry #0 failed > Jun 16 10:26:15 WeatherPi weewx[583]: vantage: Rude wake up of console > successful > Jun 16 10:26:19 WeatherPi weewx[583]: vantage: LOOP try #4; error: > Expected to read 99 chars; got 0 instead > Jun 16 10:26:19 WeatherPi weewx[583]: vantage: LOOP max tries (4) exceeded > . > Jun 16 10:26:19 WeatherPi weewx[583]: engine: Main loop exiting. Shutting > engine down. > Jun 16 10:26:19 WeatherPi weewx[583]: restx: Shut down Wunderground-PWS > thread. > Jun 16 10:26:19 WeatherPi weewx[583]: engine: Caught WeeWxIOError: Max > tries exceeded while getting LOOP data. > Jun 16 10:26:19 WeatherPi weewx[583]: Waiting 60 seconds then > retrying... > > Without a connection to the ISS there is no data to put in a loop packet > but I am not sure what the console does in this case, maybe if just refuses > to send loop packets but does send archive records (which would contain > pressure and inside temperature). Maybe those log entries are as a a result > of your efforts to get things working again in the morning and they did not > go on all night. > > I would be inclined to give it the benefit of the doubt for now, but I > expect it will happen again and it might then be a case of replacing one or > both of the super cap and lithium battery. If your ISS is easily accessible > it might be worth a look inside for any signs of leakage or bulging of the > super cap. > > Gary > > > On Sunday, 16 June 2019 09:57:42 UTC+10, monmul wrote: > > Oh! Mirabile Dictu!...it has started recording temp again.I am > wondering if the battery has run out and when the sun started hitting the > solar panel of the weather station, it started recording againbut why > would
[weewx-user] Re: Temp showing N/A
Hi, Mirabile Dictu! > Sort of guessed what that meant but had to look that one up to be sure! A few comments. Pressure comes from a sensor in the console as does inside temperature so it is possible that if your ISS cannot be contacted by the console WeeWX may still have communications with the console and pressure and inside temperature may well still be recorded and posted to WU - everything else will likely be None or N/A (or a WU default in the case of WU). Since you mention a solar panel I presume you are referring to the solar panel on your ISS meaning you have the wireless version. I don't have one myself but I understand there was a super cap (high capacity capacitor) in the ISS that stores solar energy to keep the ISS running overnight. If that fails the ISS falls back to a non-rechargeable lithium battery. Could be lack of sun or the super cap failing has meant it did not have enough energy to keep your ISS running overnight and if your lithium battery happens to be dead your ISS would die. It would then take until there was enough solar power to get the ISS running (and maybe charging the super cap to a certain extent) before things came back again. Given it's winter and depending on your solar panel orientation/location/shielding, it could take until around 11:30am before it had sufficient power to get the ISS running again. Super caps do fail (Google replace Davis super cap) as do lithium batteries. It could be a case of the super cap (largely) failing some time ago and the lithium battery has been carrying the ISS overnight for a while and now it is finally flat. If WeeWX was posting pressure data to WU overnight then WeeWX must have had good comms with the console (which you would expect even if the ISS failed). In the log extract you post there is a repeated and seemingly continuous failure to obtain loop packets from the console: Jun 16 10:25:59 WeatherPi weewx[583]: vantage: Gentle wake up of console successful Jun 16 10:25:59 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets. Jun 16 10:25:59 WeatherPi weewx[583]: vantage: Gentle wake up of console successful Jun 16 10:26:03 WeatherPi weewx[583]: vantage: LOOP try #1; error: Expected to read 99 chars; got 0 instead Jun 16 10:26:03 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets. Jun 16 10:26:04 WeatherPi weewx[583]: vantage: Retry #0 failed Jun 16 10:26:04 WeatherPi weewx[583]: vantage: Rude wake up of console successful Jun 16 10:26:08 WeatherPi weewx[583]: vantage: LOOP try #2; error: Expected to read 99 chars; got 0 instead Jun 16 10:26:08 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets. Jun 16 10:26:10 WeatherPi weewx[583]: vantage: Retry #0 failed Jun 16 10:26:10 WeatherPi weewx[583]: vantage: Rude wake up of console successful Jun 16 10:26:14 WeatherPi weewx[583]: vantage: LOOP try #3; error: Expected to read 99 chars; got 0 instead Jun 16 10:26:14 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets. Jun 16 10:26:15 WeatherPi weewx[583]: vantage: Retry #0 failed Jun 16 10:26:15 WeatherPi weewx[583]: vantage: Rude wake up of console successful Jun 16 10:26:19 WeatherPi weewx[583]: vantage: LOOP try #4; error: Expected to read 99 chars; got 0 instead Jun 16 10:26:19 WeatherPi weewx[583]: vantage: LOOP max tries (4) exceeded. Jun 16 10:26:19 WeatherPi weewx[583]: engine: Main loop exiting. Shutting engine down. Jun 16 10:26:19 WeatherPi weewx[583]: restx: Shut down Wunderground-PWS thread. Jun 16 10:26:19 WeatherPi weewx[583]: engine: Caught WeeWxIOError: Max tries exceeded while getting LOOP data. Jun 16 10:26:19 WeatherPi weewx[583]: Waiting 60 seconds then retrying... Without a connection to the ISS there is no data to put in a loop packet but I am not sure what the console does in this case, maybe if just refuses to send loop packets but does send archive records (which would contain pressure and inside temperature). Maybe those log entries are as a a result of your efforts to get things working again in the morning and they did not go on all night. I would be inclined to give it the benefit of the doubt for now, but I expect it will happen again and it might then be a case of replacing one or both of the super cap and lithium battery. If your ISS is easily accessible it might be worth a look inside for any signs of leakage or bulging of the super cap. Gary On Sunday, 16 June 2019 09:57:42 UTC+10, monmul wrote: > > Oh! Mirabile Dictu!...it has started recording temp again.I am > wondering if the battery has run out and when the sun started hitting the > solar panel of the weather station, it started recording againbut why > would the pressure have continued recordinghmmm! more mysteries! > > On Sunday, 16 June 2019 10:47:36 UTC+12, monmul wrote: > > Around midnight last night - after months of operating properly my ststem > started recording N/A for temperature. I have tried dumping memory etc and >
[weewx-user] Re: Temp showing N/A
Oh! Mirabile Dictu!...it has started recording temp again.I am
wondering if the battery has run out and when the sun started hitting the
solar panel of the weather station, it started recording againbut why
would the pressure have continued recordinghmmm! more mysteries!
On Sunday, 16 June 2019 10:47:36 UTC+12, monmul wrote:
>
> Around midnight last night - after months of operating properly my ststem
> started recording N/A for temperature. I have tried dumping memory etc and
> restartedit has restarted but the problem is the same. Here is the log.
> What has happened and how do I fix it please.
>
> base 'weewx.sdb'
> Jun 16 10:24:37 WeatherPi weewx[583]: manager: Starting backfill of daily
> summaries
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.engine.StdArchive
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdStationRegistry
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: StationRegistry: Registration
> not requested.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdStationRegistry
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdWunderground
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: WU essentials: {}
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: Wunderground-PWS: Data for
> station IOTAGOQU2 will be posted
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdWunderground
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdPWSweather
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: PWSweather: Posting not
> enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdPWSweather
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdCWOP
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: CWOP: Posting not enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdCWOP
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdWOW
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: WOW: Posting not enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdWOW
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdAWEKAS
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: AWEKAS: Posting not enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdAWEKAS
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.engine.StdPrint
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.engine.StdPrint
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.engine.StdReport
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.engine.StdReport
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Starting up weewx version
> 3.9.1
> Jun 16 10:24:37 WeatherPi weewx[583]: manager: Daily summary version is 2.0
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Clock error is 1.22 seconds
> (positive is fast)
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Getting archive packets
> since 2019-06-16 10:10:00 NZST (1560636600)
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Retrieving 0 page(s);
> starting index= 0
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Starting main packet loop.
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:41 WeatherPi weewx[583]: vantage: LOOP try #1; error:
> Expected to read 99 chars; got 0 instead
> Jun 16 10:24:41 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:43 WeatherPi weewx[583]: vantage: Retry #0 failed
> Jun 16 10:24:43 WeatherPi weewx[583]: vantage: Rude wake up of console
> successful
> Jun 16 10:24:47 WeatherPi weewx[583]: vantage: LOOP try #2; error:
> Expected to read 99 chars; got 0 instead
> Jun 16 10:24:47 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:48 WeatherPi weewx[583]: vantage: Retry #0 failed
> Jun 16 10:24:48 WeatherPi weewx[583]: vantage: Rude wake up of console
> successful
> Jun 16 10:24:52 WeatherPi weewx[583]: vantage: LOOP try #3; error:
> Expected to read 99 chars; got 0 instead
> Jun 16 10:24:52 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:53 WeatherPi weewx[583]: vantage: Retry #0 failed
> Jun 16 10:24:53 WeatherPi weewx[583]: vantage: Rude wake up of console
> successful
> Jun 16 10:24:58 WeatherPi weewx[583]:
[weewx-user] Re: Temp showing N/A
I notice the signal quality went from 100 to 0 at midnight also!!the
Barometer is still reading as normal and posting to the template!
On Sunday, 16 June 2019 10:47:36 UTC+12, monmul wrote:
>
> Around midnight last night - after months of operating properly my ststem
> started recording N/A for temperature. I have tried dumping memory etc and
> restartedit has restarted but the problem is the same. Here is the log.
> What has happened and how do I fix it please.
>
> base 'weewx.sdb'
> Jun 16 10:24:37 WeatherPi weewx[583]: manager: Starting backfill of daily
> summaries
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.engine.StdArchive
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdStationRegistry
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: StationRegistry: Registration
> not requested.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdStationRegistry
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdWunderground
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: WU essentials: {}
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: Wunderground-PWS: Data for
> station IOTAGOQU2 will be posted
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdWunderground
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdPWSweather
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: PWSweather: Posting not
> enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdPWSweather
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdCWOP
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: CWOP: Posting not enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdCWOP
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdWOW
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: WOW: Posting not enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdWOW
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdAWEKAS
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: AWEKAS: Posting not enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdAWEKAS
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.engine.StdPrint
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.engine.StdPrint
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.engine.StdReport
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.engine.StdReport
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Starting up weewx version
> 3.9.1
> Jun 16 10:24:37 WeatherPi weewx[583]: manager: Daily summary version is 2.0
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Clock error is 1.22 seconds
> (positive is fast)
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Getting archive packets
> since 2019-06-16 10:10:00 NZST (1560636600)
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Retrieving 0 page(s);
> starting index= 0
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Starting main packet loop.
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:41 WeatherPi weewx[583]: vantage: LOOP try #1; error:
> Expected to read 99 chars; got 0 instead
> Jun 16 10:24:41 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:43 WeatherPi weewx[583]: vantage: Retry #0 failed
> Jun 16 10:24:43 WeatherPi weewx[583]: vantage: Rude wake up of console
> successful
> Jun 16 10:24:47 WeatherPi weewx[583]: vantage: LOOP try #2; error:
> Expected to read 99 chars; got 0 instead
> Jun 16 10:24:47 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:48 WeatherPi weewx[583]: vantage: Retry #0 failed
> Jun 16 10:24:48 WeatherPi weewx[583]: vantage: Rude wake up of console
> successful
> Jun 16 10:24:52 WeatherPi weewx[583]: vantage: LOOP try #3; error:
> Expected to read 99 chars; got 0 instead
> Jun 16 10:24:52 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:53 WeatherPi weewx[583]: vantage: Retry #0 failed
> Jun 16 10:24:53 WeatherPi weewx[583]: vantage: Rude wake up of console
> successful
> Jun 16 10:24:58 WeatherPi weewx[583]: vantage: LOOP try #4; error:
> Expected to read 99 chars; got 0 instead
> Jun 16 10:24:58 WeatherPi weewx[583]: vantage: LOOP max tries (4) exceeded.
>
[weewx-user] Temp showing N/A
Around midnight last night - after months of operating properly my ststem
started recording N/A for temperature. I have tried dumping memory etc and
restartedit has restarted but the problem is the same. Here is the log.
What has happened and how do I fix it please.
base 'weewx.sdb'
Jun 16 10:24:37 WeatherPi weewx[583]: manager: Starting backfill of daily
summaries
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.engine.StdArchive
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.restx.StdStationRegistry
Jun 16 10:24:37 WeatherPi weewx[583]: restx: StationRegistry: Registration
not requested.
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.restx.StdStationRegistry
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.restx.StdWunderground
Jun 16 10:24:37 WeatherPi weewx[583]: restx: WU essentials: {}
Jun 16 10:24:37 WeatherPi weewx[583]: restx: Wunderground-PWS: Data for
station IOTAGOQU2 will be posted
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.restx.StdWunderground
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.restx.StdPWSweather
Jun 16 10:24:37 WeatherPi weewx[583]: restx: PWSweather: Posting not
enabled.
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.restx.StdPWSweather
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.restx.StdCWOP
Jun 16 10:24:37 WeatherPi weewx[583]: restx: CWOP: Posting not enabled.
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.restx.StdCWOP
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.restx.StdWOW
Jun 16 10:24:37 WeatherPi weewx[583]: restx: WOW: Posting not enabled.
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.restx.StdWOW
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.restx.StdAWEKAS
Jun 16 10:24:37 WeatherPi weewx[583]: restx: AWEKAS: Posting not enabled.
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.restx.StdAWEKAS
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.engine.StdPrint
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.engine.StdPrint
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.engine.StdReport
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.engine.StdReport
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Starting up weewx version
3.9.1
Jun 16 10:24:37 WeatherPi weewx[583]: manager: Daily summary version is 2.0
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
successful
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Clock error is 1.22 seconds
(positive is fast)
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Getting archive packets
since 2019-06-16 10:10:00 NZST (1560636600)
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
successful
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Retrieving 0 page(s);
starting index= 0
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Starting main packet loop.
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
successful
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
successful
Jun 16 10:24:41 WeatherPi weewx[583]: vantage: LOOP try #1; error: Expected
to read 99 chars; got 0 instead
Jun 16 10:24:41 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
Jun 16 10:24:43 WeatherPi weewx[583]: vantage: Retry #0 failed
Jun 16 10:24:43 WeatherPi weewx[583]: vantage: Rude wake up of console
successful
Jun 16 10:24:47 WeatherPi weewx[583]: vantage: LOOP try #2; error: Expected
to read 99 chars; got 0 instead
Jun 16 10:24:47 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
Jun 16 10:24:48 WeatherPi weewx[583]: vantage: Retry #0 failed
Jun 16 10:24:48 WeatherPi weewx[583]: vantage: Rude wake up of console
successful
Jun 16 10:24:52 WeatherPi weewx[583]: vantage: LOOP try #3; error: Expected
to read 99 chars; got 0 instead
Jun 16 10:24:52 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
Jun 16 10:24:53 WeatherPi weewx[583]: vantage: Retry #0 failed
Jun 16 10:24:53 WeatherPi weewx[583]: vantage: Rude wake up of console
successful
Jun 16 10:24:58 WeatherPi weewx[583]: vantage: LOOP try #4; error: Expected
to read 99 chars; got 0 instead
Jun 16 10:24:58 WeatherPi weewx[583]: vantage: LOOP max tries (4) exceeded.
Jun 16 10:24:58 WeatherPi weewx[583]: engine: Main loop exiting. Shutting
engine down.
Jun 16 10:24:58 WeatherPi weewx[583]: restx: Shut down Wunderground-PWS
thread.
Jun 16 10:24:58 WeatherPi weewx[583]: engine: Caught WeeWxIOError: Max
tries exceeded while getting LOOP data.
Jun 16 10:24:58 WeatherPi weewx[583]: Waiting 60 seconds then
retrying...
Jun 16 10:25:58
Re: [weewx-user] Re: weewx stop working
Thank you.
Finally, I thought I was insane, trying everything.
I think some update must happend on april 4th when weewx stops to work.
Now I have a log and this is all what I have for weewx.
Jun 16 00:14:01 povej weewx: Starting weewx: [ V redu ]
Jun 16 00:14:01 povej systemd: Started SYSV: start and stop the weewx
weather system.
Jun 16 00:14:01 povej weewx[503]: engine: Using configuration file
/etc/weewx/weewx.conf
Jun 16 00:14:01 povej weewx[503]: engine: Debug is 1
Jun 16 00:14:01 povej weewx[503]: engine: Initializing engine
Jun 16 00:14:01 povej weewx[503]: engine: Loading station type Interceptor
(user.interceptor)
Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: driver version
is 0.45
Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: device type:
observer
Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: sensor map: None
Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: mode is listen
Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: listen on :9900
Jun 16 00:14:01 povej weewx[503]: interceptor: ServerThread: start tcp
server
Jun 16 00:14:01 povej weewx[503]: engine: Loading service
weewx.engine.StdTimeSynch
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service
weewx.engine.StdTimeSynch
Jun 16 00:14:01 povej weewx[503]: engine: Loading service
weewx.engine.StdConvert
Jun 16 00:14:01 povej weewx[503]: engine: StdConvert target unit is 0x1
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service
weewx.engine.StdConvert
Jun 16 00:14:01 povej weewx[503]: engine: Loading service
weewx.engine.StdCalibrate
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service
weewx.engine.StdCalibrate
Jun 16 00:14:01 povej weewx[503]: engine: Loading service weewx.engine.StdQC
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service
weewx.engine.StdQC
Jun 16 00:14:01 povej weewx[503]: engine: Loading service
weewx.wxservices.StdWXCalculate
Jun 16 00:14:01 povej weewx[503]: wxcalculate: The following values will be
calculated: barometer=prefer_hardware, windchill=prefer_hardware,
dewpoint=prefer_hardware, appTemp=prefer_hardware,
rainRate=prefer_hardware, windrun=prefer_hardware,
heatindex=prefer_hardware, maxSolarRad=prefer_hardware,
humidex=prefer_hardware, pressure=prefer_hardware,
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware,
cloudbase=prefer_hardware
Jun 16 00:14:01 povej weewx[503]: wxcalculate: The following algorithms
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service
weewx.wxservices.StdWXCalculate
Jun 16 00:14:01 povej weewx[503]: engine: Loading service
weewx.engine.StdArchive
Jun 16 00:14:01 povej weewx[503]: engine: Archive will use data binding
wx_binding
Jun 16 00:14:01 povej weewx[503]: engine: Record generation will be
attempted in 'hardware'
Jun 16 00:14:01 povej weewx[503]: engine: Using archive interval of 60
seconds (specified in weewx configuration)
Jun 16 00:14:01 povej weewx[503]: engine: Use LOOP data in hi/low
calculations: 1
Jun 16 00:14:01 povej weewx[503]: manager: Daily summary version is 2.0
Jun 16 00:14:01 povej weewx[503]: engine: Using binding 'wx_binding' to
database 'weewx'
Jun 16 00:14:01 povej weewx[503]: manager: Starting backfill of daily
summaries
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service
weewx.engine.StdArchive
Jun 16 00:14:01 povej weewx[503]: engine: Loading service
weewx.restx.StdStationRegistry
Jun 16 00:14:01 povej weewx[503]: restx: StationRegistry: Registration not
requested.
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service
weewx.restx.StdStationRegistry
Jun 16 00:14:01 povej weewx[503]: engine: Loading service
weewx.restx.StdWunderground
Jun 16 00:14:01 povej weewx[503]: restx: WU essentials: {}
Jun 16 00:14:01 povej weewx[503]: restx: Wunderground-PWS: Data for station
ido10 will be posted
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service
weewx.restx.StdWunderground
Jun 16 00:14:01 povej weewx[503]: engine: Loading service
weewx.restx.StdPWSweather
Jun 16 00:14:01 povej weewx[503]: restx: PWSweather: Posting not enabled.
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service
weewx.restx.StdPWSweather
Jun 16 00:14:01 povej weewx[503]: engine: Loading service
weewx.restx.StdCWOP
Jun 16 00:14:01 povej weewx[503]: restx: CWOP: Posting not enabled.
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service
weewx.restx.StdCWOP
Jun 16 00:14:01 povej weewx[503]: engine: Loading service weewx.restx.StdWOW
Jun 16 00:14:01 povej weewx[503]: restx: WOW: Posting not enabled.
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service
weewx.restx.StdWOW
Jun 16 00:14:01 povej weewx[503]: engine: Loading service
weewx.restx.StdAWEKAS
Jun 16 00:14:01 povej weewx[503]: restx: AWEKAS: Posting not enabled.
Jun 16 00:14:01 povej weewx[503]: engine: Finished
[weewx-user] Re: Problem with MQTT
Thanks mwall. Might explain why I go through cars every 3,000 miles :) It seems that mosquitto version 1.4.15 is more forgiving with the configs. I just tried to break it with known whitespace problems and it started without issue. So check the mosquitto.log to see what's wrong. On Saturday, June 15, 2019 at 2:51:04 PM UTC-4, mwall wrote: > > On Friday, June 14, 2019 at 7:52:27 PM UTC-4, Pat wrote: >> >> >> Third, "when in doubt, reboot". You'll be surprised at how often a reboot >> fixes many mosquitto problems. >> > > um... no! > > check the mosquitto log. if necessary, restart the mostquitto process. > or turn up the logging level in mosquitto. > > reboot is what you do if you cannot be bothered to actually fix the > problem. its putting black tape over the "out of oil" indicator in your > car, then wondering why, one day, your car won't ever start again. > > -- 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/cbd25b4b-f3fe-4428-8785-dc3b81685393%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Web Server auf dem Raspberry Apache2
Did you look the following https://github.com/weewx/weewx/wiki/webserver On Saturday, June 15, 2019 at 3:07:27 AM UTC-4, Günther Wrana wrote: > Das wurde mir angezeigt nach dem ich den Befehl eingegeben habe. > > sudo tail -f /var/log/syslog > > Jun 15 08:50:24 raspberrypi weewx[5203]: cheetahgenerator: Generated 8 > files for report SeasonsReport in 1.80 seconds > Jun 15 08:50:25 raspberrypi weewx[5203]: imagegenerator: Generated 14 > images for SeasonsReport in 1.16 seconds > Jun 15 08:50:25 raspberrypi weewx[5203]: copygenerator: copied 0 files to > /home/weewx/public_html > Jun 15 08:55:25 raspberrypi weewx[5203]: manager: Added record 2019-06-15 > 08:55:00 CEST (1560581700) to database 'weewx.sdb' > Jun 15 08:55:25 raspberrypi weewx[5203]: manager: Added record 2019-06-15 > 08:55:00 CEST (1560581700) to daily summary in 'weewx.sdb' > Jun 15 08:55:25 raspberrypi weewx[5203]: restx: AWEKAS: Published record > 2019-06-15 08:55:00 CEST (1560581700) > Jun 15 08:55:26 raspberrypi weewx[5203]: restx: Wunderground-PWS: > Published record 2019-06-15 08:55:00 CEST (1560581700) > Jun 15 08:55:27 raspberrypi weewx[5203]: cheetahgenerator: Generated 8 > files for report SeasonsReport in 1.78 seconds > Jun 15 08:55:28 raspberrypi weewx[5203]: imagegenerator: Generated 14 > images for SeasonsReport in 1.15 seconds > Jun 15 08:55:28 raspberrypi weewx[5203]: copygenerator: copied 0 files to > /home/weewx/public_html > > Das die files in diesem Ordner liegen wusste ich. > > Nur wie bringe ich apache2 dazu in diesem Ordner nach zu sehen. > Nach dem kopieren der weewx.conf > > sudo cp util/apache/conf.d/weewx.conf /etc/apache2/conf.d > > > Sieht es in der conf.d von apache2 so aus. > > Alias /weewx /home/weewx/public_html > > Options FollowSymlinks > AllowOverride None > Require all granted > > > Ist das richtig oder muss ich noch etwas tun um apache2 dazu zu bringen > unter /home/weewx/public_html die Daten ab zu holen und im Browser an zu > zeigen? > > Ich dachte wenn ich alles so mache wie auf der Seite beschrieben > http://www.weewx.com/docs/usersguide.htm#If_the_server_is_on_the_same_machine > funktioniert das. > -- 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/5a2477f4-5bb0-482b-a7c8-399b462e588a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Problem with MQTT
On Friday, June 14, 2019 at 7:52:27 PM UTC-4, Pat wrote: > > > Third, "when in doubt, reboot". You'll be surprised at how often a reboot > fixes many mosquitto problems. > um... no! check the mosquitto log. if necessary, restart the mostquitto process. or turn up the logging level in mosquitto. reboot is what you do if you cannot be bothered to actually fix the problem. its putting black tape over the "out of oil" indicator in your car, then wondering why, one day, your car won't ever start again. -- 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/88464707-345b-4ba5-a444-b8bbc7371628%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: weewx stop working
FYI, on all RH/Fedora (including CantOS) there are multiple consoles, which can be accessed by pressing CTRL-ALT 1 thru =. IIRC the debug messages go to console 12, the last one behind CRTL-ALT =, but having them in a file is preferred in my book. So, good job! =D Regards, \Leon -- Leon Shaner :: Dearborn, Michigan (iPhone) > On Jun 15, 2019, at 11:09 AM, gjr80 wrote: > > Thanks, so if I am reading the centos7.6 /etc/rsyslog.conf correctly only > info and above go to /var/log/messages. There is nothing covering debug at > all so I expect that is why debug is (effectively) discarded. We could send > them to another file but that will make debugging difficult so let's just > send debug to /var/log/messages as well. > > Damjan. Try the following: > > 1. edit /etc/rsyslog.conf and add the following to the bottom of the file > (you will need privileged access to edit the file): > > # all debug to /var/log/messages > *.=debug /var/log/messages > > 2. restart rsyslog: > > $ sudo systemctl restart rsyslog > > 3. make sure /etc/weewx/weewx.conf has debug=1 > > 4. restart WeeWX: > > $ sudo systemctl restart weewx > > check /var/log/messages and you should see some debug output. > > Gary > >> On Sunday, 16 June 2019 00:36:45 UTC+10, Leon Shaner wrote: >> Gary, good sleuthing. >> >> Could it be that the debug messages simply go to a different file, such as >> /var/log/debug? >> >> Check to see where the debug logs are pointed in /etc/rsyslog.conf. >> >> Also, see here: >> >> https://www.the-art-of-web.com/system/rsyslog-config/ >> >> Regards, >> \Leon >> -- >> Leon Shaner :: Dearborn, Michigan (iPhone) >> >>> On Jun 15, 2019, at 10:19 AM, gjr80 wrote: >>> >>> I guess the question is where to from here given that it appears you cannot >>> get any debug output when running under centos7.6. I think we can assume >>> that your system is running properly (debug issue aside) with the simulator >>> driver. Troubleshooting the interceptor driver is going to be difficult >>> without any debug output. One thing I did notice, some time ago Matthew >>> suggested running WeeWX (with the interceptor driver) directly. You could >>> try that again, remember what we are seeking when running WeeWX directly is >>> not the log output but rather the console output, ie what you see on the >>> screen. I notice you don't appear to have provided the console output, >>> rather you gave the log output. >>> >>> Gary >>> On Saturday, 15 June 2019 02:28:14 UTC+10, Damjan Hajsek wrote: Ok I did logs again I hope this time better. Dne petek, 14. junij 2019 14.44.03 UTC+2 je oseba Andrew Milner napisala: > > Not really, no > > The first part appears to show normal running with archive records every > minute - but no log for the startup process > > The second part, manual running , shows us the startup but only loop data > - it runs for under a minute so does not give the coverage for two > archive periods (which in your case would be at least 2 minutes) > > The third part says debug disabled - but there does not appear to be any > section where debug is enabled - so it is not clear if you are enabling > debug correctly or not. > > it is much better to just attach the logfile directly rather than trying > to extract relevant portions. you can identify sections by the > timestamps of when you did things > > we are making slow progress - but have yet to see debug successfully > enabled!! However, simulator does appear to be OK - and indeed the > website confirms that simulator is running just fine. > > See if you can get us some log which shows debug enabled at startup!! > > > > > >> On Friday, 14 June 2019 15:13:07 UTC+3, Damjan Hajsek wrote: >> here it is. >> Is this ok what I attach? >> regards >> >> Dne petek, 14. junij 2019 12.45.41 UTC+2 je oseba Andrew Milner napisala: >>> >>> Keep running the simulator for a while, but can you now give us the log >>> from startup for at least two archive intervals FOR SIMULATOR so that >>> we can be SURE everything is working as it should be. Then, if that >>> looks ok, can you stop weewx, set debug = 1, restart weewx and again >>> attach the log from startup until at least two archive intervals. This >>> should show that all is ok with debug also!! >>> >>> >>> On Friday, 14 June 2019 12:36:32 UTC+3, Damjan Hajsek wrote: https://github.com/matthewwall/weewx-interceptor this is what I have for interceptor in weewx.conf [Interceptor] # This section is for the network traffic interceptor driver. # The driver to use: driver = user.interceptor # Specify the hardware device to
Re: [weewx-user] Re: weewx stop working
On Saturday, June 15, 2019 at 8:09:28 AM UTC-7, gjr80 wrote: > > Thanks, so if I am reading the centos7.6 /etc/rsyslog.conf correctly only > info and above go to /var/log/messages. There is nothing covering debug > at all so I expect that is why debug is (effectively) discarded. We could > send them to another file but that will make debugging difficult so let's > just send debug to /var/log/messages as well. > I've verified Gary's solution. In a vagrant VM, I added a *.debug line pointing to a different file, and after restarting syslog and weewx I 'do' see debug output in the second file. The original non-debug output also goes to /var/log/messages as expected. *.info;mail.none;authpriv.none;cron.none/var/log/messages *.debug /var/log/messages.debug -- 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/52725735-fd4b-4a80-a8ee-2e64066066d3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: weewx stop working
Thanks, so if I am reading the centos7.6 /etc/rsyslog.conf correctly only info and above go to /var/log/messages. There is nothing covering debug at all so I expect that is why debug is (effectively) discarded. We could send them to another file but that will make debugging difficult so let's just send debug to /var/log/messages as well. Damjan. Try the following: 1. edit /etc/rsyslog.conf and add the following to the bottom of the file (you will need privileged access to edit the file): # all debug to /var/log/messages *.=debug /var/log/messages 2. restart rsyslog: $ sudo systemctl restart rsyslog 3. make sure /etc/weewx/weewx.conf has debug=1 4. restart WeeWX: $ sudo systemctl restart weewx check /var/log/messages and you should see some debug output. Gary On Sunday, 16 June 2019 00:36:45 UTC+10, Leon Shaner wrote: > > Gary, good sleuthing. > > Could it be that the debug messages simply go to a different file, such as > /var/log/debug? > > Check to see where the debug logs are pointed in /etc/rsyslog.conf. > > Also, see here: > > https://www.the-art-of-web.com/system/rsyslog-config/ > > Regards, > \Leon > -- > Leon Shaner :: Dearborn, Michigan (iPhone) > > On Jun 15, 2019, at 10:19 AM, gjr80 > > wrote: > > I guess the question is where to from here given that it appears you > cannot get any debug output when running under centos7.6. I think we can > assume that your system is running properly (debug issue aside) with the > simulator driver. Troubleshooting the interceptor driver is going to be > difficult without any debug output. One thing I did notice, some time ago > Matthew suggested running WeeWX (with the interceptor driver) directly. You > could try that again, remember what we are seeking when running WeeWX > directly is not the log output but rather the console output, ie what you > see on the screen. I notice you don't appear to have provided the console > output, rather you gave the log output. > > Gary > > On Saturday, 15 June 2019 02:28:14 UTC+10, Damjan Hajsek wrote: >> >> Ok I did logs again I hope this time better. >> >> >> Dne petek, 14. junij 2019 14.44.03 UTC+2 je oseba Andrew Milner napisala: >>> >>> Not really, no >>> >>> The first part appears to show normal running with archive records every >>> minute - but no log for the startup process >>> >>> The second part, manual running , shows us the startup but only loop >>> data - it runs for under a minute so does not give the coverage for two >>> archive periods (which in your case would be at least 2 minutes) >>> >>> The third part says debug disabled - but there does not appear to be any >>> section where debug is enabled - so it is not clear if you are enabling >>> debug correctly or not. >>> >>> it is much better to just attach the logfile directly rather than trying >>> to extract relevant portions. you can identify sections by the timestamps >>> of when you did things >>> >>> we are making slow progress - but have yet to see debug successfully >>> enabled!! However, simulator does appear to be OK - and indeed the website >>> confirms that simulator is running just fine. >>> >>> See if you can get us some log which shows debug enabled at startup!! >>> >>> >>> >>> >>> >>> On Friday, 14 June 2019 15:13:07 UTC+3, Damjan Hajsek wrote: here it is. Is this ok what I attach? regards Dne petek, 14. junij 2019 12.45.41 UTC+2 je oseba Andrew Milner napisala: > > Keep running the simulator for a while, but can you now give us the > log from startup for at least two archive intervals FOR SIMULATOR so that > we can be SURE everything is working as it should be. Then, if that > looks > ok, can you stop weewx, set debug = 1, restart weewx and again attach the > log from startup until at least two archive intervals. This should show > that all is ok with debug also!! > > > > On Friday, 14 June 2019 12:36:32 UTC+3, Damjan Hajsek wrote: >> >> https://github.com/matthewwall/weewx-interceptor >> >> this is what I have for interceptor in weewx.conf >> >> [Interceptor] >> # This section is for the network traffic interceptor driver. >> >> # The driver to use: >> driver = user.interceptor >> >> # Specify the hardware device to capture. Options include: >> # acurite-bridge - acurite internet bridge, smarthub, or access >> # observer - fine offset WH2600/HP1000/HP1003, ambient WS2902 >> # lw30x - oregon scientific LW301/LW302 >> # lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge >> # wu-client - any hardware that uses the weather underground >> protocol >> #device_type = acurite-bridge >> device_type = observer >> port = 990 >> > -- > You received this message because you are subscribed to the Google Groups > "weewx-user"
Re: [weewx-user] Re: weewx stop working
Gary, good sleuthing. Could it be that the debug messages simply go to a different file, such as /var/log/debug? Check to see where the debug logs are pointed in /etc/rsyslog.conf. Also, see here: https://www.the-art-of-web.com/system/rsyslog-config/ Regards, \Leon -- Leon Shaner :: Dearborn, Michigan (iPhone) > On Jun 15, 2019, at 10:19 AM, gjr80 wrote: > > I guess the question is where to from here given that it appears you cannot > get any debug output when running under centos7.6. I think we can assume that > your system is running properly (debug issue aside) with the simulator > driver. Troubleshooting the interceptor driver is going to be difficult > without any debug output. One thing I did notice, some time ago Matthew > suggested running WeeWX (with the interceptor driver) directly. You could try > that again, remember what we are seeking when running WeeWX directly is not > the log output but rather the console output, ie what you see on the screen. > I notice you don't appear to have provided the console output, rather you > gave the log output. > > Gary > >> On Saturday, 15 June 2019 02:28:14 UTC+10, Damjan Hajsek wrote: >> Ok I did logs again I hope this time better. >> >> >> Dne petek, 14. junij 2019 14.44.03 UTC+2 je oseba Andrew Milner napisala: >>> >>> Not really, no >>> >>> The first part appears to show normal running with archive records every >>> minute - but no log for the startup process >>> >>> The second part, manual running , shows us the startup but only loop data - >>> it runs for under a minute so does not give the coverage for two archive >>> periods (which in your case would be at least 2 minutes) >>> >>> The third part says debug disabled - but there does not appear to be any >>> section where debug is enabled - so it is not clear if you are enabling >>> debug correctly or not. >>> >>> it is much better to just attach the logfile directly rather than trying to >>> extract relevant portions. you can identify sections by the timestamps of >>> when you did things >>> >>> we are making slow progress - but have yet to see debug successfully >>> enabled!! However, simulator does appear to be OK - and indeed the website >>> confirms that simulator is running just fine. >>> >>> See if you can get us some log which shows debug enabled at startup!! >>> >>> >>> >>> >>> On Friday, 14 June 2019 15:13:07 UTC+3, Damjan Hajsek wrote: here it is. Is this ok what I attach? regards Dne petek, 14. junij 2019 12.45.41 UTC+2 je oseba Andrew Milner napisala: > > Keep running the simulator for a while, but can you now give us the log > from startup for at least two archive intervals FOR SIMULATOR so that we > can be SURE everything is working as it should be. Then, if that looks > ok, can you stop weewx, set debug = 1, restart weewx and again attach the > log from startup until at least two archive intervals. This should show > that all is ok with debug also!! > > > >> On Friday, 14 June 2019 12:36:32 UTC+3, Damjan Hajsek wrote: >> https://github.com/matthewwall/weewx-interceptor >> >> this is what I have for interceptor in weewx.conf >> >> [Interceptor] >> # This section is for the network traffic interceptor driver. >> >> # The driver to use: >> driver = user.interceptor >> >> # Specify the hardware device to capture. Options include: >> # acurite-bridge - acurite internet bridge, smarthub, or access >> # observer - fine offset WH2600/HP1000/HP1003, ambient WS2902 >> # lw30x - oregon scientific LW301/LW302 >> # lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge >> # wu-client - any hardware that uses the weather underground >> protocol >> #device_type = acurite-bridge >> device_type = observer >> port = 990 > > -- > 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/2dc29325-db15-4831-899a-f256e2c024b4%40googlegroups.com. > 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/AD3FDEC5-6CF4-4A58-9132-D1D9EE55BC44%40isylum.org. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: weewx stop working
I guess the question is where to from here given that it appears you cannot get any debug output when running under centos7.6. I think we can assume that your system is running properly (debug issue aside) with the simulator driver. Troubleshooting the interceptor driver is going to be difficult without any debug output. One thing I did notice, some time ago Matthew suggested running WeeWX (with the interceptor driver) directly. You could try that again, remember what we are seeking when running WeeWX directly is not the log output but rather the console output, ie what you see on the screen. I notice you don't appear to have provided the console output, rather you gave the log output. Gary On Saturday, 15 June 2019 02:28:14 UTC+10, Damjan Hajsek wrote: > > Ok I did logs again I hope this time better. > > > Dne petek, 14. junij 2019 14.44.03 UTC+2 je oseba Andrew Milner napisala: >> >> Not really, no >> >> The first part appears to show normal running with archive records every >> minute - but no log for the startup process >> >> The second part, manual running , shows us the startup but only loop data >> - it runs for under a minute so does not give the coverage for two archive >> periods (which in your case would be at least 2 minutes) >> >> The third part says debug disabled - but there does not appear to be any >> section where debug is enabled - so it is not clear if you are enabling >> debug correctly or not. >> >> it is much better to just attach the logfile directly rather than trying >> to extract relevant portions. you can identify sections by the timestamps >> of when you did things >> >> we are making slow progress - but have yet to see debug successfully >> enabled!! However, simulator does appear to be OK - and indeed the website >> confirms that simulator is running just fine. >> >> See if you can get us some log which shows debug enabled at startup!! >> >> >> >> >> >> On Friday, 14 June 2019 15:13:07 UTC+3, Damjan Hajsek wrote: >>> >>> here it is. >>> Is this ok what I attach? >>> regards >>> >>> Dne petek, 14. junij 2019 12.45.41 UTC+2 je oseba Andrew Milner napisala: Keep running the simulator for a while, but can you now give us the log from startup for at least two archive intervals FOR SIMULATOR so that we can be SURE everything is working as it should be. Then, if that looks ok, can you stop weewx, set debug = 1, restart weewx and again attach the log from startup until at least two archive intervals. This should show that all is ok with debug also!! On Friday, 14 June 2019 12:36:32 UTC+3, Damjan Hajsek wrote: > > https://github.com/matthewwall/weewx-interceptor > > this is what I have for interceptor in weewx.conf > > [Interceptor] > # This section is for the network traffic interceptor driver. > > # The driver to use: > driver = user.interceptor > > # Specify the hardware device to capture. Options include: > # acurite-bridge - acurite internet bridge, smarthub, or access > # observer - fine offset WH2600/HP1000/HP1003, ambient WS2902 > # lw30x - oregon scientific LW301/LW302 > # lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge > # wu-client - any hardware that uses the weather underground > protocol > #device_type = acurite-bridge > device_type = observer > port = 990 > -- 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/2dc29325-db15-4831-899a-f256e2c024b4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: weewx stop working
Well installing centos 7.6 on a VM was interesting. WeeWX 3.9.1 was installed from .rpm. It seems that when run under centos7.6 WeeWX (and python) any attempts to log at the debug level are discarded or otherwise lost. With debug=1: [root@VBCentosMaster ~]# cat /etc/weewx/weewx.conf|more # WEEWX CONFIGURATION FILE # # Copyright (c) 2009-2019 Tom Keffer # See the file LICENSE.txt for your rights. ## # This section is for general configuration information. # Set to 1 for extra debug info, otherwise comment it out or set to zero debug = 1 # Root directory of the weewx data file hierarchy for this station WEEWX_ROOT = / # Whether to log successful operations log_success = True # Whether to log unsuccessful operations log_failure = True # How long to wait before timing out a socket (FTP, HTTP) connection socket_timeout = 20 # Do not modify this. It is used when installing and updating weewx. version = 3.9.1 starting WeeWX gives: Jun 16 00:06:28 localhost systemd: Starting SYSV: start and stop the weewx weather system... Jun 16 00:06:28 localhost weewx[7392]: engine: Initializing weewx version 3.9.1 Jun 16 00:06:28 localhost weewx[7392]: engine: Using Python 2.7.5 (default, Apr 9 2019, 14:30:50) #012[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)] Jun 16 00:06:28 localhost weewx[7392]: engine: Platform Linux-3.10.0- 957.el7.x86_64-x86_64-with-centos-7.6.1810-Core Jun 16 00:06:28 localhost weewx[7392]: engine: Locale is 'en_AU.UTF-8' Jun 16 00:06:28 localhost weewx[7392]: engine: pid file is /var/run/weewx. pid Jun 16 00:06:28 localhost weewx: Starting weewx: [ OK ] Jun 16 00:06:28 localhost systemd: Started SYSV: start and stop the weewx weather system. Jun 16 00:06:28 localhost weewx[7397]: engine: Using configuration file /etc /weewx/weewx.conf Jun 16 00:06:28 localhost weewx[7397]: engine: Loading station type Simulator (weewx.drivers.simulator) Jun 16 00:06:28 localhost weewx[7397]: engine: StdConvert target unit is 0x1 Jun 16 00:06:28 localhost weewx[7397]: wxcalculate: The following values will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, windrun=prefer_hardware, heatindex=prefer_hardware, maxSolarRad= prefer_hardware, humidex=prefer_hardware, pressure=prefer_hardware, inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, cloudbase=prefer_hardware Jun 16 00:06:28 localhost weewx[7397]: wxcalculate: The following algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS Jun 16 00:06:28 localhost weewx[7397]: engine: Archive will use data binding wx_binding Jun 16 00:06:28 localhost weewx[7397]: engine: Record generation will be attempted in 'hardware' Jun 16 00:06:28 localhost weewx[7397]: engine: Using archive interval of 300 seconds (specified in weewx configuration) Jun 16 00:06:28 localhost weewx[7397]: engine: Using binding 'wx_binding' to database 'weewx.sdb' Jun 16 00:06:28 localhost weewx[7397]: manager: Starting backfill of daily summaries Jun 16 00:06:28 localhost weewx[7397]: restx: StationRegistry: Registration not requested. Jun 16 00:06:28 localhost weewx[7397]: restx: Wunderground: Posting not enabled. Jun 16 00:06:28 localhost weewx[7397]: restx: PWSweather: Posting not enabled. Jun 16 00:06:28 localhost weewx[7397]: restx: CWOP: Posting not enabled. Jun 16 00:06:28 localhost weewx[7397]: restx: WOW: Posting not enabled. Jun 16 00:06:28 localhost weewx[7397]: restx: AWEKAS: Posting not enabled. Jun 16 00:06:28 localhost weewx[7397]: engine: Starting up weewx version 3.9 .1 Jun 16 00:06:28 localhost weewx[7397]: engine: Clock error is -0.02 seconds (positive is fast) Jun 16 00:06:28 localhost weewx[7397]: engine: Starting main packet loop. WeeWX appears to otherwise run properly it just cannot log at the debug level. Opening a python console importing syslog and doing a few syslog calls produced the same result, anything at LOG_DEBUG was ignored. Not sure where the issue lies, probably needs someone with a better understanding of rsyslog than me. Makes me wonder if given centos' parentage whether RH will be the same. Enough for me, I hurt my brain enough battling with centos, will be glad to get back to debian. 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/048923b3-9094-4717-8a07-c9d1552e4372%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: KeyError: 'temperatureLow'
I don't think it's database corruption, but it took me a minute to figure out what skin you're using. Looks like Belchertown. Looks like an error with the DarkSky forecast. Maybe delete the darksky json file from your html_folder/json subfolder and let it download a new copy. What version of Belchertown are you using? I don't remember seeing daily_data in any recent version. Version 1.0.1 is out now. On Saturday, June 15, 2019 at 1:28:42 AM UTC-4, Scott Grayban wrote: > > Just started getting this error after a months of running with no > issues... is this a db corruption ? > > Jun 14 22:22:24 weewx-pi weewx[23128]: reportengine: Caught unrecoverable > exception in generator 'weewx.cheetahgenerator.CheetahGenerator' > Jun 14 22:22:24 weewx-pi weewx[23128]: 'temperatureLow' > Jun 14 22:22:24 weewx-pi weewx[23128]: Traceback (most > recent call last): > Jun 14 22:22:24 weewx-pi weewx[23128]: File > "/usr/share/weewx/weewx/reportengine.py", line 204, in run > Jun 14 22:22:24 weewx-pi weewx[23128]: obj.start() > Jun 14 22:22:24 weewx-pi weewx[23128]: File > "/usr/share/weewx/weewx/reportengine.py", line 300, in start > Jun 14 22:22:24 weewx-pi weewx[23128]: self.run() > Jun 14 22:22:24 weewx-pi weewx[23128]: File > "/usr/share/weewx/weewx/cheetahgenerator.py", line 160, in run > Jun 14 22:22:24 weewx-pi weewx[23128]: ngen = self. > generate(gen_dict[section_name], self.gen_ts) > Jun 14 22:22:24 weewx-pi weewx[23128]: File > "/usr/share/weewx/weewx/cheetahgenerator.py", line 234, in generate > Jun 14 22:22:24 weewx-pi weewx[23128]: ngen += self. > generate(section[subsection], gen_ts) > Jun 14 22:22:24 weewx-pi weewx[23128]: File > "/usr/share/weewx/weewx/cheetahgenerator.py", line 234, in generate > Jun 14 22:22:24 weewx-pi weewx[23128]: ngen += self. > generate(section[subsection], gen_ts) > Jun 14 22:22:24 weewx-pi weewx[23128]: File > "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate > Jun 14 22:22:24 weewx-pi weewx[23128]: default_binding) > Jun 14 22:22:24 weewx-pi weewx[23128]: File > "/usr/share/weewx/weewx/cheetahgenerator.py", line 374, in _getSearchList > Jun 14 22:22:24 weewx-pi weewx[23128]: searchList += obj > .get_extension_list(timespan, db_lookup) > Jun 14 22:22:24 weewx-pi weewx[23128]: File > "/usr/share/weewx/user/belchertown.py", line 599, in get_extension_list > Jun 14 22:22:24 weewx-pi weewx[23128]: output += ' class="forecast-high">'+str( int( daily_data["temperatureHigh"] ) > )+' > | '+str( int( daily_data["temperatureLow"] ) )+ > '' > Jun 14 22:22:24 weewx-pi weewx[23128]: KeyError: > 'temperatureLow' > Jun 14 22:22:24 weewx-pi weewx[23128]: Generator terminated > > > -- 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/2eaa6aa0-5536-4749-a305-0a8b25234d32%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Weewx running on Raspberry Pi using NAS and Read-Only SD Card
I initially tried BerryBoot out of curiosity and did not expect to keep using it but decided to do so when I found it worked so well. I have only had one SD Card fail in about five year of using weewx - and that by conincidence was one week after I configured the NFS mounts so I was lucky I didn't lose anything. Even before that I was using log2ram to minimise writes to the SD Card. Once BerryBoot has been configured with the iSCSI Target and an OS installed, it can be flagged as the default OS so it boots up automatically, no manual intervention required. It displays the boot menu for 20 secs (default time) before booting the default OS. If you run headless (no monitor attached), it can be configured to run up a VNC server so you can view the boot menu and configure remotely. Once the OS starts booting, you do lose the VNC. The other advantage is that you end up with a fast filesystem - faster than the SD card. It will also work over WiFi but I have not tried it. I expect it wouldn't be as stable (or as fast) as using an Ethernet cable. Also, because it uses the NAS filesystem, you can also utilise the NAS's snapshot and backup features - depends on how paranoid you want to be. It's not a solution for everyone but it impressed me so I kept using it. Peter -- 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/390855bc-58b3-48e2-8485-8a6ef648077d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Web Server auf dem Raspberry Apache2
Das wurde mir angezeigt nach dem ich den Befehl eingegeben habe. sudo tail -f /var/log/syslog Jun 15 08:50:24 raspberrypi weewx[5203]: cheetahgenerator: Generated 8 files for report SeasonsReport in 1.80 seconds Jun 15 08:50:25 raspberrypi weewx[5203]: imagegenerator: Generated 14 images for SeasonsReport in 1.16 seconds Jun 15 08:50:25 raspberrypi weewx[5203]: copygenerator: copied 0 files to /home/weewx/public_html Jun 15 08:55:25 raspberrypi weewx[5203]: manager: Added record 2019-06-15 08:55:00 CEST (1560581700) to database 'weewx.sdb' Jun 15 08:55:25 raspberrypi weewx[5203]: manager: Added record 2019-06-15 08:55:00 CEST (1560581700) to daily summary in 'weewx.sdb' Jun 15 08:55:25 raspberrypi weewx[5203]: restx: AWEKAS: Published record 2019-06-15 08:55:00 CEST (1560581700) Jun 15 08:55:26 raspberrypi weewx[5203]: restx: Wunderground-PWS: Published record 2019-06-15 08:55:00 CEST (1560581700) Jun 15 08:55:27 raspberrypi weewx[5203]: cheetahgenerator: Generated 8 files for report SeasonsReport in 1.78 seconds Jun 15 08:55:28 raspberrypi weewx[5203]: imagegenerator: Generated 14 images for SeasonsReport in 1.15 seconds Jun 15 08:55:28 raspberrypi weewx[5203]: copygenerator: copied 0 files to /home/weewx/public_html Das die files in diesem Ordner liegen wusste ich. Nur wie bringe ich apache2 dazu in diesem Ordner nach zu sehen. Nach dem kopieren der weewx.conf sudo cp util/apache/conf.d/weewx.conf /etc/apache2/conf.d Sieht es in der conf.d von apache2 so aus. Alias /weewx /home/weewx/public_html Options FollowSymlinks AllowOverride None Require all granted Ist das richtig oder muss ich noch etwas tun um apache2 dazu zu bringen unter /home/weewx/public_html die Daten ab zu holen und im Browser an zu zeigen? Ich dachte wenn ich alles so mache wie auf der Seite beschrieben http://www.weewx.com/docs/usersguide.htm#If_the_server_is_on_the_same_machine funktioniert das. -- 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/add60cf0-dfbc-4461-a7ce-13f4c185787d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Web Server auf dem Raspberry Apache2
Das wurde mir angezeigt nach dem ich den Befehl eingegeben habe. sudo tail -f /var/log/syslog Jun 15 08:50:24 raspberrypi weewx[5203]: cheetahgenerator: Generated 8 files for report SeasonsReport in 1.80 seconds Jun 15 08:50:25 raspberrypi weewx[5203]: imagegenerator: Generated 14 images for SeasonsReport in 1.16 seconds Jun 15 08:50:25 raspberrypi weewx[5203]: copygenerator: copied 0 files to /home/weewx/public_html Jun 15 08:55:25 raspberrypi weewx[5203]: manager: Added record 2019-06-15 08:55:00 CEST (1560581700) to database 'weewx.sdb' Jun 15 08:55:25 raspberrypi weewx[5203]: manager: Added record 2019-06-15 08:55:00 CEST (1560581700) to daily summary in 'weewx.sdb' Jun 15 08:55:25 raspberrypi weewx[5203]: restx: AWEKAS: Published record 2019-06-15 08:55:00 CEST (1560581700) Jun 15 08:55:26 raspberrypi weewx[5203]: restx: Wunderground-PWS: Published record 2019-06-15 08:55:00 CEST (1560581700) Jun 15 08:55:27 raspberrypi weewx[5203]: cheetahgenerator: Generated 8 files for report SeasonsReport in 1.78 seconds Jun 15 08:55:28 raspberrypi weewx[5203]: imagegenerator: Generated 14 images for SeasonsReport in 1.15 seconds Jun 15 08:55:28 raspberrypi weewx[5203]: copygenerator: copied 0 files to /home/weewx/public_html Das die files in diesem Ordner liegen wusste ich. Nur wie bringe ich apache2 dazu in diesem Ordner nach zu sehen. Nach dem kopieren der weewx.conf sudo cp util/apache/conf.d/weewx.conf /etc/apache2/conf.d Sieht es in der conf.d vaon apache2 so aus. Alias /weewx /home/weewx/public_html Options FollowSymlinks AllowOverride None Require all granted Ist das richtig oder muss ich noch etwas tun um apache2 dazu zu bringen unter /home/weewx/public_html die Daten ab zu holen und im Browser an zu zeigen? Ich dachte wenn ich alles so mache wie auf der Seite beschrieben http://www.weewx.com/docs/usersguide.htm#If_the_server_is_on_the_same_machine funktioniert das. -- 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/f61da6cb-b416-400c-96b1-5a1dafcfaaa4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
