SUMMARY: rules.ok being ignored by jumpstart client

From: Alex J. Avriette (avriette_at_gmail.com)
Date: 01/13/05

  • Next message: GDS: "Network attached storage ideas" 
    Date: Thu, 13 Jan 2005 11:08:52 -0500
To: sunmanagers@sunmanagers.org

    So the list of people who responded with help:

    Casper ***
    Dale Hirchert
    Conor Svensson
    Matt Clausen
    Lai Wei
    Peter van Genmert
    Fernando Boveda

    First and foremost, Dale was very helpful. After going through just
    about everything in the book, he suggested from a Sunsolve document
    that I remove the hostname and ip_address directives from the sysidcfg
    file. I did so, without any success. Around the same time, both
    Fernando and Peter suggested I check the netmasks of the client and
    server.

    After setting the netmask on the server from /16 to /24, to match the
    client's /24, the jumpstart proceeded in an automated fashion, which
    is as it should be.

    This frustrates me, as all the mounts worked, and the rules were
    plainly visible to the client. The sysidcfg was correct and crafted
    per the manpage, and Sun's Jumpstart Technology Blueprint book (I've
    been using jumpstart for a long time, but this is a new install at a
    new network). So it strikes me that everything was configured that it
    *could* be working correctly, but that it simply chose not to.

    Dale is correct in saying that the hostname and the IP address are
    configured during boot, and having them in the sysidcfg file is not
    necessary, however, it seems to me that it should be possible to have
    a machine come up with one ip, supplied by the bootserver, and to
    install the OS with the configuration of another ip. Afterall, the
    installed server does not use the bootserver to ascertain its
    configuration information. In this case, specifying the hostname and
    ip address would be required.

    But I digress.

    I will say that I am once again impressed by the fabulous volume of
    responses I received from Sunmanagers, and most especially so by the
    diligence and indeed correctness on the part of Dale, Peter, and
    Fernando (which is not to say I do not appreciate any of the rest of
    it. I'll take anything after days of pounding on something that
    "should work").

    Cheers,
    alex

    I have included the original message below for the spiders.

    I have a peculiar jumpstart problem. I've included output of the
    client jumpstarting, here:

    Rebooting with command: boot net - install
    Boot device: /pci@1f,700000/network@2 File and args: - install
    1000 Mbps FDX Link up
    Timeout waiting for ARP/RARP packet
    Timeout waiting for ARP/RARP packet
    29200 1000 Mbps FDX Link up
    SunOS Release 5.9 Version Generic_117171-07 64-bit
    Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    whoami: no domain name
    Hardware watchdog enabled
    SC unretrieved msg JAN 13 06:09:06 2005 UTC [Host System has Reset]
    Configuring /dev and /devices
    Using RPC Bootparams for network configuration information.
    Skipping interface bge3
    Skipping interface bge2
    Skipping interface bge1
    Configured interface bge0
    Searching for configuration file(s)...
    Using sysid configuration file
    10.2.3.251:/export/jumpstart/config/dc-mvncrmas2/sysidcfg
    Search complete.
    The system is coming up. Please wait.
    Begin system identification...
    Starting remote procedure call (RPC) services: sysidns done.
    System identification complete.
    Generating software table of contents [this may take a few minutes...]
    Table of contents complete.
    Starting Solaris installation program...
    Searching for JumpStart directory...
    not found
    Warning: Could not find matching rule in rules.ok
    Press the return key for an interactive Solaris install program...^C
    Executing JumpStart preinstall phase...
    Searching for SolStart directory...
    Checking rules.ok file...
    ^Cawk: trying to access field -2
    record number 1
    /sbin/suninstall: test: argument expected
    # ^C
    # df -h
    Filesystem size used avail capacity Mounted on
    dc-suntools:/export/jumpstart/install/Solaris_9/Tools/Boot
                           20G 1.1G 18G 6% /
    swap 1.9G 560K 1.9G 1% /tmp
    proc 0K 0K 0K 0% /proc
    mnttab 0K 0K 0K 0% /etc/mnttab
    /tmp/devices 1.9G 560K 1.9G 1% /devices
    /tmp/dev 1.9G 560K 1.9G 1% /dev
    10.2.3.251:/export/jumpstart/install
                           20G 1.1G 18G 6% /cdrom
    fd 0K 0K 0K 0% /dev/fd
    10.2.3.251:/export/jumpstart/config/dc-mvncrmas2
                           20G 1.1G 18G 6% /tmp/sysid_config.141
    /usr/sbin/install.d/install_config
                           20G 1.1G 18G 6% /tmp/_install_config
    # cd /cdrom
    # ls rules.ok
    rules.ok
    # ls -la
    total 202
    drwxr-xr-x 5 root other 512 Jan 12 20:31 .
    drwxr-xr-x 17 root other 512 Dec 29 16:45 ..
    -r--r--r-- 1 root root 85 Jun 17 2004 .cdtoc
    drwxr-xr-x 5 root other 512 Dec 27 07:21 .install
    lrwxrwxrwx 1 root other 32 Dec 27 06:59 .install_config
    -> ./Solaris_9/Misc/.install_config
    -r--r--r-- 1 root root 462 Dec 27 07:08 .slicemapfile
    -r--r--r-- 1 root root 20 Jun 17 2004 .volume.inf
    -r--r--r-- 1 root other 22 Dec 27 07:21 .volume.inf.2
    -r--r--r-- 1 root root 7052 Jun 17 2004 Copyright
    drwxr-xr-x 2 root other 512 Jan 12 15:28 Profiles
    drwxr-xr-x 8 root root 512 Dec 27 07:20 Solaris_9
    -rw-r--r-- 1 root other 377 Dec 30 04:23 actual_size
    -rwxr-xr-x 1 root other 383 Jan 12 20:31 addclient.sh
    -rwxr-xr-x 1 root other 55475 Dec 29 15:43 check
    -rwxr-xr-x 1 root other 257 Dec 27 07:21 installer
    -rw-r--r-- 1 root other 4808 Jan 12 15:27 rules
    -rw-r--r-- 1 root other 80 Jan 12 16:17 rules.ok
    # cat rules.ok
    any - - Profiles/mvno.profile -
    # version=2 checksum=3435
    # ls -la Profiles/mvno.profile
    -rw-r--r-- 1 root other 492 Jan 12 15:28 Profiles/mvno.profile

    And so on. On the server, we see:

    # showmount -a
    dc-mvncrmas2:/export/jumpstart/install
    dc-mvncrmas2:/export/jumpstart/install/Configs/dc-mvncrmas2
    dc-mvncrmas2:/export/jumpstart/config/dc-mvncrmas2
    dc-mvncrmas2:/export/jumpstart/install/Solaris_9/Tools/Boot
    # grep dc-mvncrmas2 /etc/bootp*
    /etc/bootparams:dc-mvncrmas2
    root=dc-suntools:/export/jumpstart/install/Solaris_9/Tools/Boot
    install=10.2.3.251:/export/jumpstart/install boottype=:in
    sysid_config=10.2.3.251:/export/jumpstart/config/dc-mvncrmas2
    install_config=10.2.3.251:/export/jumpstart/install
    rootopts=:rsize=32768

    It is extremely frustrating, as you can see. The directories all get
    mounted, sysidcfg is seen and used, the client box is configured
    properly, and for some reason, although rules.ok is sitting right
    where it is supposed to be, it is being ignored. I can then proceed
    manually through the install, but this means that all the filesystem
    configuration I've done in my profiles, and all the users/patches/etc
    that get done by finish scripts are going to be done by hand. And I've
    got a lot of these to do.

    When it says it's searching for the "jumpstart directory", watching
    snoop seems to indicate that it is looking for the 'install' parameter
    from bootparams. However, that parameter is clearly defined, and even
    mounted on the system (/cdrom).

    Thanks in advance for any help.

    alex 

    --
Alex Avriette
avriette@gmail.com
-- 
Alex Avriette
avriette@gmail.com
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
  • Next message: GDS: "Network attached storage ideas"
    • Quantcast