Re: [BackupPC-users] Got fatal error during xfer (No files dumped for share E)

[jose marquez]

Something interesting happened, I believe the 2nd attempt was successful, but 
another full backup was automatically started and erased the old one that ended 
with a different error:


2018-08-21 00:20:58 Aborting backup up after signal INT
2018-08-21 00:21:00 Got fatal error during xfer (Unexpected end of tar archive)
2018-08-21 00:21:02 Saved partial dump 0

I may have actually set this up incorrectly or something. I'm very new to Linux.

I'll figure this out tomorrow. I need sleep.



From: jose marquez 
Sent: Tuesday, August 21, 2018 12:07 AM
To: General list for user discussion, questions and support
Subject: Re: [BackupPC-users] Got fatal error during xfer (No files dumped for 
share E)


I am using BackupPC 3.3.1 and Version 4.3.11 of smb (I used "smbstatus 
--version" to get that verison)


I have also realized that this isn't the latest version which is interesting. 
If that's the reason why the backup failed then I'm not the smartest one when 
it comes to checking things before asking for help...


From: Craig Barratt via BackupPC-users 
Sent: Monday, August 20, 2018 11:48 PM
To: General list for user discussion, questions and support
Cc: Craig Barratt
Subject: Re: [BackupPC-users] Got fatal error during xfer (No files dumped for 
share E)

What versions of BackupPC and smbclient are you using?

Craig

On Mon, Aug 20, 2018 at 10:16 PM jose marquez 
mailto:jose...@live.com>> wrote:

Hello, I recently was given a Dell Precision T1500 and decided to finally make 
a backup server. I wanted to backup my storage drive (Drive letter E) offsite 
automatically from my main computer which runs Windows 7. So I found out about 
BackupPC and set it up according to this source: 
https://www.howtoforge.com/linux_backuppc and was able to start a backup. I had 
personal errands to take care of so I left the backup to run and came back to 
this in the XferLOG:

This snippet is from the top of the log:


Contents of file /var/lib/backuppc/pc/blunt-pc/XferLOG.0.z, modified 2018-08-20 
17:22:14

Running: /usr/bin/smbclient blunt-pc\\E -I 192.168.1.3 -U Blunt -E -d 1 -c 
tarmode\ full -Tc -
full backup started for share E
Xfer PIDs are now 6250,6249
WARNING: The "syslog" option is deprecated
Domain=[BLUNT-PC] OS=[Windows 7 Ultimate 7601 Service Pack 1] Server=[Windows 7 
Ultimate 6.1]
tar:316  tarmode is now full, system, hidden, noreset, quiet

This snippet is from the bottom of the log:

create   644   0/0  6440353792 pagefile.sys
tarExtract: �6���Y��<�H���}�  �c��j�P���
tarExtract:  d���l�)�> = �C��&�
tarExtract: �U���{�+ �|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/9: 
checksum error at
tarExtract: Can't open 
/var/lib/backuppc/pc/blunt-pc/new/fE/f�6���Y��<�H���}�  �c��j�P���%0a 
d���l�)�> = �C��&�%0d�U���{�+ 
�|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/f9 for empty output  
create 0   0/0   0 �6���Y��<�H���}�  �c��j�P���
tarExtract:  d���l�)�> = �C��&�
tarExtract: �U���{�+ �|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/9
tarExtract: �1! . � d�,���e�  �yi�Z���H��r�Y�C��z ��7�1�~� 
�  < �e��
tarExtract: ���
tarExtract: 7 � M �m���D�BJ � �   
tarExtract:  ] � /_: checksum error at
tarExtract: Unable to open 
/var/lib/backuppc/pc/blunt-pc/new/fE/f�6���Y��<�H���}�  �c��j�P���%0a 
d���l�)�> = �C��&�%0d�U���{�+ 
�|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/attrib for writingBotch, no 
matches on /var/lib/backuppc/pc/blunt-pc/new/fE/f�6���Y��<�H���}�  
�c��j�P���%0a d���l�)�> = �C��&�%0d�U���{�+ 
�|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/attrib 
(715fadf75232a925b6f7e60587a51417)Can't open 
/var/lib/backuppc/pc/blunt-pc/new/fE/f�1! . � d�,���e�  
�yi�Z���H��r�Y�C��z ��7�1�~� �  < �e��%0a���%0d7 � M 
�m���D�BJ � �     %0a ] � /f_ for empty output  create 0
   0/0   0 �1! . � d�,���e�  �yi�Z���H��r�Y�C��z 
��7�1�~� �  < �e��
tarExtract: ���
tarExtract: 7 � M �m���D�BJ � �   
tarExtract:  ] � /_
tarExtract: � ���8�3 * �
tarExtract: Z�2  ? �P�   L   t�� ��� 5 n $ vn���c�bN � �
tarExtract:���n��� � r �I���6�/  � v �k�{�"�,; � /a: checksum 
error at
NT_STATUS_ACCESS_DENIED listing \System Volume Information\*
tar:712  Total bytes received: 131331187102
tarExtract: Unable to open /var/lib/backuppc/pc/blunt-pc/new/fE/f�1! . � 
d�,���e�  �yi�Z���H��r�Y�C��z ��7�1�~� �  < �e��%0a���%0d7 
� M �m���D�BJ � �     %0a ] � /attrib for writingBotch, no 
matches on /var/lib/backuppc/pc/blunt-pc/new/fE/f�1! . � d�,���e�  
�yi�Z���H��r�Y�C��z ��7�1�~� �  < �e��%0a���%0d7 � M 
�m���D�BJ � �   

Re: [BackupPC-users] Got fatal error during xfer (No files dumped for share E)

[jose marquez]

I am using BackupPC 3.3.1 and Version 4.3.11 of smb (I used "smbstatus 
--version" to get that verison)


I have also realized that this isn't the latest version which is interesting. 
If that's the reason why the backup failed then I'm not the smartest one when 
it comes to checking things before asking for help...


From: Craig Barratt via BackupPC-users 
Sent: Monday, August 20, 2018 11:48 PM
To: General list for user discussion, questions and support
Cc: Craig Barratt
Subject: Re: [BackupPC-users] Got fatal error during xfer (No files dumped for 
share E)

What versions of BackupPC and smbclient are you using?

Craig

On Mon, Aug 20, 2018 at 10:16 PM jose marquez 
mailto:jose...@live.com>> wrote:

Hello, I recently was given a Dell Precision T1500 and decided to finally make 
a backup server. I wanted to backup my storage drive (Drive letter E) offsite 
automatically from my main computer which runs Windows 7. So I found out about 
BackupPC and set it up according to this source: 
https://www.howtoforge.com/linux_backuppc and was able to start a backup. I had 
personal errands to take care of so I left the backup to run and came back to 
this in the XferLOG:

This snippet is from the top of the log:


Contents of file /var/lib/backuppc/pc/blunt-pc/XferLOG.0.z, modified 2018-08-20 
17:22:14

Running: /usr/bin/smbclient blunt-pc\\E -I 192.168.1.3 -U Blunt -E -d 1 -c 
tarmode\ full -Tc -
full backup started for share E
Xfer PIDs are now 6250,6249
WARNING: The "syslog" option is deprecated
Domain=[BLUNT-PC] OS=[Windows 7 Ultimate 7601 Service Pack 1] Server=[Windows 7 
Ultimate 6.1]
tar:316  tarmode is now full, system, hidden, noreset, quiet

This snippet is from the bottom of the log:

create   644   0/0  6440353792 pagefile.sys
tarExtract: �6���Y��<�H���}�  �c��j�P���
tarExtract:  d���l�)�> = �C��&�
tarExtract: �U���{�+ �|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/9: 
checksum error at
tarExtract: Can't open 
/var/lib/backuppc/pc/blunt-pc/new/fE/f�6���Y��<�H���}�  �c��j�P���%0a 
d���l�)�> = �C��&�%0d�U���{�+ 
�|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/f9 for empty output  
create 0   0/0   0 �6���Y��<�H���}�  �c��j�P���
tarExtract:  d���l�)�> = �C��&�
tarExtract: �U���{�+ �|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/9
tarExtract: �1! . � d�,���e�  �yi�Z���H��r�Y�C��z ��7�1�~� 
�  < �e��
tarExtract: ���
tarExtract: 7 � M �m���D�BJ � �   
tarExtract:  ] � /_: checksum error at
tarExtract: Unable to open 
/var/lib/backuppc/pc/blunt-pc/new/fE/f�6���Y��<�H���}�  �c��j�P���%0a 
d���l�)�> = �C��&�%0d�U���{�+ 
�|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/attrib for writingBotch, no 
matches on /var/lib/backuppc/pc/blunt-pc/new/fE/f�6���Y��<�H���}�  
�c��j�P���%0a d���l�)�> = �C��&�%0d�U���{�+ 
�|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/attrib 
(715fadf75232a925b6f7e60587a51417)Can't open 
/var/lib/backuppc/pc/blunt-pc/new/fE/f�1! . � d�,���e�  
�yi�Z���H��r�Y�C��z ��7�1�~� �  < �e��%0a���%0d7 � M 
�m���D�BJ � �     %0a ] � /f_ for empty output  create 0
   0/0   0 �1! . � d�,���e�  �yi�Z���H��r�Y�C��z 
��7�1�~� �  < �e��
tarExtract: ���
tarExtract: 7 � M �m���D�BJ � �   
tarExtract:  ] � /_
tarExtract: � ���8�3 * �
tarExtract: Z�2  ? �P�   L   t�� ��� 5 n $ vn���c�bN � �
tarExtract:���n��� � r �I���6�/  � v �k�{�"�,; � /a: checksum 
error at
NT_STATUS_ACCESS_DENIED listing \System Volume Information\*
tar:712  Total bytes received: 131331187102
tarExtract: Unable to open /var/lib/backuppc/pc/blunt-pc/new/fE/f�1! . � 
d�,���e�  �yi�Z���H��r�Y�C��z ��7�1�~� �  < �e��%0a���%0d7 
� M �m���D�BJ � �     %0a ] � /attrib for writingBotch, no 
matches on /var/lib/backuppc/pc/blunt-pc/new/fE/f�1! . � d�,���e�  
�yi�Z���H��r�Y�C��z ��7�1�~� �  < �e��%0a���%0d7 � M 
�m���D�BJ � �     %0a ] � /attrib 
(e4894caf9ef0d79e617cfceb23934040)Can't open 
/var/lib/backuppc/pc/blunt-pc/new/fE/f� ���8�3 * �%0dZ�2  ? �P� 
  L   t�� ��� 5 n $ vn���c�bN � � %0d   ���n��� � r 
�I���6�/f  � v �k�{�"�,; � /fa for empty output  create 0   0/0 
  0 � ���8�3 * �
tarExtract: Z�2  ? �P�   L   t�� ��� 5 n $ vn���c�bN � �
tarExtract:���n��� � r �I���6�/  � v �k�{�"�,; � /a
tarExtract:  � �Y�S��s � B m��_  ~ V ��� � D e   u��A� 
�[  ( �AI� �� n� � ���<�c l
tarExtract:  We�'�< 7 ���B�/�: checksum error at
tarExtract: Unable to open /var/lib/backuppc/pc/blu

Re: [BackupPC-users] Got fatal error during xfer (No files dumped for share E)

[Craig Barratt via BackupPC-users]

What versions of BackupPC and smbclient are you using?

Craig

On Mon, Aug 20, 2018 at 10:16 PM jose marquez  wrote:

> Hello, I recently was given a Dell Precision T1500 and decided to finally
> make a backup server. I wanted to backup my storage drive (Drive letter E)
> offsite automatically from my main computer which runs Windows 7. So I
> found out about BackupPC and set it up according to this source:
> https://www.howtoforge.com/linux_backuppc and was able to start a backup.
> I had personal errands to take care of so I left the backup to run and came
> back to this in the XferLOG:
>
> This snippet is from the top of the log:
>
>
> Contents of file /var/lib/backuppc/pc/blunt-pc/XferLOG.0.z, modified
> 2018-08-20 17:22:14
>
> Running: /usr/bin/smbclient blunt-pc\\E -I 192.168.1.3 -U Blunt -E -d 1 
> -c tarmode\ full -Tc -
> full backup started for share E
> Xfer PIDs are now 6250,6249
> WARNING: The "syslog" option is deprecated
> Domain=[BLUNT-PC] OS=[Windows 7 Ultimate 7601 Service Pack 1] Server=[Windows 
> 7 Ultimate 6.1]
> tar:316  tarmode is now full, system, hidden, noreset, quiet
>
> This snippet is from the bottom of the log:
>
> create   644   0/0  6440353792 pagefile.sys
> tarExtract: �6���Y��<�H���}�  �c��j�P���
> tarExtract: d���l�)�> = �C��&�
> tarExtract: �U���{�+ �|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/9: 
> checksum error at
> tarExtract: Can't open 
> /var/lib/backuppc/pc/blunt-pc/new/fE/f�6���Y��<�H���}�  �c��j�P���%0a
> d���l�)�> = �C��&�%0d�U���{�+ 
> �|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/f9 for empty output  
> create 0   0/0   0 �6���Y��<�H���}�  �c��j�P���
> tarExtract: d���l�)�> = �C��&�
> tarExtract: �U���{�+ �|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/9
> tarExtract: �1! . � d�,���e�  �yi�Z���H��r�Y�C��z 
> ��7�1�~� �  < �e��
> tarExtract: ���
> tarExtract: 7 � M �m���D�BJ � �   
> tarExtract:  ] � /_: checksum error at
> tarExtract: Unable to open 
> /var/lib/backuppc/pc/blunt-pc/new/fE/f�6���Y��<�H���}�  �c��j�P���%0a
> d���l�)�> = �C��&�%0d�U���{�+ 
> �|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/attrib for writingBotch, no 
> matches on /var/lib/backuppc/pc/blunt-pc/new/fE/f�6���Y��<�H���}�  
> �c��j�P���%0ad���l�)�> = �C��&�%0d�U���{�+ 
> �|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/attrib 
> (715fadf75232a925b6f7e60587a51417)Can't open 
> /var/lib/backuppc/pc/blunt-pc/new/fE/f�1! . � d�,���e�  
> �yi�Z���H��r�Y�C��z ��7�1�~� �  < �e��%0a���%0d7 � M 
> �m���D�BJ � �     %0a ] � /f_ for empty output  create 0  
>  0/0   0 �1! . � d�,���e�  
> �yi�Z���H��r�Y�C��z ��7�1�~� �  < �e��
> tarExtract: ���
> tarExtract: 7 � M �m���D�BJ � �   
> tarExtract:  ] � /_
> tarExtract: � ���8�3 * �
> tarExtract: Z�2  ? �P�   L   t�� ��� 5 n $ vn���c�bN 
> � �
> tarExtract:���n��� � r �I���6�/  � v �k�{�"�,; � /a: checksum 
> error at
> NT_STATUS_ACCESS_DENIED listing \System Volume Information\*
> tar:712  Total bytes received: 131331187102
> tarExtract: Unable to open /var/lib/backuppc/pc/blunt-pc/new/fE/f�1! . � 
> d�,���e�  �yi�Z���H��r�Y�C��z ��7�1�~� �  < 
> �e��%0a���%0d7 � M �m���D�BJ � �     %0a ] � /attrib for 
> writingBotch, no matches on /var/lib/backuppc/pc/blunt-pc/new/fE/f�1! . � 
> d�,���e�  �yi�Z���H��r�Y�C��z ��7�1�~� �  < 
> �e��%0a���%0d7 � M �m���D�BJ � �     %0a ] � /attrib 
> (e4894caf9ef0d79e617cfceb23934040)Can't open 
> /var/lib/backuppc/pc/blunt-pc/new/fE/f� ���8�3 * �%0dZ�2  ? �P� 
>   L   t�� ��� 5 n $ vn���c�bN � � %0d   ���n��� � r 
> �I���6�/f  � v �k�{�"�,; � /fa for empty output  create 0   
> 0/0   0 � ���8�3 * �
> tarExtract: Z�2  ? �P�   L   t�� ��� 5 n $ vn���c�bN 
> � �
> tarExtract:���n��� � r �I���6�/  � v �k�{�"�,; � /a
> tarExtract:  � �Y�S��s � B m��_  ~ V ��� � D e   
> u��A� �[  ( �AI� �� n� � ���<�c l
> tarExtract:  We�'�< 7 ���B�/�: checksum error at
> tarExtract: Unable to open /var/lib/backuppc/pc/blunt-pc/new/fE/f� ���8�3 * 
> �%0dZ�2  ? �P�   L   t�� ��� 5 n $ vn���c�bN � � %0d  
>  ���n��� � r �I���6�/f  � v �k�{�"�,; � /attrib for writingBotch, 
> no matches on /var/lib/backuppc/pc/blunt-pc/new/fE/f� ���8�3 * 
> �%0dZ�2  ? �P�   L   t�� ��� 5 n $ vn���c�bN � � %0d  
>  ���n��� � r �I���6�/f  � v �k�{�"�,; � /attrib 
> (583fc6779d9ccc4b6731ef590de7624f)Unable to open 
> /var/lib/backuppc/pc/blunt-pc/new/fE/f� ���8�3 * �%0dZ�2  ? �P� 
>   L   t�� ��� 5 n $ vn���c�bN � � %0d   ���n��� � r 
> �I���6�/attrib for 

Re: [BackupPC-users] 'Got fatal error during xfer' with no additional comment

[Carl T. Miller]

Have you tried running the tar command on the host
that is being backed up?  It's possible that you
will see errors that you wouldn't see otherwise.

Have you had previous successful backups and only
occasionally seen failures?  If so, it's possible
that a file is changing as tar is reading it.  Tar
will complete the backup, but will exit with an
error status.

c


Lucie et Bruno Seguin wrote:
> Hello,
>
> I performed a fresh install of backuppc on Ubuntu and while running the
> backup of /home directory using tar method I am getting the following
> message in logs:
>
> 2015-02-22 14:33:36 full backup started for directory /home
> 2015-02-22 14:33:38 Got fatal error during xfer (Nombre total d'octets
> écrits: 19834880 (19MiB, 61MiB/s))
> 2015-02-22 14:33:43 Backup aborted (Nombre total d'octets écrits:
> 19834880 (19MiB, 61MiB/s))
> 2015-02-22 14:33:43 Saved partial dump 0
>
> In Error logs I have:
>
> Running: /usr/bin/sudo /bin/tar -c -v -f - -C /home --totals .
> full backup started for directory /home
> Xfer PIDs are now 17561,17560
> [ skipped 70 lines ]
> tarExtract: Got file './', mode 0755, size 0, type 5
> [ skipped 1 lines ]
> tarExtract: Got file './servadmin/', mode 0755, size 0, type 5
> [ skipped 1 lines ]
> tarExtract: Got file './servadmin/.ssh/', mode 0700, size 0, type 5
> [ skipped 1 lines ]
> 
> tarExtract: Done: 0 errors, 58 filesExist, 19779080 sizeExist, 18093679
> sizeExistComp, 58 filesTotal, 19779080 sizeTotal
> Got fatal error during xfer (Nombre total d'octets écrits: 19834880
> (19MiB, 61MiB/s))
> Backup aborted (Nombre total d'octets écrits: 19834880 (19MiB, 61MiB/s))
> Saving this as a partial backup
>
> I have no clue how to identify the reason of the failure (no error code
> or any explaination).
> Does someone have an idea?
>
> --
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki:http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>



--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer after 20 MiB (tar on localhost)

[Timothy J Massey]

"Jost Schenck"  wrote on 03/14/2014 07:37:00 AM:

> I guess you're right that backing up the backup servers system 
> config with backuppc itself may not be such a brilliant idea :)

You can *never* back up something with itself.

> What
> I thought was, that in case my home server fails I could restore 
> configuration by first installing a new linux with backuppc and then
> pointing backuppc to my backup disc.

The last part (pointing to the backup disk) won't work:  BackupPC mangles 
file names, for one thing.  You would need to do a proper restore in order 
to use the data.

If you want a copy of your data that is 100% ready to put into production, 
you'd use a different tool.  Rsync by itself would work fine (but no 
versioning), as would things like rdiff-backup (a kind of BackupPC-style 
method of versioning but with unmangled files).

> But your idea sounds easier. Thanks!

His idea is not any easier on the *RESTORE* side.  In either case, you'll 
have to do a restore.

Tim Massey
 
Out of the Box Solutions, Inc. 
Creative IT Solutions Made Simple!
http://www.OutOfTheBoxSolutions.com
tmas...@obscorp.com 
 
22108 Harper Ave.
St. Clair Shores, MI 48080
Office: (800)750-4OBS (4627)
Cell: (586)945-8796 
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer after 20 MiB (tar on localhost)

[Jost Schenck]

Hi,

 

thanks for your tips, I will definitely think about this. My problem has been solved by Holger's tip, I accidentally answered by private mail only.

 


I guess you're right that backing up the backup servers system config with backuppc itself may not be such a brilliant idea :) What I thought was, that in case my home server fails I could restore configuration by first installing a new linux with backuppc and then pointing backuppc to my backup disc. But your idea sounds easier. Thanks!

 

Jost


Gesendet: Donnerstag, 13. März 2014 um 10:36 Uhr
Von: "Jurie Botha" 
An: "General list for user discussion, questions and support" 
Cc: "Jost Schenck" 
Betreff: Re: [BackupPC-users] Got fatal error during xfer after 20 MiB (tar on localhost)

Hi Josh,

Why not just export your local folders that need to be backed up via rsync daemon? Much easier in the long run.

Also I presume you are backing up /etc to back up the system config, bad idea to do that to backuppc if you are doing it for DR purposes. rather have a cronjob (rsync ) backup your system config, that way if your backup server fails - you can simply re-install & restore config & backup pool.

	
		
			--
			 
			

	
		 
		
			

	
	Jurie Botha 
	
	Senior IT Support Engineer | Trans-Africa Projects (Pty) Ltd
	
	Tel: +27 11 205 9467 | Mobile: +27 83 225 1819 | Email: jur...@taprojects.co.za

			
		
		
	

			
			
			 
		
	

-Original Message-
From: Holger Parplies <wb...@parplies.de>
Reply-to: "General list for user discussion, questions and support" 
To: Jost Schenck <jost.sche...@gmx.de>
Subject: Re: [BackupPC-users] Got fatal error during xfer after 20 MiB (tar on localhost)
Date: Wed, 12 Mar 2014 20:59:36 +0100
 
Hi,

Jost Schenck wrote on 2014-03-11 19:39:21 +0100 [Re: [BackupPC-users] Got fatal error during xfer after 20 MiB (tar on localhost)]:
> I probably should add:

right, but you prepend instead.

Earlier on, Jost Schenck had written:
> > Hi,
> >
> > I set up backuppc in my small home network. It works fine now backing up my 
> > work linux PC over ssh/rsync. However, trying to backup /etc on localhost 
> > over tar, I get an error after most of /etc (but not all) has been backed up:
> > [...]
> > Got fatal error during xfer (Gesamtzahl geschriebener Bytes: 20613120 (20MiB, 2,1MiB/s))

yes, you translated it for us, but who is supposed to translate it to
BackupPC? As far as BackupPC is concerned, some unexpected message is an
error.

Are you sure that not all of /etc has, in fact, been backed up? You get a
"partial" backup due to the "error", but I would expect the backup to
contain all files.

> > Tar over sudo is configured using visudo as explained in the documentation. 
> > I have no idea why this fails. Can you help me?

I generally think that setting up a *nix system with a default language !=
English is a bad idea. Language is a user preference, not a system preference
(yes, you might want your DM to greet your users in a different language, and
*all* of your users might prefer a single different language, but still the
*system* should remain comprehensible). Just a few minutes ago, I read a
system error message "Speicherzugriffsfehler" on a different mailing list.
Now, was that originally a "bus error" or a "segmentation fault"? I'm sure I
can find out, but the point is: I need to translate it back to the original to
understand it, and I wouldn't be in the least surprised if the same is true
for almost anyone else who actually understands the difference.

Since your system language seems to disagree with BackupPC's requirements,
you'll have to fix things for BackupPC - add an 'env LANG=C' command in an
appropriate place in your backup command. Strictly speaking, you don't need
root privileges to change the environment for a child process, so it would be
something like

	env LANG=C sudo ... tar ...

but then, sudo does have a habit of filtering the environment, so you might
need to explicitly whitelist the LANG variable (see sudoers(5)).

On the other hand, if you use

	sudo ... env LANG=C tar ...

you'll need to allow the 'env' command in sudoers. Unless you narrow that down
by including the starting parameters at least upto the 'tar', you'll be
allowing arbitrary commands, which you don't want to do.

Actually, the sudo(8) man page suggests that you can also use

	sudo ... LANG=C tar ...

(my experimentation agrees). The same notes as for the "env sudo tar" case
apply.

Hope that helps.

Regards,
Holger

--
Learn Graph Databases - Download F

Re: [BackupPC-users] Got fatal error during xfer after 20 MiB (tar on localhost)

[Jurie Botha]

Hi Josh,

Why not just export your local folders that need to be backed up via
rsync daemon? Much easier in the long run.

Also I presume you are backing up /etc to back up the system config, bad
idea to do that to backuppc if you are doing it for DR purposes. rather
have a cronjob (rsync :)) backup your system config, that way if your
backup server fails - you can simply re-install & restore config &
backup pool.
-- 



Jurie Botha 

Senior IT Support Engineer
| Trans-Africa Projects (Pty) Ltd

Tel: +27 11 205 9467 | Mobile: +27
83 225 1819 |
Email: jur...@taprojects.co.za



-Original Message-
From: Holger Parplies 
Reply-to: "General list for user discussion,questions and support"

To: Jost Schenck 
Subject: Re: [BackupPC-users] Got fatal error during xfer after 20 MiB
(tar on localhost)
Date: Wed, 12 Mar 2014 20:59:36 +0100


Hi,

Jost Schenck wrote on 2014-03-11 19:39:21 +0100 [Re: [BackupPC-users] Got fatal 
error during xfer after 20 MiB (tar on localhost)]:
> I probably should add:

right, but you prepend instead.

Earlier on, Jost Schenck had written:
> > Hi,
> >
> > I set up backuppc in my small home network. It works fine now backing up my 
> > work linux PC over ssh/rsync. However, trying to backup /etc on localhost 
> > over tar, I get an error after most of /etc (but not all) has been backed 
> > up:
> > [...]
> > Got fatal error during xfer (Gesamtzahl geschriebener Bytes: 20613120 
> > (20MiB, 2,1MiB/s))

yes, you translated it for us, but who is supposed to translate it to
BackupPC? As far as BackupPC is concerned, some unexpected message is an
error.

Are you sure that not all of /etc has, in fact, been backed up? You get a
"partial" backup due to the "error", but I would expect the backup to
contain all files.

> > Tar over sudo is configured using visudo as explained in the documentation. 
> > I have no idea why this fails. Can you help me?

I generally think that setting up a *nix system with a default language !=
English is a bad idea. Language is a user preference, not a system preference
(yes, you might want your DM to greet your users in a different language, and
*all* of your users might prefer a single different language, but still the
*system* should remain comprehensible). Just a few minutes ago, I read a
system error message "Speicherzugriffsfehler" on a different mailing list.
Now, was that originally a "bus error" or a "segmentation fault"? I'm sure I
can find out, but the point is: I need to translate it back to the original to
understand it, and I wouldn't be in the least surprised if the same is true
for almost anyone else who actually understands the difference.

Since your system language seems to disagree with BackupPC's requirements,
you'll have to fix things for BackupPC - add an 'env LANG=C' command in an
appropriate place in your backup command. Strictly speaking, you don't need
root privileges to change the environment for a child process, so it would be
something like

env LANG=C sudo ... tar ...

but then, sudo does have a habit of filtering the environment, so you might
need to explicitly whitelist the LANG variable (see sudoers(5)).

On the other hand, if you use

sudo ... env LANG=C tar ...

you'll need to allow the 'env' command in sudoers. Unless you narrow that down
by including the starting parameters at least upto the 'tar', you'll be
allowing arbitrary commands, which you don't want to do.

Actually, the sudo(8) man page suggests that you can also use

sudo ... LANG=C tar ...

(my experimentation agrees). The same notes as for the "env sudo tar" case
apply.

Hope that helps.

Regards,
Holger

--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
<><><>--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer after 20 MiB (tar on localhost)

[Holger Parplies]

Hi,

Jost Schenck wrote on 2014-03-11 19:39:21 +0100 [Re: [BackupPC-users] Got fatal 
error during xfer after 20 MiB (tar on localhost)]:
> I probably should add:

right, but you prepend instead.

Earlier on, Jost Schenck had written:
> > Hi,
> >
> > I set up backuppc in my small home network. It works fine now backing up my 
> > work linux PC over ssh/rsync. However, trying to backup /etc on localhost 
> > over tar, I get an error after most of /etc (but not all) has been backed 
> > up:
> > [...]
> > Got fatal error during xfer (Gesamtzahl geschriebener Bytes: 20613120 
> > (20MiB, 2,1MiB/s))

yes, you translated it for us, but who is supposed to translate it to
BackupPC? As far as BackupPC is concerned, some unexpected message is an
error.

Are you sure that not all of /etc has, in fact, been backed up? You get a
"partial" backup due to the "error", but I would expect the backup to
contain all files.

> > Tar over sudo is configured using visudo as explained in the documentation. 
> > I have no idea why this fails. Can you help me?

I generally think that setting up a *nix system with a default language !=
English is a bad idea. Language is a user preference, not a system preference
(yes, you might want your DM to greet your users in a different language, and
*all* of your users might prefer a single different language, but still the
*system* should remain comprehensible). Just a few minutes ago, I read a
system error message "Speicherzugriffsfehler" on a different mailing list.
Now, was that originally a "bus error" or a "segmentation fault"? I'm sure I
can find out, but the point is: I need to translate it back to the original to
understand it, and I wouldn't be in the least surprised if the same is true
for almost anyone else who actually understands the difference.

Since your system language seems to disagree with BackupPC's requirements,
you'll have to fix things for BackupPC - add an 'env LANG=C' command in an
appropriate place in your backup command. Strictly speaking, you don't need
root privileges to change the environment for a child process, so it would be
something like

env LANG=C sudo ... tar ...

but then, sudo does have a habit of filtering the environment, so you might
need to explicitly whitelist the LANG variable (see sudoers(5)).

On the other hand, if you use

sudo ... env LANG=C tar ...

you'll need to allow the 'env' command in sudoers. Unless you narrow that down
by including the starting parameters at least upto the 'tar', you'll be
allowing arbitrary commands, which you don't want to do.

Actually, the sudo(8) man page suggests that you can also use

sudo ... LANG=C tar ...

(my experimentation agrees). The same notes as for the "env sudo tar" case
apply.

Hope that helps.

Regards,
Holger

--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer after 20 MiB (tar on localhost)

[Jost Schenck]

I probably should add: that German expression "Gesamtzahl geschriebener 
Bytes" translates to "total number of written bytes".

Thanks
Jost

Gesendet mit AquaMail für Android
http://www.aqua-mail.com


Am 11. März 2014 17:21:46 schrieb Jost Schenck :

> Hi,
>
> I set up backuppc in my small home network. It works fine now backing up my 
> work linux PC over ssh/rsync. However, trying to backup /etc on localhost 
> over tar, I get an error after most of /etc (but not all) has been backed up:
>
>
> --- snip 
>pool 777   0/0  15 rc5.d/S50rsync
>pool 777   0/0  17 rc5.d/S91apache2
>create   755   0/0   0 perl
>create   755   0/0   0 perl/CPAN
>create   755   0/0   0 perl/Net
>pool 644   0/0 611 perl/Net/libnet.cfg
>pool 644   0/01332 colord.conf
> tarExtract: Done: 0 errors, 2639 filesExist, 18642603 sizeExist, 2480451 
> sizeExistComp, 2640 filesTotal, 18643116 sizeTotal
> Got fatal error during xfer (Gesamtzahl geschriebener Bytes: 20613120 
> (20MiB, 2,1MiB/s))
> Backup aborted (Gesamtzahl geschriebener Bytes: 20613120 (20MiB, 2,1MiB/s))
> Saving this as a partial backup
>
> Tar over sudo is configured using visudo as explained in the documentation. 
> I have no idea why this fails. Can you help me?
>
> Thanks a lot in advance
> Jost
>
>
>
> --
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki:http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/



--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (Child exited prematurely)

[Les Mikesell]

On Thu, Sep 27, 2012 at 7:25 AM, isubhransu
 wrote:
> I have a backup server which takes backup of other servers and in few days 
> back the backup server started experiencing error and the not able to take 
> back. I think the error log bellow could describe the problem better than me:
>
> 2012-09-10 20:05:40 Aborting backup up after signal PIPE

That just means the transfer program died or disconnected at the other
end, so you will need more information to diagnose it.  Possible
problems could be disk corruption on the target system or running out
of memory.  If you are connecting through a firewall or NAT router,
there may be time limits for either idle periods or total connection
length that you might exceed.

-- 
   Les Mikesell
 lesmikes...@gmail.com

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://ad.doubleclick.net/clk;258768047;13503038;j?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (Total bytes written: 640049664)

[Guillaume Filion]

Le 2010-11-10 14:23, Guillaume Filion a écrit :
> Looking at the samba source code, I'd guess that the problem has to do
> with the iconv stuff done in lib/util/dprintf.c:d_vfprintf but I didn't
> spend a lot of time looking...
> 
> I filed a bug with samba.org:
> https://bugzilla.samba.org/show_bug.cgi?id=7790

Volker Lendecke from the Samba team found the culprit: the locale was
invalid.

Running
dpkg-reconfigure locales
on the debian server fixed the problem.

Cheers,
GFK's
-- 
Guillaume Filion
http://guillaume.filion.org/



signature.asc
Description: OpenPGP digital signature
--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (Total bytes written: 640049664)

[Guillaume Filion]

Hello Craig,

It's been a while, I hope you're doing well.

I ran the smbclient command directly and it looks like a problem with
accented chars in Samba.

On each problematic client, the last file backuped contains an accented
char "Voisinage réseau" (Network Places) and it confuses smbclient.

--- Problematic Win7 ---
directory \Videos\
 504 (504000.0 kb/s) \Videos\desktop.ini
directory \Voisinage d'impression\
NT_STATUS_ACCESS_DENIED listing \Voisinage d'impression\*
directory \Voisinage réseau\
NT_STATUS_ACCESS_DENIED listing \Voisinage rtar: dumped 4813 files and
directories
Total bytes written: 657149952
--

--- Correct WinXP  ---
NT_STATUS_ACCESS_DENIED listing \LocalService\*
directory \NetworkService\
NT_STATUS_ACCESS_DENIED listing \NetworkService\*
tar: dumped 373 files and directories
Total bytes written: 1856
--

I added a file Z.txt in the directory that is being backuped and it
works! :)
--- Workaround Win7 ---
directory \Videos\
 504 (  123.0 kb/s) \Videos\desktop.ini
directory \Voisinage d'impression\
NT_STATUS_ACCESS_DENIED listing \Voisinage d'impression\*
directory \Voisinage réseau\
NT_STATUS_ACCESS_DENIED listing \Voisinage r   0 (0.0 kb/s)
\Z.txt.txt
tar: dumped 4655 files and directories
Total bytes written: 650930688
--
The "Voisinage réseau" line is still getting skewed but at least the
last two lines are right.

Looking at the samba source code, I'd guess that the problem has to do
with the iconv stuff done in lib/util/dprintf.c:d_vfprintf but I didn't
spend a lot of time looking...

I filed a bug with samba.org:
https://bugzilla.samba.org/show_bug.cgi?id=7790

Cheers,
GFK's

Le 2010-11-10 01:47, Craig Barratt a écrit :
> Guillaume,
> 
> Good to hear from you.
> 
> This error seems strange - the closing line from tar is
> "Total bytes written: 640049664", which is exactly what
> lib/BackupPC/Xfer/Tar.pm expects to see to think the backup
> is good.
> 
> I'd be interested if you could debug what is going wrong...
> 
> Craig
-- 
Guillaume Filion
http://guillaume.filion.org/



signature.asc
Description: OpenPGP digital signature
--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer

[Robin Lee Powell]

On Thu, Dec 03, 2009 at 08:13:47PM +, Tyler J. Wagner wrote:
> Are you sure this isn't a ClientTimeout problem?  Try increasing
> it and see if the backup runs for longer.

Just as a general comment (I've been reviewing all the SIGPIPE mails
and people keep saying that), no.  SIGPIPE means the remote rsync
stopped talking for some reason.  SIGALRM is what's generated by the
timeout possing.

-Robin

-- 
They say:  "The first AIs will be built by the military as weapons."
And I'm  thinking:  "Does it even occur to you to try for something
other  than  the default  outcome?"  See http://shrunklink.com/cdiz
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/

--
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer

[Kameleon]

Not a client timeout as the setting is set at 72000 and it will die within
30 minutes if it is going to die. We are going to update the client server
and run a file system check to see what is going on there. Hopefully we can
find something.



On Thu, Dec 3, 2009 at 2:13 PM, Tyler J. Wagner  wrote:

> Are you sure this isn't a ClientTimeout problem?  Try increasing it and see
> if
> the backup runs for longer.
>
> Tyler
>
> On Thursday 03 Dec 2009 17:25:31 Kameleon wrote:
> > Update:
> >
> > We moved the backuppc server to the same room as the client server and on
> > the same switch. The backup still failed, but got alot further. The error
> >  is the same as last time:
> >
> > Read EOF:
> > Tried again: got 0 bytes
> > Child is aborting
> > Can't write 33792 bytes to socket
> > Sending csums, cnt = 250243, phase = 1
> > Done: 26416 files, 31698685174 bytes
> > Got fatal error during xfer (aborted by signal=PIPE)
> > Backup aborted by user signal
> > Saving this as a partial backup
> >
> >
> > So I ran the exact command as the backuppc user that it uses according to
> > the log file and ran it manually. Then I straced the pid on the client
> > machine and got this:
> >
> > select(1, [0], [], NULL, {45, 57000})   = 0 (Timeout)
> > select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
> > select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
> > select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
> > select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
> > select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
> > select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
> > select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
> > select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
> > select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {29, 17})
> > read(0, "", 4)  = 0
> > write(2, "rsync: connection unexpectedly c"..., 72) = -1 EPIPE (Broken
> >  pipe) --- SIGPIPE (Broken pipe) @ 0 (0) ---
> > rt_sigaction(SIGUSR1, {0x1, [], 0}, NULL, 8) = 0
> > rt_sigaction(SIGUSR2, {0x1, [], 0}, NULL, 8) = 0
> > write(2, "rsync error: errors with program"..., 83) = -1 EPIPE (Broken
> >  pipe) --- SIGPIPE (Broken pipe) @ 0 (0) ---
> > rt_sigaction(SIGUSR1, {0x1, [], 0}, NULL, 8) = 0
> > rt_sigaction(SIGUSR2, {0x1, [], 0}, NULL, 8) = 0
> > gettimeofday({1259860374, 861962}, NULL) = 0
> > select(0, NULL, NULL, NULL, {0, 10}) = 0 (Timeout)
> > gettimeofday({1259860374, 961981}, NULL) = 0
> > exit_group(13)  = ?
> > Process 13532 detached
> >
> > It still appears the problem is on the remote server since it is exiting.
> > The client server is a Dell poweredge so I would hope it wasn't hardware
> > related. Anything else I can check before I give it a swift kick in the
> > pants?
> >
> > Donny B.
> >
> > On Wed, Dec 2, 2009 at 3:56 PM, Kameleon  wrote:
> > > I did some more testing watching top and such on both backuppc server
> and
> > > the client. Both had plenty of memory and such. The thing we are
> thinking
> > > is possibly the cable or switch between the two. Tomorrow we plan to
> > > relocate the backuppc server from it's current location and plug it
> > > directly in via crossover cable to the server. That will eliminate the
> > > networking gear all except the network intercafe cards.
> > >
> > > Thanks for the input.
> > >
> > > On Wed, Dec 2, 2009 at 3:10 PM, Les Mikesell  >wrote:
> > >> Kameleon wrote:
> > >> > I do apologize. The backuppc server is Ubuntu 9.10 and the server
> > >> > being backed up is Centos 5.4. I have changed everything back to
> rsync
> > >> > and tried a manual full backup (since that is what it was attempting
> > >> > to do when it failed) I ran strace on the PID of rsync on the remote
> > >> > server being backed up. The last few lines of the output are below.
> > >>
> > >> [...]
> > >>
> > >> >  read(0,
> > >>
> > >>
> "\256\374O\362\350\224\30\3101(Y\"8\3279z\300nt\10*\367\26+\355\364\245W
> > >>)/\224\301"...,
> > >>
> > >> > 8184) = 8184
> > >> > select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {60, 0})
> > >> > read(0,
> > >>
> > >>
> "\314\326\4\242P\345\3\332\245b\317\363\4\253'\307\3056Y\307X\313\364I\5
> > >>\3746\fH\340\212w"...,
> > >>
> > >> > 8184) = 1056
> > >> > select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {58,
> > >> > 296000}) read(0, "", 8184)   = 0
> > >> > select(2, NULL, [1], [1], {60, 0})  = 1 (out [1], left {60, 0})
> > >> > write(1, "O\0\0\10rsync: connection unexpected"..., 83) = -1 EPIPE
> > >> > (Broken pipe)
> > >>
> > >> Looks like something is wrong on the target side, dropping the
> > >> connection.  File system problems?  Out of memory?  Are both machines
> on
> > >> the same LAN or could there be a problem with networking equipment
> > >> between them?
> > >>
> > >> > Backuppc shows the following error when it fails:
> > >> >
> > >> > 2009-12-02 14:17:58 full backup started for directory /; updating
> > >>
> > >> partial #4
> > >>
> > >> > 2009-1

Re: [BackupPC-users] Got fatal error during xfer

[Tyler J. Wagner]

Are you sure this isn't a ClientTimeout problem?  Try increasing it and see if 
the backup runs for longer.

Tyler

On Thursday 03 Dec 2009 17:25:31 Kameleon wrote:
> Update:
> 
> We moved the backuppc server to the same room as the client server and on
> the same switch. The backup still failed, but got alot further. The error
>  is the same as last time:
> 
> Read EOF:
> Tried again: got 0 bytes
> Child is aborting
> Can't write 33792 bytes to socket
> Sending csums, cnt = 250243, phase = 1
> Done: 26416 files, 31698685174 bytes
> Got fatal error during xfer (aborted by signal=PIPE)
> Backup aborted by user signal
> Saving this as a partial backup
> 
> 
> So I ran the exact command as the backuppc user that it uses according to
> the log file and ran it manually. Then I straced the pid on the client
> machine and got this:
> 
> select(1, [0], [], NULL, {45, 57000})   = 0 (Timeout)
> select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
> select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
> select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
> select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
> select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
> select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
> select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
> select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
> select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {29, 17})
> read(0, "", 4)  = 0
> write(2, "rsync: connection unexpectedly c"..., 72) = -1 EPIPE (Broken
>  pipe) --- SIGPIPE (Broken pipe) @ 0 (0) ---
> rt_sigaction(SIGUSR1, {0x1, [], 0}, NULL, 8) = 0
> rt_sigaction(SIGUSR2, {0x1, [], 0}, NULL, 8) = 0
> write(2, "rsync error: errors with program"..., 83) = -1 EPIPE (Broken
>  pipe) --- SIGPIPE (Broken pipe) @ 0 (0) ---
> rt_sigaction(SIGUSR1, {0x1, [], 0}, NULL, 8) = 0
> rt_sigaction(SIGUSR2, {0x1, [], 0}, NULL, 8) = 0
> gettimeofday({1259860374, 861962}, NULL) = 0
> select(0, NULL, NULL, NULL, {0, 10}) = 0 (Timeout)
> gettimeofday({1259860374, 961981}, NULL) = 0
> exit_group(13)  = ?
> Process 13532 detached
> 
> It still appears the problem is on the remote server since it is exiting.
> The client server is a Dell poweredge so I would hope it wasn't hardware
> related. Anything else I can check before I give it a swift kick in the
> pants?
> 
> Donny B.
> 
> On Wed, Dec 2, 2009 at 3:56 PM, Kameleon  wrote:
> > I did some more testing watching top and such on both backuppc server and
> > the client. Both had plenty of memory and such. The thing we are thinking
> > is possibly the cable or switch between the two. Tomorrow we plan to
> > relocate the backuppc server from it's current location and plug it
> > directly in via crossover cable to the server. That will eliminate the
> > networking gear all except the network intercafe cards.
> >
> > Thanks for the input.
> >
> > On Wed, Dec 2, 2009 at 3:10 PM, Les Mikesell wrote:
> >> Kameleon wrote:
> >> > I do apologize. The backuppc server is Ubuntu 9.10 and the server
> >> > being backed up is Centos 5.4. I have changed everything back to rsync
> >> > and tried a manual full backup (since that is what it was attempting
> >> > to do when it failed) I ran strace on the PID of rsync on the remote
> >> > server being backed up. The last few lines of the output are below.
> >>
> >> [...]
> >>
> >> >  read(0,
> >>
> >> "\256\374O\362\350\224\30\3101(Y\"8\3279z\300nt\10*\367\26+\355\364\245W
> >>)/\224\301"...,
> >>
> >> > 8184) = 8184
> >> > select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {60, 0})
> >> > read(0,
> >>
> >> "\314\326\4\242P\345\3\332\245b\317\363\4\253'\307\3056Y\307X\313\364I\5
> >>\3746\fH\340\212w"...,
> >>
> >> > 8184) = 1056
> >> > select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {58,
> >> > 296000}) read(0, "", 8184)   = 0
> >> > select(2, NULL, [1], [1], {60, 0})  = 1 (out [1], left {60, 0})
> >> > write(1, "O\0\0\10rsync: connection unexpected"..., 83) = -1 EPIPE
> >> > (Broken pipe)
> >>
> >> Looks like something is wrong on the target side, dropping the
> >> connection.  File system problems?  Out of memory?  Are both machines on
> >> the same LAN or could there be a problem with networking equipment
> >> between them?
> >>
> >> > Backuppc shows the following error when it fails:
> >> >
> >> > 2009-12-02 14:17:58 full backup started for directory /; updating
> >>
> >> partial #4
> >>
> >> > 2009-12-02 14:24:59 Aborting backup up after signal PIPE
> >> > 2009-12-02 14:25:00 Got fatal error during xfer (aborted by
> >> > signal=PIPE)
> >>
> >> This doesn't tell you anything except that the other end died.
> >>
> >> > remote machine: rsync  version 3.0.6  protocol version 30
> >> > backuppc: rsync  version 3.0.6  protocol version 30
> >>
> >> Backuppc doesn't use the rsync binary on the server side - it has its
> >> own implementation in perl.  But it looks like things started OK and
> >> then either the remote side 

Re: [BackupPC-users] Got fatal error during xfer

[Les Mikesell]

Kameleon wrote:
> Update:
> 
> We moved the backuppc server to the same room as the client server and 
> on the same switch. The backup still failed, but got alot further. The 
> error is the same as last time:
> 
> Read EOF:
> Tried again: got 0 bytes
> Child is aborting
> Can't write 33792 bytes to socket
> Sending csums, cnt = 250243, phase = 1
> Done: 26416 files, 31698685174 bytes
> Got fatal error during xfer (aborted by signal=PIPE)
> Backup aborted by user signal
> Saving this as a partial backup
> 
> 
> So I ran the exact command as the backuppc user that it uses according 
> to the log file and ran it manually. Then I straced the pid on the 
> client machine and got this:

That won't tell you what you want, because you don't have the perl 
version running on the server side doing its part.  Try an strace of the 
actual run on the client side and it might catch some real error.

> It still appears the problem is on the remote server since it is 
> exiting. The client server is a Dell poweredge so I would hope it wasn't 
> hardware related. Anything else I can check before I give it a swift 
> kick in the pants?

An fsck of the filesystems can't hurt.  Or you could test reading all 
the files with 'tar --one-file-system -cf - / |cat >/dev/null' (repeat 
for each mounted filesystem) to see if it encounters any errors.  Don't 
use '-f /dev/null' or gnutar will cheat and skip the file read (it's a 
feature).  'dmesg' might show something if you are getting hardware 
errors instead of filesystem errors.

Also, be sure you are excluding /proc, /sys, etc.  Some strange things 
can happen if you read everything in there.  I like to use the 
--one-file-system option and explicitly back up every mount point which 
will avoid the issue - along with random iso or nfs mounts that might 
accidentally be followed otherwise, but if you do that, be sure you 
include everything you want.

-- 
   Les Mikesell
lesmikes...@gmail.com


--
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer

[Peter Walter]

I have seen similar problems, and they were hardware-related. Have you 
eliminated problems with the network connections? Have you checked the 
network interfaces on both computers for errors? Try connecting both 
computers together using different cables and a different switch.


Peter

Kameleon wrote:

Update:

We moved the backuppc server to the same room as the client server and 
on the same switch. The backup still failed, but got alot further. The 
error is the same as last time:


Read EOF:
Tried again: got 0 bytes
Child is aborting
Can't write 33792 bytes to socket
Sending csums, cnt = 250243, phase = 1
Done: 26416 files, 31698685174 bytes
Got fatal error during xfer (aborted by signal=PIPE)
Backup aborted by user signal
Saving this as a partial backup


So I ran the exact command as the backuppc user that it uses according 
to the log file and ran it manually. Then I straced the pid on the 
client machine and got this:


select(1, [0], [], NULL, {45, 57000})   = 0 (Timeout)
select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {29, 17})
read(0, "", 4)  = 0
write(2, "rsync: connection unexpectedly c"..., 72) = -1 EPIPE (Broken 
pipe)

--- SIGPIPE (Broken pipe) @ 0 (0) ---
rt_sigaction(SIGUSR1, {0x1, [], 0}, NULL, 8) = 0
rt_sigaction(SIGUSR2, {0x1, [], 0}, NULL, 8) = 0
write(2, "rsync error: errors with program"..., 83) = -1 EPIPE (Broken 
pipe)

--- SIGPIPE (Broken pipe) @ 0 (0) ---
rt_sigaction(SIGUSR1, {0x1, [], 0}, NULL, 8) = 0
rt_sigaction(SIGUSR2, {0x1, [], 0}, NULL, 8) = 0
gettimeofday({1259860374, 861962}, NULL) = 0
select(0, NULL, NULL, NULL, {0, 10}) = 0 (Timeout)
gettimeofday({1259860374, 961981}, NULL) = 0
exit_group(13)  = ?
Process 13532 detached

It still appears the problem is on the remote server since it is 
exiting. The client server is a Dell poweredge so I would hope it 
wasn't hardware related. Anything else I can check before I give it a 
swift kick in the pants?


Donny B.

On Wed, Dec 2, 2009 at 3:56 PM, Kameleon > wrote:


I did some more testing watching top and such on both backuppc
server and the client. Both had plenty of memory and such. The
thing we are thinking is possibly the cable or switch between the
two. Tomorrow we plan to relocate the backuppc server from it's
current location and plug it directly in via crossover cable to
the server. That will eliminate the networking gear all except the
network intercafe cards.

Thanks for the input.



On Wed, Dec 2, 2009 at 3:10 PM, Les Mikesell
mailto:lesmikes...@gmail.com>> wrote:

Kameleon wrote:
> I do apologize. The backuppc server is Ubuntu 9.10 and the
server being
> backed up is Centos 5.4. I have changed everything back to
rsync and
> tried a manual full backup (since that is what it was
attempting to do
> when it failed) I ran strace on the PID of rsync on the
remote server
> being backed up. The last few lines of the output are below.
[...]
>  read(0,
>

"\256\374O\362\350\224\30\3101(Y\"8\3279z\300nt\10*\367\26+\355\364\245W)/\224\301"...,
> 8184) = 8184
> select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left
{60, 0})
> read(0,
>

"\314\326\4\242P\345\3\332\245b\317\363\4\253'\307\3056Y\307X\313\364I\5\3746\fH\340\212w"...,
> 8184) = 1056
> select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left
{58, 296000})
> read(0, "", 8184)   = 0
> select(2, NULL, [1], [1], {60, 0})  = 1 (out [1], left
{60, 0})
> write(1, "O\0\0\10rsync: connection unexpected"..., 83) = -1
EPIPE
> (Broken pipe)

Looks like something is wrong on the target side, dropping the
connection.  File system problems?  Out of memory?  Are both
machines on
the same LAN or could there be a problem with networking equipment
between them?


> Backuppc shows the following error when it fails:
>
> 2009-12-02 14:17:58 full backup started for directory /;
updating partial #4
> 2009-12-02 14:24:59 Aborting backup up after signal PIPE
> 2009-12-02 14:25:00 Got fatal error during xfer (aborted by
signal=PIPE)

This doesn't tell you anything except that the other end died.


> remote machine: rsync  version 3.0.6  protocol version 30
> 

Re: [BackupPC-users] Got fatal error during xfer

[Kameleon]

Update:

We moved the backuppc server to the same room as the client server and on
the same switch. The backup still failed, but got alot further. The error is
the same as last time:

Read EOF:
Tried again: got 0 bytes
Child is aborting
Can't write 33792 bytes to socket
Sending csums, cnt = 250243, phase = 1
Done: 26416 files, 31698685174 bytes
Got fatal error during xfer (aborted by signal=PIPE)
Backup aborted by user signal
Saving this as a partial backup


So I ran the exact command as the backuppc user that it uses according to
the log file and ran it manually. Then I straced the pid on the client
machine and got this:

select(1, [0], [], NULL, {45, 57000})   = 0 (Timeout)
select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
select(1, [0], [], NULL, {60, 0})   = 0 (Timeout)
select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {29, 17})
read(0, "", 4)  = 0
write(2, "rsync: connection unexpectedly c"..., 72) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
rt_sigaction(SIGUSR1, {0x1, [], 0}, NULL, 8) = 0
rt_sigaction(SIGUSR2, {0x1, [], 0}, NULL, 8) = 0
write(2, "rsync error: errors with program"..., 83) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
rt_sigaction(SIGUSR1, {0x1, [], 0}, NULL, 8) = 0
rt_sigaction(SIGUSR2, {0x1, [], 0}, NULL, 8) = 0
gettimeofday({1259860374, 861962}, NULL) = 0
select(0, NULL, NULL, NULL, {0, 10}) = 0 (Timeout)
gettimeofday({1259860374, 961981}, NULL) = 0
exit_group(13)  = ?
Process 13532 detached

It still appears the problem is on the remote server since it is exiting.
The client server is a Dell poweredge so I would hope it wasn't hardware
related. Anything else I can check before I give it a swift kick in the
pants?

Donny B.

On Wed, Dec 2, 2009 at 3:56 PM, Kameleon  wrote:

> I did some more testing watching top and such on both backuppc server and
> the client. Both had plenty of memory and such. The thing we are thinking is
> possibly the cable or switch between the two. Tomorrow we plan to relocate
> the backuppc server from it's current location and plug it directly in via
> crossover cable to the server. That will eliminate the networking gear all
> except the network intercafe cards.
>
> Thanks for the input.
>
>
>
> On Wed, Dec 2, 2009 at 3:10 PM, Les Mikesell wrote:
>
>> Kameleon wrote:
>> > I do apologize. The backuppc server is Ubuntu 9.10 and the server being
>> > backed up is Centos 5.4. I have changed everything back to rsync and
>> > tried a manual full backup (since that is what it was attempting to do
>> > when it failed) I ran strace on the PID of rsync on the remote server
>> > being backed up. The last few lines of the output are below.
>> [...]
>> >  read(0,
>> >
>> "\256\374O\362\350\224\30\3101(Y\"8\3279z\300nt\10*\367\26+\355\364\245W)/\224\301"...,
>> > 8184) = 8184
>> > select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {60, 0})
>> > read(0,
>> >
>> "\314\326\4\242P\345\3\332\245b\317\363\4\253'\307\3056Y\307X\313\364I\5\3746\fH\340\212w"...,
>> > 8184) = 1056
>> > select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {58, 296000})
>> > read(0, "", 8184)   = 0
>> > select(2, NULL, [1], [1], {60, 0})  = 1 (out [1], left {60, 0})
>> > write(1, "O\0\0\10rsync: connection unexpected"..., 83) = -1 EPIPE
>> > (Broken pipe)
>>
>> Looks like something is wrong on the target side, dropping the
>> connection.  File system problems?  Out of memory?  Are both machines on
>> the same LAN or could there be a problem with networking equipment
>> between them?
>>
>>
>> > Backuppc shows the following error when it fails:
>> >
>> > 2009-12-02 14:17:58 full backup started for directory /; updating
>> partial #4
>> > 2009-12-02 14:24:59 Aborting backup up after signal PIPE
>> > 2009-12-02 14:25:00 Got fatal error during xfer (aborted by signal=PIPE)
>>
>> This doesn't tell you anything except that the other end died.
>>
>>
>> > remote machine: rsync  version 3.0.6  protocol version 30
>> > backuppc: rsync  version 3.0.6  protocol version 30
>>
>> Backuppc doesn't use the rsync binary on the server side - it has its
>> own implementation in perl.  But it looks like things started OK and
>> then either the remote side quite or the network connection had a problem.
>>
>>
>> --
>>Les Mikesell
>>lesmikes...@gmail.com
>>
>>
>> --
>> Join us December 9, 2009 for the Red Hat Virtual Experience,
>> a free event focused on virtualization and cloud computing.
>> Attend in-depth sessions from your desk. Your couch. Anywhere.
>> http://p.sf.net/sfu/

Re: [BackupPC-users] Got fatal error during xfer

[Kameleon]

I did some more testing watching top and such on both backuppc server and
the client. Both had plenty of memory and such. The thing we are thinking is
possibly the cable or switch between the two. Tomorrow we plan to relocate
the backuppc server from it's current location and plug it directly in via
crossover cable to the server. That will eliminate the networking gear all
except the network intercafe cards.

Thanks for the input.



On Wed, Dec 2, 2009 at 3:10 PM, Les Mikesell  wrote:

> Kameleon wrote:
> > I do apologize. The backuppc server is Ubuntu 9.10 and the server being
> > backed up is Centos 5.4. I have changed everything back to rsync and
> > tried a manual full backup (since that is what it was attempting to do
> > when it failed) I ran strace on the PID of rsync on the remote server
> > being backed up. The last few lines of the output are below.
> [...]
> >  read(0,
> >
> "\256\374O\362\350\224\30\3101(Y\"8\3279z\300nt\10*\367\26+\355\364\245W)/\224\301"...,
> > 8184) = 8184
> > select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {60, 0})
> > read(0,
> >
> "\314\326\4\242P\345\3\332\245b\317\363\4\253'\307\3056Y\307X\313\364I\5\3746\fH\340\212w"...,
> > 8184) = 1056
> > select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {58, 296000})
> > read(0, "", 8184)   = 0
> > select(2, NULL, [1], [1], {60, 0})  = 1 (out [1], left {60, 0})
> > write(1, "O\0\0\10rsync: connection unexpected"..., 83) = -1 EPIPE
> > (Broken pipe)
>
> Looks like something is wrong on the target side, dropping the
> connection.  File system problems?  Out of memory?  Are both machines on
> the same LAN or could there be a problem with networking equipment
> between them?
>
>
> > Backuppc shows the following error when it fails:
> >
> > 2009-12-02 14:17:58 full backup started for directory /; updating partial
> #4
> > 2009-12-02 14:24:59 Aborting backup up after signal PIPE
> > 2009-12-02 14:25:00 Got fatal error during xfer (aborted by signal=PIPE)
>
> This doesn't tell you anything except that the other end died.
>
>
> > remote machine: rsync  version 3.0.6  protocol version 30
> > backuppc: rsync  version 3.0.6  protocol version 30
>
> Backuppc doesn't use the rsync binary on the server side - it has its
> own implementation in perl.  But it looks like things started OK and
> then either the remote side quite or the network connection had a problem.
>
>
> --
>Les Mikesell
>lesmikes...@gmail.com
>
>
> --
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing.
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki:http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
--
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer

[Les Mikesell]

Kameleon wrote:
> I do apologize. The backuppc server is Ubuntu 9.10 and the server being 
> backed up is Centos 5.4. I have changed everything back to rsync and 
> tried a manual full backup (since that is what it was attempting to do 
> when it failed) I ran strace on the PID of rsync on the remote server 
> being backed up. The last few lines of the output are below.
[...]
>  read(0, 
> "\256\374O\362\350\224\30\3101(Y\"8\3279z\300nt\10*\367\26+\355\364\245W)/\224\301"...,
>  
> 8184) = 8184
> select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {60, 0})
> read(0, 
> "\314\326\4\242P\345\3\332\245b\317\363\4\253'\307\3056Y\307X\313\364I\5\3746\fH\340\212w"...,
>  
> 8184) = 1056
> select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {58, 296000})
> read(0, "", 8184)   = 0
> select(2, NULL, [1], [1], {60, 0})  = 1 (out [1], left {60, 0})
> write(1, "O\0\0\10rsync: connection unexpected"..., 83) = -1 EPIPE 
> (Broken pipe)

Looks like something is wrong on the target side, dropping the 
connection.  File system problems?  Out of memory?  Are both machines on 
the same LAN or could there be a problem with networking equipment 
between them?


> Backuppc shows the following error when it fails:
> 
> 2009-12-02 14:17:58 full backup started for directory /; updating partial #4
> 2009-12-02 14:24:59 Aborting backup up after signal PIPE
> 2009-12-02 14:25:00 Got fatal error during xfer (aborted by signal=PIPE)

This doesn't tell you anything except that the other end died.


> remote machine: rsync  version 3.0.6  protocol version 30
> backuppc: rsync  version 3.0.6  protocol version 30

Backuppc doesn't use the rsync binary on the server side - it has its 
own implementation in perl.  But it looks like things started OK and 
then either the remote side quite or the network connection had a problem.


-- 
   Les Mikesell
lesmikes...@gmail.com

--
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer

[Kameleon]

I do apologize. The backuppc server is Ubuntu 9.10 and the server being
backed up is Centos 5.4. I have changed everything back to rsync and tried a
manual full backup (since that is what it was attempting to do when it
failed) I ran strace on the PID of rsync on the remote server being backed
up. The last few lines of the output are below.

read(0,
"\276\202\271p\351\235\273\357g\36\274~[\4Y\265z\276,\321\344`\246\266\341\276\3158\264RA\366"...,
8184) = 8184
select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {60, 0})
read(0,
"4\274\370\2620\20\6\312\244M\22\353\r\304{\211\32h\276\310\\\256\303\217\4\217X\274\237\6z\311"...,
8184) = 8184
select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {60, 0})
read(0,
"\303\255\0374n\360D\355dvvi\254\264\333\224]lX\n*\336Y*\205\3510\374`t\210\303"...,
8184) = 8184
select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {60, 0})
read(0,
"\256\374O\362\350\224\30\3101(Y\"8\3279z\300nt\10*\367\26+\355\364\245W)/\224\301"...,
8184) = 8184
select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {60, 0})
read(0,
"\314\326\4\242P\345\3\332\245b\317\363\4\253'\307\3056Y\307X\313\364I\5\3746\fH\340\212w"...,
8184) = 1056
select(1, [0], [], NULL, {60, 0})   = 1 (in [0], left {58, 296000})
read(0, "", 8184)   = 0
select(2, NULL, [1], [1], {60, 0})  = 1 (out [1], left {60, 0})
write(1, "O\0\0\10rsync: connection unexpected"..., 83) = -1 EPIPE (Broken
pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(2, "rsync: writefd_unbuffered failed"..., 87) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
rt_sigaction(SIGUSR1, {0x1, [], 0}, NULL, 8) = 0
rt_sigaction(SIGUSR2, {0x1, [], 0}, NULL, 8) = 0
write(2, "rsync error: errors with program"..., 83) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
rt_sigaction(SIGUSR1, {0x1, [], 0}, NULL, 8) = 0
rt_sigaction(SIGUSR2, {0x1, [], 0}, NULL, 8) = 0
gettimeofday({1259785360, 391955}, NULL) = 0
select(0, NULL, NULL, NULL, {0, 10}) = 0 (Timeout)
gettimeofday({1259785360, 492092}, NULL) = 0
exit_group(13)  = ?
Process 28645 detached


Backuppc shows the following error when it fails:

2009-12-02 14:17:58 full backup started for directory /; updating partial #4
2009-12-02 14:24:59 Aborting backup up after signal PIPE
2009-12-02 14:25:00 Got fatal error during xfer (aborted by signal=PIPE)


remote machine: rsync  version 3.0.6  protocol version 30
backuppc: rsync  version 3.0.6  protocol version 30

Both using ext3 filesystem

Donny B.

On Wed, Dec 2, 2009 at 2:18 PM, Les Mikesell  wrote:

> Kameleon wrote:
> > I have an issue with one of my backuppc servers. This server is used to
> > only backup one server and has been doing flawless since it was
> > installed about a week ago. Until last night
> >
> > I checked it this morning to find the above error in the host summary. I
> > did some checking and even manually ran the backup with an strace on the
> > process on the remote server. Every time it would fail. I had a similar
> > issue on my home backuppc server on a few servers and switching them
> > from rsync to rsyncd and changing the needed settings did the trick. Not
> > so much with this one. Here are the last few lines of the log when doing
> > both rsync and rsyncd:
> >
> > via rsync:
> >
> > 2009-12-02 10:18:04 full backup started for directory /; updating partial
> #4
> > 2009-12-02 10:25:09 Aborting backup up after signal PIPE
> > 2009-12-02 10:25:10 Got fatal error during xfer (aborted by signal=PIPE)
> > 2009-12-02 10:25:10 Saved partial dump 4
> >
> > Via rsyncd:
> >
> > 2009-12-02 11:09:00 full backup started for directory main; updating
> > partial #4
> > 2009-12-02 11:15:01 Aborting backup up after signal PIPE
> > 2009-12-02 11:15:02 Got fatal error during xfer (aborted by signal=PIPE)
> >
> > I am at a loss. Something is causing the remote end to fail. I did a
> > little research and found that if doing backup via rsync and ssh it
> > could be a large file causing it, as in over 2GB. I looked in the
> > directories being backed up and there are a few files larger than 2GB
> > that are being backed up. Is there a workaround for this?
>
> It might help if you mentioned the OS involved.  Cygwin/windows should
> be the only thing with low size limits and I think that might be version
> specific.
>
> --
>   Les Mikesell
> lesmikes...@gmail.com
>
>
> --
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing.
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki:http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>

Re: [BackupPC-users] Got fatal error during xfer

[Les Mikesell]

Kameleon wrote:
> I have an issue with one of my backuppc servers. This server is used to 
> only backup one server and has been doing flawless since it was 
> installed about a week ago. Until last night
> 
> I checked it this morning to find the above error in the host summary. I 
> did some checking and even manually ran the backup with an strace on the 
> process on the remote server. Every time it would fail. I had a similar 
> issue on my home backuppc server on a few servers and switching them 
> from rsync to rsyncd and changing the needed settings did the trick. Not 
> so much with this one. Here are the last few lines of the log when doing 
> both rsync and rsyncd:
> 
> via rsync:
> 
> 2009-12-02 10:18:04 full backup started for directory /; updating partial #4
> 2009-12-02 10:25:09 Aborting backup up after signal PIPE
> 2009-12-02 10:25:10 Got fatal error during xfer (aborted by signal=PIPE)
> 2009-12-02 10:25:10 Saved partial dump 4
> 
> Via rsyncd:
> 
> 2009-12-02 11:09:00 full backup started for directory main; updating 
> partial #4
> 2009-12-02 11:15:01 Aborting backup up after signal PIPE
> 2009-12-02 11:15:02 Got fatal error during xfer (aborted by signal=PIPE)
> 
> I am at a loss. Something is causing the remote end to fail. I did a 
> little research and found that if doing backup via rsync and ssh it 
> could be a large file causing it, as in over 2GB. I looked in the 
> directories being backed up and there are a few files larger than 2GB 
> that are being backed up. Is there a workaround for this?

It might help if you mentioned the OS involved.  Cygwin/windows should 
be the only thing with low size limits and I think that might be version 
specific.

-- 
   Les Mikesell
 lesmikes...@gmail.com

--
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (fileListReceive failed)

[Terri Kelley]

Finally found it. Path was wrong to the rsync script on the server.  
Fixed that and it ran so it seems there are many reasons you can get  
that error.


But looks like another issue. The job is stil running after all night.  
I see the processes on both ends, connection is established over the  
network but the actual transfer seems not to work.

Haven't looked far enough into that yet.
Anyway, will look into that and start a new thread if need.

thanks for the help to all on this one.


Terri



On Aug 21, 2008, at 6:42 PM, Holger Parplies wrote:


Hi,

Terri Kelley wrote on 2008-08-21 14:52:40 -0500 [Re: [BackupPC- 
users] Got fatal error during xfer (fileListReceive failed)]:

[...]
Went to the host and looked in secure logs. Found the following:

Aug 21 12:39:45 test sudo: pam_unix(sudo:auth): authentication
failure; logname= uid=0 euid=0 tty= ruser= rhost=  user=backuppc


you'll find more in the BackupPC XferLOG before the line you will have
quoted once we get to that part of your e-mail (thank you for top- 
posting).


Regards,
Holger


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (fileListReceive failed)

[Holger Parplies]

Hi,

Terri Kelley wrote on 2008-08-21 14:52:40 -0500 [Re: [BackupPC-users] Got fatal 
error during xfer (fileListReceive failed)]:
> [...]
> Went to the host and looked in secure logs. Found the following:
> 
> Aug 21 12:39:45 test sudo: pam_unix(sudo:auth): authentication  
> failure; logname= uid=0 euid=0 tty= ruser= rhost=  user=backuppc

you'll find more in the BackupPC XferLOG before the line you will have
quoted once we get to that part of your e-mail (thank you for top-posting).

> On Aug 21, 2008, at 1:07 PM, Nils Breunese (Lemonbit) wrote:
> >Terri Kelley wrote:
> >
> >> [...]
> >>full backup started for directory /home/backuppc/test/log/
> >>Got fatal error during xfer (fileListReceive failed)

That one. You probably have something like
"Fatal error (bad version): sudo: bla" in there, where "bla" is the sudo error
message. Comment out 'requiretty' in your sudo configuration. Sorry, that was
stolen from Nils ;-). It's currently the favorite sudo problem on the list,
though I'm not sure if it will lead to an authentication failure.

Regards,
Holger

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (fileListReceive failed)

[Terri Kelley]

The ssh works fine with the keys manually, did do it manually the  
first time for the ok on the fingerprint. -D is there.
Couldn't find anything wrong in the server. Went to the host and  
looked in secure logs. Found the following:


Aug 21 12:39:45 test sudo: pam_unix(sudo:auth): authentication  
failure; logname= uid=0 euid=0 tty= ruser= rhost=  user=backuppc


So have to hunt that down.

Terri




On Aug 21, 2008, at 1:07 PM, Nils Breunese (Lemonbit) wrote:


Terri Kelley wrote:


I have set up BackupPC on a Centos server and am testing now. Trying
the first backup to a host, also Centos, I received the following:

full backup started for directory /home/backuppc/test/log/
Got fatal error during xfer (fileListReceive failed)

I tried it first without the ending / on that directory with the
same results. backuppc is the owner etc of everything in that
directory.

Can someone give me a pointer where to look for the problem?


Have you searched for 'fileListReceive failed' in the list archives?
There are quite a few threads on this: 
http://www.mail-archive.com/search?q=fileListReceive+failed&l=backuppc-users%40lists.sourceforge.net
 I assume you're using rsync over SSH, but you don't give us a lot of
info to go on.

- Make sure you're using -D instead of --devices in the rsync command
lines with more recent versions of rsync
- Make sure you can login to your client by running the command as the
backuppc user on the backup server manually. If you're using SSH keys
you need to OK the host fingerprint the first time you login, which
BackupPC cannot do for you.

Nils Breunese.

-
This SF.Net email is sponsored by the Moblin Your Move Developer's  
challenge
Build the coolest Linux based applications with Moblin SDK & win  
great prizes
Grand prize is a trip for two to an Open Source event anywhere in  
the world

http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (fileListReceive failed)

[Nils Breunese (Lemonbit)]

Terri Kelley wrote:

> I have set up BackupPC on a Centos server and am testing now. Trying  
> the first backup to a host, also Centos, I received the following:
>
> full backup started for directory /home/backuppc/test/log/
> Got fatal error during xfer (fileListReceive failed)
>
> I tried it first without the ending / on that directory with the  
> same results. backuppc is the owner etc of everything in that  
> directory.
>
> Can someone give me a pointer where to look for the problem?

Have you searched for 'fileListReceive failed' in the list archives?  
There are quite a few threads on this: 
http://www.mail-archive.com/search?q=fileListReceive+failed&l=backuppc-users%40lists.sourceforge.net
 
  I assume you're using rsync over SSH, but you don't give us a lot of  
info to go on.

- Make sure you're using -D instead of --devices in the rsync command  
lines with more recent versions of rsync
- Make sure you can login to your client by running the command as the  
backuppc user on the backup server manually. If you're using SSH keys  
you need to OK the host fingerprint the first time you login, which  
BackupPC cannot do for you.

Nils Breunese.

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (fileListReceivefailed)

[Holger Parplies]

Hi,

Anthony J Biacco wrote on 12.09.2007 um 09:13:12 [Re: [BackupPC-users] Got 
fatal error during xfer (fileListReceivefailed)]:
> 
> I'm betting it is in some profile script somewhere..

I believe that is what I said.

> in addition to
> looking in those files, you might try in your ssh command the option: -o
> ForwardX11=no 

And you might as well not. '-x' is shorthand for that, and you've tried
that. In fact, presuming the message comes from the client side, '-x' is
guaranteed not to help, as something is trying to connect to :0.0 on the
client computer (robert-laptop). If ssh could and would set up X11
forwarding and thus pass $DISPLAY,  would not try :0.0 but rather
the forwarded channel (unless it ignores DISPLAY, in which case it is simply
wrong anyway). Disabling it when it obviously already is disabled or ignored
won't help.

I've just done a further test: point DISPLAY to a non-existing X11 display
(:1.0 for this test), run ssh (works without complaint), echo $DISPLAY on the
remote side (gives localhost:12.0 in my case, depends on which ports are free
on the remote side), then try to access $DISPLAY (that's what 'xeyes' is for,
right?). At this point I get an error, or in fact two errors:

1.) "connect to /tmp/.X11-unix/X1: No such file or directory"
This error occurs on the local side when ssh tries to access :1.0.
2.) "X connection to localhost:12.0 broken ..."
This error occurs on the remote side to the client application when ssh
closes the socket.

If I set DISPLAY locally to hostname:1.0 and rerun the test, error message
#1 changes to "connect hostname port 6001: Connection refused".

My point: unless your 'ssh' acts differently, the error message 'Xlib:
connection to ":0.0" refused by server' is *on the client machine side*
(in your case robert-laptop) as I suspected before, *not* on the BackupPC
server side.

In fact, *even if* your 'ssh' acts differently (different implementation),
nobody in their right mind implementing X11 tunnelling will use Xlib to
connect to the X server ;-).

To sum it up: 'Xlib: connection to ":0.0" refused by server' *always* means
the culprit is on the remote side.

Or have I overlooked something?

Regards,
Holger

P.S.: As a side note, my test shows that at least the ssh implementation I
  use does not contact the X server unless an application on the remote
  end requests a connection. This makes perfect sense. I see no reason
  why other implementations should differ. Consequentially, setting up
  X11 forwarding without a meaningful local X display is harmless,
  *unless the remote end tries to use it*. Granted, the existance of
  a DISPLAY environment variable *might* lead a shell startup sequence
  to do just that, but the user account you use for running backups
  should probably not attempt any such exotic things anyway ;-).

  In fact, the '-x' flag to ssh will prevent $DISPLAY from being set and
  thus *can* actually help in some cases, but, in my opinion, that is
  just a workaround for an incorrect configuration.

  Maybe the BackupPC daemon should undef $ENV {DISPLAY} ?

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (fileListReceivefailed)

[Anthony J Biacco]

I'm betting it is in some profile script somewhere..in addition to
looking in those files, you might try in your ssh command the option: -o
ForwardX11=no 

-Tony
-- 
Anthony J. Biacco
Senior Systems/Network Administrator
Decentrix Inc.
303-899-4000 x303

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Holger Parplies
Sent: Wednesday, September 12, 2007 7:57 AM
To: Craig Barratt
Cc: backuppc-users@lists.sourceforge.net; Robert Saunders
Subject: Re: [BackupPC-users] Got fatal error during xfer
(fileListReceivefailed)

Hi,

Craig Barratt wrote on 12.09.2007 um 06:32:29 [Re: [BackupPC-users] Got
fatal error during xfer (fileListReceive failed)]:
> Robert writes:

[re-inserted quote from Robert from a previous e-mail]:
> > I removed the -v option from config.pl, restarted backuppc, this is
the
> > log:
> >
> > Running: /usr/bin/ssh -q -l root robert-laptop /usr/bin/rsync
--server
> > --sender --numeric-ids --perms --owner --group -D --links --times
> > --block-size=2048 --recursive -D --ignore-times . /home/
> > Xfer PIDs are now 5985
> > Got remote protocol 1651076184
> > Fatal error (bad version): Xlib: connection to ":0.0" refused by
server
[/re-inserted quote]

> > I have added -x but this makes no difference.  I have (I think)
disabled
> > X11 port forwarding in /etc/ssh/ssh_config (on the laptop).  Again
no
> > difference.  Error is currently:
> 
> It's still enabled.  There might be two ssh_config files - the
> global one and the per-user one.  You should check both.

are you sure about that? I'd be looking for things in the shell startup
sequence on the client that try to connect to the X-server. True, they'd
have to set $DISPLAY to :0.0 or default it, but the same is true for ssh
-
in fact, a quick test suggests that ssh does *not* propagate DISPLAY or
try
to connect to a local X-server if DISPLAY is not set in its environment.
For
the BackupPC daemon running the ssh command, DISPLAY should *not*
normally
be set.

So: I think your problem is on 'robert-laptop' somewhere in
~root/.profile or
~root/.bashrc (or possibly the equivalents under /etc) - adjust to match
root's
shell.

Hope that helps.

Regards,
Holger


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (fileListReceive failed)

[Holger Parplies]

Hi,

Craig Barratt wrote on 12.09.2007 um 06:32:29 [Re: [BackupPC-users] Got fatal 
error during xfer (fileListReceive failed)]:
> Robert writes:

[re-inserted quote from Robert from a previous e-mail]:
> > I removed the -v option from config.pl, restarted backuppc, this is the
> > log:
> >
> > Running: /usr/bin/ssh -q -l root robert-laptop /usr/bin/rsync --server
> > --sender --numeric-ids --perms --owner --group -D --links --times
> > --block-size=2048 --recursive -D --ignore-times . /home/
> > Xfer PIDs are now 5985
> > Got remote protocol 1651076184
> > Fatal error (bad version): Xlib: connection to ":0.0" refused by server
[/re-inserted quote]

> > I have added -x but this makes no difference.  I have (I think) disabled
> > X11 port forwarding in /etc/ssh/ssh_config (on the laptop).  Again no
> > difference.  Error is currently:
> 
> It's still enabled.  There might be two ssh_config files - the
> global one and the per-user one.  You should check both.

are you sure about that? I'd be looking for things in the shell startup
sequence on the client that try to connect to the X-server. True, they'd
have to set $DISPLAY to :0.0 or default it, but the same is true for ssh -
in fact, a quick test suggests that ssh does *not* propagate DISPLAY or try
to connect to a local X-server if DISPLAY is not set in its environment. For
the BackupPC daemon running the ssh command, DISPLAY should *not* normally
be set.

So: I think your problem is on 'robert-laptop' somewhere in ~root/.profile or
~root/.bashrc (or possibly the equivalents under /etc) - adjust to match root's
shell.

Hope that helps.

Regards,
Holger

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (fileListReceive failed)

[Craig Barratt]

Robert writes:

> I have added -x but this makes no difference.  I have (I think) disabled
> X11 port forwarding in /etc/ssh/ssh_config (on the laptop).  Again no
> difference.  Error is currently:

It's still enabled.  There might be two ssh_config files - the
global one and the per-user one.  You should check both.

Craig

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (fileListReceive failed)

[Robert Saunders]

On Mon, 2007-09-10 at 23:49 -0700, Craig Barratt wrote:
> Robert writes:
> 
> > I removed the -v option from config.pl, restarted backuppc, this is the
> > log:
> > 
> > Running: /usr/bin/ssh -q -l root robert-laptop /usr/bin/rsync --server
> > --sender --numeric-ids --perms --owner --group -D --links --times
> > --block-size=2048 --recursive -D --ignore-times . /home/
> > Xfer PIDs are now 5985
> > Got remote protocol 1651076184
> > Fatal error (bad version): Xlib: connection to ":0.0" refused by server
> 
> Ssh is saying "Xlib: connection to ":0.0" refused by server".
> 
> Add the -x option to rsync (to disable X11 port forwarding).  Note that
> the user's and global ssh_config override the command-line options, so
> if you get the same error you should disable X11 port forwarding there
> too.
> 
> Craig

I have added -x but this makes no difference.  I have (I think) disabled
X11 port forwarding in /etc/ssh/ssh_config (on the laptop).  Again no
difference.  Error is currently:

Running: /usr/bin/ssh -q -x -l root robert-laptop /usr/bin/rsync
--server --sender --numeric-ids --perms --owner --group -D --links
--times --block-size=2048 --recursive -D --ignore-times . /home/
Xfer PIDs are now 9126
Got remote protocol 1651076184
Fatal error (bad version): Xlib: connection to ":0.0" refused by server
Xlib: 
Read EOF: 
Tried again: got 0 bytes
fileListReceive() failed
Done: 0 files, 0 bytes
Got fatal error during xfer (fileListReceive failed)
Backup aborted (fileListReceive failed)

Robert

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (fileListReceive failed)

[Robert Saunders]

On Mon, 2007-09-10 at 23:49 -0700, Craig Barratt wrote:
> Robert writes:
> 
> > I removed the -v option from config.pl, restarted backuppc, this is the
> > log:
> > 
> > Running: /usr/bin/ssh -q -l root robert-laptop /usr/bin/rsync --server
> > --sender --numeric-ids --perms --owner --group -D --links --times
> > --block-size=2048 --recursive -D --ignore-times . /home/
> > Xfer PIDs are now 5985
> > Got remote protocol 1651076184
> > Fatal error (bad version): Xlib: connection to ":0.0" refused by server
> 
> Ssh is saying "Xlib: connection to ":0.0" refused by server".
> 
> Add the -x option to rsync (to disable X11 port forwarding).  Note that
> the user's and global ssh_config override the command-line options, so
> if you get the same error you should disable X11 port forwarding there
> too.
> 
> Craig

Ok, I will reinstate the -x option and try again when I get home.
However, logically, it would seem unlikely this can be the problem
perse, since both the laptops (one of which backs up successfully) are
using the same config.pl file.

Robert

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (fileListReceive failed)

[Craig Barratt]

Robert writes:

> I removed the -v option from config.pl, restarted backuppc, this is the
> log:
> 
> Running: /usr/bin/ssh -q -l root robert-laptop /usr/bin/rsync --server
> --sender --numeric-ids --perms --owner --group -D --links --times
> --block-size=2048 --recursive -D --ignore-times . /home/
> Xfer PIDs are now 5985
> Got remote protocol 1651076184
> Fatal error (bad version): Xlib: connection to ":0.0" refused by server

Ssh is saying "Xlib: connection to ":0.0" refused by server".

Add the -x option to rsync (to disable X11 port forwarding).  Note that
the user's and global ssh_config override the command-line options, so
if you get the same error you should disable X11 port forwarding there
too.

Craig

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (fileListReceive failed)

[Robert Saunders]

On Mon, 2007-09-10 at 06:37 -0700, Craig Barratt wrote:
> Robert writes:
> 
> > OK.  When I try to initiate a backup, it fails, with the following error
> > message (I included -v to get errors listed):
> > 
> > Running: /usr/bin/ssh -q -v -l root robert-laptop /usr/bin/rsync
> > --server --sender --numeric-ids --perms --owner --group -D --links
> > --times --block-size=2048 --recursive -D --ignore-times . /home/
> > Xfer PIDs are now 5370
> > Got remote protocol 1852141647
> > Fatal error (bad version): OpenSSH_4.3p2 Debian-8ubuntu1, OpenSSL 0.9.8c 05 
> > Sep 2006
> 
> The -v option to ssh is causing this error, since it causes ssh to
> emit this text:
> 
> OpenSSH_4.3p2 Debian-8ubuntu1, OpenSSL 0.9.8c 05 Sep 2006
> 
> What happens without the -v?
> 
> Craig

I removed the -v option from config.pl, restarted backuppc, this is the
log:

Running: /usr/bin/ssh -q -l root robert-laptop /usr/bin/rsync --server
--sender --numeric-ids --perms --owner --group -D --links --times
--block-size=2048 --recursive -D --ignore-times . /home/
Xfer PIDs are now 5985
Got remote protocol 1651076184
Fatal error (bad version): Xlib: connection to ":0.0" refused by server
Xlib: 
Read EOF: 
Tried again: got 0 bytes
fileListReceive() failed
Done: 0 files, 0 bytes
Got fatal error during xfer (fileListReceive failed)
Backup aborted (fileListReceive failed)

Robert

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (fileListReceive failed)

[Craig Barratt]

Robert writes:

> OK.  When I try to initiate a backup, it fails, with the following error
> message (I included -v to get errors listed):
> 
> Running: /usr/bin/ssh -q -v -l root robert-laptop /usr/bin/rsync
> --server --sender --numeric-ids --perms --owner --group -D --links
> --times --block-size=2048 --recursive -D --ignore-times . /home/
> Xfer PIDs are now 5370
> Got remote protocol 1852141647
> Fatal error (bad version): OpenSSH_4.3p2 Debian-8ubuntu1, OpenSSL 0.9.8c 05 
> Sep 2006

The -v option to ssh is causing this error, since it causes ssh to
emit this text:

OpenSSH_4.3p2 Debian-8ubuntu1, OpenSSL 0.9.8c 05 Sep 2006

What happens without the -v?

Craig

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (fileListReceive failed)

[Rob Owens]

Is rsync installed on the second Ubuntu laptop?

Are there any differences in the file /etc/ssh/sshd_config on the two
laptops?

-Rob

Robert Saunders wrote:
> I have successfully set up backuppc on a Ubuntu 7.04 box, and equally
> successfully set up one Ubuntu 7.04 laptop as a client, using rsync.  I
> generated ssh keys on both the client (laptop) and host (backuppc),
> exchanged public keys and appended to the authorized_keys2 and
> known_hosts files.  This first laptop backs up fine.
>
> I then tried to set up a second Ubuntu 7.04 laptop.  I copied over the
> host (backuppc)'s public key file (the same one generated above), and
> appended it to the second client laptop's authorized_keys2 file.
>
> When logged in as backuppc on the host (backuppc) PC, executing 
>   ssh -l root 192.168.0.9 whoami
> gives the output
>   root
> without being prompted for root's password.  So at this point all looks
> OK.  When I try to initiate a backup, it fails, with the following error
> message (I included -v to get errors listed):
>
>
> Running: /usr/bin/ssh -q -v -l root robert-laptop /usr/bin/rsync
> --server --sender --numeric-ids --perms --owner --group -D --links
> --times --block-size=2048 --recursive -D --ignore-times . /home/
> Xfer PIDs are now 5370
> Got remote protocol 1852141647
> Fatal error (bad version): OpenSSH_4.3p2 Debian-8ubuntu1, OpenSSL 0.9.8c 05 
> Sep 2006
>
> Read EOF: 
> Tried again: got 0 bytes
> fileListReceive() failed
> Done: 0 files, 0 bytes
> Got fatal error during xfer (fileListReceive failed)
> Backup aborted (fileListReceive failed)
>
> I realise I'm probably a bit inexperienced with ssh - I googled and searched 
> this mailing list, 
> but found nothing that has sorted this issue out.  I'd be very grateful for 
> any advice to sort this out.
>
> Robert
>
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/backuppc-users
> http://backuppc.sourceforge.net/
>   

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (Call timed out

[Craig Barratt]

Craig writes:

> Hi, I'm using backuppc 2.1.2-2ubuntu5 on Ubuntu Server 6.06 LTS
> 
> I get "Got fatal error during xfer (Call timed out: server did not
> respond after 2 milliseconds opening remote file" which causes the
> backup to abort.
> 
> How do I make it just continue on automatically?  Log the errors but
> backup as many files as it can?

This is a fixed timeout in smbclient and is related to your anti-virus
software taking too long to respond to a directory or file read request.

Search on the archives and you will see some people have re-built
smbclient with a longer timeout.

Craig

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (Call timed out

[Lowe, Bryan]

 



From: [EMAIL PROTECTED] on behalf of Craig Knights
Sent: Mon 8/6/2007 6:56 AM
To: backuppc-users@lists.sourceforge.net
Subject: [BackupPC-users] Got fatal error during xfer (Call timed out



Hi, I'm using backuppc 2.1.2-2ubuntu5 on Ubuntu Server 6.06 LTS

I get "Got fatal error during xfer (Call timed out: server did not
respond after 2 milliseconds opening remote file" which causes the
backup to abort.

How do I make it just continue on automatically?  Log the errors but
backup as many files as it can?

Should I try to install a much more recent version of backuppc?

Using smb to a Windows 2000 Server box.  It gets through the first 10GB OK

Thanks!
Craig


p.s. great piece of software so far

this is the relevant part of the log:
>>
2007-08-06 21:22:09 full backup started for share Class Folders

2007-08-06 21:48:49 Got fatal error during xfer (Call timed out:
server did not respond after 2 milliseconds opening remote file \-
2006 Folders\Year 13 Computing\2006 Class Work\Computing\Flash\Flash
Exam Movie.fla (\- 2006 Folders\Year 13 Computing\2006 Class
Work\Computing Wunger\Flash\))

2007-08-06 21:48:54 Backup aborted (Call timed out: server did not
respond after 2 milliseconds opening remote file \- 2006
Folders\Year 13 Computing\2006 Class Work\Computing\Flash\Flash Exam
Movie.fla (\- 2006 Folders\Year 13 Computing\2006 Class Work\Computing
Wunger\Flash\))
2007-08-06 21:48:54 Saved partial dump 0
>>

Can you increase the Timeout to something like 9? that's what I do.  

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (aborted by signal=PIPE)

[John Villalovos]

Just a thought.  Maybe that host's rsync has gotten updated and you
are not yet using the "-D" flag in an rsync backup.  The 2.1.2pl2 diff
file can be applied to 2.1.2.tar.gz and will fix that issue.

I know I had that problem myself.

John

On 7/12/06, Nils Breunese (Lemonbit Internet) <[EMAIL PROTECTED]> wrote:
> I wrote:
>
> > I wrote:
> >
> >> I'm getting this error for one of my hosts. I found the nightly run
> >> hadn't succesfully backed up this host but when I ran the incremental
> >> again I got the error again:
> >>
> >> Got fatal error during xfer (aborted by signal=PIPE)
> >>
> >> Any idea what could be wrong?
> >
> > I started the incremental another time and this time it worked.
>
> I still get a daily e-mail telling me that some of my hosts
> (sometimes only one, not always the same hosts) have had errors:
>
> The following hosts had an error that is probably caused by a
> misconfiguration.  Please fix these hosts:
>   -  (aborted by signal=PIPE)
>
> What is the cause of signal=PIPE? What configuration options should I
> be looking at?
>
> Nils Breunese.
>
>
>
>
> -
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/backuppc-users
> http://backuppc.sourceforge.net/
>


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (aborted by signal=PIPE)

[Nils Breunese (Lemonbit Internet)]

I wrote:

> I wrote:
>
>> I'm getting this error for one of my hosts. I found the nightly run
>> hadn't succesfully backed up this host but when I ran the incremental
>> again I got the error again:
>>
>> Got fatal error during xfer (aborted by signal=PIPE)
>>
>> Any idea what could be wrong?
>
> I started the incremental another time and this time it worked.

I still get a daily e-mail telling me that some of my hosts  
(sometimes only one, not always the same hosts) have had errors:

The following hosts had an error that is probably caused by a
misconfiguration.  Please fix these hosts:
  -  (aborted by signal=PIPE)

What is the cause of signal=PIPE? What configuration options should I  
be looking at?

Nils Breunese.




-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer (aborted by signal=PIPE)

[Nils Breunese (Lemonbit Internet)]

I wrote:

> I'm getting this error for one of my hosts. I found the nightly run
> hadn't succesfully backed up this host but when I ran the incremental
> again I got the error again:
>
> Got fatal error during xfer (aborted by signal=PIPE)
>
> Any idea what could be wrong?

I started the incremental another time and this time it worked.

Nils Breunese.



___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer

[Craig Barratt]

"Paul S. Gumerman" writes:

> This one is easy --- I fixed this on my installation just the other day.
> 
> Change this conf file setting:
> 
> $Conf{BackupZeroFilesIsFatal} = 1;
> 
> to
> 
> $Conf{BackupZeroFilesIsFatal} = 0;

That's right.  However, the reason that the default is fatal is
that it really might be a problem that no files were dumped:

2005-10-16 15:16:56 full backup started for directory /var/mail
2005-10-16 15:16:58 Got fatal error during xfer (No files dumped for share 
/var/mail)

Normally /var/mail should have files.  Or perhaps it is a symlink
somewhere else.  You should look at the XferLOG file to see exactly
what commands are being run and why BackupPC thinks there are no
files to be backed up.

Craig


---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer

[Paul S. Gumerman]

This one is easy --- I fixed this on my installation just the other day.

Change this conf file setting:
$Conf{BackupZeroFilesIsFatal} = 1;

to

$Conf{BackupZeroFilesIsFatal} = 0;


Paul






Tormod Omholt-Jensen wrote:
I'm
running backuppc, but I'm experiencing a couple of problems. When I 
run a full backup for a remote server, the backup fails for one of the 
directories. I can not see any reason for this to happen, and the
error  message doesn't describe the error very well. Can anyone give me
a hint?
  
  
  
Tormod
  
  
  
CONFIG:
  

  
Conf{XferMethod} = 'tar';
  
  
$Conf{TarShareName} = ['/etc', '/var/spool',
'/var/lib/postgres/backup',  '/var/mail'];
  
  
  
LOG:
  
-
  
2005-10-16 15:15:59 full backup started for directory /etc
  
2005-10-16 15:16:28 full backup started for directory /var/spool
  
2005-10-16 15:16:28 full backup started for directory 
/var/lib/postgres/backup
  
2005-10-16 15:16:56 full backup started for directory /var/mail
  
2005-10-16 15:16:58 Got fatal error during xfer (No files dumped for
share  /var/mail)
  
2005-10-16 15:17:03 Backup aborted (No files dumped for share
/var/mail)
  
2005-10-16 15:17:03 Saved partial dump 21
  
  
  
  
---
  
This SF.Net email is sponsored by:
  
Power Architecture Resource Center: Free content, downloads,
discussions,
  
and more. http://solutions.newsforge.com/ibmarch.tmpl
  
___
  
BackupPC-users mailing list
  
BackupPC-users@lists.sourceforge.net
  
https://lists.sourceforge.net/lists/listinfo/backuppc-users
  
http://backuppc.sourceforge.net/
  
  
  

Re: [BackupPC-users] Got fatal error during xfer

[mna.news]

Le mercredi 24 Août 2005 13:34, Craig Barratt a écrit :
> Tony Del Porto writes:
> > On Aug 4, 2005, at 7:32 PM, Craig Barratt wrote:
> > > Tony Del Porto writes:
>
> The problem is that there is no --totals argument to tar, and
> BackupPC expects to see the output from the --totals at the
> very end of the archive.  Does xtar support --totals?
>
> Craig
>

i run in the same behaviour this days using backuppc 2.12 and gnutar to backup 
somes files on AIX (4.x and 5.x) systems.

I confirm the diagnostics of Craig about the --totals option, and i put here 
somes tricks than can help :

1 / 

the option --totals placed at the end of the commande ligne after the 
--exclude command does not works on AIX system ( gnutar version tar (GNU tar) 
1.15.1 )
so you have to modify the config.pl to move the --totals option before 
--exclude like this :

$Conf{TarClientCmd} = '$sshPath -q -x -n -l root $host'
. ' $tarPath -c -v --totals -f - -C $shareName+ ;'

2 /

am using this software in France and then there is trouble parsing the result 
of the commande due to translation and "Locale" parameter


here is "french output"  of tar command :
/usr/local/bin/tar  -c -v -f mna.tar --totals Install*
InstallApache.sh
InstallAppliTomcat.sh
InstallTomcat.sh
Nombre total d'octets écrits: 30720 (30KiB, 392KiB/s)

so you can have to set the locale correctly to obtain correct answer, you do 
this by adding something like LANGUAGE=EN before the tar commande so the 
final $Conf{TarClientCmd} is :

$Conf{TarClientCmd} = '$sshPath -q -x -n -l root $host'
. ' LANGUAGE=EN $tarPath -c -v --totals -f - '
. ' -C $shareName+ ;'

hope this can help anybody and perhaps Craig can add those tricks to the FAQ 
of BackupPC online documentation.

bye.
Michael.
 
-- 
Quand quelqu'un dit qu'il est réaliste,
c'est qu'il s'apprête à faire quelque chose dont il a sacrement honte.
Sydney Harrys


---
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer

[Craig Barratt]

Tony Del Porto writes:

> On Aug 4, 2005, at 7:32 PM, Craig Barratt wrote:
> 
> > Tony Del Porto writes:
> >
> >> I'm testing BackupPC with a couple of machines and full backups don't
> >> complete. The test machines are a Redhad 7.2 machine and an OS 10.3.9
> >> machine. Both are using tar (or xtar) and ssh.  The errors in the Xfer
> >> log are basically the same:
> >>
> >> Redhat 7.2
> >> ...
> >>pool   l 777   0/0   1 mount
> >>create   600   0/0 574 ntp.keys.3204915872
> >>pool 600   0/0 574 ntp.keys.3204916062
> >>create   600   0/0 574 ntp.keys.3204916081
> >>pool 600   0/0  29 .bash_history
> >>create d 755   0/0   0 initrd
> >> tarExtract: Done: 0 errors, 224692 filesExist, 8825497672 sizeExist,
> >> 3116053660 sizeExistComp, 252541 filesTotal, 9321259784 sizeTotal
> >> Got fatal error during xfer (./initrd/)
> >> Backup aborted (./initrd/)
> >>
> > OS 10.3.9 + xtar
> >> ...
> >>pool 644501/20   25141
> >> Users/tony/Sites/tony/socal/yurt_views.jpg
> >>pool 644501/20 1035594 Users/tony/Sites/tony/socal.zip
> >>pool 644501/203265 
> >> Users/tony/Sites/tony/thelist.html
> >>pool 644501/20  815874 Users/tony/tonybackup.tgz
> >> tarExtract: Done: 0 errors, 21624 filesExist, 2952991765 sizeExist,
> >> 2374350093 sizeExistComp, 21666 filesTotal, 2963158042 sizeTotal
> >> Got fatal error during xfer (./Users/tony/tonybackup.tgz)
> >> Backup aborted (./Users/tony/tonybackup.tgz)
> >
> > Is there a real error shown in the log file?  If not, it could
> > just be a problem with the exit status of tar on the mac.
> > Perhaps it's a minor error (eg: can't read a file) that
> > causes an exit status that makes BackupPC think the backup
> > failed.
> >
> > You could run this command manually (substituting the variables):
> >
> > $sshPath -q -x -n -l root $host $tarPath -c -v -f - -C / > 
> > /dev/null
> >
> > and then print the exit status (echo $status in tcsh).
> >
> > Craig
> 
> Craig,
> 
> Thanks a lot for your response. I've been otherwise occupied and 
> haven't had time to explore the above until recently.
> 
> I limited the backup to a very small set of files for testing and ran 
> the ssh'd tar command both manually per your suggestion and via 
> backuppc:
> 
> 
> [backuppc]$ sudo -u backuppc /usr/bin/ssh -q -x -n -l root lucca 
> /usr/bin/xtar -c -v -f - -C / --exclude=.Trash --exclude=./Trash 
> --exclude=./automount --exclude=./Network 
> --exclude=./private/var/automount --exclude=./private/var/run 
> --exclude=./private/var/vm --exclude=./private/var/tmp 
> --exclude=./private/tmp --exclude=Caches --exclude=CachedMessages 
> ./Users/tony/Sites/tony > /dev/null
> ./Users/tony/Sites/tony/
> ./Users/tony/Sites/tony/.DS_Store
> ./Users/tony/Sites/tony/.rsrc/.DS_Store
> ./Users/tony/Sites/tony/bookmark.htm
> ./Users/tony/Sites/tony/condo/
> ./Users/tony/Sites/tony/condo/.DS_Store
> 
> ./Users/tony/Sites/tony/socal/yurt_skylights.jpg
> ./Users/tony/Sites/tony/socal/yurt_view.jpg
> ./Users/tony/Sites/tony/socal/yurt_views.jpg
> ./Users/tony/Sites/tony/socal.zip
> ./Users/tony/Sites/tony/thelist.html
> [backuppc]$ echo $?
> 0
> 
> Contents of file /usr/local/backuppc/data/pc/lucca/XferLOG.0.z, 
> modified 2005-08-18 16:00:20
> 
> Running: /usr/bin/ssh -q -x -n -l root lucca /usr/bin/xtar -c -v -f - 
> -C / --exclude=.Trash --exclude=./Trash --exclude=./automount 
> --exclude=./Network --exclude=./private/var/automount 
> --exclude=./private/var/run --exclude=./private/var/vm 
> --exclude=./private/var/tmp --exclude=./private/tmp --exclude=Caches 
> --exclude=CachedMessages ./Users/tony/Sites/tony
> Xfer PIDs are now 52678,52677
>create d 755501/20   0 Users/tony/Sites/tony
>pool 755501/20   12292 Users/tony/Sites/tony/.DS_Store
>pool 755501/20  64 
> Users/tony/Sites/tony/.rsrc/.DS_Store
>pool 644501/20   37396 Users/tony/Sites/tony/bookmark.htm
>create d 755501/20   0 Users/tony/Sites/tony/condo
>pool 644501/20   12292 
> Users/tony/Sites/tony/condo/.DS_Store
> ...
>pool 644501/20  117042 
> Users/tony/Sites/tony/socal/yurt_view.jpg
>pool 644501/20   25141 
> Users/tony/Sites/tony/socal/yurt_views.jpg
>pool 644501/20 1035594 Users/tony/Sites/tony/socal.zip
>pool 644501/203265 Users/tony/Sites/tony/thelist.html
> tarExtract: Done: 0 errors, 289 filesExist, 21440784 sizeExist, 
> 20746069 sizeExistComp, 289 filesTotal, 21440784 sizeTotal
> Got fatal error during xfer (./Users/tony/Sites/tony/thelist.html)
> Backup aborted (./Users/tony/Sites/tony/thelist.html)
> 
> LOG:
> 2005-08-18 16:00:01 full backup started for directory /
> 2005-08-18 16:00:15 Got fatal error during xfer 
> (./Users/tony/Sites/tony/thelist.html)
> 2005-08-18 16:00:20 Backup aborted 
> (./Users/

Re: [BackupPC-users] Got fatal error during xfer

[Tony Del Porto]

On Aug 18, 2005, at 5:13 PM, Sam Przyswa wrote:

Try to ping the backuped machine during the backup from your backup 
machine, I have a similar problem with rsync over ssh too.


I got echo ping about 5000/7000ms and then the backup failed.


That doesn't appear to be the problem in my case. I ran ping from the 
backup server to the machine being backed up during a backup of the 
same small set of files and saw no latency or packet loss:


--- lucca.usenix.org ping statistics ---
73 packets transmitted, 73 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.243/0.377/1.582/0.157 ms

and the backup did fail in the same way as previous attempts.

Thanks for the suggestion though!

Regards,

Tony



---
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Re: [BackupPC-users] Got fatal error during xfer

[Tony Del Porto]

On Aug 4, 2005, at 7:32 PM, Craig Barratt wrote:


Tony Del Porto writes:


I'm testing BackupPC with a couple of machines and full backups don't
complete. The test machines are a Redhad 7.2 machine and an OS 10.3.9
machine. Both are using tar (or xtar) and ssh.  The errors in the Xfer
log are basically the same:

Redhat 7.2
...
   pool   l 777   0/0   1 mount
   create   600   0/0 574 ntp.keys.3204915872
   pool 600   0/0 574 ntp.keys.3204916062
   create   600   0/0 574 ntp.keys.3204916081
   pool 600   0/0  29 .bash_history
   create d 755   0/0   0 initrd
tarExtract: Done: 0 errors, 224692 filesExist, 8825497672 sizeExist,
3116053660 sizeExistComp, 252541 filesTotal, 9321259784 sizeTotal
Got fatal error during xfer (./initrd/)
Backup aborted (./initrd/)


OS 10.3.9 + xtar

...
   pool 644501/20   25141
Users/tony/Sites/tony/socal/yurt_views.jpg
   pool 644501/20 1035594 Users/tony/Sites/tony/socal.zip
   pool 644501/203265 
Users/tony/Sites/tony/thelist.html

   pool 644501/20  815874 Users/tony/tonybackup.tgz
tarExtract: Done: 0 errors, 21624 filesExist, 2952991765 sizeExist,
2374350093 sizeExistComp, 21666 filesTotal, 2963158042 sizeTotal
Got fatal error during xfer (./Users/tony/tonybackup.tgz)
Backup aborted (./Users/tony/tonybackup.tgz)


Is there a real error shown in the log file?  If not, it could
just be a problem with the exit status of tar on the mac.
Perhaps it's a minor error (eg: can't read a file) that
causes an exit status that makes BackupPC think the backup
failed.

You could run this command manually (substituting the variables):

$sshPath -q -x -n -l root $host $tarPath -c -v -f - -C / > 
/dev/null


and then print the exit status (echo $status in tcsh).

Craig


Craig,

Thanks a lot for your response. I've been otherwise occupied and 
haven't had time to explore the above until recently.


I limited the backup to a very small set of files for testing and ran 
the ssh'd tar command both manually per your suggestion and via 
backuppc:



[backuppc]$ sudo -u backuppc /usr/bin/ssh -q -x -n -l root lucca 
/usr/bin/xtar -c -v -f - -C / --exclude=.Trash --exclude=./Trash 
--exclude=./automount --exclude=./Network 
--exclude=./private/var/automount --exclude=./private/var/run 
--exclude=./private/var/vm --exclude=./private/var/tmp 
--exclude=./private/tmp --exclude=Caches --exclude=CachedMessages 
./Users/tony/Sites/tony > /dev/null

./Users/tony/Sites/tony/
./Users/tony/Sites/tony/.DS_Store
./Users/tony/Sites/tony/.rsrc/.DS_Store
./Users/tony/Sites/tony/bookmark.htm
./Users/tony/Sites/tony/condo/
./Users/tony/Sites/tony/condo/.DS_Store

./Users/tony/Sites/tony/socal/yurt_skylights.jpg
./Users/tony/Sites/tony/socal/yurt_view.jpg
./Users/tony/Sites/tony/socal/yurt_views.jpg
./Users/tony/Sites/tony/socal.zip
./Users/tony/Sites/tony/thelist.html
[backuppc]$ echo $?
0

Contents of file /usr/local/backuppc/data/pc/lucca/XferLOG.0.z, 
modified 2005-08-18 16:00:20


Running: /usr/bin/ssh -q -x -n -l root lucca /usr/bin/xtar -c -v -f - 
-C / --exclude=.Trash --exclude=./Trash --exclude=./automount 
--exclude=./Network --exclude=./private/var/automount 
--exclude=./private/var/run --exclude=./private/var/vm 
--exclude=./private/var/tmp --exclude=./private/tmp --exclude=Caches 
--exclude=CachedMessages ./Users/tony/Sites/tony

Xfer PIDs are now 52678,52677
  create d 755501/20   0 Users/tony/Sites/tony
  pool 755501/20   12292 Users/tony/Sites/tony/.DS_Store
  pool 755501/20  64 
Users/tony/Sites/tony/.rsrc/.DS_Store

  pool 644501/20   37396 Users/tony/Sites/tony/bookmark.htm
  create d 755501/20   0 Users/tony/Sites/tony/condo
  pool 644501/20   12292 
Users/tony/Sites/tony/condo/.DS_Store

...
  pool 644501/20  117042 
Users/tony/Sites/tony/socal/yurt_view.jpg
  pool 644501/20   25141 
Users/tony/Sites/tony/socal/yurt_views.jpg

  pool 644501/20 1035594 Users/tony/Sites/tony/socal.zip
  pool 644501/203265 Users/tony/Sites/tony/thelist.html
tarExtract: Done: 0 errors, 289 filesExist, 21440784 sizeExist, 
20746069 sizeExistComp, 289 filesTotal, 21440784 sizeTotal

Got fatal error during xfer (./Users/tony/Sites/tony/thelist.html)
Backup aborted (./Users/tony/Sites/tony/thelist.html)

LOG:
2005-08-18 16:00:01 full backup started for directory /
2005-08-18 16:00:15 Got fatal error during xfer 
(./Users/tony/Sites/tony/thelist.html)
2005-08-18 16:00:20 Backup aborted 
(./Users/tony/Sites/tony/thelist.html)

2005-08-18 16:00:20 Saved partial dump 0

So something is failing, but it doesn't appear to be tar. I can browse 
the backup using the web interface and everything appears to be there 
as the Xfer log indicates. Is there anything else that backuppc updates 
upon a successful backup? A file with bad permissions perhaps? Any 
other idea

Re: [BackupPC-users] Got fatal error during xfer

[Craig Barratt]

Tony Del Porto writes:

> I'm testing BackupPC with a couple of machines and full backups don't 
> complete. The test machines are a Redhad 7.2 machine and an OS 10.3.9 
> machine. Both are using tar (or xtar) and ssh.  The errors in the Xfer 
> log are basically the same:
> 
> Redhat 7.2
> ...
>pool   l 777   0/0   1 mount
>create   600   0/0 574 ntp.keys.3204915872
>pool 600   0/0 574 ntp.keys.3204916062
>create   600   0/0 574 ntp.keys.3204916081
>pool 600   0/0  29 .bash_history
>create d 755   0/0   0 initrd
> tarExtract: Done: 0 errors, 224692 filesExist, 8825497672 sizeExist, 
> 3116053660 sizeExistComp, 252541 filesTotal, 9321259784 sizeTotal
> Got fatal error during xfer (./initrd/)
> Backup aborted (./initrd/)
> 
OS 10.3.9 + xtar
> ...
>pool 644501/20   25141 
> Users/tony/Sites/tony/socal/yurt_views.jpg
>pool 644501/20 1035594 Users/tony/Sites/tony/socal.zip
>pool 644501/203265 Users/tony/Sites/tony/thelist.html
>pool 644501/20  815874 Users/tony/tonybackup.tgz
> tarExtract: Done: 0 errors, 21624 filesExist, 2952991765 sizeExist, 
> 2374350093 sizeExistComp, 21666 filesTotal, 2963158042 sizeTotal
> Got fatal error during xfer (./Users/tony/tonybackup.tgz)
> Backup aborted (./Users/tony/tonybackup.tgz)

Is there a real error shown in the log file?  If not, it could
just be a problem with the exit status of tar on the mac.
Perhaps it's a minor error (eg: can't read a file) that
causes an exit status that makes BackupPC think the backup
failed.

You could run this command manually (substituting the variables):

$sshPath -q -x -n -l root $host $tarPath -c -v -f - -C / > /dev/null

and then print the exit status (echo $status in tcsh).

Craig


---
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/