-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
Armbian ` 22.02.1` with Linux `5.15.25-sunxi`.
jenkins/binary,now ` 2.348`
Hello,
I've been trying to install Jenkins controller on an `armhf` machine, and it does not go up to the end because of a timeout.
The machine is not powerful (as most of the ` armhf` machines (there are a few exceptions of course), so... Would it be possible to have a longer timeout for this architecture by default when installing the package?
Here is what the initial installation gives me:
Les NOUVEAUX paquets suivants seront installés : jenkins 0 mis à jour, 1 nouvellement installés, 0 à enlever et 0 non mis à jour. Il est nécessaire de prendre 87,4 Mo dans les archives. Après cette opération, 91,0 Mo d'espace disque supplémentaires seront utilisés. Réception de :1 https://pkg.jenkins.io/debian binary/ jenkins 2.348 [87,4 MB] 87,4 Mo réceptionnés en 23s (3 874 ko/s) Sélection du paquet jenkins précédemment désélectionné. (Lecture de la base de données... 44883 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../archives/jenkins_2.348_all.deb ... Dépaquetage de jenkins (2.348) ... Paramétrage de jenkins (2.348) ... Created symlink /etc/systemd/system/multi-user.target.wants/jenkins.service → /lib/systemd/system/jenkins.service. Job for jenkins.service failed because a timeout was exceeded. See "systemctl status jenkins.service" and "journalctl -xe" for details. invoke-rc.d: initscript jenkins, action "start" failed. ● jenkins.service - Jenkins Continuous Integration Server Loaded: loaded (/lib/systemd/system/jenkins.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: timeout) since Wed 2022-05-18 21:38:28 CEST; 83ms ago Process: 30586 ExecStart=/usr/bin/jenkins (code=exited, status=143) Main PID: 30586 (code=exited, status=143) Status: "Jenkins stopped" CPU: 2min 23.410s dpkg: erreur de traitement du paquet jenkins (--configure) : installed jenkins package post-installation script subprocess returned error exit status 1 Des erreurs ont été rencontrées pendant l'exécution : jenkins E: Sub-process /usr/bin/dpkg returned an error code (1)
Later on, when I try to relaunch Jenkins, here is what I get:
mai 23 16:17:18 orangepizero jenkins[1513]: WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.vmplugin.v7.Java7$1 mai 23 16:17:18 orangepizero jenkins[1513]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations mai 23 16:17:18 orangepizero jenkins[1513]: WARNING: All illegal access operations will be denied in a future release mai 23 16:18:02 orangepizero systemd[1]: jenkins.service: start operation timed out. Terminating. Job for jenkins.service failed because a timeout was exceeded. See "systemctl status jenkins.service" and "journalctl -xe" for details. poddingue@orangepizero:~$ mai 23 16:18:06 orangepizero systemd[1]: jenkins.service: Failed with result 'timeout'. mai 23 16:18:06 orangepizero systemd[1]: Failed to start Jenkins Continuous Integration Server. mai 23 16:18:06 orangepizero systemd[1]: jenkins.service: Consumed 2min 36.313s CPU time. mai 23 16:18:06 orangepizero sudo[1504]: pam_unix(sudo:session): session closed for user root mai 23 16:18:06 orangepizero systemd[1]: jenkins.service: Scheduled restart job, restart counter is at 1. mai 23 16:18:06 orangepizero systemd[1]: Stopped Jenkins Continuous Integration Server. mai 23 16:18:06 orangepizero systemd[1]: jenkins.service: Consumed 2min 36.313s CPU time. mai 23 16:18:06 orangepizero systemd[1]: Starting Jenkins Continuous Integration Server... mai 23 16:18:11 orangepizero jenkins[1622]: Running from: /usr/share/java/jenkins.war
Thanks.
