Topic
  • 3 replies
  • Latest Post - ‏2012-10-25T14:56:33Z by mmveiga
robinsguk
robinsguk
46 Posts

Pinned topic Nim customoization script - logging

‏2012-10-17T12:11:31Z |
Hello,

AIX 6.1.

I specify a customization script to run after a nimP_bosinst using a mksysb which cleans up file systems etc. It doesn't appear to be executing as I'd expect using NIM.

If I log in to the LPAR and run the script it works as designed.

Does the nim server log the execution of the customization script anywhere so that I can investigate this?

Thanks

Glenn
Updated on 2012-10-25T14:56:33Z at 2012-10-25T14:56:33Z by mmveiga
  • teletype
    teletype
    27 Posts

    Re: Nim customoization script - logging

    ‏2012-10-25T06:56:02Z  
    Did you make de bosinst and the script in the same nim statement like:
    
    nim -o bosinst -a script=<value> ... <standalone>
    

    Or dit you us two sepperate nim commands?
    Did you look in /var/adm/ras/nimlog (alog file)?
    Is the name resolving on the client correct after the bosinst?
    Maybe you can do an
    
    exec 1>/tmp/logfile exec 2>&1
    

    in the beginning of your script and a cat of that logfile at the end?

    Hope this helps
  • teletype
    teletype
    27 Posts

    Re: Nim customoization script - logging

    ‏2012-10-25T06:58:56Z  
    • teletype
    • ‏2012-10-25T06:56:02Z
    Did you make de bosinst and the script in the same nim statement like:
    <pre class="jive-pre"> nim -o bosinst -a script=<value> ... <standalone> </pre>
    Or dit you us two sepperate nim commands?
    Did you look in /var/adm/ras/nimlog (alog file)?
    Is the name resolving on the client correct after the bosinst?
    Maybe you can do an
    <pre class="jive-pre"> exec 1>/tmp/logfile exec 2>&1 </pre>
    in the beginning of your script and a cat of that logfile at the end?

    Hope this helps
    You should cat it in a different session ofcource
  • mmveiga
    mmveiga
    78 Posts

    Re: Nim customoization script - logging

    ‏2012-10-25T14:56:33Z  
    Glenn,

    Have you tried the "showlog" operation?

    
    nim -o showlog -a full_log=yes -a log_type=script CLIENT_HOSTNAME
    


    or

    
    nim -o showlog -a full_log=yes -a log_type=bosinst CLIENT_HOSTNAME
    

    Hope that helps,

    Marcelo.