Automic Workload Automation

  • Private Community

  • 1.  Jobs nor run due to error (line 4: -bash -s: command not found)

    Posted Feb 15, 2016 08:09 AM
    Hi, can you help me to identify what is this error and what is the solution> this is a unix job. /app/uc4/agents/linux/bin/./../temp/JAADAGIU.TXT: line 4: -bash -s: command not found


  • 2.  Jobs nor run due to error (line 4: -bash -s: command not found)

    Posted Feb 15, 2016 09:21 AM
    Hard to say without some additional info.  Are you selecting a shell on the UNIX tab?  Or is the script you are trying to run trying to use the bash shell?  Is that shell available on the server you are trying to run on?

    I did a quick Google search on "What is -s flag in bash" and didn't find anything.  Not sure where that is coming from - I assume the script.  Are you sure that is valid? 

    Can you run the script from the command line without issue?

    Turning on "verbose" is something that often helps me when I am troubleshooting scripts.


  • 3.  Jobs nor run due to error (line 4: -bash -s: command not found)

    Posted Feb 15, 2016 12:51 PM
    Best would be if you can show us the generated script.

    IMHO bash is reporting, that a command named '-s' does not exist. It's not a parameter to the bash itself.

    Possibly the line break character (\) that allows to spread long unix commands has not been specified.

    Like:
    ./cmd.sh -t arg1 \
    -x arg2
    -s arg3

    This could raise an error like you stated 


  • 4.  Jobs nor run due to error (line 4: -bash -s: command not found)

    Posted Feb 16, 2016 04:13 AM
    Hi,


     
    job calling the script shell and when i tried to re run it ended_ok but still no log created and if i tried to run via unix its work. then i change the configuration and new message appears


    ssh: Could not resolve the hostname ***-xx-xx-x : Name or service not Known running:


    What is the solution for this error.


  • 5.  Jobs nor run due to error (line 4: -bash -s: command not found)

    Posted Feb 16, 2016 06:46 AM
    Hi NoahGochuico603609 

    These are not Automic errors but Unix messages. This one is likely an ssh command tried to connect to a host that couldn't be resolved in the DNS. For these messages google is a better place to find answers.

    If you don't know what exactly is being executed on Unix, write the following line at the top of the preprocess script:
    set -x

    Alternatively you can set the -x also in the "Unix Attribute" tab of the job (Shell parameters or something like that, I don't have access to an AE system right now). 

    The report will be way more chatty then.