Re: [SSI-users] Kernel panic after installing openssi-9.1
Brought to you by:
brucewalker,
rogertsang
From: Roger T. <rog...@gm...> - 2005-12-07 21:34:56
|
Can you verify all files installed on your system are indeed the latest SSI rpm's? Do `rpm -V`. Roger On 12/7/05, Manilal K M <lib...@gm...> wrote: > > On 12/7/05, Roger Tsang <rog...@gm...> wrote: > > Alright lets find out what the problem is. Can I see your /etc/fstab > and > > /etc/clustertab? > > > /ETC/FSTAB > # This file is edited by fstab-sync - see 'man fstab-sync' for details > UUID=3D7ee28e53-e573-463e-80b5-e66728d7de5b / ext3 > chard,defaults,node=3D1 1 1 > none /dev/pts devpts gid=3D5,mode=3D620,node=3D* 0 0 > #none /dev/shm tmpfs defaults = 0 > 0 > LABEL=3D/ /fc4 ext3 defaults,node=3D1 1 2 > LABEL=3D/home /fc4/home ext3 defaults,node=3D1 1 2 > LABEL=3D/opt /fc4/opt ext3 defaults,node=3D1 1 2 > LABEL=3D/usr /fc4/usr ext3 defaults,node=3D1 1 2 > LABEL=3D/usr/local /fc4/usr/local ext3 defaults,node=3D1 1 = 2 > LABEL=3D/var /fc4/var ext3 defaults,node=3D1 1 2 > none /proc proc defaults,node=3D* 0 0 > none /sys sysfs defaults,node=3D1 0 0 > /dev/sda11 swap swap defaults,node=3D1 0 0 > /dev/hda /media/cdrom auto > pamconsole,ro,exec,noauto,managed,node=3D1 0 0 > /dev/fd0 /media/floppy auto > pamconsole,exec,noauto,managed,node=3D1 0 0 > # > -------------------------------------------------------------------------= --------------------------------------------------------- > /ETC/CLUSTERTAB > # /etc/clustertab > # > # Provide a list of nodes in the cluster. Run mkinitrd (with the --cfs > option) > # then ssi-ksync to propagate any changes you make. > # > # Initnodes are nodes that are allowed to run the single init in the > cluster. > # They must be listed in order of precedence. This order is used to > determine > # which node starts init during the cluster boot or after failure of the > # active initnode. The order of non-initnodes can be arbitrary. > # > # An initnode must have a local boot device, as well as physical access t= o > # the shared root. Non-initnodes may leave the boot device field blank an= d > # always use Etherboot or PXE to boot. > # > # The Boot Protocol field indicates the network booting technology used t= o > # boot a node into the cluster, (P)XE or (E)therboot. Certain network > cards > # and blade computers come pre-installed with PXE support, so it is > # convenient. The other option is the open-source Etherboot. It requires > # a system administrator to create a boot disk or flash a ROM for each > # new node, although it is free. This field is mostly irrelevant if a > local > # boot device is specified. > # > # WARNING: The ssi-addnode/rmnode/chnode command suite rewrites this file > # in a vanilla format. Any special comments and formatting are lost. > Before > # rewriting, a backup copy is made at /etc/clustertab~. > # > # Example (node 2 is the primary initnode and node 1 is the secondary): > # > # Node IP address Hardware address Boot Prot Initnode? Boot devic= e > # ---- ----------- ----------------- --------- --------- ----------= - > # 2 192.168.0.2 00:11:22:AA:BB:DD E 1 /dev/sda1 > # 1 192.168.0.1 00:11:22:AA:BB:CC E 1 /dev/sda3 > # 3 192.168.0.3 00:11:22:AA:BB:EE P 0 > > 1 192.168.202.1 00:13:20:20:19:E4 E 1 /dev/sda1= 2 > |