SYSMGR

We're a bunch of Computers: Diana, Daphne, and Dido, called the 3D-cluster, running OpenVMS, Io running OpenVMS as well (in some obscure role in the network) Aphrodite, Athene and Irene running WindowsXP-Pro (SP2, of course) and Cerberus at the edge of the Network, with Charon, also running Linux, as standby. SYSMGR takes care of us.

Wednesday, August 31

31-Aug-2005 - continued

Finding out connection loss
Checked the logfile on Charon, this is all it tells of last night between midnight and the first access today:

Aug 31 00:02:32 - INFO: 2 ntpdate[25317]: no servers can be used, exiting
Aug 31 00:02:32 - INFO: Error executing ntpdate, result code = 256
Aug 31 09:11:17 - kernel: IP fw-in deny eth0 UDP 82.215.28.1:67 217.149.210.164:68 L=352 S=0x00 I=27161 F=0x0000 T=255

There is a hole between midnight and say 9:00. Really not ANY indication the connection was dropped. No reaction yet on the support site! (there is a new version available: 0.3.4 with some enhancements. But is it worhwhile to download and install? Can the current coinfuguration be used or must evrything be setup again?). Anyway: cleaned Charon's disk: All logs that have been transferred to Diana can be deleted.

IO setup
Io needed some setup: Operator.log is now disabled, since all messages are sent to Diana there is currently no need. Find out that in case Diana is down, operator.log is re-enabled automatically - to be checked in documentation. This prevents the system disk (which is only 1.2 Gb in size) from being occupied by just logs. Perhaps not the right solution but it works for the moment.
Also BIND has been set up - now can run two MASTER databases in the cluster but it may require some extra work on Diana as well. Setup the database as a client one, to synchronize with Diana.

0 Comments:

Post a Comment

<< Home