> Struggles to create the charts ? Lets see some logs showing that. You did 
not post any debug=1 logs.

I did, in fact, 400+ lines' worth.  Nothing that I saw there about image 
generation, but it's certainly possible I overlooked it.  I inferred the 
"struggle" from the fact that, at that time, index.html had updated but 
none of the charts had.  Over time (30+ minutes), the charts gradually 
updated.

> The only thing I can think of along those lines is weewx being slow 
calculating things you refer to in your skin that are not elements the db 
but that shouldn’t happen with a clean v5 installation tunning unaltered 
Seasons

If it's still using the existing database, which it was, that seems 
plausible.  Rich also mentioned something similar.

> I’m thinking you have the old wview not wview-extended db perhaps. You 
should have around 113 elements in the archive table not the small old 
schema with 52 or so.

I think you're right.  `describe archive` lists 53 rows.  Looks like some 
reading 
at 
https://weewx.com/docs/5.1/custom/database/#modify-the-schema-of-an-existing-database
 
is in order.

On Saturday, June 27, 2026 at 4:31:07 PM UTC-4 Vince Skahan wrote:

> Struggles to create the charts ? Lets see some logs showing that. You did 
> not post any debug=1 logs.
>
> The only thing I can think of along those lines is weewx being slow 
> calculating things you refer to in your skin that are not elements the db 
> but that shouldn’t happen with a clean v5 installation tunning unaltered 
> Seasons.
>
> On Saturday, June 27, 2026 at 12:42:32 PM UTC-7 Tom Keffer wrote:
>
>> On Sat, Jun 27, 2026 at 12:03 PM [email protected] <[email protected]> 
>> wrote:
>>
>>> > MySQL server. You had a "Cannot connect" error on startup, so there 
>>> is something flaky about the connection.
>>>
>>> It seems weewx starts up earlier than mysql, and thus fails to connect.  
>>> It also seems to shut down earlier (on system shutdown or reboot) than 
>>> mysql, leading to errors then.
>>>
>>> Enabling the general query log and following it doesn't show anything 
>>> obvious.  Nothing gets logged to the slow query log.
>>>
>>
>> It should show the types of queries running and how long they take. Are 
>> you saying they were all quick?  The time *must* be going somewhere!
>>
>> Trying to rule out sources of a slowdown, I moved the VM storage to a 
>>> local disk (it had been over the network), and again rebooted.  And it now 
>>> quickly generates the index.html page for the Seasons report, but it still 
>>> seems to be struggling to create the --
>>>
>>
>> Good idea. Try using sqlite and see if that's faster.
>>
>> -tk
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/weewx-user/367d2d60-042b-4ac0-a5e2-b836b7d0e6b0n%40googlegroups.com.

Reply via email to