There are two known causes for this issue:
- Determine if the cause of the issue is a stale key:
- Open a command-line session.
- Type grep -i ssh_bind_listen /var/log/edsftp.log and press Enter.
- Look for the error:
ssh_bind_listen failed : [0][Success]
- If you don't see the error, skip to the next section.
- If the error is listed, continue with the next step.
- On the ELM, run the following commands. Press Enter after each command:
rm /root/.ssh/id_rsa
rm /root/.ssh/id_rsa.pub
service sshd restart
- View the output of the below command in /var/log/messages and wait until you see Generating NitroSecurity ESM RSA Identity key... [ OK ]
killall -HUP elmdctl
- To start ELM: Type ELMStart and press Enter.
- To make sure that edsftp starts and stays up: Type ps auxf|grep -i eds and press Enter.
- Verify the PID number of the edsftp process several times to make sure that it doesn't change.
- If the cause was not an invalid key, continue with the following:
- Click ELM properties, Settings, ELM Configuration, Interfaces.
- Set the SFTP port to 23, and click OK.
- Close the ELM user interface.
- On the ELM, run the ELMStart command to start the ELM processes, then run NitroStarted again to confirm that edsftp is now running.
- If edsftp don't start, on all ESMs, type service sshcc restart and press Enter.
- Run NitroStarted again to confirm that edsftp is now running.
If you still experience this issue after you perform the steps above, contact Technical Support for assistance.
- If you are a registered user, type your User ID and Password, and then click Log In.
- If you are not a registered user, click Register and complete the fields to have your password and instructions emailed to you.
