Systemd sends "Executing ..." message to the socket instead of logging it

Solution Verified - Updated -

Issue

  • systemd sends "Executing ..." to the socket instead of logging it
  • When the systemd.socket initializes the service, systemd is injecting "Executing: some command line" into the stream instead of logging it
  • systemd transmits additional data through the socket and causes the receiving application to crash:

    # dbtest % telnet localhost 26120
    Trying ::1...
    Connected to localhost.
    Escape character is '^]'.
    Executing: /test/ultra45/ultra/local/bin/hl7recv -e LINK=sbh_oe,TRIPLEG=/test/ultra45/ultra -c /test/ultra45/ultra/etc/hl7/hl7recv.conf
    
  • When we submit a print job to the CUPS server via LPD, the queue goes down and CUPS does not create the job.

    bash-4.2# qchk -Ppr12
    Queue   Dev   Status    Job Files              User         PP %   Blks  Cp Rnk
    ------- ----- --------- --- ------------------ ---------- ---- -- ----- --- ---
    pr12  @ppri READY
    pr12: Executing: /usr/lib/cups/daemon/cups-lpd
    pr12: Executing: /usr/lib/cups/daemon/cups-lpd
    

Environment

  • Red Hat Enterprise Linux 7.3
  • systemd-219-30

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