Without root: ssh [email protected] -p2222 -v OpenSSH_8.4p1 Raspbian-5+deb11u2, OpenSSL 1.1.1w 11 Sep 2023 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug1: Connecting to kq5s.com [199.250.194.206] port 2222. debug1: Connection established. debug1: identity file /home/pi/.ssh/id_rsa type 0 debug1: identity file /home/pi/.ssh/id_rsa-cert type -1 debug1: identity file /home/pi/.ssh/id_dsa type -1 debug1: identity file /home/pi/.ssh/id_dsa-cert type -1 debug1: identity file /home/pi/.ssh/id_ecdsa type -1 debug1: identity file /home/pi/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/pi/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/pi/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/pi/.ssh/id_ed25519 type -1 debug1: identity file /home/pi/.ssh/id_ed25519-cert type -1 debug1: identity file /home/pi/.ssh/id_ed25519_sk type -1 debug1: identity file /home/pi/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/pi/.ssh/id_xmss type -1 debug1: identity file /home/pi/.ssh/id_xmss-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.4p1 Raspbian-5+deb11u2 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4 debug1: match: OpenSSH_7.4 pat OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x04000002 debug1: Authenticating to kq5s.com:2222 as 'xxxxxx' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: aes128-ctr MAC: [email protected] compression: none debug1: kex: client->server cipher: aes128-ctr MAC: [email protected] compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ecdsa-sha2-nistp256 SHA256:p4xX8yxXsJ+3l/Xg8B29Qbdc5r9iHXvoX0bpFCpCwes debug1: Host '[kq5s.com]:2222' is known and matches the ECDSA host key. debug1: Found key in /home/pi/.ssh/known_hosts:2 debug1: rekey out after 4294967296 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 4294967296 blocks debug1: Will attempt key: /home/pi/.ssh/id_rsa RSA SHA256:PCS+HvqfV/Y0X/UuplMbVw+cfzk+v5Bk+pC7hQubdbU debug1: Will attempt key: /home/pi/.ssh/id_dsa debug1: Will attempt key: /home/pi/.ssh/id_ecdsa debug1: Will attempt key: /home/pi/.ssh/id_ecdsa_sk debug1: Will attempt key: /home/pi/.ssh/id_ed25519 debug1: Will attempt key: /home/pi/.ssh/id_ed25519_sk debug1: Will attempt key: /home/pi/.ssh/id_xmss debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512> debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering public key: /home/pi/.ssh/id_rsa RSA SHA256:PCS+HvqfV/Y0X/UuplMbVw+cfzk+v5Bk+pC7hQubdbU debug1: Server accepts key: /home/pi/.ssh/id_rsa RSA SHA256:PCS+HvqfV/Y0X/UuplMbVw+cfzk+v5Bk+pC7hQubdbU debug1: Authentication succeeded (publickey). Authenticated to kq5s.com ([199.250.194.206]:2222). debug1: channel 0: new [client-session] debug1: Requesting [email protected] debug1: Entering interactive session. debug1: pledge: network debug1: client_input_global_request: rtype [email protected] want_reply 0 debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 debug1: Sending env LC_ALL = en_US.UTF-8 [xxxxxx@ecbiz246 ~]$
On Sunday, October 29, 2023 at 5:54:01 PM UTC-5 Tom -KQ5S wrote: > No cron jobs running rsync. > > The only files in my /root/.ssh directory are the rsa keys and a > known_hosts file. There is no config file. > > ps uaxw | grep weewx > root 10111 2.6 0.6 117148 52824 ? Ssl 11:31 9:09 > /usr/bin/python3 /home/weewx/bin/weewxd /home/weewx/weewx.conf > pi 13411 0.0 0.0 7444 580 pts/4 S+ 17:21 0:00 grep > --color=auto weewx > On Sunday, October 29, 2023 at 5:51:46 PM UTC-5 Tom -KQ5S wrote: > >> sudo ssh [email protected] -p2222 -v >> OpenSSH_8.4p1 Raspbian-5+deb11u2, OpenSSL 1.1.1w 11 Sep 2023 >> debug1: Reading configuration data /etc/ssh/ssh_config >> debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf >> matched no files >> debug1: /etc/ssh/ssh_config line 21: Applying options for * >> debug1: Connecting to kq5s.com [199.250.194.206] port 2222. >> debug1: Connection established. >> debug1: identity file /root/.ssh/id_rsa type 0 >> debug1: identity file /root/.ssh/id_rsa-cert type -1 >> debug1: identity file /root/.ssh/id_dsa type -1 >> debug1: identity file /root/.ssh/id_dsa-cert type -1 >> debug1: identity file /root/.ssh/id_ecdsa type -1 >> debug1: identity file /root/.ssh/id_ecdsa-cert type -1 >> debug1: identity file /root/.ssh/id_ecdsa_sk type -1 >> debug1: identity file /root/.ssh/id_ecdsa_sk-cert type -1 >> debug1: identity file /root/.ssh/id_ed25519 type -1 >> debug1: identity file /root/.ssh/id_ed25519-cert type -1 >> debug1: identity file /root/.ssh/id_ed25519_sk type -1 >> debug1: identity file /root/.ssh/id_ed25519_sk-cert type -1 >> debug1: identity file /root/.ssh/id_xmss type -1 >> debug1: identity file /root/.ssh/id_xmss-cert type -1 >> debug1: Local version string SSH-2.0-OpenSSH_8.4p1 Raspbian-5+deb11u2 >> debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4 >> debug1: match: OpenSSH_7.4 pat >> OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* >> >> compat 0x04000002 >> debug1: Authenticating to kq5s.com:2222 as 'xxxxx' >> debug1: SSH2_MSG_KEXINIT sent >> debug1: SSH2_MSG_KEXINIT received >> debug1: kex: algorithm: curve25519-sha256 >> debug1: kex: host key algorithm: ecdsa-sha2-nistp256 >> debug1: kex: server->client cipher: aes128-ctr MAC: [email protected] >> compression: none >> debug1: kex: client->server cipher: aes128-ctr MAC: [email protected] >> compression: none >> debug1: expecting SSH2_MSG_KEX_ECDH_REPLY >> debug1: Server host key: ecdsa-sha2-nistp256 >> SHA256:p4xX8yxXsJ+3l/Xg8B29Qbdc5r9iHXvoX0bpFCpCwes >> debug1: Host '[kq5s.com]:2222' is known and matches the ECDSA host key. >> debug1: Found key in /root/.ssh/known_hosts:2 >> debug1: rekey out after 4294967296 blocks >> debug1: SSH2_MSG_NEWKEYS sent >> debug1: expecting SSH2_MSG_NEWKEYS >> debug1: SSH2_MSG_NEWKEYS received >> debug1: rekey in after 4294967296 blocks >> debug1: Will attempt key: /root/.ssh/id_rsa RSA >> SHA256:PCS+HvqfV/Y0X/UuplMbVw+cfzk+v5Bk+pC7hQubdbU >> debug1: Will attempt key: /root/.ssh/id_dsa >> debug1: Will attempt key: /root/.ssh/id_ecdsa >> debug1: Will attempt key: /root/.ssh/id_ecdsa_sk >> debug1: Will attempt key: /root/.ssh/id_ed25519 >> debug1: Will attempt key: /root/.ssh/id_ed25519_sk >> debug1: Will attempt key: /root/.ssh/id_xmss >> debug1: SSH2_MSG_EXT_INFO received >> debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512> >> debug1: SSH2_MSG_SERVICE_ACCEPT received >> debug1: Authentications that can continue: publickey >> debug1: Next authentication method: publickey >> debug1: Offering public key: /root/.ssh/id_rsa RSA >> SHA256:PCS+HvqfV/Y0X/UuplMbVw+cfzk+v5Bk+pC7hQubdbU >> debug1: Server accepts key: /root/.ssh/id_rsa RSA >> SHA256:PCS+HvqfV/Y0X/UuplMbVw+cfzk+v5Bk+pC7hQubdbU >> debug1: Authentication succeeded (publickey). >> Authenticated to kq5s.com ([199.250.194.206]:2222). >> debug1: channel 0: new [client-session] >> debug1: Requesting [email protected] >> debug1: Entering interactive session. >> debug1: pledge: network >> debug1: client_input_global_request: rtype [email protected] >> want_reply 0 >> debug1: Sending environment. >> debug1: Sending env LANG = en_US.UTF-8 >> debug1: Sending env LC_ALL = en_US.UTF-8 >> [kxxxx@ecbiz246 ~]$ >> On Sunday, October 29, 2023 at 5:33:37 PM UTC-5 vince wrote: >> >>> So yet again - what is the ~/.ssh/config entry for kq5s.com for the >>> user weewx is running as. >>> Typically that is root based on the paths you've provided. >>> >>> >>> - Are you 'sure' you are running weewx specifically as user pi ? >>> >>> >>> - if you're running as the non-standard user pi, show us how you did >>> that >>> >>> >>> - What is in /root/.ssh/config ? >>> >>> >>> - What is in /home/pi/.ssh/config ? >>> >>> >>> - Are you 'sure' you do not have any cron entries trying to do rsync >>> outside weewx ? >>> >>> >>> You should be able to do something like "ssh [email protected] date" >>> successfully if you have shell access there. >>> >>> On Sunday, October 29, 2023 at 3:25:55 PM UTC-7 Tom -KQ5S wrote: >>> >>>> Thanks Chris. >>>> >>>> ps uaxw | grep weewx >>>> root 10111 2.6 0.6 117148 52824 ? Ssl 11:31 9:09 >>>> /usr/bin/python3 /home/weewx/bin/weewxd /home/weewx/weewx.conf >>>> pi 13411 0.0 0.0 7444 580 pts/4 S+ 17:21 0:00 grep >>>> --color=auto weewx >>>> >>>> [[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 >>>> >>>> >>>> On Sunday, October 29, 2023 at 5:10:44 PM UTC-5 [email protected] >>>> wrote: >>>> >>>>> So, here's one of mine: >>>>> renogy0_/home/crichmon> cat .ssh/config >>>>> # hosts with more than two components are probably external >>>>> PubkeyAuthentication yes >>>>> # relax checking on internal hosts/networks # hopefully this list will >>>>> not grow and all new site's networks will be >>>>> Host 192.168.0.* 192.168.1.* 192.168.2.* 192.168.3.* >>>>> StrictHostKeyChecking no >>>>> Host *.chaos.home *.csrhome.home *.garage.home >>>>> StrictHostKeyChecking no >>>>> Host *.* >>>>> StrictHostKeyChecking yes >>>>> >>>>> Not particularly interesting. I'd suggest looking at: man ssh_config >>>>> At the end of the day, this is not the likely problem. As you said, >>>>> the issue seems to be somewhat intermittent, so it isn't >>>>> a complete config failure, but something a bit harder to figure out. >>>>> >>>>> Still, we need as many details as you can provide. One thing... You >>>>> said you are running weewx as userID pi. >>>>> Is that a fact or an assumption? How do you know? ps uaxw | grep >>>>> weewx will give that answer. Knowing that >>>>> will narrow down the possible problems. The other bit is how your >>>>> rsync is configured. We can sort-of see that >>>>> from the logs, but nothing is clear yet. >>>>> You still haven't provided the RSYNC config. One of mine is: >>>>> [[RSYNC]] >>>>> skin = Rsync >>>>> enable = false >>>>> server = router1 >>>>> user = crichmon >>>>> path = /var/www/html/solar >>>>> delete = 0 >>>>> Nothing secret here, at least for me. This one is internal to my >>>>> network. I don't actually have weewx push externally. >>>>> That's done elsewhere. >>>>> >>>>> The other bit is the mystery of how ssh is set up for both ends of >>>>> your connection, and details of what happens >>>>> when running either ssh or rsync manually. >>>>> >>>>> I'll step out here a bit: >>>>> renogy0_/home/crichmon> ls -la .ssh >>>>> drwx------ 2 crichmon crichmon 4096 Jul 19 12:50 . >>>>> drwxr-xr-x 14 crichmon crichmon 4096 Oct 29 15:57 .. >>>>> -rw------- 1 crichmon crichmon 1029 Aug 24 2019 authorized_keys >>>>> -rw------- 1 crichmon crichmon 415 Jul 19 12:50 config >>>>> -rw------- 1 crichmon crichmon 883 Jan 16 2009 id_rsa >>>>> -rw------- 1 crichmon crichmon 226 Jan 16 2009 id_rsa.pub >>>>> -rw------- 1 crichmon crichmon 1675 Jan 18 2019 id_rsa_r1 >>>>> -rw------- 1 crichmon crichmon 398 Jan 18 2019 id_rsa_r1.pub >>>>> -rw------- 1 crichmon crichmon 2558 Jul 7 2019 identity >>>>> -rw------- 1 crichmon users 26801 Sep 27 15:35 known_hosts >>>>> >>>>> The same from you might also eliminate a possible source of error. >>>>> We'd need this for all your users and all >>>>> ends of the connections, or at least confirmation that your >>>>> permissions are reasonable. >>>>> Chris >>>>> On Sunday, October 29, 2023 at 3:26:51 PM UTC-6 Tom -KQ5S wrote: >>>>> >>>>>> Hi Vince, >>>>>> As mentioned earlier I do not have a .ssh/config file so perhaps that >>>>>> is the issue. Would the file look like: >>>>>> >>>>>> Host website >>>>>> Hostname kq5s.com >>>>>> User pi (or the name in my [Rsync] part of weewx.conf) >>>>>> Port 2222 >>>>>> >>>>>> On Sunday, October 29, 2023 at 4:12:43 PM UTC-5 vince wrote: >>>>>> >>>>>>> you said you run as user 'pi' so you need to provide your >>>>>>> /home/pi/.ssh/config file so we see the rsync/ssh setup for the user >>>>>>> weewx >>>>>>> is running as... >>>>>>> >>>>>>> On Sunday, October 29, 2023 at 2:09:56 PM UTC-7 Tom -KQ5S wrote: >>>>>>> >>>>>>>> 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/a3732586-7a52-47ae-9d7f-3cc8e0759268n%40googlegroups.com.
