[Bug 228438] security/acme-client: dies with "bad exit: netproc(29011): 1\0"

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228438

            Bug ID: 228438
           Summary: security/acme-client: dies with "bad exit:
                    netproc(29011): 1\0"
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: brnrd at freebsd.org
          Reporter: dch at freebsd.org
          Assignee: brnrd at freebsd.org
             Flags: maintainer-feedback?(brnrd at freebsd.org)
 Attachment #193632 text/plain
         mime type:

Created attachment 193632
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=193632&action=edit
dtruss log FTW

dtruss log attached for a failed renewal:

- 11.1Rp10 amd64
- security/acme-client 0.1.16_3 from latest pkg.freebsd.org 

# /usr/local/share/dtrace-toolkit/dtruss -f -l /usr/local/bin/acme-client -b
-mnN -vvv -s -F \                                                              
                                                                               
                                               -e \                            
                                                                               
                                                                               
                                                                               
         -C /var/www/acme  \                                                   
                                                                               
                                                                               
                                                 i09.example.com
www.example.com > /tmp/acme.dtruss.log 2>&1

This seems to break on both existing production systems and on a fresh test
install; this log is from a fresh install. Reverting to 

AFAICT the port now statically includes libressl and therefore should work fine
in a "normal openssl" deployed environment.

previous working release (when custom built with default SSL=libressl ports
tree) is 0.1.16_2.

-- 
You are receiving this mail because:
You are the assignee for the bug.