Error 'This function is not implemented'

[mike_brooker]

I'm running 10.0d Backup exec for windows server and BE.RALUS.10.0.5520 remote agent for Unix and windows, windows agents are fine, however, I have a problem with 1 of the 2 Unix agents.

I have 2 Unix agents displayed in remote selections but when trying to connect to the second agent in the browse list I get the following error 'This function is not implemented', the first Unix agent works fine, it is the same agent for both and both Unix servers are running the same OS - what is going on?

The default port is 10000 for both, both config files look identical. Port 10000 is not being used buy any other process.

[mike_brooker]

What I have found out is this, I ran Ethereal on the Linux box and can confirm that the BE10d server is sending the username and password to the agent on the Linux server, it seems to be the agent that is at fault, what I don't understand is why the first one in the selection list works? Could this be a licensing issue? We have licenses for everything so not sure what else to do now.

As a side note, the vendor who supplied us 10d said they have seen the same problem but with the Windows agents and they recommend upgrading to BE11, which is annoying as they sold us 10d less than 4 months ago!

[David_Sanz]

Mike

Did you install the trial version before the licensed one?

[Sanjay_Raval]

Here is the technote

http://seer.support.veritas.com/docs/284269.htm

[mike_brooker]

As I said, NDMP port 10000 is not being blocked (there is no firewall running at all) and the /etc/services files is the same for NDMP port 10000 on both servers

As far as I can remember we downloaded the full version then added our registration/serial numbers - don't think we had a trial version.

I might try removing the agent that works and then running the suspect one first, i.e. they will be swapped around the selection/browse list, this might give tell me if it is a licensing issue - other than that I'm at a loss, and pretty annoyed!!

[mike_brooker]

debug output

b6ef36b0 Wed Dec 13 16:25:05 2006: Starting BE Remote Agent
b6ef36b0 Wed Dec 13 16:25:05 2006: Requested no generation of log file
b6ef36b0 Wed Dec 13 16:25:05 2006: No configuration file specified. Using default.
b6ef36b0 Wed Dec 13 16:25:05 2006: Log to console: enabled
b6ef36b0 Wed Dec 13 16:25:05 2006: Starting NDMP processor
b6ef2ba0 Wed Dec 13 16:25:05 2006: FS_InitFileSys
b6ef2ba0 Wed Dec 13 16:25:05 2006: libbedsnt5.so could not be loaded: 0x 2 (2)
b6ef2ba0 Wed Dec 13 16:25:05 2006: libbedssql2.so could not be loaded: 0x 2 (2)
b6ef2ba0 Wed Dec 13 16:25:05 2006: libbedsxchg.so could not be loaded: 0x 2 (2)
b6ef2ba0 Wed Dec 13 16:25:05 2006: libbedsxese.so could not be loaded: 0x 2 (2)
b6ef2ba0 Wed Dec 13 16:25:05 2006: libbedsmbox.so could not be loaded: 0x 2 (2)
b6ef2ba0 Wed Dec 13 16:25:06 2006: libbedspush.so could not be loaded: 0x 2 (2)
b6ef2ba0 Wed Dec 13 16:25:06 2006: libbedsnote.so could not be loaded: 0x 2 (2)
b6ef2ba0 Wed Dec 13 16:25:06 2006: libbedsmdoc.so could not be loaded: 0x 2 (2)
b6ef2ba0 Wed Dec 13 16:25:06 2006: libbedssps2.so could not be loaded: 0x 2 (2)
b6ef2ba0 Wed Dec 13 16:25:06 2006: libbedsupfs.so could not be loaded: 0x 2 (2)
b6ef2ba0 Wed Dec 13 16:25:06 2006: libbedsshadow.so could not be loaded: 0x 2 (2)
b6ef2ba0 Wed Dec 13 16:25:06 2006: libbedsoffhost.so could not be loaded: 0x 2 (2)
b6ef2ba0 Wed Dec 13 16:25:06 2006: loaded libbedsvx.so
b6ef2ba0 Wed Dec 13 16:25:06 2006: libbedsorcl.so could not be loaded: 0x 2 (2)
b6ef2ba0 Wed Dec 13 16:25:06 2006: libbedsagnt.so could not be loaded: 0x 2 (2)
b6ef2ba0 Wed Dec 13 16:25:06 2006: libbedssms.so could not be loaded: 0x 2 (2)
b6ef2ba0 Wed Dec 13 16:25:06 2006: loaded libbedssmsp.so
b6ef2ba0 Wed Dec 13 16:25:06 2006: libbedsra.so could not be loaded: 0x 2 (2)
b6ef2ba0 Wed Dec 13 16:25:06 2006: Initializing FSs
b6ef2ba0 Wed Dec 13 16:25:06 2006: Using 'UTF-8' Encoding.
b6ef2ba0 Wed Dec 13 16:25:06 2006: VXMS Initialization OK.
b6ef2ba0 Wed Dec 13 16:25:07 2006: Listening on port 10000
b6ef2ba0 Wed Dec 13 16:25:07 2006: ERROR: system call (bind): 0.
b6ef36b0 Wed Dec 13 16:25:10 2006: Stopping remote agent due to explicitly failed initialization
b6ef36b0 Wed Dec 13 16:25:16 2006: Startup failure detected
b6ef36b0 Wed Dec 13 16:25:16 2006: Remote agent exit
b6ef36b0 Wed Dec 13 16:25:16 2006: unloading libbedssmsp.so
b6ef36b0 Wed Dec 13 16:25:16 2006: unloading libbedsvx.so

[mike_brooker]

The above debug output was generated during one install of the agent, however, the agent is running, so not sure what is going on.

[Sanjay_Raval]

I hope this technote may help you


http://seer.entsupport.symantec.com/docs/275147.htm

technote for how change the port
http://seer.support.veritas.com/docs/275228.htm

[mike_brooker]

Well, I changed the port over and it has made no difference.

Any more suggestion?

[mike_brooker]

One question, when changing the port for ndmp, Veritas says that the changes must take place on every server in the environment, so I assuem that I have to change ports for Windows as well as Linux?