Sponsored Content
Top Forums Shell Programming and Scripting Problem with ssh on target server. Post 303038813 by stomp on Saturday 14th of September 2019 09:22:53 AM
Old 09-14-2019
Hi Mohtashims,

I'm now sitting on my notebook and I checked the two different Debug-Outputs of the 2 ssh connections. I clearly see differences.

I assume, you have - as I suggested - to debug the server side. But from the client side, there are visible differences, which shed a little light on the situation.

General Hints

I'm watching you and your questions quite a while. Your technical knowledge is quite good. You have scripting skills. You know how to use the commands and build programs upon that. That's very good.

What I see too, is that you are quickly asking questions if you stumble upon errors like here. So I think a further good skill, which will bring you forward in your overall competence would be problem investigation and problem solving capability.

What do you need for that?
  • Patience and willingness to deeply and carefully investigate a problem. Take your time, read debug output very carefully.
  • Try to understand what's happening! Step by step.
  • Think about it! What can be wrong? Where can be an error?
  • Think about how to get more information in the process! Where to get more information in the process?
  • Isolate more and more exactly the spot of the error
  • Debug output your variables
  • Make small test programs

    If you do not understand why the whole program reacts like it does, take small bits out of it and make a small testing program and take the problematic data into that.
  • Be prepared for own blind spots.

    Program errors you do not recognize even if they are directly in front of you, even if you'd seen them a dozen of times.(I had two spelling errors in your name in this post even if I read a hundred times in this forum so far.) Maybe Programming language behaviour that is not like you always believed it to be.
  • From time to time a break helps a lot


Apply that on the current problem and you will get closer to the cause.

So my question to you is here: What are the differences between the two client connection session debug logs?

Last edited by stomp; 09-14-2019 at 11:39 AM..
 

9 More Discussions You Might Find Interesting

1. Programming

Problem in registering new netfilter target module

Friends I'm facing a big problem trying to extend the netfilter. Somone please help me with your quick reply (any hint) as I've to meet a deadline. My problem is that I've written a new netfilter target module and its corresponding userspace program for iptables to change the packet type of a... (0 Replies)
Discussion started by: Rakesh Ranjan
0 Replies

2. Solaris

network config problem - how to set the server for others to ssh without password

Hi, I want to ssh the linux server without inputting the password, how can I config this server? Thanks in advance! (1 Reply)
Discussion started by: GCTEII
1 Replies

3. AIX

Problem in SSH Install in AIX 4.3 Server.

Hi Friends I am trying to install ssh in one of my AIX4.3 server. I downloaded openssh and openssl from IBM site. While installing them openssh failed. The lpcheck command display looks like this: # lppchk -v lppchk: The following filesets need to be installed or corrected to bring ... (5 Replies)
Discussion started by: efunds
5 Replies

4. Shell Programming and Scripting

Shell script to transfer the files from source to target server.

I need to write a shell script to transfer the files every hour from source - target server. The cron job should be running every hour and shouldn't copy already copied files to the remote server ? I was able to write intial script but not able to get the logic for (in the next run it should... (12 Replies)
Discussion started by: radhirk
12 Replies

5. Solaris

Improperly formatted value for 'tftp-server' error while booting the target from LAN

Hi, I wish to install solaris 10 on a target machine (t1000) by using Jumpstart. I have configured by jumpstart environment for the same. When i boot the target with the option "boot net -v install" i get the following error... {0} ok boot net -v install Boot device: /pci@7c0/pci@0/network@4... (3 Replies)
Discussion started by: hemalsid
3 Replies

6. Shell Programming and Scripting

copy files from remote server (B) to target server (A)?

Hi All, what is the comand to log off the remote server? I have 2 servers A, B. I need to find all files older than 7 days on server B and copy over to server A. My logic is: login the remote server: ================= ssh hostB cd /data/test find . -mtime -7 -ls | awk '{print... (4 Replies)
Discussion started by: Beginer0705
4 Replies

7. Shell Programming and Scripting

Problem running ssh from remote server

So I have a script which performs some basic commands on another server via ssh. It works great, no issues at all. Let's call this "Script A" BUT, this working script is to be executed remotely from a different UNIX script on another server, also by ssh. Let's call this "Script B". When... (1 Reply)
Discussion started by: newerakb
1 Replies

8. UNIX for Dummies Questions & Answers

Problem setting up SSH keys between my laptop and a server.

This is probably somewhat trivial but it's driving me crazy. I have 6 servers with identical configurations. I'm trying to set up ssh keys between my laptop (windows XP using cygwin) and these servers (rhel). On 5 of the machines this works perfectly, but on one, no matter what I do, it gives me a... (2 Replies)
Discussion started by: DeCoTwc
2 Replies

9. UNIX for Advanced & Expert Users

VxWorks target server

hi all. i have omniswitch 6800 that runs vxworks 5.4.x The folder that is result of compiling my image consists of : -rw-r--r-- 1 root other 8128249 Jun 21 05:21 Kbase.img -rw-r--r-- 1 root other 971810 Jun 21 06:07 Kos.img -rw-r--r-- 1 root other 295076 Jun 21... (0 Replies)
Discussion started by: sadgb
0 Replies
AMANDA-CLIENT.CON(5)					   File formats and conventions 				      AMANDA-CLIENT.CON(5)

NAME
amanda-client.conf - Client configuration file for Amanda, the Advanced Maryland Automatic Network Disk Archiver DESCRIPTION
amanda-client.conf(5) is the client configuration file for Amanda. This manpage lists the relevant sections and parameters of this file for quick reference. The files <CONFIG_DIR>/amanda-client.conf and <CONFIG_DIR>/<config>/amanda-client.conf are loaded. SYNTAX
The syntax of amanda-client.conf(5) is identical to that for amanda.conf(5). GLOBAL PARAMETERS
conf string Default: Set by configure. The conf use by amrecover. client-username string Default: CLIENT_LOGIN. Similar to the parameter of the same name in amanda.conf(5), this specifies the username that amrecover should send when connecting to the server. It should match the username specified in .amandahosts on the server. client-port [ int | string ] Default: "amanda". Similar to the parameter of the same name in amanda.conf(5), this specifies the port to connect on the server. It can be a service name or a numeric port number. amdump-server string No default: Set by configure. The amanda server to connect with the amdump_client program. index-server string Default: Set by configure. The amindexd server amrecover will connect to. tape-server string Default: Set by configure. The amidxtaped server amrecover will connect to. tapedev string Default: Set by configure. The tapedev amrecover will use. auth string Default: "bsdtcp". Type of authorization to perform between tape server and backup client hosts. "bsd", bsd authorization with udp initial connection and one tcp connection by data stream. "bsdtcp", bsd authorization but use only one tcp connection. "bsdudp", like bsd, but will use only one tcp connection for all data stream. "krb5" to use Kerberos-V authorization. "local", if the client is the server, it doesn't require authencation setup. "rsh" to use rsh authorization. "ssh" to use OpenSSH authorization. ssh-keys string Default: No default. The key file the ssh auth will use, it must be the private key. If this parameter is not specified, then the default ssh key will be used. gnutar-list-dir string Default from configure --with-gnutar-listdir=DIR. The directory where gnutar keep its state file. mailer string Default found by configure. A mail program that can send mail with 'MAILER -s "subject" user < message_file'. amandates string Default: /etc/amandates. The file where amanda keep the last date of each dumplevel. connect-tries int Default: 3. How many times the server will try a connection. rep-tries int Default: 5. How many times amandad will resend a REP packet if it doesn't get the ACK packet. debug-days int Default: 3. The number of days the debug files are kept. debug-amandad int Default: 0. Debug level of the amandad process debug-amidxtaped int Default: 0. Debug level of the amidxtaped process debug-amindexd int Default: 0. Debug level of the amindexd process debug-amrecover int Default: 0. Debug level of the amrecover process debug-auth int Default: 0. Debug level of the auth module debug-event int Default: 0. Debug level of the event module debug-holding int Default: 0. Debug level of the holdingdisk module debug-protocol int Default: 0. Debug level of the protocol module debug-selfcheck int Default: 0. Debug level of the selfcheck process debug-sendsize int Default: 0. Debug level of the sendsize process debug-sendbackup int Default: 0. Debug level of the sendbackup process reserved-udp-port int,int Default: --with-udpportrange or 512,1023. Reserved udp port that will be used (amrecover with bsd or bsdudp) reserved-tcp-port int,int Default: --with-low-tcpportrange or 512,1023. Reserved tcp port that will be used (amrecover with bsdtcp) unreserved-tcp-port int,int Default: --with-tcpportrange or 1025,65536. Unreserved tcp port that will be used (bsd, bsdudp) property string string+ Adds a global property for this client host, useful for e.g., Application API plugins. The first string is the property name, the following strings are the property values APPLICATION SECTION
The amanda-client.conf file may define multiple types of application. The information is entered in a application section, which looks like this: define application "name" { application-option application-value ... } name is the name of this type of application. The setting from an application is merged with the dle setting if the name is the same as the client-application-name from the dle or if the client-application-name from the dle is not set and the name is the same as the plugin from the dle. The application options and values are: client-application-name string Default: none. Not use on the client. comment string Default: none. A comment string describing this application. plugin string No default. Must be set to the name of the program. This program must be in the $libexecdir/amanda/application directory on the client. If set, it must be the same as the dle plugin. property [append] [priority] string string+ No default. You can set property for the application, each application have a different set of property. Both strings are quoted; the first string contains the name of the property to set, and the others contains its values. append keyword append the values to the list of values for that property. priority keyword disallow the setting of that property on the server. SCRIPT SECTION
The amanda-client.conf file may define multiple types of script. The information is entered in a script section, which looks like this: define script "name" { script-option script-value ... } name is the name of this type of script. The setting from a script is merged with the dle setting if the name is the same as the client-script-name from the dle or if the client-script-name from the dle is not set and the name is the same as the plugin from the dle. The script options and values are: client-script-name string Default: none. Not used on the client. comment string Default: none. A comment string describing this script. plugin string No default. Must be set to the name of the program. This program must be in the $libdir/amanda/application directory on the client. If set, it must be the same as the dle plugin. execute-where client Default: client. Value can't be changed. execute-on execute_on[,execute_on]* No default. When the script must be executed, you can specify many of them: pre-dle-amcheck Execute before the amcheck command for the dle. pre-host-amcheck Execute before the amcheck command for all dle for the client. post-dle-amcheck Execute after the amcheck command for the dle. post-host-amcheck Execute after the amcheck command for all dle for the client. pre-dle-estimate Execute before the estimate command for the dle. pre-host-estimate Execute before the estimate command for all dle for the client. post-dle-estimate Execute after the estimate command for the dle. post-host-estimate Execute after the estimate command for all dle for the client. pre-dle-backup Execute before the backup command for the dle. post-dle-backup Execute after the backup command for the dle. pre-recover Execute before any level is recovered. post-recover Execute after all levels are recovered. pre-level-recover Execute before each level recovery. post-level-recover Execute after each level recovery. inter-level-recover Execute between two levels of recovery. property [append] [priority] string string+ No default. You can set property for the script, each script have a different set of property. Both strings are quoted; the first string contains the name of the property to set, and the others contains its values. append keyword append the values to the list of values for that property. priority keyword disallow the setting of that property on the server. SEE ALSO
amanda(8), amanda.conf(5), amcrypt(8), aespipe(1) The Amanda Wiki: : http://wiki.zmanda.com/ AUTHORS
James da Silva <jds@amanda.org> Stefan G. Weichinger <sgw@amanda.org> Amanda 3.3.1 02/21/2012 AMANDA-CLIENT.CON(5)
All times are GMT -4. The time now is 04:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy