Re: Problems with conserver after OS upgrade

On Jun 6, 2009, at 18:06, Bryan Stansell wrote:
> Does 'conserver -DS' show 127.0.0.1 in the ProbeInterfaces()  
> output?  If
> it's not there (or ProbeInterfaces() isn't showing anything or the  
> wrong
> things), the mapping won't happen correctly.  You should see all your
> interfaces listed.

  There's only one line of "ProbeInterfaces()" output.  It doesn't  
seem interesting.

  The following is the beginning of the conserver -DS output,  
including the one line of ProbeInterfaces() output, and the one line  
after that.

[Sun Jun  7 21:29:23 2009] conserver (13449): DEBUG: [cutil.c:355]  
AllocString(): 0xbb818040 created string #1
[Sun Jun  7 21:29:23 2009] conserver (13449): DEBUG: [cutil.c:355]  
AllocString(): 0xbb818060 created string #2
[Sun Jun  7 21:29:23 2009] conserver (13449): DEBUG: [cutil.c:355]  
AllocString(): 0xbb818080 created string #3
[Sun Jun  7 21:29:23 2009] conserver (13449): performing configuration  
file syntax check
[Sun Jun  7 21:29:23 2009] conserver (13449): DEBUG: [main.c:1364]  
main(): bind address set to `0.0.0.0'
[Sun Jun  7 21:29:23 2009] conserver (13449): DEBUG: [cutil.c:2263]  
ProbeInterfaces(): ifc_len==4464 max_count==31
[Sun Jun  7 21:29:23 2009] conserver (13449): DEBUG: [cutil.c:355]  
AllocString(): 0xbb8180a0 created string #4


  Does this mean the interfaces aren't being probed [correctly] ?   
That would certainly explain the behaviour...

  Thanks.

         - Chris