| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 616.1 | | STEVMS::PETTENGILL | mulp | Thu Feb 13 1997 00:41 | 2 |
| I think so; have you tried creating /var/dss/dtss/dtss.conf just as you
did on Ultrix?
|
| 616.2 | dtss.conf don't work and not documented. | COPCLU::JENS | | Wed Feb 19 1997 03:03 | 9 |
| Hi again !
Thanks for the response. I cannot get it to work. There is no
directory /var/dss/dtss or file /var/dss/dtss/dtss.template_conf.
I tried to create directory and file dtss.conf, but when doing
ncl -command show dtss all , the command just hangs. Even if the
file dtss.conf is not having any global server entries.
Regards Jens
|
| 616.3 | You have some other problem... | STEVMS::PETTENGILL | mulp | Mon Feb 24 1997 21:13 | 83 |
| /var/dss/dtss/dtss.conf just worked for me.
The ncl command hanging indicates another problem.
Try this:
steosf_root# ps ax | grep dtss
386 ?? S 0:05.16 /usr/sbin/dtssd
21204 ttypf S + 0:00.01 grep dtss
Is dtssd running?
Here's how I setup dtss.conf
steosf_root# ls /var/dss/dtss
/var/dss/dtss not found
steosf_root# mkdir /var/dss/dtss
steosf_root# cat >/var/dss/dtss/dtss.conf
global decnet .FNO.HSKDNS
steosf_root# ncl
ncl> disa dtss
ncl> ena dtss
ncl> sho dtss glo server * all
Node 0 DTSS Global Servers [ Transport = DECnet , Full Name = DEC:.DTSS_GlobalT
AT 1997-02-24-21:03:51.049-05:00I0.307
Identifiers
Name =
[
Transport = DECnet ,
Full Name = DEC:.DTSS_GlobalTimeServers.REO-UKDNS
]
Status
Used In Last Synchronization = False
Characteristics
Transport = DECnet
_______
Node 0 DTSS Global Servers [ Transport = DECnet , Full Name = DEC:.FNO.HSKDNS ]
AT 1997-02-24-21:03:51.052-05:00I0.307
Identifiers
Name =
[
Transport = DECnet ,
Full Name = DEC:.FNO.HSKDNS
]
Status
Used In Last Synchronization = False
Characteristics
Transport = DECnet
ncl> sho impl
Node 0
AT 1997-02-24-21:10:19.733-05:00I0.346
Characteristics
Implementation =
{
[
Type ........ = DECnet/OSI for Digital UNIX ,
Implementation = "DECnet/OSI for Digital UNIX V3.2A-0 (Rev. 23."
] ,
[
Type ........ = Digital UNIX ,
Implementation = "Digital UNIX V3.2C (Rev. 148); Mon Oct 9 22:2"
] ,
[
Type ........ = Alpha ,
Implementation = ""DEC7000""
]
}
|
| 616.4 | using local naming option ? | COPCLU::JENS | | Tue Feb 25 1997 10:51 | 49 |
|
Hi again !
Thanks for the response. Well after reboot my show dtss command
does not hang anymore. But it seems that you are running Decdns
and not local naming option. Your status for global dtss server
indicates that a syncronization with the global server has not
taken place as the indication is false.
My dtss-client is not on the same lan as the servers. When I
start dtss I see the status like this for the global servers:
ncl> show dtss glo serv * all
Node 0 DTSS Global Servers [ Transport = DECnet , Full Name = LOCAL:.copged ]
AT 1997-02-25-16:39:45.121+01:00I708.605
Identifiers
Name =
[
Transport = DECnet ,
Full Name = LOCAL:.copged
]
Status
Used In Last Synchronization = False
Characteristics
Transport = DECnet
ncl>
And after the a little while I don't see the global server anymore.
Regards
Jens
|
| 616.5 | What does the event logging say? | STEVMS::PETTENGILL | mulp | Wed Feb 26 1997 22:00 | 32 |
| If the server can't make a connection to any server, it removes it from its
list of available servers. It will refresh the list of global servers from
DNS global directory or from the conf file periodically (10 hours?).
The event logging is where you normally get information on the success and
failure of the various DTSS operations.
The following are some comments based on a quick check of one baselevel of
the source code. Years ago I had done some tracing to aid in checking some
problems, but that was well before the server was switched to using NCL for
most of its configuration. I can't remember the details of how to set it up.
And I'm looking at a snapshot of the code for VMS, not for unix.
It is possible to turn on logging/tracking, but I don't recall the command.
"set dtss synch trace true" turns on a portion of the trace logic for doing
the graphing.
Try
set dtss service trace true
set dtss comm trace true
set dtss arith trace true
in succession. Ie., do a disable dtss, set one of these, then enable dtss,
and check the list of global servers. Then force a synch (synch dtss).
I'm not sure where the trace file goes on unix. If that doesn't provide
enough info, then try again with more tracing turned on. You might need to
modify the startup of the dtss server so that the output goes to a file
instead of to the null device.
But first enable the event logging for dtss.
Footnote: VMS supports additional tracing by defining system logicals
DTSS$_DEBUG_DECNET and DTSS$_WAN_PERF.
|