I used "scp" because we have ftp turned off just about everywhere. Which leads me back to - how does clientupdate transfer the tar file?

Smith, Jim wrote:

If you transferred the file via FTP, did you do so in binary mode?

-----Original Message----- From: Jay Brislin [mailto:brislin at bc.edu] Sent: Monday, April 23, 2007 1:35 PM To: hobbit at hswn.dk Subject: [hobbit] AIX clientupdate problem

I keep getting these error messages from clientupdate failing on AIX 5.2

tar: tape read error: unexpected EOF 2007-04-23 14:01:09 Upgrade failed, tar exited with status 256 tar: tape read error: unexpected EOF 2007-04-23 14:06:10 Upgrade failed, tar exited with status 256 tar: tape read error: unexpected EOF 2007-04-23 14:11:12 Upgrade failed, tar exited with status 256

I can't really tell what clientupdate is doing and I haven't been successful tracking down the problem. Has anyone seen this?

I do have clientupdate working on a couple of pilot Linux systems and it looks great over there.

Jay

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

NOTICE: This email contains confidential or proprietary information which may be legally privileged. It is intended only for the named recipient(s). If an addressing error has misdirected the email, please notify the author by replying to this message. If you are not the named recipient, you are not authorized to use, disclose, distribute, copy, print or rely on this email, and should immediately delete it from your computer system.

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

-- Jay

I *believe* that clientupdate uses its own method for transferring the file.

-----Original Message----- From: martin roby [mailto:stonepound at gmail.com] Sent: Tuesday, April 24, 2007 8:49 AM To: hobbit at hswn.dk Subject: Re: [hobbit] AIX clientupdate problem

Jay,

Scp should work on the tar file. Because you get the message about the unexpected end of the tar file it must be in binary format and you must have some of the file. Check the original source machine using tar -tf filename. If it is compressed, uncompress it first to eliminate any confusion. If it works on the source machine, check the sizes of the file on the source machine and the destination. ( ls -l or du -sk filename ) If the sizes are different check for a full filesystem using df -k and check the permissions in the directory where you are sending the file.

If you can't get it run scp with the -v option and email me the results.

Regards, martin roby

On 4/24/07, Jay Brislin <brislin at bc.edu> wrote:

I used "scp" because we have ftp turned off just about everywhere. Which leads me back to - how does clientupdate transfer the tar file?

Smith, Jim wrote:

...

If you transferred the file via FTP, did you do so in binary mode?

-----Original Message----- From: Jay Brislin [mailto:brislin at bc.edu] Sent: Monday, April 23, 2007 1:35 PM To: hobbit at hswn.dk Subject: [hobbit] AIX clientupdate problem

I keep getting these error messages from clientupdate failing on AIX

...

5.2

tar: tape read error: unexpected EOF 2007-04-23 14:01:09 Upgrade failed, tar exited with status 256 tar: tape read error: unexpected EOF 2007-04-23 14:06:10 Upgrade failed, tar exited with status 256 tar: tape read error: unexpected EOF 2007-04-23 14:11:12 Upgrade failed, tar exited with status 256

I can't really tell what clientupdate is doing and I haven't been successful tracking down the problem. Has anyone seen this?

I do have clientupdate working on a couple of pilot Linux systems and it looks great over there.

Jay

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

NOTICE: This email contains confidential or proprietary information which may be legally privileged. It is intended only for the named recipient(s). If an addressing error has misdirected the email, please notify the author by replying to this message. If you are not the named recipient, you are not authorized to use, disclose, distribute, copy, print or rely on this email, and should immediately delete it from your computer system.

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

-- Jay

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

No, look at the "known issues" list for Hobbit 4.2 -- clientupdate does not work right for AIX. You are probably doing nothing wrong.

GLH

-----Original Message----- From: Jay Brislin [mailto:brislin at bc.edu] Sent: Tuesday, April 24, 2007 10:28 AM To: hobbit at hswn.dk Subject: Re: [hobbit] AIX clientupdate problem

I meant to clarify that I used scp to copy it to "~/hobbit/server/downloads". I think you're right that clientupdate uses it's own method of transfer. Maybe my AIX systems aren't set up the way they should be to allow clientupdate to transfer the tar files properly.

Hubbard, Greg L wrote:

I *believe* that clientupdate uses its own method for transferring the

file.

-----Original Message----- From: martin roby [mailto:stonepound at gmail.com] Sent: Tuesday, April 24, 2007 8:49 AM To: hobbit at hswn.dk Subject: Re: [hobbit] AIX clientupdate problem

Jay,

Scp should work on the tar file. Because you get the message about the unexpected end of the tar file it must be in binary format and you

must have some of the file. Check the original source machine using tar -tf filename. If it is compressed, uncompress it first to eliminate any confusion. If it works on the source machine, check the sizes of the file on the source machine and the destination. ( ls -l or du -sk filename ) If the sizes are different check for a full filesystem using df -k and check the permissions in the directory where you are sending the file.

If you can't get it run scp with the -v option and email me the results.

Regards, martin roby

On 4/24/07, Jay Brislin <brislin at bc.edu> wrote:

...

I used "scp" because we have ftp turned off just about everywhere. Which leads me back to - how does clientupdate transfer the tar file?

Smith, Jim wrote:

...

If you transferred the file via FTP, did you do so in binary mode?

-----Original Message----- From: Jay Brislin [mailto:brislin at bc.edu] Sent: Monday, April 23, 2007 1:35 PM To: hobbit at hswn.dk Subject: [hobbit] AIX clientupdate problem

I keep getting these error messages from clientupdate failing on AIX

...

...

5.2

tar: tape read error: unexpected EOF 2007-04-23 14:01:09 Upgrade failed, tar exited with status 256 tar: tape read error: unexpected EOF 2007-04-23 14:06:10 Upgrade failed, tar exited with status 256 tar: tape read error: unexpected EOF 2007-04-23 14:11:12 Upgrade failed, tar exited with status 256

I can't really tell what clientupdate is doing and I haven't been successful tracking down the problem. Has anyone seen this?

I do have clientupdate working on a couple of pilot Linux systems and it looks great over there.

Jay

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

NOTICE: This email contains confidential or proprietary information which may be legally privileged. It is intended only for the named recipient(s). If an addressing error has misdirected the email, please

notify the author by replying to this message. If you are not the named recipient, you are not authorized to use, disclose, distribute, copy, print or rely on this email, and should immediately delete it from your computer system.

...

...

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

-- Jay

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

-- Jay

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk