Failed to stop testeci.service: Interactive Authentication required

Asked

Viewed 146 times

0

I’m trying to restart a service in the successful execution of a JOB in Jenkins. Everything works except the fact that Jenkins can’t execute the command systemctl restart testeci.service. It returns me the error below:

Failed to stop logicaldelivery.service: Interactive authentication required.
See system logs and 'systemctl status testeci.service' for details.
Failed to start testeci.service: Interactive authentication required.
See system logs and 'systemctl status testeci.service' for details.
Failed to restart testeci.service: Interactive authentication required.
See system logs and 'systemctl status testeci.service' for details.

When executing the user command on the terminal, it works. The problem is only when running it via Jenkins.

Someone can help me?

  • I did not understand the reason for the negativity.. If you can inform the reason, thank you.

  • The downvote it’s not mine, but really your question this difficult to help, as far as it seems to me you have not configured your repository or have something ambiguous, I think that for the question to be answered it is always necessary to inform minimum details necessary to reproduce the problem. To summarize, the message just seems to state that you have not configured your testecil.service to authenticate, or the data is incorrect. Try to do what the program asks, run the command systemctl status testeci.service and say what comes back.

  • @Guilhermenascimento I understand, but my problem is exactly this, when executing the command by own terminal everything works... But when part of a job in Jenkins he presents this error. If I type this command, everything will go as it should, but I’d like Jenkins to do it.

  • And is testeci.service found "globally" in any folder that enters the command? Or do you have to type in the folder where it is located?

  • When you manually run you run on your user or SUDO? [

  • No, no SUDO, I created it in the /etc/systemd/system/testeci.service. After that I ran the daemon Reload.

  • Okay, and tried everything I said before?

  • Yes @Guilhermenascimento, it shows that the service is running normally (this is because I ran in hand before systemctl start testeci).

  • Okay, I’ll ask again, tried to put the command systemctl status testeci.service on Jenkins to see what he returns?

  • Sorry @Guilhermenascimento now I understood what I meant. No I did not put. I ran by my user. I will do, thank you

Show 5 more comments
No answers

Browser other questions tagged

You are not signed in. Login or sign up in order to post.