# HAProxy dataplaneapi Error

**URL:** <https://discourse.haproxy.org/t/haproxy-dataplaneapi-error/4223>\
**Category:** Help!\
**Created:** [August 21, 2019, 9:46am UTC](https://discourse.haproxy.org/t/haproxy-dataplaneapi-error/4223 "2019-08-21T09:46:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![void\_in](https://avatars.discourse-cdn.com/v4/letter/v/3ec8ea/32.png) [@void\_in](https://discourse.haproxy.org/u/void_in)\
**Post date:** [August 21, 2019, 9:46am UTC](https://discourse.haproxy.org/t/haproxy-dataplaneapi-error/4223/1 "2019-08-21T09:46:15Z")

</div>

Good morning/evening. We are using the new HAProxy dataplane API in order to perform runtime changes to the HAProxy configuration. It is working perfectly fine on one server but on another, it is generating the error “Runtime API not configured, not using it”. Due to this, the dataplaneapi binary is not able to read the /etc/haproxy/haproxy.cfg file.

Following are the details:

> # haproxy -vv
> 
> HA-Proxy version 2.0.5 2019/08/16 - [https://haproxy.org/](https://haproxy.org/)  
> Build options :  
> TARGET = linux-glibc  
> CPU = generic  
> CC = gcc  
> CFLAGS = -O2 -g -fno-strict-aliasing -DTCP\_USER\_TIMEOUT=18  
> OPTIONS = USE\_PCRE=1 USE\_PCRE\_JIT=1 USE\_THREAD=1 USE\_OPENSSL=1 USE\_ZLIB=1 USE\_SYSTEMD=1
> 
> Feature list : +EPOLL -KQUEUE -MY\_EPOLL -MY\_SPLICE +NETFILTER +PCRE +PCRE\_JIT -PCRE2 -PCRE2\_JIT +POLL -PRIVATE\_CACHE +THREAD -PTHREAD\_PSHARED -REGPARM -STATIC\_PCRE -STATIC\_PCRE2 +TPROXY +LINUX\_TPROXY +LINUX\_SPLICE +LIBCRYPT +CRYPT\_H -VSYSCALL +GETADDRINFO +OPENSSL -LUA +FUTEX +ACCEPT4 -MY\_ACCEPT4 +ZLIB -SLZ +CPU\_AFFINITY +TFO +NS +DL +RT -DEVICEATLAS -51DEGREES -WURFL +SYSTEMD -OBSOLETE\_LINKER +PRCTL +THREAD\_DUMP -EVPORTS
> 
> Default settings :  
> bufsize = 16384, maxrewrite = 1024, maxpollevents = 200
> 
> Built with multi-threading support (MAX\_THREADS=64, default=56).  
> Built with OpenSSL version : OpenSSL 1.0.2k-fips 26 Jan 2017  
> Running on OpenSSL version : OpenSSL 1.0.2k-fips 26 Jan 2017  
> OpenSSL library supports TLS extensions : yes  
> OpenSSL library supports SNI : yes  
> OpenSSL library supports : SSLv3 TLSv1.0 TLSv1.1 TLSv1.2  
> Built with network namespace support.  
> Built with transparent proxy support using: IP\_TRANSPARENT IPV6\_TRANSPARENT IP\_FREEBIND  
> Built with zlib version : 1.2.7  
> Running on zlib version : 1.2.7  
> Compression algorithms supported : identity(“identity”), deflate(“deflate”), raw-deflate(“deflate”), gzip(“gzip”)  
> Built with PCRE version : 8.32 2012-11-30  
> Running on PCRE version : 8.32 2012-11-30  
> PCRE library supports JIT : yes  
> Encrypted password support via crypt(3): yes
> 
> Available polling systems :  
> epoll : pref=300, test result OK  
> poll : pref=200, test result OK  
> select : pref=150, test result OK  
> Total: 3 (3 usable), will use epoll.
> 
> Available multiplexer protocols :  
> (protocols marked as cannot be specified using ‘proto’ keyword)  
> h2 : mode=HTX side=FE|BE mux=H2  
> h2 : mode=HTTP side=FE mux=H2  
> : mode=HTX side=FE|BE mux=H1  
> : mode=TCP|HTTP side=FE|BE mux=PASS
> 
> Available services : none
> 
> Available filters :  
> [SPOE] spoe  
> [COMP] compression  
> [CACHE] cache  
> [TRACE] trace
> 
> ./dataplaneapi  
> time=“2019-08-21T14:42:19+05:00” level=warning msg=“Runtime API not configured, not using it”

---

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [August 21, 2019, 1:07pm UTC](https://discourse.haproxy.org/t/haproxy-dataplaneapi-error/4223/2 "2019-08-21T13:07:53Z")

</div>

Crossposted on the mailing list:

[https://www.mail-archive.com/haproxy@formilux.org/msg34749.html](https://www.mail-archive.com/haproxy@formilux.org/msg34749.html)

---

<div class="post-metadata">

**Author:** ![void\_in](https://avatars.discourse-cdn.com/v4/letter/v/3ec8ea/32.png) [@void\_in](https://discourse.haproxy.org/u/void_in)\
**Post date:** [August 22, 2019, 10:51am UTC](https://discourse.haproxy.org/t/haproxy-dataplaneapi-error/4223/3 "2019-08-22T10:51:58Z")

</div>

For anyone who might have the same problem, my issue was the CR characters inserted by the windows editor which although can be read by the HAProxy, the dataplaneapi was having problem reading the config file. Therefore, make sure the configuration file has the Unix compatible new line chars.

Thanks a lot.