tar ssh는 백업 후 즉시 연결을 닫습니다.

tar ssh는 백업 후 즉시 연결을 닫습니다.

비슷한 질문을 다른 곳에서도 본 적이 있지만 내 질문은 약간 다른 것 같습니다. Ubuntu 16 서버로 SSH를 연결하고 있는데 몇 시간 전에 작동하기 시작했습니다. 다음을 사용하여 백업을 시작합니다.

tar -cvpzf backup.tar.gz --one-file-system /

(이제 해당 플래그를 포함하지 않았기 때문에 걱정됩니다 exclude. 이로 인해 문제가 발생한 것 같습니다. 내 이론은 백업 자체가 포함되어 디스크가 가득 찰 때까지 공간을 차지한다는 것입니다.)

이 백업을 실행 상태로 두었습니다 screen.이제 ssh를 통해 로그인할 수 있지만 연결이 즉시 닫힙니다.출력은 다음과 같습니다 -vvv.

OpenSSH_9.0p1, LibreSSL 3.3.6
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 21: include /etc/ssh/ssh_config.d/* matched no files
debug1: /etc/ssh/ssh_config line 54: Applying options for *
debug2: resolve_canonicalize: hostname 128.138.229.184 is address
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/Users/milesper/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/Users/milesper/.ssh/known_hosts2'
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug3: ssh_connect_direct: entering
debug1: Connecting to 128.138.229.184 [128.138.229.184] port 22.
debug3: set_sock_tos: set socket 3 IP_TOS 0x48
debug1: Connection established.
debug1: identity file /Users/milesper/.ssh/id_rsa type 0
debug1: identity file /Users/milesper/.ssh/id_rsa-cert type -1
debug1: identity file /Users/milesper/.ssh/id_ecdsa type -1
debug1: identity file /Users/milesper/.ssh/id_ecdsa-cert type -1
debug1: identity file /Users/milesper/.ssh/id_ecdsa_sk type -1
debug1: identity file /Users/milesper/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /Users/milesper/.ssh/id_ed25519 type -1
debug1: identity file /Users/milesper/.ssh/id_ed25519-cert type -1
debug1: identity file /Users/milesper/.ssh/id_ed25519_sk type -1
debug1: identity file /Users/milesper/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /Users/milesper/.ssh/id_xmss type -1
debug1: identity file /Users/milesper/.ssh/id_xmss-cert type -1
debug1: identity file /Users/milesper/.ssh/id_dsa type -1
debug1: identity file /Users/milesper/.ssh/id_dsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_9.0
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.2p2 Ubuntu-4ubuntu2.10
debug1: compat_banner: match: OpenSSH_7.2p2 Ubuntu-4ubuntu2.10 pat OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x04000002
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to 128.138.229.184:22 as 'mginn'
debug3: record_hostkey: found key type ED25519 in file /Users/milesper/.ssh/known_hosts:10
debug3: record_hostkey: found key type RSA in file /Users/milesper/.ssh/known_hosts:11
debug3: record_hostkey: found key type ECDSA in file /Users/milesper/.ssh/known_hosts:12
debug3: load_hostkeys_file: loaded 3 keys from 128.138.229.184
debug1: load_hostkeys: fopen /Users/milesper/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug3: order_hostkeyalgs: have matching best-preference key type [email protected], using HostkeyAlgorithms verbatim
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: [email protected],curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c
debug2: host key algorithms: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-512,rsa-sha2-256
debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,[email protected],zlib
debug2: compression stoc: none,[email protected],zlib
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: [email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
debug2: host key algorithms: ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519
debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,[email protected]
debug2: compression stoc: none,[email protected]
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug1: kex: algorithm: [email protected]
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none
debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-ed25519 SHA256:nNAFge1goZ9nuPuB49e/JeStkOeG7gY20U0A8CIwlrc
debug3: record_hostkey: found key type ED25519 in file /Users/milesper/.ssh/known_hosts:10
debug3: record_hostkey: found key type RSA in file /Users/milesper/.ssh/known_hosts:11
debug3: record_hostkey: found key type ECDSA in file /Users/milesper/.ssh/known_hosts:12
debug3: load_hostkeys_file: loaded 3 keys from 128.138.229.184
debug1: load_hostkeys: fopen /Users/milesper/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: Host '128.138.229.184' is known and matches the ED25519 host key.
debug1: Found key in /Users/milesper/.ssh/known_hosts:10
debug3: send packet: type 21
debug2: ssh_set_newkeys: mode 1
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: SSH2_MSG_NEWKEYS received
debug2: ssh_set_newkeys: mode 0
debug1: rekey in after 134217728 blocks
debug1: get_agent_identities: bound agent to hostkey
debug1: get_agent_identities: ssh_fetch_identitylist: agent contains no identities
debug1: Will attempt key: /Users/milesper/.ssh/id_rsa RSA SHA256:MJa9ZCJ1R44hgE9ma0fpcgiu7fCrp8ioNW1ddAvNzM4
debug1: Will attempt key: /Users/milesper/.ssh/id_ecdsa 
debug1: Will attempt key: /Users/milesper/.ssh/id_ecdsa_sk 
debug1: Will attempt key: /Users/milesper/.ssh/id_ed25519 
debug1: Will attempt key: /Users/milesper/.ssh/id_ed25519_sk 
debug1: Will attempt key: /Users/milesper/.ssh/id_xmss 
debug1: Will attempt key: /Users/milesper/.ssh/id_dsa 
debug2: pubkey_prepare: done
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password
debug3: start over, passed a different list publickey,password
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /Users/milesper/.ssh/id_rsa RSA SHA256:MJa9ZCJ1R44hgE9ma0fpcgiu7fCrp8ioNW1ddAvNzM4
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 60
debug1: Server accepts key: /Users/milesper/.ssh/id_rsa RSA SHA256:MJa9ZCJ1R44hgE9ma0fpcgiu7fCrp8ioNW1ddAvNzM4
debug3: sign_and_send_pubkey: using publickey with RSA SHA256:MJa9ZCJ1R44hgE9ma0fpcgiu7fCrp8ioNW1ddAvNzM4
debug3: sign_and_send_pubkey: signing using rsa-sha2-512 SHA256:MJa9ZCJ1R44hgE9ma0fpcgiu7fCrp8ioNW1ddAvNzM4
debug3: send packet: type 50
debug3: receive packet: type 52
Authenticated to 128.138.229.184 ([128.138.229.184]:22) using "publickey".
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug3: send packet: type 90
debug1: Requesting [email protected]
debug3: send packet: type 80
debug1: Entering interactive session.
debug1: pledge: filesystem
debug3: receive packet: type 80
debug1: client_input_global_request: rtype [email protected] want_reply 0
debug3: client_input_hostkeys: received RSA key SHA256:9LlJzfm3JZJatDtV1wrkeYPOfrvnXGvM0iMhkinLLS0
debug3: client_input_hostkeys: received DSA key SHA256:rV/AvtW5tqEuf21sl2El6jZT2FgEv7ZIkUS4/kR781o
debug3: client_input_hostkeys: ssh-dss key not permitted by HostkeyAlgorithms
debug3: client_input_hostkeys: received ECDSA key SHA256:Dk9cDgvAFGnCCRAtiPmifbY25oeqekXgwuIW6YR+j8I
debug3: client_input_hostkeys: received ED25519 key SHA256:nNAFge1goZ9nuPuB49e/JeStkOeG7gY20U0A8CIwlrc
debug1: client_input_hostkeys: searching /Users/milesper/.ssh/known_hosts for 128.138.229.184 / (none)
debug3: hostkeys_foreach: reading file "/Users/milesper/.ssh/known_hosts"
debug3: hostkeys_find: found ssh-ed25519 key at /Users/milesper/.ssh/known_hosts:10
debug3: hostkeys_find: found ssh-rsa key at /Users/milesper/.ssh/known_hosts:11
debug3: hostkeys_find: found ecdsa-sha2-nistp256 key at /Users/milesper/.ssh/known_hosts:12
debug1: client_input_hostkeys: searching /Users/milesper/.ssh/known_hosts2 for 128.138.229.184 / (none)
debug1: client_input_hostkeys: hostkeys file /Users/milesper/.ssh/known_hosts2 does not exist
debug3: client_input_hostkeys: 3 server keys: 0 new, 3 retained, 0 incomplete match. 0 to remove
debug1: client_input_hostkeys: no new or deprecated keys from server
debug3: receive packet: type 91
debug2: channel_input_open_confirmation: channel 0: callback start
debug2: fd 3 setting TCP_NODELAY
debug3: set_sock_tos: set socket 3 IP_TOS 0x48
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 1
debug3: send packet: type 98
debug1: Sending environment.
debug3: Ignored env __CFBundleIdentifier
debug3: Ignored env TMPDIR
debug3: Ignored env XPC_FLAGS
debug3: Ignored env TERM
debug3: Ignored env DISPLAY
debug3: Ignored env SSH_AUTH_SOCK
debug3: Ignored env XPC_SERVICE_NAME
debug3: Ignored env TERM_PROGRAM
debug3: Ignored env TERM_PROGRAM_VERSION
debug3: Ignored env TERM_SESSION_ID
debug3: Ignored env SHELL
debug3: Ignored env HOME
debug3: Ignored env LOGNAME
debug3: Ignored env USER
debug3: Ignored env PATH
debug3: Ignored env SHLVL
debug3: Ignored env PWD
debug3: Ignored env OLDPWD
debug3: Ignored env ANDROID_SDK
debug3: Ignored env CONDA_EXE
debug3: Ignored env _CE_M
debug3: Ignored env _CE_CONDA
debug3: Ignored env CONDA_PYTHON_EXE
debug3: Ignored env CONDA_SHLVL
debug3: Ignored env CONDA_PREFIX
debug3: Ignored env CONDA_DEFAULT_ENV
debug3: Ignored env CONDA_PROMPT_MODIFIER
debug3: Ignored env PYTORCH_ENABLE_MPS_FALLBACK
debug3: Ignored env GSETTINGS_SCHEMA_DIR_CONDA_BACKUP
debug3: Ignored env GSETTINGS_SCHEMA_DIR
debug3: Ignored env rvm_prefix
debug3: Ignored env rvm_path
debug3: Ignored env rvm_bin_path
debug3: Ignored env rvm_version
debug1: channel 0: setting env LANG = "en_US.UTF-8"
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env _
debug3: Ignored env __CF_USER_TEXT_ENCODING
debug2: channel 0: request shell confirm 1
debug3: send packet: type 98
debug2: channel_input_open_confirmation: channel 0: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug3: receive packet: type 99
debug2: channel_input_status_confirm: type 99 id 0
debug2: PTY allocation request accepted on channel 0
debug2: channel 0: rcvd adjust 2097152
debug3: receive packet: type 99
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
debug3: receive packet: type 98
debug1: client_input_channel_req: channel 0 rtype exit-signal reply 0
debug3: receive packet: type 98
debug1: client_input_channel_req: channel 0 rtype [email protected] reply 0
debug2: channel 0: rcvd eow
debug2: chan_shutdown_read: channel 0: (i0 o0 sock -1 wfd 4 efd 6 [write])
debug2: channel 0: input open -> closed
debug3: receive packet: type 96
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug3: receive packet: type 97
debug2: channel 0: rcvd close
debug3: channel 0: will not send data after close
Welcome to Ubuntu 16.04.7 LTS (GNU/Linux 4.15.0-142-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

69 packages can be updated.
0 updates are security updates.

debug3: channel 0: will not send data after close
debug2: channel 0: obuf empty
debug2: chan_shutdown_write: channel 0: (i3 o1 sock -1 wfd 5 efd 6 [write])
debug2: channel 0: output drain -> closed
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug3: send packet: type 97
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 1
debug3: channel 0: status: The following connections are open:
  #0 client-session (t4 r0 i3/0 o3/0 e[write]/0 fd -1/-1/6 sock -1 cc -1 io 0x00/0x00)

debug3: send packet: type 1
Connection to 128.138.229.184 closed.
Transferred: sent 3436, received 3212 bytes, in 0.1 seconds
Bytes per second: sent 25656.7, received 23984.1
debug1: Exit status -1

run 명령을 사용해도 작동하지 않습니다 ssh user@server "rm -f /backup.tar.gz".

내 백업 작업이 심각하게 엉망이 되었나요? 복원이 가능한가요?

답변1

내 이론은 백업이 자체적으로 포함되어 디스크가 가득 찰 때까지 공간을 차지한다는 것입니다...이 백업을 화면으로 실행하고 있습니다...이제 SSH를 통해 로그인할 수 있지만 연결이 즉시 닫힙니다.

귀하의 지시에 따르면 단순히 ssh로 연결하여 100% 꽉 찼는 지 df -h확인할 수는 없습니다 . 저는 직장에서 OS 디스크가 꽉 찼을 때 때로는 루트 파티션 아래에 있고 때로는 별도의 파티션에서 이런 상황에 직면하는 경우가 많습니다. 언제. . . 언제//home/home/ 뿌리파티션이 100% 가득 차면 SSH(및 사용자가 Linux 서버에 원격으로 액세스하는 데 사용하는 vnc)가 작동하지 않는 등 모든 종류의 기능 장애가 발생하기 시작합니다.

별도의 파티션에 있으면 /home문제가 조금 완화되지만, 별도의 파티션에 있고 100% 가득 차면 /homeSSH에서 사용하는 사용자의 홈 계정 아래에 폴더를 위한 공간이 남지 않을 것이라고 추측합니다. , 그래서 .ssh당신이 겪고 있는 일의 원인이 될 수 있습니다. /home파티션이 별도의 파티션이 아니고 파티션이 100% 가득 찬 경우 /이는 문제 1입니다.

어쨌든, [운영 체제] 디스크가 100% 꽉 찼다고 의심되면 콘솔에 로그인하여(때때로 단일 사용자 모드에서) 공간을 확보할 수 있는 것을 삭제해야 합니다. 그렇지 않으면 모든 유형의 프로그램과 서비스가 실패하다 .

답변2

SFTP를 통해 서버에 연결을 시도할 수 있습니다. 서버가 셸 세션을 허용하지 않는 경우에도 작동할 수 있으며 tar 파일(또는 다른 파일)을 삭제하여 일부 디스크 공간을 확보할 수 있습니다.

지적한 대로 SSH 디버그 출력에는 원격 서버에 연결하고 세션을 시작하고 있음이 표시됩니다. 그러나 원격 서버의 파일 시스템 공간이 부족하거나 기타 문제로 인해 세션이 즉시 종료됩니다.

시스템은 SFTP 세션을 수락할 수 있습니다. 이는 문제와 원격 시스템에서 SFTP가 구성된 방식에 따라 다릅니다. SFTP를 통해 연결할 수 있는 경우 디렉터리를 확인하고 공간을 확보할 만큼 충분한 파일을 다운로드하거나 삭제할 수 있어야 합니다.

관련 정보