Has to be?? Both using same router, same network, etc via ethernet.
Firewall enabled?
Port 22 open / enabled?
Closing down machine 2, and machine one for today . . . have to get to work. Later on.
@non_space you need to check both machines gateway address… if it’s wrong on the machine not working properly this could be the underlying issue with a slow boot…
ip a
ip route
I’m on NetworkManager here;
ip route
default via 192.168.xxx.xxx dev eno1 proto static metric 100
192.168.xxx.xxx/24 dev eno1 proto kernel scope link src 192.168.xxx.xxx metric 100
2 Likes
Alrighty . . . but, question, would not the IP address and gateway be the same for each distro that I am running on the machine?
Today is Deb Sid day and it boots to the log in manager in the blink of an eye, and loads the GUI after the password in another blink.
On TW I also am using Network Manager , , , Sid has another layout in the toolbar, so I don’t know what they are using . . . but, just for the record, the other 6 distros have so far not had this TW slowness to do stuff problem. Caveat being that there is a Gecko rolling distro in the mix as well, so far TW is the exclusive condition.
That all depends if using dhcp. So in Sid can you ping from the other machine to its ip address
Already off to work . . . but as far as “ping” goes, I could ping from the machine 1 to the TW machine 2 the other day . . . it just won’t “connect” via ssh.
OK, same question as before, where do I find “firewalld” or turn it off and on?? I haven’t specifically turned it on, but if the system provides it, then perhaps that is one of the problems with ssh??
Check status with
systemctl status firewalldYou can stop it (if needed) with
sudo systemctl stop firewalld
1 Like
And note the name it is the system Firewall and should only be shut down for testing.
1 Like
OK, when I stop the firewalld then I can get to the same question I got to before, showing me a sha256?? “fingerprint” and asking me if I want to move forward>
I typed yes, then it shows me a cursor to enter my password . . . and as it was before, entering the login/admin password for the system, keeps showing that same line . . . .
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '192.168.' (ED25) to the list of known hosts.
(no@192.168.xxx.xxx) Password:
(no@192.168.) Password:
(n@192.168.) Password:
no@192.168. password:
I looked at the ip route data and as far as I can tell, as posted before the IP data for the two machines is one numeral different.
Booting up the TW distro still takes several minutes to get past the black screen and get the cursor up there and then another minute or more to get the GUI populated. Then half a minute to launch the console. So machine 2 is still in distress. And something is interfering with ssh connection.
I have turned firewalld back on on the afflicted system.
@non_space and you have the 01-ssh.conf file in place? The username on the machine (client) your running ssh from is the same username as on the Tumbleweed machine?
Add some verbosity to the command ssh -v 192.168.xxx.xxx and post the error(s) you see when it keeps asking for the password…
And your up to the 20230917 snapshot release?
Well, for some reason I ran "sudo ssh -v 192. and that through a series of “debugs” did get me to root cursor on the TW problem machine!!???
The user names are not the same, but close. The TW system has been updated every day for the last few days, a few packages here and there, problems still happening. Today was Leap 15.6 day, as for all the other systems, fast log in,fast boot of apps. TW still takes a lot of time to launch the console, etc.
So now what will we do with our remote access? Do we have a “diagnosis” that we are pursuing?? I’m not following how this is related to an IP address problem if all of my other installs are running fine on the samemachine?
sudo ssh -v 192.168.xxx.xxx
[sudo] password for no:
OpenSSH_9.4p1, OpenSSL 3.1.2 1 Aug 2023
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 2: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: Connecting to 192.168. [192.168.] port 22.
debug1: Connection established.
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_rsa-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_ed type -1
debug1: identity file /root/.ssh/id_ed-cert type -1
debug1: identity file /root/.ssh/id_ed_sk type -1
debug1: identity file /root/.ssh/id_ed_sk-cert type -1
debug1: identity file /root/.ssh/id_xmss type -1
debug1: identity file /root/.ssh/id_xmss-cert type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: identity file /root/.ssh/id_dsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_9.4
debug1: Remote protocol version 2.0, remote software version OpenSSH_9.3
debug1: compat_banner: match: OpenSSH_9.3 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 192.168.:22 as 'root'
debug1: load_hostkeys: fopen /root/.ssh/known_hosts: No such file or directory
debug1: load_hostkeys: fopen /root/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: sntrupxxxxxxx-sha512@openssh.com
debug1: kex: host key algorithm: ssh-xxxxxxxx
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-ed25519 SHA256:xxxxxxxxxxxxxxxxxxxxxxxxxx
debug1: load_hostkeys: fopen /root/.ssh/known_hosts: No such file or directory
debug1: load_hostkeys: fopen /root/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: hostkeys_find_by_key_hostfile: hostkeys file /root/.ssh/known_hosts does not exist
debug1: hostkeys_find_by_key_hostfile: hostkeys file /root/.ssh/known_hosts2 does not exist
debug1: hostkeys_find_by_key_hostfile: hostkeys file /etc/ssh/ssh_known_hosts does not exist
debug1: hostkeys_find_by_key_hostfile: hostkeys file /etc/ssh/ssh_known_hosts2 does not exist
The authenticity of host '192.168. (192.168.)' can't be established.
ED25519 key fingerprint is SHA256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '192.168.' (EDxxxxx) to the list of known hosts.
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: /root/.ssh/id_rsa
debug1: Will attempt key: /root/.ssh/id_ecdsa
debug1: Will attempt key: /root/.ssh/id_ecdsa_sk
debug1: Will attempt key: /root/.ssh/id_edxxxxx
debug1: Will attempt key: /root/.ssh/id_edxxxxx_sk
debug1: Will attempt key: /root/.ssh/id_xmss
debug1: Will attempt key: /root/.ssh/id_dsa
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-edxxxx,sk-ssh-edxxxx@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ecdsa-sha2-nistp256@openssh.com,webauthn-sk-ecdsa-sha2-nistp256@openssh.com,ssh-dss,ssh-rsa,rsa-sha2-256,rsa-sha2-512>
debug1: kex_input_ext_info: publickey-hostbound@openssh.com=<0>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /root/.ssh/id_rsa
debug1: Trying private key: /root/.ssh/id_ecdsa
debug1: Trying private key: /root/.ssh/id_ecdsa_sk
debug1: Trying private key: /root/.ssh/id_edxxxxxx
debug1: Trying private key: /root/.ssh/id_edxxxxxx
debug1: Trying private key: /root/.ssh/id_xmss
debug1: Trying private key: /root/.ssh/id_dsa
debug1: Next authentication method: keyboard-interactive
(root@192.168.) Password:
Authenticated to 192.168. ([192.168.]:22) using "keyboard-interactive".
debug1: channel 0: new session [client-session] (inactive timeout: 0)
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: filesystem
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
debug1: client_input_hostkeys: searching /root/.ssh/known_hosts for 192.168. / (none)
debug1: client_input_hostkeys: searching /root/.ssh/known_hosts2 for 192.168. / (none)
debug1: client_input_hostkeys: hostkeys file /root/.ssh/known_hosts2 does not exist
Learned new hostkey: RSA SHA256:xxxxxxxxxxxxxxxxxxxxxx
Learned new hostkey: ECDSA xxxxxxxxxxxxxxxxxxxxxxxxxx
Adding new key for 192.168 to /root/.ssh/known_hosts: ssh-rsa SHA256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adding new key for 192.168 to /root/.ssh/known_hosts: ecdsa-sha2-nistp256 SHA256:Aqc+xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
debug1: update_known_hosts: known hosts file /root/.ssh/known_hosts2 does not exist
debug1: pledge: fork
Have a lot of fun...
n-macpro02:~ #
@non_space so you have to append the username on the Tumbleweed machine to the ssh command, so ssh tw_username@192.168.xxx.xxx.
So, on the Tumbleweed machine, set the default to multi-user.target and reboot the machine, turn off the firewall etc.
Now on the client log in at your user and switch to root user and run journalctl -f. Not on the Tumbleweed machine, run systemctl isolate graphical.target and on the machine running the journal and watch the output, especially time stamps to see what may be slowing it down.
So, finally got it all figured out . . . ran the “journalctl -f” on the client and then the “systemctl isolate graphical.target” on the problem TW machine. And there were a number of errors that showed up, but one of the problems is that when we did the “isolate graphical.target” move the system actually works fairly quickly . . . unlike when back in regular system. But, after I revived from suspend I opened a few apps, the pasted data is from when I opened YaSt.
The “failure to load nouveau” was one of the repeated errors that showed up, time was used for another step … . . I don’t know if that will give an idea of the potential problem?? There was another red error on aspect of bluetooth, but I don’t use BT.
typSep 21 11:38:26 n-MacPro.home dbus-daemon[3611]: [session uid=0 pid=3611] Activating via systemd: service name='org.freedesktop.impl.portal.desktop.gtk' unit='xdg-desktop-portal-gtk.service' requested by ':1.2' (uid=0 pid=3613 comm="/usr/libexec/xdg-desktop-portal")
Sep 21 11:38:26 n-MacPro.home systemd[1696]: Starting Portal service (GTK/GNOME implementation)...
Sep 21 11:38:26 n-MacPro.home xdg-desktop-por[3636]: cannot open display:
Sep 21 11:38:26 n-MacPro.home systemd[1696]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Sep 21 11:38:26 n-MacPro.home systemd[1696]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Sep 21 11:38:26 n-MacPro.home systemd[1696]: Failed to start Portal service (GTK/GNOME implementation).
Sep 21 11:38:26 n-MacPro.home y2controlcenter[3609]: Qt: Session management error: None of the authentication protocols specified are supported
Sep 21 11:38:26 n-MacPro.home xdg-su[3609]: libGL error: MESA-LOADER: failed to open nouveau: /usr/lib64/dri/nouveau_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)
Sep 21 11:38:26 n-MacPro.home xdg-su[3609]: libGL error: failed to load driver: nouveau
Sep 21 11:38:26 n-MacPro.home xdg-su[3609]: libGL error: MESA-LOADER: failed to open nouveau: /usr/lib64/dri/nouveau_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)
Sep 21 11:38:26 n-MacPro.home xdg-su[3609]: libGL error: failed to load driver: nouveau
Sep 21 11:38:27 n-MacPro.home wnck-applet[2057]: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner WnckButton)
Sep 21 11:38:27 n-MacPro.home wnck-applet[2057]: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner WnckButton)
Sep 21 11:38:44 n-MacPro.home chronyd[1154]: Selected source 50.205.57.38 (2.opensuse.pool.ntp.org)
Sep 21 11:38:51 n-MacPro.home xdg-desktop-por[3613]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gtk: Timeout was reached
Sep 21 11:38:51 n-MacPro.home xdg-desktop-por[3613]: No skeleton to export
Sep 21 11:39:44 n-MacPro.home gnomesu-pam-backend[3561]: pam_unix(gnomesu-pam:session): session closed for user root
Sep 21 11:39:53 n-MacPro.home wnck-applet[2057]: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner WnckButton)
Broadcast message from b@localhost (Thu 2023-09-21 11:39:55 PDT):
The system will suspend now!
@non_space so is this system hybrid or pure nvidia?
inxi -Gxxz
Where you running the nvidia driver at all?
??? I guess the answer is “hybrid”?? Nvidia card, but I have found the nvidia drivers to be problematic keeping pace with TW, so all of my installs are with nouveau . . . .
Recalling there was some issue with nouveau some time back . . . but can’t recall the details on it.
inxi -Gxxz
Graphics:
Device-1: NVIDIA GK110 [GeForce GTX 780] vendor: eVga.com. driver: nouveau
v: kernel arch: Kepler pcie: speed: 5 GT/s lanes: 16 ports: active: DVI-I-1
empty: DP-1,DVI-D-1,HDMI-A-1 bus-ID: 05:00.0 chip-ID: 10de:1004
temp: 34.0 C
Display: x11 server: X.org v: 1.21.1.8 compositor: marco v: 1.26.2 driver:
X: loaded: modesetting unloaded: fbdev,vesa alternate: nouveau,nv,nvidia
dri: zink gpu: nouveau display-ID: :0 screens: 1
Screen-1: 0 s-res: 1280x1024
Monitor-1: DVI-I-1 model: ViewSonic VA951S res: 1280x1024 dpi: 86
diag: 482mm (19")
API: OpenGL v: 4.5 Mesa 23.1.7 renderer: llvmpipe (LLVM 16.0.6 128 bits)
direct-render: Yes
@non_space so you using modesetting, not nouveau… so is nouveau blacklisted? What do you have as the startup kernel-options?
cat /proc/cmdline
Hmm, well I didn’t do any such modesetting, as we used to do in PPC linux to get a GUI, but I guess the “system” did something??
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-6.5.3-1-default root=UUID=929e9949-2d18-424c-be4a-xxxxxxxxx