Unable to rebuild job

[Budianto]

I have a jenkins server which jenkins was upgraded from version 2.220 to 2.387.1, all plugins have been upgraded.

When I rebuilt jobs, it gave me these output:

Started by user abc
Running as SYSTEM
Building in workspace /var/lib/jenkins/workspace/DEF_GW_ENROLL_USER_PREPROD
[DEF_GW_ENROLL_USER_PREPROD] $ /bin/bash -x /tmp/jenkins81696621479514690.sh
+ export SSH_CONF=/var/lib/jenkins/.ssh/config/ssh_config_preprod-ue1
+ SSH_CONF=/var/lib/jenkins/.ssh/config/ssh_config_preprod-ue1
+ echo PREPROD
PREPROD
+ export targets=batch-host
+ targets=batch-host
+ for host in '$targets'
+ ssh -F /var/lib/jenkins/.ssh/config/ssh_config_preprod-ue1 batch-host 'sudo python add_user_pastdated.py web.pre.domain.com abc1234 1 target.internal.domain.com false AUTHSERVER_V1R1 KPREHA_002 8  PST true'
ssh_exchange_identification: Connection closed by remote host
Build step 'Execute shell' marked build as failure
[WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] Skipped based on build state FAILURE
Finished: FAILURE

I've tried to do a manual ssh, by copying the config file from /var/lib/jenkins/.ssh/config/ssh_config_preprod-ue1 to ~/.ssh/, and then run the ssh command, the connection was successfully made, I was able to enter the server.

The jenkins.log is empty, and the ssh plugins show no error message, so I have no clues at the moment.

What possibly could be the root cause?

[Dirk Heinrichs]

Am Samstag, dem 08.04.2023 um 16:45 -0700 schrieb Budianto:

What possibly could be the root cause?

Well, it's your remote host that closed the connection, isn't it?

HTH...

Dirk

-- 

Dirk Heinrichs

Senior Systems Engineer, Delivery Pipeline

OpenText ™ Discovery | Recommind

Phone: +49 2226 15966 18

Email: dhei...@opentext.com

Website: www.recommind.de

Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach

Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet.

[Pavel Zaikin]

Add -vvv to the ssh command and you will see the error message. (Possible authentication algorithm issue)

Like this `ssh -vvv -F /path/to/ssh/config ...`

вс, 9 апр. 2023 г. в 04:30, Budianto <budia...@gmail.com>:

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d4daeb8b-4d9b-467b-90ae-331344935053n%40googlegroups.com.

--

Pavel Zaikin

https://github.com/zztalker

[Budianto]

Thanks Dirk and Pavel, your answers really helped me to find the root cause.

So, the manual ssh that I did before was run against an incorrect hostname. Well, the config file stores a lot of hostnames, and the hostname naming is quite similar to one another.

But, once I run against the correct one, I finally found out the server was turned off, and after I turned it on, the pipeline is now running properly.