Title: | POLYCENTER Console Manager |
Notice: | Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS: |
Moderator: | CSC32::BUTTERWORTH |
Created: | Thu Aug 06 1992 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 1541 |
Total number of notes: | 6564 |
hi there, has anyone seen a similar problem between CM and MCC ???? I have one data collector for all CM events on the MCC side which is triggered by an action routine on CM side. Sometimes I don't get the events I send onto console of a serviced system in MCC. When I call my action routine by hand - it works. When I restart complete CM - it works again. I traced my action routine by setting -x option in rthe script and with output to a tmp file. It turns out that I get an unaligned access in process ... and no output to my tmpfile even if I put an output into the first line of the script. I am in a test state and I terminated and restarted the MCC few times - is this a problem? Is there an ordering problem in startup up the two guys? Any idea???? Thanks Maik
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
251.1 | EEMELI::OJUSSILA | Olli Jussila, IS/SMGT Finland | Mon Apr 25 1994 21:44 | 23 | |
Maik, Your problem seems to something else I had. But maybe my story could help ypu. I had problem when I started to feed alarms send by PSW through OPA0: and CM to MCC. There was two problems. I could not get the event text to action routine. With help of CM engineering I changed event from literal to regular expression incluing eol. Other problem were lines containing $-signs. CM V1.0 used " around event text instead of ' which caused problems This has been fixed in V1.1. I used echo to write events to logfile also when I started with this. Now it works just fine. Of course there might have been events which haven't been passed to MCC but atleast I don't have to restart CM. I would start MCC before CM. Then MCC event collector is ready to collect events send from CM. -Olli | |||||
251.2 | fixed | MUNDIS::MBACHMANN | MAIK BACHMANN @MFR | Tue Apr 26 1994 15:49 | 20 |
hi Olli, I fixed the problem. Use /bin/sh instead of /usr/bin/ksh in teh action routine and all seem to work fine. This seems not to be very sensible - despite the guys who answered to you when you posted your problem mentioned that the rott shell is always Bourne shell ( which is definitely not true ) and this would explain the problem ( not to me ). Anyway - it works now. May be one of you who mentioned the conjunction between sh and root shell can make that clearer. ( for me there is not a big difference between calling "system" to a Bourne shell or Korn shell script if the script and the profile are reasonable. regards Maik |