Re: Error: gtar: uid_t value 4294967294 too large (max=16777215)

2001-03-23 Thread Jonathan Dill

"John R. Jackson" wrote:
> 
> >I checked the /etc/passwd and /etc/group files which had user/group
> >nobody with the id of 4294967294.  After I changed that ...
> 
> Ummm, you changed the gid and uid of "nobody"?  That was probably kind
> of rash.  There are things floating around that know about that and
> expect a specific value.  Like NFS :-).

Yes, for example we have a piece of lab equipment from England which
requires an Acorn computer.  If you don't have other Acorn devices on
the network, usually the only way to print and share files is via PCNFS,
and to get that to work correctly I had to set UID nobody to some such
value as that, and changing the value would "break" printing and file
sharing from the Acorn.

-- 
"Jonathan F. Dill" ([EMAIL PROTECTED])



Re: Error: gtar: uid_t value 4294967294 too large (max=16777215)

2001-03-23 Thread John R. Jackson

>I checked the /etc/passwd and /etc/group files which had user/group
>nobody with the id of 4294967294.  After I changed that ...

Ummm, you changed the gid and uid of "nobody"?  That was probably kind
of rash.  There are things floating around that know about that and
expect a specific value.  Like NFS :-).

>Terry

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]



Re: Error: gtar: uid_t value 4294967294 too large (max=16777215)

2001-03-23 Thread Terry Koyama

Thanks to both John and Jonathan!!!

I checked the /etc/passwd and /etc/group files which had user/group
nobody with the id of 4294967294.  After I changed that, I ran amdump
and still got the same error.  I found a directory with the uid/gid as
4294967294.  When I changed that, no more errors!  

Thanks again,

Terry

"John R. Jackson" wrote:
> 
> >Anyone know what's going on with runtar?
> 
> Runtar is a simple wrapper around GNU tar.  It's only point in life is
> to be setuid-root so it can pass that privilege on to GNU tar.  It's
> GNU tar that's having trouble with the unsigned long uid_t on AIX.
> 
> Actually, that's not even quite true.  The tar header format has room
> for 8 *octal* characters in the uid field.  8**8 -> 16777215.
> 
> The tar header extension (ustar) supports a login *name* rather than uid,
> so there might be hope.
> 
> I could not find this message in the tar sources I looked at.
> What version of GNU tar are you using?  /usr/local/bin/tar --version
> 
> You might also do this on hendrix:
> 
>   find /usr -xdev -user 4294967294 -print
> 
> and see what showed up on your system all of the sudden.  Note that
> 4294967294 is probably also known as -2.
> 
> "If it hurts when you do that, don't do that."  :-)
> 
> >Terry
> 
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

-- 
CONFIDENTIAL and PROPRIETARY
COPYRIGHT NOEMIX INC, SAN DIEGO, CA 2001



Re: Error: gtar: uid_t value 4294967294 too large (max=16777215)

2001-03-23 Thread John R. Jackson

>Anyone know what's going on with runtar?  

Runtar is a simple wrapper around GNU tar.  It's only point in life is
to be setuid-root so it can pass that privilege on to GNU tar.  It's
GNU tar that's having trouble with the unsigned long uid_t on AIX.

Actually, that's not even quite true.  The tar header format has room
for 8 *octal* characters in the uid field.  8**8 -> 16777215.

The tar header extension (ustar) supports a login *name* rather than uid,
so there might be hope.

I could not find this message in the tar sources I looked at.
What version of GNU tar are you using?  /usr/local/bin/tar --version

You might also do this on hendrix:

  find /usr -xdev -user 4294967294 -print

and see what showed up on your system all of the sudden.  Note that
4294967294 is probably also known as -2.

"If it hurts when you do that, don't do that."  :-)

>Terry

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]



Re: Error: gtar: uid_t value 4294967294 too large (max=16777215)

2001-03-23 Thread Jonathan Dill

Hi Terry,

I have seen this problem with Unix computers running either Samba,
Appletalk sharing, or PCNFS.  Something, possibly a misconfigured Samba,
is probably using that UID as the "nobody" UID.  If you're not using
Samba for anything and it's just installed and "turned on" I think it
would be a good idea to turn it off as it could be a security liability,
plus that may take care of your UID problem.  You also might try
upgrading to tar-1.13.19 if you haven't already--that seems to clear up
some problems where an exit code should be returned to indicate a
"warning" rather than a total "failure."

Terry Koyama wrote:
> I ran amanda last night and received the below report.  The client with
> the error (hendrix) is an AIX machine running amanda v2.4.2p1.  I tried
> checking out the UID's in /usr but didn't find anything out of the
> ordinary.
> 
> I've also included  sendback.debug and sendsize.debug to see the actual
> command that was executed.  The syntax of runtar looks kinda funky (to
> me anyway) but seems to run fine on all the other clients.  Plus, I
> don't have a clear understanding of how runtar and gnutar are related.

-- 
"Jonathan F. Dill" ([EMAIL PROTECTED])
CARB Systems and Network Administrator
Home Page:  http://www.umbi.umd.edu/~dill



Error: gtar: uid_t value 4294967294 too large (max=16777215)

2001-03-23 Thread Terry Koyama

I ran amanda last night and received the below report.  The client with
the error (hendrix) is an AIX machine running amanda v2.4.2p1.  I tried
checking out the UID's in /usr but didn't find anything out of the
ordinary.

I've also included  sendback.debug and sendsize.debug to see the actual
command that was executed.  The syntax of runtar looks kinda funky (to
me anyway) but seems to run fine on all the other clients.  Plus, I
don't have a clear understanding of how runtar and gnutar are related.  

Anyone know what's going on with runtar?  

Thanks,

Terry

--
DAILY REPORT


These dumps were to tape noemix-daily01.
The next tape Amanda expects to use is: noemix-daily02.

FAILURE AND STRANGE DUMP SUMMARY:
  hendrix.no /usr lev 0 FAILED [/usr/local/bin/tar returned 2]


STATISTICS:
  Total   Full  Daily
      
Estimate Time (hrs:min)0:01
Run Time (hrs:min) 2:44
Dump Time (hrs:min)1:04   1:04   0:00
Output Size (meg)9237.9 9237.90.0
Original Size (meg)  9237.9 9237.90.0
Avg Compressed Size (%) -- -- -- 
Filesystems Dumped   22 22  0
Avg Dump Rate (k/s)  2464.8 2464.8-- 

Tape Time (hrs:min)2:29   2:29   0:00
Tape Size (meg)  9238.6 9238.60.0
Tape Used (%)  90.3   90.30.0
Filesystems Taped22 22  0
Avg Tp Write Rate (k/s)  1060.2 1060.2-- 


FAILED AND STRANGE DUMP DETAILS:

/-- hendrix.no /usr lev 0 FAILED [/usr/local/bin/tar returned 2]
sendbackup: start [hendrix.noemix.com:/usr level 0]
sendbackup: info BACKUP=/usr/local/bin/tar
sendbackup: info RECOVER_CMD=/usr/local/bin/tar -f... -
sendbackup: info end
? gtar: uid_t value 4294967294 too large (max=16777215)
? gtar: gid_t value 4294967294 too large (max=16777215)
? gtar: uid_t value 4294967294 too large (max=16777215)
? gtar: gid_t value 4294967294 too large (max=16777215)
? gtar: uid_t value 4294967294 too large (max=16777215)
? gtar: gid_t value 4294967294 too large (max=16777215)
(NOTE:  ...this goes on for a while...)
? gtar: uid_t value 4294967294 too large (max=16777215)
? gtar: gid_t value 4294967294 too large (max=16777215)
? gtar: uid_t value 4294967294 too large (max=16777215)
? gtar: gid_t value 4294967294 too large (max=16777215)
? gtar: uid_t value 4294967294 too large (max=16777215)
? gtar: gid_t value 4294967294 too large (max=16777215)

| Total bytes written: 851374080
? gtar: Error exit delayed from previous errors
sendbackup: error [/usr/local/bin/tar returned 2]
\


NOTES:
  planner: Adding new disk vedder.noemix.com:/home.
  planner: Adding new disk vedder.noemix.com:/etc.
  planner: Adding new disk vedder.noemix.com:/var/www.
  planner: Adding new disk vedder.noemix.com:/usr/local/cvs-noemix.
  planner: Adding new disk vedder.noemix.com:/usr/local/cvs-public.
  planner: Adding new disk vedder.noemix.com:/var/lib/mailman.
  planner: Adding new disk vedder.noemix.com:/var/lib/mysql.
  planner: Adding new disk vedder.noemix.com:/var/mail.
  planner: Adding new disk marley.noemix.com:/home.
  planner: Adding new disk marley.noemix.com:/etc.
  planner: Adding new disk keenan.noemix.com:/space/home.
  planner: Adding new disk keenan.noemix.com:/etc.
  planner: Adding new disk keenan.noemix.com:/usr/local/lsf/mnt/conf.
  planner: Adding new disk keenan.noemix.com:/usr/local/flexlm.
  planner: Adding new disk
keenan.noemix.com:/usr/local/share/gridware/default.
  planner: Adding new disk plant.noemix.com:/space/home.
  planner: Adding new disk plant.noemix.com:/etc.
  planner: Adding new disk hendrix.noemix.com:/home.
  planner: Adding new disk hendrix.noemix.com:/.
  planner: Adding new disk hendrix.noemix.com:/usr.
  planner: Adding new disk hendrix.noemix.com:/var.
  planner: Adding new disk vedder.noemix.com://ozzy.noemix.com/noemix.
  planner: Adding new disk vedder.noemix.com://ozzy.noemix.com/ximeon.
  taper: tape noemix-daily01 kb 9460320 fm 22 [OK]


DUMP SUMMARY:
 DUMPER STATSTAPER STATS 
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS 
KB/s
-- -

hendrix.noem /   04576   4576   --0:041023.5  
0:041173.4
hendrix.noem /home   0  170880 170880   --0:592877.7   2:54
984.0
hendrix.noem /usr0 FAILED
---
hendrix.noem /var02112   2112   --0:03 761.8   0:02
861.1
keenan.noemi /etc02368   2368   --0:011747.5  
0:021074.2
keenan.noemi /space/home 0 21468802146880   --   16:562113.6 
28:501240.6
keenan.noemi -cal/flexlm 0  32 32   --0:00 214.1   0:02 
41.5
keenan.noemi -f/mnt/conf 0 128128   --0:00 405.6   0:02 
87.5
keenan.noemi -re/default 01152