[Info-vax] TCPIP 5.4 - ssh -SYSTEM-F-BADPARAM, bad parameter value

[onedbguru]

On Nov 13, 6:16 pm, VAXman-  @SendSpamHere.ORG wrote:
> In article <5e097e09-236a-4be8-8121-80e15b295... at y3g2000vbm.googlegroups.com>, onedbguru <onedbg... at yahoo.com> writes:
>
>
>
>
>
>
>
>
>
> >Okay, I have beat my head against the wall and cannot for the life of
> >me figure out why my ssh suddenly stopped working.
>
> >  HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 7
> >  on a AlphaServer DS10L 466 MHz running OpenVMS V7.3-2
>
> > @sys$startup:tcpip$ssh_startup
> >%TCPIP-I-INFO, image SYS$SYSTEM:TCPIP$SSH_SSHD2.EXE installed
> >%TCPIP-I-INFO, image SYS$SYSTEM:TCPIP$SSH_SFTP-SERVER2.EXE installed
> >%TCPIP-I-INFO, logical names created
> >%TCPIP-E-STARTERROR, error starting SSH service
> >-SYSTEM-F-BADPARAM, bad parameter value
> >%TCPIP-E-STARTFAIL, failed to start TCPIP$SSH
> >-TCPIP-E-ENABLERR, error enabling service
>
> >TCPIP> enable service ssh
> >%TCPIP-E-STARTERROR, error starting SSH service
> >-SYSTEM-F-BADPARAM, bad parameter value
>
> >I have dropped and recreated this service with no luck.  I have even
> >attempted to start the sshd manually with debug on (level 99)
> >and I get:
>
> >the command is:
>
> >sshd -i -d 99
> >......
> >debug(13-NOV-2010 17:59:08.90): SshCertEdb/CMI-EDB.C:277: EDB: Adding
> >database:
> >ssh.http
> >debug(13-NOV-2010 17:59:08.90): Becoming server.
> >Sat 13 17:59:08 WARNING: Starting image in auxiliary server mode.
> >Sat 13 17:59:08 ERROR: FATAL ERROR: Failed to create a socket. errno
> >=  6
> >$1$dqa0:[sys0.syscommon.][sysexe]tcpip$ssh_sshd2.exe[1227]: FATAL:
> >Failed to create a socket. errno =  6
>
> >If I modify this and remove the -i, I can get the interactive server
> >to startup and can connect via this process, but tcpip enable service
> >ssh still fails.
>
> >WTShamolies?
>
> What account are you using?
>
> $ DEFINE/SYSTEM/EXEC TCPIP$SSH_SERVER_DEBUG DEBUG
>
> and start...
>
> Take a look at SYS$SYSDEVICE:[TCPIP$SSH]TCPIP$SSH_RUN.LOG
>
> Post it here.
>
> Post: $ TCPIP SHOW SERVICE SSH/FULL too.
> --
> VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG
>
> All your spirit rack abuses, come to haunt you back by day.
> All your Byzantine excuses, given time, given you away.


For some reason the service never had the /log parameter configured,
so there were no log files to see - even after defining the logical.

After all this time, I finally got it working by:

disable service ssh
set noservice ssh
set service ssh /port=2222 /proc=tcpip$ssh/user=tcpip$ssh —
/file=tcpip$system:tcpip$ssh_run.com /proto=tcp/limit=10000 —
/log=(all,file=tcpip$ssh_device:[tcpip$ssh]tcpip$ssh_run.log)
enable service ssh


disable service ssh
set noservice ssh
set service ssh /port=22 /proc=tcpip$ssh/user=tcpip$ssh —
/file=tcpip$system:tcpip$ssh_run.com /proto=tcp/limit=10000 —
/log=(all,file=tcpip$ssh_device:[tcpip$ssh]tcpip$ssh_run.log)
enable service ssh

I was never able to see exactly how it was configured when it was
failing, so I have no idea of how it was broken.

Thanks for the help :)