| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5299.1 | are your paths ok ? | HERON::PATEL_A | LoLo-AQIC-I82Q-B4IP, - LMF | Tue Jul 06 1993 04:28 | 17 |
| Dominique.
have you tried decnet as the transport ? also if your paths are set
correctly then you should be able to get to the alarm manager
application without changing directory ie
unimax.vbo.dec.com> which mcc_alarm_mgr
/usr/bin/mcc_alarm_mgr
unimax.vbo.dec.com> ls -l /usr/bin/mcc_alarm_mgr
lrwxr-xr-x 1 root 28 May 24 16:29 /usr/bin/mcc_alarm_mgr ->
/usr/mcc/
mmexe/mcc_alarm_mgr
unimax.vbo.dec.com>
also try from MCC>
test mcc 0 alm_mgr -- see if its enrolled correctly etc...
|
| 5299.2 | Soemthing more fundamental ! | KETJE::PACCO | Gallia divisa est in partes tres | Tue Jul 06 1993 13:27 | 57 |
| Amrit,
I already did all what you suggested. The symbolic link exists, and
the alarm_mgr is enrolled: the test is successful. I also tried to
define DECnet transport.
First I had security problems:
csh> setenv DISPLAY .gkk.m.mgkk01::0
csh> mcc_alarm_mgr
Start Command processor in background
Starting application
[1] 16434
Xlib: connection to ".gkk.m.mgkk01::0.0" refused by server
Xlib: Client is not authorized to connect to Server
mcc_alarm_mgr_ui: Can't open display
[1] + Exit 1 mcc_alarm_mgr_ui
Then
csh> setenv DISPLAY bc:.gkk.m.mgkk01::0
csh> mcc_alarm_mgr
Start Command processor in background
Starting application
[1] 16448
mcc_alarm_mgr_ui: Can't open display
[1] + Exit 1
With printenv I get
DISPLAY=bc:.gkk.m.mgkk01::0.0
Isn't here some confusion because of the ":" and "::" colons ?
The I put ".gkk.m.mgkk01::0.0" as the authorized host node in the Xwindows
security data base. The I finally get:
csh> mcc_alarm_mgr
Start Command processor in background
Starting application
[1] 16552
I see heree
ps -aux | grep al
root 36 0.0 0.0 112 0 ? IW 0:00 /usr/etc/dnalimd
root 16552 0.0 5.3 4668 2852 p5 S 0:00 mcc_alarm_mgr_ui
root 270 0.0 0.5 4968 276 ? S 9:19 mcc_alarms_fm 2 N
root 16565 0.0 0.1 40 32 p6 S 0:00 grep al
root 16551 0.0 0.2 364 120 p5 I 0:00 csh -f mcc_alarm_mgr
root 16405 0.0 2.7 2096 1436 ? S 0:03 mcc_alarm_mgr_fm 16 N
But nothing happens.
Then after a while (1 minute or more)
Exception: Invalid memory address (dce / thd)
and I see that process mcc_alarm_mgr_ui disappeared !
DECmcc V1.3 was installed after DECnet V5.1 was put on the system.
Has this any relation?
Regards,
Dominique.
|
| 5299.3 | looks like ultrix/dns bug | GOSTE::CALLANDER | | Wed Jul 28 1993 14:33 | 20 |
| to me it really looks like the alarm manager on ultrix is having
a big problem when being run with DNS. I am not even certain that
that configuration was adequately tested before the prototype was
released.
Ookay I am going to have to take a look into this one more closely.
If you could try changing over to a local MIR for a few minutes
and try bringing it up I would appreciate knowing if that lets
you get the application running.
Since the alarm manager is a prototype you can not submit a CLD
on it, but we have established a support account for reporting
(to management and engineering) problems with the application.
To report a critical bug send mail with a description of your
management environment (version/hardware) and the problem to:
GOSTE::ALARM_MGR (goste == 55.44)
jill
|