Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-64302

Couldn't open /etc/securetty

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • packaging
    • None
    • Ubuntu 20.04.1 LTS

      After updating to the latest Jenkins version the service refuses to start:

       

      Nov 24 10:38:13 ubu-build sudo[1294]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

       

          [JENKINS-64302] Couldn't open /etc/securetty

          Kees de Kooter created issue -
          Kees de Kooter made changes -
          Description Original: After updating to the latest Jenkins version the service refuses to start:

           

          Nov 24 10:38:13 ubu-build sudo[1294]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

                      		New: After updating to the latest Jenkins version the service refuses to start:

           
          {code:java}
          Nov 24 10:38:13 ubu-build sudo[1294]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory{code}
           

          Tim Jacomb added a comment -

          maybe relates to https://askubuntu.com/a/1239584?

          Need more information though, did you just upgrade to 20.04? has it worked previously?

          cc markewaite

          Tim Jacomb added a comment - maybe relates to https://askubuntu.com/a/1239584? Need more information though, did you just upgrade to 20.04? has it worked previously? cc markewaite

          Kees de Kooter added a comment -

          It did work previously.

          In the meantime I found out that the actual issue seemed to be the Java version on the machine. After a downgrade to JRE 8 the service started just fine.

          Kees de Kooter added a comment - It did work previously. In the meantime I found out that the actual issue seemed to be the Java version on the machine. After a downgrade to JRE 8 the service started just fine.

          Kees de Kooter added a comment -

          A downgrade to JRE 8 fixed the issue

          Kees de Kooter added a comment - A downgrade to JRE 8 fixed the issue
          Kees de Kooter made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            Unassigned Unassigned
            kdekooter Kees de Kooter
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: