Welcome to the VanDyke Software Forums

Join the discussion today!


Go Back   VanDyke Software Forums > Secure Shell

Reply
 
Thread Tools Display Modes
  #1  
Old 04-09-2021, 03:59 AM
Jorgen Jorgen is offline
Registered User
 
Join Date: Apr 2021
Posts: 1
Getting exit-status: 259 randomly

Hi All,

Reasently changed application server and was forced to move the VShell server 4.0.3 to the new Windows 2016 box.
Now when running the vsh command line utility (v.5.0.0) against the VShell server it is randomly failing for about 50% of the time with exit-status: 259.
Cannot see any differences in the client log between a working and non-working execution.

Server side log for a failed execution;
2021-04-06 23:27:33 VShellSSH2 auth 56 - - WIN-6MFHSRM3ENJ\userXXX - - 0 0 0 0 - - "00056: Client specified user name userXXX, resolved as WIN-6MFHSRM3ENJ\userXXX"
2021-04-06 23:27:33 VShellSSH2 auth 56 192.168.52.27 4695 WIN-6MFHSRM3ENJ\userXXX - - 0 0 0 0 - - "00056: none for user WIN-6MFHSRM3ENJ\userXXX rejected because it is unavailable"
2021-04-06 23:27:33 VShellSSH2 auth 56 192.168.52.27 4695 WIN-6MFHSRM3ENJ\userXXX - - 0 0 0 0 - - "00056: password for user WIN-6MFHSRM3ENJ\userXXX accepted"
2021-04-06 23:27:33 VShellSSH2 dbg 56 - - - - - 0 0 0 0 - - "00056: [LOCAL DEBUG] RECV: CHANNEL_OPEN[session]"
2021-04-06 23:27:33 VShellSSH2 conn 56 192.168.52.27 4695 WIN-6MFHSRM3ENJ\userXXX - - 0 0 0 0 - - "00056: Session channel open request accepted"
2021-04-06 23:27:33 VShellSSH2 conn 56 192.168.52.27 4695 WIN-6MFHSRM3ENJ\userXXX - - 0 0 0 0 - - "00056: Session channel failing unsupported x11-req request"
2021-04-06 23:27:33 VShellSSH2 conn 56 192.168.52.27 4695 WIN-6MFHSRM3ENJ\userXXX - - 0 0 0 0 - - "00056: Started agent forwarding from VShell.2192.56.0.4.SSH_AUTH_SOCK"
2021-04-06 23:27:33 VShellSSH2 dbg 56 192.168.52.27 4695 WIN-6MFHSRM3ENJ\userXXX - - 0 0 0 0 - - "00056: Process SessionChannel exec request: \msysTV4\bin\sh --login -c '/tv/inst/tv4/prod/bin/CreateAgtSchedDetail -s04/05/21 -e04/18/21' 1>> vsh_log.txt 2>>&1"
2021-04-06 23:27:33 VShellSSH2 dbg 56 - - WIN-6MFHSRM3ENJ\userXXX - - 0 0 0 0 - - "00056: Queued worker thread to load user environment"
2021-04-06 23:27:33 VShellSSH2 dbg 56 - - - - - 0 0 0 0 - - "00056: Worker thread starting user environment load. User name=userXXX Logon Server=WIN-6MFHSRM3ENJ Profile Path=''"
2021-04-06 23:27:33 VShellSSH2 dbg 56 - - - - - 0 0 0 0 - - "00056: Worker thread finished user environment load"
2021-04-06 23:27:33 VShellSSH2 dbg 56 - - WIN-6MFHSRM3ENJ\userXXX - - 0 0 0 0 - - "00056: VSHELL_HOME is not valid, trying profile for user's home directory"
2021-04-06 23:27:33 VShellSSH2 dbg 56 - - WIN-6MFHSRM3ENJ\userXXX - - 0 0 0 0 - - "00056: Profile home directory is not valid, trying 'My Documents' for user's home directory"
2021-04-06 23:27:33 VShellSSH2 dbg 56 - - WIN-6MFHSRM3ENJ\userXXX - - 0 0 0 0 - - "00056: Using home directory 'C:\Users\userXXX\Documents' for user userXXX"
2021-04-06 23:27:33 VShellSSH2 dbg 56 192.168.52.27 4695 WIN-6MFHSRM3ENJ\userXXX - - 0 0 0 0 - - "00056: Received request to start \msysTV4\bin\sh --login -c '/tv/inst/tv4/prod/bin/CreateAgtSchedDetail -s04/05/21 -e04/18/21' 1>> vsh_log.txt 2>>&1"
2021-04-06 23:27:33 VShellSSH2 dbg 56 192.168.52.27 4695 WIN-6MFHSRM3ENJ\userXXX - - 0 0 0 0 - - "00056: started user process (31384)"
2021-04-06 23:28:01 VShellSSH2 dbg 56 192.168.52.27 4695 WIN-6MFHSRM3ENJ\userXXX - - 0 0 0 0 - - "00056: Received EOF on stderr from running program"
2021-04-06 23:28:01 VShellSSH2 dbg 56 192.168.52.27 4695 WIN-6MFHSRM3ENJ\userXXX - - 0 0 0 0 - - "00056: Received EOF on stdout from running program"
2021-04-06 23:28:01 VShellSSH2 dbg 56 192.168.52.27 4695 WIN-6MFHSRM3ENJ\userXXX - - 0 0 0 0 - - "00056: Process 31384 has exited, exit-status: 259"
2021-04-06 23:28:01 VShellSSH2 dbg 56 192.168.52.27 4695 WIN-6MFHSRM3ENJ\userXXX - - 0 0 0 0 - - "00056: Initiating close on session channel"
2021-04-06 23:28:01 VShellSSH2 conn 56 192.168.52.27 4695 WIN-6MFHSRM3ENJ\userXXX - - 0 0 0 0 - - "00056: Session channel has been closed (pid: 31384)"
2021-04-06 23:28:01 VShellSSH2 dbg 56 - - - - - 0 0 0 0 - - "00056: [LOCAL DEBUG] RECV: TCP/IP close"
2021-04-06 23:28:01 VShellSSH2 dbg 56 - - - - - 0 0 0 0 - - "00056: [LOCAL DEBUG] Changing state from STATE_CONNECTION to STATE_CLOSED"
2021-04-06 23:28:01 VShellSSH2 dbg 56 - - - - - 0 0 0 0 - - "00056: [LOCAL DEBUG] Connected for 28 seconds, 2257 bytes sent, 1426 bytes received"
2021-04-06 23:28:01 VShellSSH2 conn 56 - - - - - 0 0 0 0 - - "00056: Connection closed"

Any idea what is going on and what the exit-status 259 means?

All help is appreciated.

Thanks

Last edited by cboyack; 04-09-2021 at 07:04 AM.
Reply With Quote
  #2  
Old 04-09-2021, 08:41 AM
bgagnon bgagnon is offline
VanDyke Technical Support
 
Join Date: Oct 2008
Posts: 4,596
Hi Jorgen,

VShell version 4.3 was the first with support for Server 2016.

Changes in VShell 4.3 (Beta 1) -- May 18, 2017
----------------------------------------------
New features:

  • Support added for Windows Server 2016.
Please send email to support@vandyke.com and reference Attn Brenda - Forum Thread #14492.

Please include your VShell serial number in that email and attach vsh_log.txt.
__________________
Thanks,
--Brenda

VanDyke Software
Technical Support
support@vandyke.com
(505) 332-5730
Reply With Quote
Reply

Tags
259 , exit-status , vsh


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -6. The time now is 11:02 PM.