I don't know if it makes a difference but I just did a search and I have 
the same .ssh folder under /home/pi/.ssh as well as /boot/.ssh.  I must 
have put it there while trying to trouble shoot the problem.

On Sunday, October 29, 2023 at 3:59:29 PM UTC-5 Tom -KQ5S wrote:

> Thanks, Vince for the help as I have seen you help many others on here.  I 
> wasn't shouting before I merely copied and pasted what my ISP sent me. 
>  That is the font they used.  
>
> The only files in my /root/.ssh directory are the rsa keys and a 
> known_hosts file.  I don't remember creating a config file so that may be 
> part of the problem.  I see where the instructions under [RSYNC] say to put 
> the server in the .ssh/config file.  Is the config file as simple as:
> ===================================================
> Host website
>         Hostname kq5s.com
>        User pi (or name in my [Rsync] part of weewx.conf)
>         Port 2222
> ==================================================
>
> [RSYNC]]
>         # rsync'ing to a webserver is treated as just another report
>         skin = Rsync
>         enable = true
>         server = kq5s.com
>         user = XXXXX ( not sure if I should post this or not.  It is a 
> user on my internet site)
>         path = public_html
>         port = 2222
>         
>         delete = 0
>
>
> Tom
> On Sunday, October 29, 2023 at 2:31:10 PM UTC-5 vince wrote:
>
>> I'm not understanding what you guys think you see.   I don't see anything 
>> in his logs saying the total time to do things is exceeding the 5-minute 
>> default archive interval.  His possibly edited log snippet above showed 
>> rsync happening every 5 minutes which is normal.  It only takes a couple 
>> seconds which is normal.   The number of files is reasonable given the 
>> skins he's using. 
>>
>> What is 'not' normal is the support ticket reply from his ISP saying he's 
>> intermittently trying to connect to an invalid user id on the remote side.
>>
>> Again - lets see your RSYNC stanza(s) from weewx.conf and also your 
>> .ssh/config stanza for the account you're using locally to connect to the 
>> ISP server.   This is almost certainly a rsync/ssh configuration issue 
>> based on what I've seen in the thread above.
>>
>> On Sunday, October 29, 2023 at 11:48:48 AM UTC-7 [email protected] wrote:
>>
>>> Tom,
>>>     So, from your hosting provider, you are getting two types of 
>>> errors.  One for userID, the other for MaxStartups.  The #27 and #28 are 
>>> the number of
>>> Startups, so something is getting hung up somewhere between you and your 
>>> hosting service, and weewx seems to be the victim.  This sure seems like
>>> a basic networking/ssh setup issue that's best debugged by hand outside 
>>> of weewx.  One more thing you can try is simply ssh'ing to your hosting 
>>> site,
>>> but include a -v (or two or three v's) in the command line.  It 
>>> generates a LOT of messages, but take your time to see what it's telling 
>>> you if there's a failure.
>>> Make sure all your permissions are correct in all the places you have an 
>>> .ssh directory (directory: chmod 2700, files: chmod 0600).
>>> Chris
>>>
>>> On Sunday, October 29, 2023 at 12:16:10 PM UTC-6 vince wrote:
>>>
>>>> You are posting very cryptic information making helping you very 
>>>> difficult.  And your font looks like you're yelling.
>>>>
>>>> We need to see pieces of your actual configuration files:
>>>>
>>>>    - post your weewx.conf RSYNC section(s)
>>>>    - post your ~/.ssh/config section for the host(s) you referenced in 
>>>>    the RSYNC section in weewx.conf
>>>>    - (make sure you show use the ssh config for the user weewx runs 
>>>>    as, whatever you are using)
>>>>
>>>> It almost sounds like you have multiple RSYNC sections in weewx and you 
>>>> are trying to upload twice, once to one user, once to a different user. 
>>>>  Regardless, we need to see your actual config file sections to help much.
>>>>
>>>>

-- 
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 on the web visit 
https://groups.google.com/d/msgid/weewx-user/00bed683-e967-40ff-a34c-9130ff69470fn%40googlegroups.com.

Reply via email to