Skip to content
This repository has been archived by the owner on Jun 18, 2020. It is now read-only.

EFSBackup: rsync error: received SIGINT, SIGTERM, or SIGHUP #60

Open
peteroruba opened this issue Sep 23, 2016 · 1 comment
Open

EFSBackup: rsync error: received SIGINT, SIGTERM, or SIGHUP #60

peteroruba opened this issue Sep 23, 2016 · 1 comment

Comments

@peteroruba
Copy link

Hello,

rsync process gets killed for an unknown reason. Please see log attached below. The production EFS volume has 50 GB of data, backup volume ends up with approximately 17 GB of backup data before rsync gets killed.

Thanks
Peter

--2016-09-23 13:24:14-- https://s3-us-west-2.amazonaws.com/xxx/aws/efsbackup/efs-backup.sh
Resolving s3-us-west-2.amazonaws.com (s3-us-west-2.amazonaws.com)... 54.231.168.196
Connecting to s3-us-west-2.amazonaws.com (s3-us-west-2.amazonaws.com)|54.231.168.196|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2986 (2.9K) [application/x-sh]
Saving to: ‘efs-backup.sh’

 0K ..                                                    100% 90.7M=0s

2016-09-23 13:24:14 (90.7 MB/s) - ‘efs-backup.sh’ saved [2986/2986]

rm: cannot remove ‘/tmp/efs-backup.log’: No such file or directory
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(544) [sender=3.0.6]
rsync: writefd_unbuffered failed to write 97 bytes to socket [generator]: Broken pipe (32)

@peteroruba peteroruba changed the title rsync error: received SIGINT, SIGTERM, or SIGHUP EFSBackup: rsync error: received SIGINT, SIGTERM, or SIGHUP Sep 23, 2016
@peteroruba
Copy link
Author

Ran efsbackup.sh on a m3.medium manually and it ran fine.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant