Entradas

Mostrando las entradas con la etiqueta Troubleshooting

MobaXterm: How to Fix Multiple Password Prompts when Connecting via SSH (Solaris/Linux)

Imagen
If you are a System Administrator, you probably use MobaXterm as your go-to tool for its versatility: integrated X server, SSH client, SFTP file transfer, and more. However, since version 21.1, many users started experiencing a frustrating issue: MobaXterm requests the password three times before allowing access to certain hosts, particularly those running Solaris . In this article, I’ll explain why this happens and how to fix it permanently by adjusting your SSH configuration. The Problem: Why does MobaXterm ask for the password repeatedly? At first, you might think the SSH package was upgraded on the server side or that a system-wide OS upgrade changed the security policies. However, if you test the connection with other clients like Putty.exe , the issue does not occur. The root cause lies in the Preferred Authentications order. MobaXterm tries several methods that the server might not accept immediately, exhausting the allowed attempts before falling back to the interactive keyb...

How to Fix “e2fsck: Cannot continue, aborting” on GNU/Linux

Imagen
(Filesystem Recovery Guide – Real Case from CentOS 6) Real case (2014): what actually happened This was the error message I got from my CentOS 6.5 in previous days but I didn't pay attention, because I was trying to boot into Windows 7. Yesterday, when I finally wanted to boot CentOS, I got the notification that /var was having issues and that I needed to fix it using fsck before mounting it . I used fsck to clean the filesystem, but after pressing Ctrl+D , the system rebooted. During the next boot, I got stuck again with a message requesting to use fsck to clean the root filesystem , which was mounted as read-only (ro) . How was it possible to have the root filesystem mounted as read-only and at the same time be asked to run fsck ? This was not expected, so I started searching for answers. After checking different forums, I decided to use a Live CD , clean all filesystems using fsck , and boot again. Same result. At that point, it was clear that the problem was not fsck ...