stunnel.service is getting failed - "stunnel.service: Consumed 7ms CPU time"

Solution Verified - Updated -

Issue

  • stunnel.service is getting failed.
Aug 31 11:46:54 lab.example.com systemd[1]: stunnel.service: Child 15734 belongs to stunnel.service.
Aug 31 11:46:54 lab.example.com systemd[1]: stunnel.service: Control process exited, code=exited, status=1/FAILURE
Aug 31 11:46:54 lab.example.com systemd[1]: stunnel.service: Got final SIGCHLD for state start-pre.
Aug 31 11:46:54 lab.example.com systemd[1]: stunnel.service: Failed with result 'exit-code'.
Aug 31 11:46:54 lab.example.com systemd[1]: stunnel.service: Service will not restart (restart setting)
Aug 31 11:46:54 lab.example.com systemd[1]: stunnel.service: Changed start-pre -> failed
Aug 31 11:46:54 lab.example.com systemd[1]: stunnel.service: Job 10689 stunnel.service/start finished, result=failed
Aug 31 11:46:54 lab.example.com systemd[1]: Failed to start TLS tunnel for network daemons.
Aug 31 11:46:54 lab.example.com systemd[1]: stunnel.service: Unit entered failed state.
Aug 31 11:46:54 lab.example.com systemd[1]: stunnel.service: Consumed 7ms CPU time.

Environment

  • Red Hat Enterprise Linux (RHEL) 9
  • Stunnel
  • Systemd

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content