Professional Web Applications Themes

autofs problem - Sun Solaris

We're seeing this on multiple hosts: Sep 24 08:10:33 bingy.acs.uci.edu krtld: [ID 995402 kern.notice] /kernel/fs/autofs: undefined symbol 'mntfs_optprint' Sep 24 08:10:33 bingy.acs.uci.edu krtld: [ID 472681 kern.notice] WARNING: mod_load: cannot load module 'autofs' We have patch 108993-25 installed, along with a bunch of others. Anyone already seen this? I found nothing about it in the archives yesterday....

  1. #1

    Default autofs problem

    We're seeing this on multiple hosts:

    Sep 24 08:10:33 bingy.acs.uci.edu krtld: [ID 995402 kern.notice] /kernel/fs/autofs: undefined symbol 'mntfs_optprint'
    Sep 24 08:10:33 bingy.acs.uci.edu krtld: [ID 472681 kern.notice] WARNING: mod_load: cannot load module 'autofs'

    We have patch 108993-25 installed, along with a bunch of others.

    Anyone already seen this? I found nothing about it in the archives
    yesterday.
    Dan Guest

  2. #2

    Default Re: autofs problem

    Dan Stromberg wrote: 

    I can't speak for Solaris 8, but in Solaris 9 and 10, the symbol
    mntfs_optprint is defined in the file /kernel/fs/mntfs, or
    /kernel/fs/sparcv9/mntfs (for 64-bit kernel), and these files are part
    of the SUNWcsr package and SUNWcarx package for 64-bit.

    If you run:

    /usr/ccs/bin/nm /kernel/fs/mntfs | grep optprint

    or for 64-bit:

    /usr/ccs/bin/nm /kernel/fs/sparcv9/mntfs | grep optprint

    If the suitable one above does not return the symbol mntfs_optprint,
    then maybe the module is broken.

    Try:

    pkgchk -x SUNWcsr 2>&1 | grep mntfs

    or for 64-bit:

    pkgchk -v SUNWcarx 2>&1 | grep mntfs

    And if the suitable one returns a line saying "ERROR", then the file is
    broke.


    If /kernel/fs/autofs is whingeing at boot about a symbol that should be
    defined in /kernel/fs/mntfs (or their 64-bit equivalents), then I
    suspect that the mntfs modules are broke somehow, and that there is no
    problem with 108993-25. You should be able to get them back from the CD
    distro.

    HTH.

    Beardy Guest

  3. #3

    Default Re: autofs problem

    On Wed, 24 Sep 2003 16:13:05 -0700, Beardy wrote:
     
    >
    > I can't speak for Solaris 8, but in Solaris 9 and 10, the symbol
    > mntfs_optprint is defined in the file /kernel/fs/mntfs, or
    > /kernel/fs/sparcv9/mntfs (for 64-bit kernel), and these files are part
    > of the SUNWcsr package and SUNWcarx package for 64-bit.
    >
    > If you run:
    >
    > /usr/ccs/bin/nm /kernel/fs/mntfs | grep optprint
    >
    > or for 64-bit:
    >
    > /usr/ccs/bin/nm /kernel/fs/sparcv9/mntfs | grep optprint
    >
    > If the suitable one above does not return the symbol mntfs_optprint,
    > then maybe the module is broken.
    >
    > Try:
    >
    > pkgchk -x SUNWcsr 2>&1 | grep mntfs
    >
    > or for 64-bit:
    >
    > pkgchk -v SUNWcarx 2>&1 | grep mntfs
    >
    > And if the suitable one returns a line saying "ERROR", then the file is
    > broke.
    >
    >
    > If /kernel/fs/autofs is whingeing at boot about a symbol that should be
    > defined in /kernel/fs/mntfs (or their 64-bit equivalents), then I
    > suspect that the mntfs modules are broke somehow, and that there is no
    > problem with 108993-25. You should be able to get them back from the CD
    > distro.
    >
    > HTH.[/ref]

    Thanks for for your reply.

    I'm getting:

    bingy-root) /usr/ccs/bin/nm /kernel/fs/mntfs | grep optprint
    [44] | 1320| 296|FUNC |LOCL |0 |1 |mntfs_optprint
    bingy-root) pkgchk -x SUNWcsr 2>&1 | grep mntfs
    bingy-root) pkgchk -x SUNWcsr
    bingy-root) echo $?
    0
    bingy-root)

    On a 32 bit machine.

    It's a fresh install, plus automatically applied patches and a few tweaks
    here and there. We haven't (intentionally) done any sort of surgery to
    automounting other than patches.

    Any further suggestions?

    Thanks again.
    Dan Guest

  4. #4

    Default Re: autofs problem (mntfs_optprint)

    Dan Stromberg <nac.uci.edu> writes: 

    Ooo. This should be something with GLOB in it, more like:

    [82] | 1272| 304|FUNC |GLOB |0 |1 |mntfs_optprint

    Check your mntfs file against the Solaris fingerprint database. You
    may have been hacked.

    -- Anton

    Anton Guest

  5. #5

    Default Re: autofs problem (mntfs_optprint)

    Anton Rang wrote: 
    >
    >
    > Ooo. This should be something with GLOB in it, more like:
    >
    > [82] | 1272| 304|FUNC |GLOB |0 |1 |mntfs_optprint
    >
    > Check your mntfs file against the Solaris fingerprint database. You
    > may have been hacked.
    >
    > -- Anton
    >[/ref]

    I concur with Anton. How recently were these systems installed/patched,
    and by whom? Also what was the origin of the patches?

    Beardy Guest

  6. #6

    Default Re: autofs problem

    On Thu, 25 Sep 2003 07:27:53 -0700, Dan Stromberg wrote:
     [/ref]
    >[/ref]

    Adding the latest cluster of recommended patches to our install process
    fixed it - er, at least for the machines we install henceforth.
    Dan Guest

  7. #7

    Default Re: autofs problem

    On Thu, 25 Sep 2003 07:27:53 -0700, Dan Stromberg wrote:
     [/ref][/ref]

    Loading on the recommended patches fixed it.
    Dan Guest

Similar Threads

  1. 2.4.20 autofs: non-toplevel mounts broken?
    By Bob Proulx in forum Debian
    Replies: 2
    Last Post: July 31st, 09:10 PM
  2. Replies: 2
    Last Post: July 17th, 07:27 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139