Summary: advfsd **ERROR esnmp_init.c line 3268: Could not connect to master: Interrupted system call (fwd)

From: Steven Timm (timm@fnal.gov)
Date: Mon Jul 29 2002 - 13:34:11 EDT


Thanks to many including Dr. Tom Blinn. Summary is--dtadvfs is
main thing that is using advfsd and if you're not going to use
dtadvfs you can turn off advfsd. So I did, and the log file
stopped growing.

Steve Timm

------------------------------------------------------------------
Steven C. Timm (630) 840-8525 timm@fnal.gov http://home.fnal.gov/~timm/
Fermilab Computing Division/Operating Systems Support
Scientific Computing Support Group--Computing Farms Operations

> I have a log file on my system running 4.0g
> that is called
>
> /var/opt/advfsd/logs/advfsd
>
> which is about 263 MB big right now and growing, full of
> this error message:
>
> advfsd **ERROR esnmp_init.c line 3268: Could not connect to master:
> Interrupted system call
>
>
> Now--I suspect that this is failing because I turned off snmp on
> this system a couple of months ago. Two questions:
>
> 1) Does advfsd require snmp to be running to operate successfully?

Probably. The evidence you've gathered certainly points that way.

> 2) If I'm not going to ever run dtadvfs, does advfsd have to
> be running at all?

No, you don't need to run advfsd at all, and if you are not going to
try to use dtadvfs, you probably should just turn it off.

> Steve Timm
>
> ------------------------------------------------------------------
> Steven C. Timm (630) 840-8525 timm@fnal.gov http://home.fnal.gov/~timm/
> Fermilab Computing Division/Operating Systems Support
> Scientific Computing Support Group--Computing Farms Operations
>



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:47 EDT