bug-cfengine
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cfengine 2.0.6 large file copy failure


From: Mark . Burgess
Subject: Re: cfengine 2.0.6 large file copy failure
Date: Thu, 24 Jul 2003 08:59:28 +0200 (MEST)

Jeremy, this has nothing to do with the file size as such. If the
error is "can't stat" that means the file appears not to be available
to cfengine. The error says that access was denied. Have you "admit"ed
the file in cfserd.conf?

You can try running client and daemon with -d2 flag to seeexactly
what is going on.


M


On 23 Jul, Jeremy 'Circ' Charles wrote:
> I seem to be having a problem getting cfengine 2.0.6 to copy a file that
> is 2220883968 bytes (2.0684 GB) in size.  Does cfengine have a problem
> with files over 2G?
> 
> I don't see any mention of this in the changelog that is published on
> the web site.
> 
> Here's the output I get on the machine running cfagent:
> 
> =-=-=-=
> gophers:: Server returned error:  Host authentication failed. Did you
> forget the domain name?
> gophers:: (Can't stat /clu/lc-cfmaster2/epic/trn/app/CACHE.DAT)
> =-=-=-=
> 
> Here's what I get in the syslog on the machine running cfservd:
> 
> =-=-=-=
> Jul 23 19:28:18 sunni cfservd[12292]: Host authorization/authentication
> failed or access denied
> Jul 23 19:28:18 sunni cfservd[12292]: From
> (host=gophers.epicsys.com,user=root,ip=172.17.1.185)
> Jul 23 19:28:19 sunni cfservd[12292]:  ID from connecting host: (SYNCH
> 1059006500 STAT /clu/lc-cfmaster2/epic/trn/app/CACHE.DAT)
> =-=-=-=
> 
> Note that the same cfagent run copies a truckload of other files just
> fine, but none of them are over 2G in size.
> 
> 
> 
> 
> _______________________________________________
> Bug-cfengine mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-cfengine



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Work: +47 22453272            Email:  address@hidden
Fax : +47 22453205            WWW  :  http://www.iu.hio.no/~mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~





reply via email to

[Prev in Thread] Current Thread [Next in Thread]