• Locked Locked
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 533 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Remote Debug Using DevRocket

MRI
Expert 1130 points

I'm having a problem connecting to the target with SSH. I'm seeing SSH related errors during boot (bold text below) There are other non-related SSH errors about No directory found. how do I fix SSH and the directory problems?

 

Mike

 

-------------------clipped-----------------------------

Starting portmap daemon: portmap/etc/rc.d/rcS.d/S41portmap: line 70: /var/run/po
rtmap.pid: No such file or directory
.
/etc/init.d/rcS: line 55: /var/run/utmp: No such file or directory
INIT: Entering runlevel: 3
Starting NFS common utilities: statdstatd: Could not chdir: No such file or dire
ctory
/etc/rc.d/rc3.d/S19nfs-common: line 70: /var/run/rpc.statd.pid: No such file or
directory
 failed (1: ).
Starting internet superserver: inetd.
mkdir: cannot create directory `/var/empty/sshd': No such file or directory
chmod: cannot access `/var/empty/sshd': No such file or directory
Starting OpenBSD Secure Shell server: sshdMissing privilege separation directory
: /var/empty/sshd
/etc/rc.d/rc3.d/S20ssh: line 70: /var/run/sshd.pid: No such file or directory
 failed (255: ).
Starting MontaVista target tools daemon: mvltdmvltd version 2.1 MontaVista Softw
are,Inc.
mvltd[1039]: started on port 34577
/etc/rc.d/rc3.d/S90mvltd: line 70: /var/run/mvltd.pid: No such file or directory

  • TI__Mastermind 37340 points

    It does not appear ssh is enabled on the target EVM by default.  Try the following and see if it helps...

    1. Using telnet, log in to the target as root.

    2. Edit the file /etc/default/ssh; change the line to read:
    AUTOKEYGEN=yes

    3. Edit the file /etc/ssh/sshd_config; find the line that includes PermitEmptyPasswords and add:
    PermitEmptyPasswords yes

    4. Enable the ssh daemon on boot:
    initdconfig ssh on

    5. Start the ssh daemon (if you do not plan to reboot):
    /etc/init.d/ssh start

     

  • in reply to Juan Gonzales
    Expert 1130 points

    Juan Gonzales said:

    It does not appear ssh is enabled on the target EVM by default.  Try the following and see if it helps...

    1. Using telnet, log in to the target as root.

    2. Edit the file /etc/default/ssh; change the line to read:
    AUTOKEYGEN=yes

    3. Edit the file /etc/ssh/sshd_config; find the line that includes PermitEmptyPasswords and add:
    PermitEmptyPasswords yes

    4. Enable the ssh daemon on boot:
    initdconfig ssh on

    5. Start the ssh daemon (if you do not plan to reboot):
    /etc/init.d/ssh start

     

     

    Do I have to change the config to enable SSH and build a new kernel?

     

    Mike

  • in reply to MRI
    Expert 1130 points

    Sorry, stupid question. ssh is running.

     

    Mike