#214 SSH jobs goes to not a valid identifier

[Sebastien DURIS]

Hello

Since 2.5.3 update i can't launch ssh jobs with parameters, for exemple :
2023-04-09 09:22:23.838+02:00 [MAIN] [OrderResumed] id=#2023-04-09#D00543530002-2023040833785694428!-Weekly_schedule|monoxpi, pos=0/lock:0/fork+monoxpi:1, Job=apt_upgrade_monoxpi
2023-04-09 09:22:24.020+02:00 [MAIN] [OrderProcessingStarted] id=#2023-04-09#D00543530002-2023040833785694428!-Weekly_schedule|monoxpi, pos=0/lock:0/fork+monoxpi:1, Job=apt_upgrade_monoxpi, Agent(url=http://127.0.0.1:4445, name=js7, time=2023-04-09 09:22:23.900+02:00)
2023-04-09 09:22:23.900+02:00 [MAIN] [Start] Job=apt_upgrade_monoxpi, Agent (url=http://127.0.0.1:4445, id=JS7_agent, name=js7)
2023-04-09 09:22:24.303+02:00 [STDOUT] [INFO]Job Parameterization:
[INFO]Resulting Arguments:
[INFO] command=apt-get upgrade -y (source=JOB)
[INFO] ignore_stderr=true (source=JOB)
[INFO] auth_method=PASSWORD (source=JOB SSHProviderArguments)
[INFO] server_alive_interval=5 (source=JOB SSHProviderArguments)
[INFO] simulate_shell=true (source=JOB SSHProviderArguments)
[INFO] host=monoxpi (source=JOB SSHProviderArguments)
[INFO] user=root (source=JOB SSHProviderArguments)
[INFO] password=** (source=JOB SSHProviderArguments)
[INFO][connect]monoxpi:22 ...
2023-04-09 09:22:31.671+02:00 [STDOUT] [INFO][connected][monoxpi:22]Server Identity=OpenSSH_8.4p1 Raspbian-5+deb11u1, OS=Linux, Shell=UNIX
[INFO][execute commands]apt-get upgrade -y
[INFO]command]apt-get upgrade -y
[INFO][stdOut] bash: line 1: export: `-y': not a valid identifier
[INFO][returnCode] 1

i tryed with ssh command and ssh scrupt with parameter, it's the same result.

can you help me to resolve this please ?

[Andreas]

Hi Sebastian,
sorry about this, in fact this bug is confirmed.

As a workaround add the following argument to your SSH job:

• Unix
  command_delimiter = ;
• Windows
  command_delimiter = &

This issue is tracked with:
JITL- 712: SHS job broken for missing command delimiter

Best regards
Andreas

[Sebastien DURIS]

Hi,
thank you for your quick answer.

just for lazy guys, just revert to 2.5.2 agents who launch ssh jobs do also the job :)

have a nice day

[Andreas]

Hi Sebastian,
sorry about this, in fact this bug is confirmed.

As a workaround add the following argument to your SSH job:

• Unix
  command_delimiter = ;
• Windows
  command_delimiter = &

This issue is tracked with:
JITL- 712: SHS job broken for missing command delimiter

Best regards
Andreas