1 Reply Latest reply on Jan 28, 2011 2:57 AM by Pedro José Barbero Iglesias

    "ERROR nsh:fg:1: no job control in this shell." during Snapshot Job execution.

      Hello everyone,

       

      I hope one of you can tell me what is this error and  how I can solve it .I got this error in job logs after executing  Snapshot Job over a Linux machine trying to get inventory information.

       

      Here is the log that contains the error last line:

       

      ##################################################################################################################################

      Info     Jan 26, 2011 4:08:49 PM    Snapshot job 'Snapshot Job for Linux'  Started taking snapshot of component 'BL - Linux Inventory (ltest101)'

      Info     Jan 26, 2011 4:08:49 PM    Snapshot job 'Snapshot Job for Linux'  Started taking snapshot of component 'BL - Linux Inventory (ltest101)'  part 'Linux Configuration'

      Info     Jan 26, 2011 4:08:50 PM    Snapshot job 'Snapshot Job for Linux'  succeeded for component 'BL - Linux Inventory (ltest101)' part 'Linux  Configuration' on server 'ltest101'

      Info     Jan 26, 2011 4:08:50 PM    Snapshot job 'Snapshot Job for Linux'  Started taking snapshot of component 'BL - Linux Inventory (ltest101)'  part 'RPMs'

      Info     Jan 26, 2011 4:09:00 PM    Snapshot job 'Snapshot Job for Linux'  succeeded for component 'BL - Linux Inventory (ltest101)' part 'RPMs' on  server 'ltest101'

      Info     Jan 26, 2011 4:09:00 PM    Snapshot job 'Snapshot Job for Linux'  Started taking snapshot of component 'BL - Linux Inventory (ltest101)'  part 'System Info'

      Info     Jan 26, 2011 4:09:04 PM    Snapshot job 'Snapshot Job for Linux'  succeeded for component 'BL - Linux Inventory (ltest101)' part 'System  Info' on server 'ltest101'

      Error    Jan 26, 2011 4:08:50 PM    nsh:fg:1: no job control in this shell.

      ##################################################################################################################################

       

       

      I  have been getting this error in a test envioroment where there are only  two test servers,one Linux and the other one Solaris, and I got the  same error on both.What is this error about? I was googling around and  find something that says that this has something to do with "monitor  mode" but I don't undertstand well what it means.

       

       

      Thanks in avanced any king or help It would be aprecciated.