Hey Heino,

For testing purposes, I did set the system timeout to 1 minute here:

$ time ssh admin@1.1.1.1

CLUSTER::> (Login timeout will occur in 30 seconds)

CLUSTER::> (Login timeout will occur in 20 seconds)

CLUSTER::> (Login timeout will occur in 10 seconds)

CLUSTER::>

Exiting due to timeout

Connection to 1.1.1.1 closed.

real    1m0.485s

user    0m0.016s

sys     0m0.000s

-> On an interactive shell, the connection closes exactly after 1 minute.

Next try, same timeout setting, but started a `sleep 120` in the interactive session:

$ time ssh admin@1.1.1.1

CLUSTER::> sleep 120

CLUSTER::> (Login timeout will occur in 30 seconds)

CLUSTER::> (Login timeout will occur in 20 seconds)

CLUSTER::> (Login timeout will occur in 10 seconds)

CLUSTER::>

Exiting due to timeout

Connection to 1.1.1.1 closed.

real    3m1.638s

user    0m0.012s

sys     0m0.004s

-> 3 minutes, 2 for the sleep, 1 for the timeout.

When I login to node shell using SSH, the timeout does not count, obviously.

I did manually exit it then, since it did not kick me out – unless the nodeshell has a separate timeout?

$ time ssh admin@1.1.1.1

CLUSTER::> node run -node  node1

Type 'exit' or 'Ctrl-D' to return to the CLI

Node1>

Node1> exit

logout

CLUSTER::> exit

Goodbye

Connection to 1.1.1.1 closed.

real    7m21.102s

user    0m0.016s

sys     0m0.004s

Depending on how exactly you ran the command, it might either be one of the timeouts on the filer, or maybe also just a timeout of the TCP connection which might be dropped due to inactivity on a firewall or the like?

Best,

Alexander Griesser

Head of Systems Operations

ANEXIA Internetdienstleistungs GmbH

E-Mail: AGriesser@anexia-it.com

Web: http://www.anexia-it.com

Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt

Geschäftsführer: Alexander Windbichler

Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601

Von: Toasters <toasters-bounces@teaparty.net> Im Auftrag von Heino Walther
Gesendet: Dienstag, 18. Mai 2021 14:15
An: toasters@teaparty.net
Betreff: [EXTERNAL] SV: Ndmpcopy times out...

ACHTUNG: Diese E-Mail stammt von einem externen Absender. Bitte vermeide es, Anhänge oder externe Links zu öffnen.

Btw. Found this article describing the process: https://kb.netapp.com/Advice_and_Troubleshooting/Data_Protection_and_Security/NDMP/Ndmpcopy_run_via_SSH_consistently_aborts_after_a_fixed_amount_of_time

Here is the “solution” as described in the article… the problem is that once I get the “disconnect” it does actually disconnect…  maybe not from the Service-Processor, but it does disconnect the “node-shell” and the ndmpcopy process as a result…

I cannot find any timeout options in the service-processor options…. So not sure if I’m doing something wrong?  I would think I am doing exactly as described below…

• Avoid SSH-related timeouts by running ndmpcopy from the console.
• To run ndmpcopy (or any command) from the console:

1) First, find the IP of the service processor (SP) by running:

::> system service-processor show

2) After the IP of the SP is known, log in to the SP.

3) From the SP prompt, run system console to access the console.

4) Once at the system console prompt, re-run the ndmpcopy command from the console.

NOTE:  It is possible the connection to the system console will time out.  Unlike a SSH session, any process started from system console will continue to run in the background.

• start ndmpcopy from the clustershell, via node run. 
• DO NOT start ndmpcopy directly from nodeshell

The command I then run as point 4 is: node run -node node1 -command “ndmpcopy…..”  and then wait…

So I’m at a loss here …

/Heino

Fra: Toasters <toasters-bounces@teaparty.net> på vegne af Heino Walther <hw@beardmann.dk>
Dato: tirsdag, 18. maj 2021 kl. 13.59
Til: toasters@teaparty.net <toasters@teaparty.net>
Emne: Ndmpcopy times out...

Hi guys

I have to migrate a large folder form one volume to another on the same system.

We are talking ONTAP 9.something, so the ndmpcopy is not a part of the cDot commandset, so the node shell have to be used…

The process runs and it starts to copy etc.. but after x-minutes the connection is terminated due to inactivity…

I have now tried to login to the service-processor, then “system console”, and then “node run -node node1 -command “ndmpcopy ….”  And once again it starts, but is then terminated as my connection as shown here:

Ndmpcopy: 10.64.9.142: Log: DUMP: dumping (Pass IV) [regular files]

Ndmpcopy: 10.64.9.142: Log: RESTORE: Tue May 18 13:08:27 2021: Creating files and directories.

Ndmpcopy: 10.64.9.142: Log: RESTORE: Tue May 18 13:10:33 2021 : We have processed 298105 files and directories.

Ndmpcopy: 10.64.9.142: Log: RESTORE: Tue May 18 13:15:33 2021 : We have processed 508611 files and directories.

Ndmpcopy: 10.64.9.142: Log: RESTORE: Tue May 18 13:20:33 2021 : We have processed 693207 files and directories.

Ndmpcopy: 10.64.9.142: Log: RESTORE: Tue May 18 13:25:33 2021 : We have processed 860486 files and directories.

Autologout: System Console being disconnected due to inactivity

Any good suggestions are very welcome 😊

/Heino