cancel
Showing results for 
Search instead for 
Did you mean: 

Query Failed on Selection list for Mac server.

fl
Level 4
Hello,

I am having a problem with being able to select one of my Mac OS server that has the Mac Backup Exec agent installed on it.  The error I'm getting when I select it and expand the [ROOT] directory is a "Query Failed" error in the name pane on the right side (see attachment).  My other three Mac OS server with the exact same OS version and Backup Exec agent works just fine.  I've tried uninstalling the Backup Exec agent and reinstalling it but same error, I've checked permissions and etc... and I've made sure it was installed and configured exactly like the other three that are working.  Please help!!!

Thanks in advanced.
11 REPLIES 11

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

Assuming that as you say other servers work that you are not running the server version of OS X 10.6 (Snow Leopard) - then it is worth checking to see if the beremote process on the MAC server stays running when you attempt to browse onto the affected MAC in the BEWS console.

If you are running Snow Leopard then I am surprised you got any of the servers to work as that platform has not yet been qualified as supported by Backup Exec.

 

fl
Level 4
No these are not Snow Leopard but just Leopard 10.5.8.  I've checked the beremote process and it is running.  The only difference between the one that is not working and the three that are working is that the non-working one is a VM meaning it is a VM using under Fusion.  I'm going to create another VM with OSX server and see if I get the same result, if I do then I seems to be a problem with the BE agent on a virtual OSX server.

fl
Level 4
I have confirmed that it does appear to be a problem with have VM Mac OSX server.  I've installed the BE agent on 2 other VMs running Mac OSX server and none of them works, they all get the "query failed" error when trying to browse the directory structure.  On a non-VM OSX server it works fine so I think it's something at the network layer between the physical Mac server and Vmware Fusion and the virtual Mac server.  I've dropped all firewalls and still no dice.

Now the million dollar question is how to you fix the problem.

Hemant_Jain
Level 6
Employee Accredited Certified
Is ther NAT involved when BE communicates to this machine? Are you able to telnet to this machine at port 10000? Try doing "telnet <mac name> 10000". Also make sure that hosts file of Backup Exec server has the entry for mac machine and mac server has the hosts file entry for BE server as well as itself.

Thanks

fl
Level 4
1) There is no NAT involved the network interface is a Bridge interface.
2) Yes I am able to telnet into the Mac server.
3) Yes the host file on the Backup Exec server has the entry for the Mac server.
4) Yes the host file on the Mac server has the entry for the BE server.

Hemant_Jain
Level 6
Employee Accredited Certified
Please enable debugging on mac using following document:
http://support.veritas.com/docs/292383

Once enabled, try selecting the machine from BE and check the debug logs, and paste the text from log here.
Thanks

fl
Level 4
Here is the text from the debug log. Note IPv6 is off on all of our Mac servers including the ones that works.

a074e720 Tue Oct 6 08:58:51 2009 : Starting BE Remote Agent
a074e720 Tue Oct 6 08:58:51 2009 : Log file: debug.txt
a074e720 Tue Oct 6 08:58:51 2009 : No configuration file specified. Using default.
a074e720 Tue Oct 6 08:58:51 2009 : Log to console: disabled
a074e720 Tue Oct 6 08:58:51 2009 : Initialized locks for SSL callbacks
a074e720 Tue Oct 6 08:58:51 2009 : Starting NDMP processor
a074e720 Tue Oct 6 08:58:51 2009 : NDMPDMainThreadFunc spawned: grpid=1, tid=-1341648896
b0081000 Tue Oct 6 08:58:51 2009 : FS_InitFileSys
b0081000 Tue Oct 6 08:58:51 2009 :   libbedsnt5.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Oct 6 08:58:51 2009 :   libbedssql2.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Oct 6 08:58:51 2009 :   libbedsxchg.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Oct 6 08:58:51 2009 :   libbedsxese.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Oct 6 08:58:51 2009 :   libbedsmbox.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Oct 6 08:58:51 2009 :   libbedspush.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Oct 6 08:58:51 2009 :   libbedsnote.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Oct 6 08:58:51 2009 :   libbedsmdoc.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Oct 6 08:58:51 2009 :   libbedssps2.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Oct 6 08:58:51 2009 :   libbedssps3.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Oct 6 08:58:51 2009 :   libbedsupfs.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Oct 6 08:58:51 2009 :   libbedsshadow.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Oct 6 08:58:51 2009 :   libbedsoffhost.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Oct 6 08:58:51 2009 :   loaded libbedsvx.dylib
b0081000 Tue Oct 6 08:58:51 2009 :   libbedssms.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Oct 6 08:58:51 2009 :   loaded libbedssmsp.dylib
b0081000 Tue Oct 6 08:58:51 2009 :   libbedsra.dylib could not be loaded: 0x       2 (2)
b0081000 Tue Oct 6 08:58:51 2009 : Initializing FSs
b0081000 Tue Oct 6 08:58:51 2009 : Using 'UTF-8' Encoding.
b0081000 Tue Oct 6 08:58:51 2009 :        VXMS Initialization OK.
b0081000 Tue Oct 6 08:58:51 2009 : Detected Mounted Filesystem: type <hfs> mounted at </>
b0081000 Tue Oct 6 08:58:51 2009 : Detected Mounted Filesystem: type <devfs> mounted at </dev>
b0081000 Tue Oct 6 08:58:51 2009 : Detected Mounted Filesystem: type <fdesc> mounted at </dev>
b0081000 Tue Oct 6 08:58:51 2009 : Detected Mounted Filesystem: type <cd9660> mounted at </Volumes/symantec>
b0081000 Tue Oct 6 08:58:51 2009 : Detected Mounted Filesystem: type <autofs> mounted at </net>
b0081000 Tue Oct 6 08:58:51 2009 : Detected Mounted Filesystem: type <autofs> mounted at </home>
b0081000 Tue Oct 6 08:58:51 2009 : Detected Mounted Filesystem: type <autofs> mounted at </Network/Servers>
b0081000 Tue Oct 6 08:58:51 2009 :                   AddToExcludedDirsList: Directory /Network added to exclude list
b0081000 Tue Oct 6 08:58:51 2009 : Adding directory /Volumes to RedirectedRestoreAsVisible list
b0081000 Tue Oct 6 08:58:51 2009 : Adding directory /Network to RedirectedRestoreAsVisible list
b0081000 Tue Oct 6 08:58:51 2009 : @@@@@@@MyCloseSocket called with sockfd = 4(0x4)      retval = 0
b0081000 Tue Oct 6 08:58:51 2009 : @@@@@@@MyCloseSocket called with sockfd = 4(0x4)      retval = 0
b0081000 Tue Oct 6 08:58:51 2009 : Successfully resolved the "ndmp" service to port: 10000 (host order)
b0081000 Tue Oct 6 08:58:51 2009 : @@@@@@@MyCloseSocket called with sockfd = 6(0x6)      retval = 0
b0081000 Tue Oct 6 08:58:51 2009 : @@@@@@@MyCloseSocket called with sockfd = 7(0x7)      retval = 0
b0081000 Tue Oct 6 08:58:51 2009 : @@@@@@@MyCloseSocket called with sockfd = 8(0x8)      retval = 0
b0081000 Tue Oct 6 08:58:51 2009 : BETCPListener::BETCPListener: This system appears to be a Dual IP system
b0081000 Tue Oct 6 08:58:51 2009 : BETCPListener::BETCPListener: Successfully set the IPV6_V6ONLY option, this listener may behave as Dual Stack listener
b0081000 Tue Oct 6 08:58:51 2009 : BETCPListener::Bind: Could not bind to port 10000 on IPv6, An error occurred during a socket bind operation: Error Code: 48, System Error Message: Address already in use
b0081000 Tue Oct 6 08:58:51 2009 : @@@@@@@MyCloseSocket called with sockfd = 5(0x5)      retval = 0
b0081000 Tue Oct 6 08:58:51 2009 : BETCPListener::Bind: Could not bind to port 10000 on IPv4, An error occurred during a socket bind operation: Error Code: 48, System Error Message: Address already in use
b0081000 Tue Oct 6 08:58:51 2009 : @@@@@@@MyCloseSocket called with sockfd = 4(0x4)      retval = 0
b0081000 Tue Oct 6 08:58:51 2009 : Could not start NDMP Listener on port 10000: An error occurred during a socket creation operation: Error Code: 48, System Error Message: Address already in use
b0081000 Tue Oct 6 08:58:51 2009 : ndmpRun: exiting
a074e720 Tue Oct 6 08:58:56 2009 : Stopping remote agent due to explicitly failed initialization
a074e720 Tue Oct 6 08:59:01 2009 : Startup failure detected
a074e720 Tue Oct 6 08:59:01 2009 : Remote agent exiting, cancelling 3 joinable threads
b0185000 Tue Oct 6 08:59:01 2009 : NrdsAdvertiserThread: advertisement cycle started.
b0103000 Tue Oct 6 08:59:01 2009 : time to exit thread
b0185000 Tue Oct  6 08:59:01 2009 : @@@@@@@MyCloseSocket called with sockfd = 4(0x4)      retval = 0
b0185000 Tue Oct 6 08:59:01 2009 : @@@@@@@MyCloseSocket called with sockfd = 4(0x4)      retval = 0
b0185000 Tue Oct 6 08:59:01 2009 : BENetConfigEx: Successfully refreshed adapter information.
b0185000 Tue Oct 6 08:59:01 2009 : NrdsAdvertiserThread: EnumSelfDLE for file system 22 returned 0(0x0) and 1 DLEs
b0185000 Tue Oct 6 08:59:01 2009 : NrdsAdvertiserThread: Nrds Message Len : 133.
b0185000 Tue Oct 6 08:59:01 2009 : VX_RemoveDLE: DestroyDLE()
b0185000 Tue Oct 6 08:59:01 2009 : NrdsAdvertiserThread: failed to send to 134.139.25.78 even after 10 attempts
b0185000 Tue Oct 6 08:59:01 2009 : NrdsAdvertiserThread: advertisement cycle complete. Waiting 240 minutes before advertising again.
b0185000 Tue Oct 6 08:59:01 2009 : NrdsAdvertiserThread: exiting
b0207000 Tue Oct 6 08:59:06 2009 : NrdsAdvertiserThread: exiting

Hemant_Jain
Level 6
Employee Accredited Certified
It is not able to send advertisement to 134.139.25.78. "failed to send to 134.139.25.78 even after 10 attempts", this is the message which i am looking at, so checking connection this IP address would be a good idea. Also, it is not able to bind port 10000, even on IPv4. It gives same message "Address already in use". Is it in use by some other machine?

Thanks

fl
Level 4

I'm pretty sure the Mac server is able to advertise to the BE server (25.78) otherwise it wouldn't show up in the Mac Systems Resources list.

I also don't know why it's giving the "address already in use" message as this the only server with that IP.  We also have another virtual Mac server which is also not working and this server was a new setup with a new IP never been used and I see the exact same debug messages.

Hemant_Jain
Level 6
Employee Accredited Certified
Check the machine if port 10000 is in use by any other process or application? The command is "netstat -a".

fl
Level 4

Have already checked that before.  No other process or application is using port 10000.

Server 1 (physical): new OSX 10.5.8 standard installation, install BE agent, no other software just OS only. - Works
Server 2 (virtual): new OSX 10.5.8 standard installation, install BE agent, no other software just OS only. - Does NOT work.