[omniORB] Name service problems

[Duncan Grisby]

On Wednesday 25 June, "Roger wenham" wrote:

> I am having problems with omniNames stopping for no apparent reason.
> 
> This happens about once a week, on various Solaris machines. 
> 
> Has anyone else seen this behaviour, if so, I would be grateful for
> any pointers on how to go about debugging this.

Run with command line arguments

 -ORBtraceLevel 25 -ORBtraceInvocations 1 -ORBtraceThreadId 1 -ORBtraceTime 1

to get loads of debugging output. That might help track it down.

> The start command looks like this
> /opt/omniORB/bin/omniNames -errlog /opt/log/omniName.log
> 
> There are no errors to be found in the omniName.log.
> 
> A second question is: When I re-start the name server after an error,
> it has of course forgotten all the names registered with it. I have
> searched the documentation for the way to make the name server non
> volatile, but have found nothing so far.

omniNames is _always_ persistent. There's no way to make it so it
isn't.

Perhaps you are starting it with a script that removes the
omninames-<hostname>.log and .bak files?  That's where the persistent
information is stored.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --