sshd service down (Error 500: got no worker upid - start worker failed)

mitt

New Member
Aug 29, 2022
11
0
1
The sshd service went down last night, and won't start, the error is as follows:

Connection failed (Error 500: got no worker upid - start worker failed)

Is there a way to fix it without restarting the server?
 
Currently i'm not being able to access the proxmox, since it does not respond through ssh, and the authentication through the web panel does not work either (Linux PAM standard authentication).
 
the issue is that the datacenter is about 4 hours from my house, and I wanted to know if there was any way to solve it without having to restart, because otherwise I would have to go to the datacenter :confused:
 
When the ssh started to fail, i was logged into the proxmox web panel with the session active, but it wouldn't let me use my node's console, and in the system section it said that the sshd was failing with that error I mentioned up. However, it was night, and I went to sleep. Today when I woke up, the session had expired and when trying to access, I could no longer access through the web panel (I guess it's because of ssh).
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!