Highlighted

beremote Killed When Remote Console Accesses

I've installed 2010 r2 client on Mac OS X Server v. 10.6.4.  That was a trick in itself as I had to boot to 32 bit mode to install it, then back to 64 after installation.

Now that the system is installed and running, when my backup admin goes to the console to add the machine to the backups, he initially sees the machine but then can't access it.  I stopped the process and then tried to run beremote manually with logging to the console.  Here's what I get:

 

 

bash-3.2# ./beremote --log-console
a0aba500 Tue Dec 21 10:12:30 2010 : Starting BE Remote Agent
a0aba500 Tue Dec 21 10:12:30 2010 : Requested no generation of log file
a0aba500 Tue Dec 21 10:12:30 2010 : No configuration file specified.  Using default.
a0aba500 Tue Dec 21 10:12:30 2010 : Log to console: enabled
a0aba500 Tue Dec 21 10:12:30 2010 : Initialized locks for SSL callbacks
a0aba500 Tue Dec 21 10:12:30 2010 : Starting NDMP processor
a0aba500 Tue Dec 21 10:12:30 2010 : NDMPDMainThreadFunc spawned: grpid=1, tid=-1341648896
b0081000 Tue Dec 21 10:12:30 2010 : FS_InitFileSys
b0081000 Tue Dec 21 10:12:30 2010 :   libbedsnt5.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Dec 21 10:12:30 2010 :   libbedssql2.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Dec 21 10:12:30 2010 :   libbedsxchg.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Dec 21 10:12:30 2010 :   libbedsxese.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Dec 21 10:12:30 2010 :   libbedsmbox.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Dec 21 10:12:30 2010 :   libbedspush.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Dec 21 10:12:30 2010 :   libbedsnote.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Dec 21 10:12:30 2010 :   libbedsmdoc.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Dec 21 10:12:30 2010 :   libbedssps2.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Dec 21 10:12:30 2010 :   libbedssps3.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Dec 21 10:12:30 2010 :   libbedsupfs.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Dec 21 10:12:30 2010 :   libbedsshadow.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Dec 21 10:12:30 2010 :   libbedsoffhost.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Dec 21 10:12:30 2010 :   loaded libbedsvx.dylib
b0081000 Tue Dec 21 10:12:30 2010 :   libbedssms.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Dec 21 10:12:30 2010 :   loaded libbedssmsp.dylib
b0081000 Tue Dec 21 10:12:30 2010 :   libbedsra.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Dec 21 10:12:30 2010 : Initializing FSs
b0081000 Tue Dec 21 10:12:30 2010 : Using 'UTF-8' Encoding.
b0081000 Tue Dec 21 10:12:30 2010 : Using vfm path /opt/VRTSralus/VRTSvxms from config.
b0081000 Tue Dec 21 10:12:30 2010 : Sucessfully set VFM_PRIVATE_ROOT env to /opt/VRTSralus/VRTSvxms.
b0081000 Tue Dec 21 10:12:30 2010 : VFM_PRIVATE_ROOT was set with value /opt/VRTSralus/VRTSvxms
b0081000 Tue Dec 21 10:12:30 2010 : VXMS Initialization OK.
b0081000 Tue Dec 21 10:12:30 2010 : Detected Mounted Filesystem: type <hfs> mounted at </>
b0081000 Tue Dec 21 10:12:30 2010 : Detected Mounted Filesystem: type <devfs> mounted at </dev>
b0081000 Tue Dec 21 10:12:30 2010 : Detected Mounted Filesystem: type <autofs> mounted at </net>
b0081000 Tue Dec 21 10:12:30 2010 : Detected Mounted Filesystem: type <autofs> mounted at </home>
b0081000 Tue Dec 21 10:12:30 2010 : Detected Mounted Filesystem: type <autofs> mounted at </Network/Servers>
b0081000 Tue Dec 21 10:12:30 2010 : Detected Mounted Filesystem: type <acfs> mounted at </Volumes/FinalCutServer>
b0081000 Tue Dec 21 10:12:30 2010 : AddToExcludedDirsList: Directory /Network added to exclude list
b0081000 Tue Dec 21 10:12:30 2010 : Adding directory /Network to RedirectedRestoreAsVisible list
b0081000 Tue Dec 21 10:12:30 2010 : Adding directory /Volumes to RedirectedRestoreAsVisible list
b0081000 Tue Dec 21 10:12:30 2010 : Successfully resolved the "ndmp" service to port: 10000 (host order)
b0081000 Tue Dec 21 10:12:30 2010 : BETCPListener successfully installed a signal handler for SIGTERM
b0081000 Tue Dec 21 10:12:30 2010 : BETCPListener::BETCPListener: This system appears to be a Dual IP system
b0081000 Tue Dec 21 10:12:30 2010 : BETCPListener::BETCPListener: Successfully set the IPV6_V6ONLY option, this listener may behave as Dual Stack listener
b0081000 Tue Dec 21 10:12:30 2010 : Started NDMP Listener on port 10000
b0185000 Tue Dec 21 10:12:40 2010 : NrdsAdvertiserThread: advertisement cycle started.
b0185000 Tue Dec 21 10:12:40 2010 : BENetConfigEx: Successfully refreshed adapter information.
b0185000 Tue Dec 21 10:12:40 2010 : NrdsAdvertiserThread: EnumSelfDLE for file system 22 returned 0(0x0) and 1 DLEs
b0185000 Tue Dec 21 10:12:40 2010 : NrdsAdvertiserThread: Nrds Message Len : 169.
b0185000 Tue Dec 21 10:12:40 2010 : VX_RemoveDLE: DestroyDLE()
b0185000 Tue Dec 21 10:12:40 2010 : This instance of BETCPListener was not requested to install a signal handler and hence will not install one!
b0185000 Tue Dec 21 10:12:40 2010 : ConnectToServerEndPoint: dest=dtbkcasosrv1.dealertire.com, service=6101
b0185000 Tue Dec 21 10:12:40 2010 : CreateConnection type=0 on socket 5 via BESocket OK
b0185000 Tue Dec 21 10:12:40 2010 : NrdsAdvertiserThread: send of dtmdcsvr2.dealertire.com type 22 subtype 0 to target=dtbkcasosrv1.dealertire.com port=6101 succeeded
b0185000 Tue Dec 21 10:12:40 2010 : NrdsAdvertiserThread: advertisement cycle complete.  Waiting 240 minutes before advertising again.
b0207000 Tue Dec 21 10:12:45 2010 : NrdsAdvertiserThread: negative (purge) advertisement cycle started.
b0207000 Tue Dec 21 10:12:45 2010 : NrdsAdvertiserThread: no purge is pending.
b0207000 Tue Dec 21 10:12:45 2010 : NrdsAdvertiserThread: negative (purge) advertisement cycle complete.  Waiting 240 minutes before advertising again.
b0081000 Tue Dec 21 10:14:29 2010 : Control connection accepted : connection established between end-points 10.106.0.13:10000 and 10.1.1.249:62308
Killed
bash-3.2#
 
As you can see, as soon as the control connection is accepted, the process is killed.  I've verified it's connecting to the correct IP as I have two NICs on this machine.  It's running Xsan and has to have the metadata over one network and the rest of the IP traffic over the other.
 
Why is my beremote process being killed?  It will run fine until the remote console connects.
1 Reply

Same Problem Selecting Resources from Server on OSX 10.6.5 x64

 

4034a00 Wed Dec 22 21:40:30 2010 : NrdsAdvertiserThread: connect to target=hp-ml530-g3 port=6101 failed
4034a00 Wed Dec 22 21:40:30 2010 : NrdsAdvertiserThread: Retrying in 60 seconds
4035800 Wed Dec 22 21:40:35 2010 : NrdsAdvertiserThread: negative (purge) advertisement cycle started.
4035800 Wed Dec 22 21:40:35 2010 : NrdsAdvertiserThread: no purge is pending.
4035800 Wed Dec 22 21:40:35 2010 : NrdsAdvertiserThread: negative (purge) advertisement cycle complete.  Waiting 240 minutes before advertising again.
380a800 Wed Dec 22 21:41:20 2010 : Control connection accepted : connection established between end-points 192.168.4.3:10000 and 192.168.4.40:1300
./monitor.sh: line 2: 11036 Killed                  ./beremote --log-console
 
Also, with IPV6 DISABLED (ipv6 -x) - The console crashes ASAP.
 
I am running these commands:
 
export DYLD_LIBRARY_PATH=/opt/VRTSralus/bin:$DYLD_LIBRARY_PATH 
./beremote --log-console
 
Cheers
 
Jeremy