more_set _headers not working

Version of nginx-mod-headers-more is 0.33-4 for archlinuxarm.org ( https://archlinuxarm.org/packages/armv7h/nginx-mod-headers-more )
Version of related software: nginx-mainline is 1.15.6-1 (https://archlinuxarm.org/packages/armv7h/nginx-mainline )

When using more_set_headers in the nginx.conf file the nginx service will not restart.

from /etc/nginx/nginx.conf
server {
listen 80;
server_name localhost;

    #charset koi8-r;

    #access_log  logs/host.access.log  main;

    location / {
        more_set_headers 'Server: what';
        root   /usr/share/nginx/html;
        index  index.html index.htm;
    }

Returns from attempt to start nginx.service

[root@alarm ~]# systemctl stop nginx.service
[10817.949211] audit: type=1131 audit(1544210399.639:50): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nginx comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[root@alarm ~]# systemctl start nginx.service
[10826.122931] audit: type=1130 audit(1544210407.811:51): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nginx comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xe" for details.
[root@alarm ~]# systemctl status nginx.service

• nginx.service - A high performance web server and a reverse proxy server
  Loaded: loaded (/usr/lib/systemd/system/nginx.service; disabled; vendor pres>
  Active: failed (Result: exit-code) since Fri 2018-12-07 19:20:07 UTC; 1min 1>
  Process: 328 ExecStart=/usr/bin/nginx -g pid /run/nginx.pid; error_log stderr>

Dec 07 19:20:07 alarm systemd[1]: Starting A high performance web server and a >
Dec 07 19:20:07 alarm nginx[328]: 2018/12/07 19:20:07 [emerg] 328#328: unknown >
Dec 07 19:20:07 alarm systemd[1]: nginx.service: Control process exited, code=e>
Dec 07 19:20:07 alarm systemd[1]: nginx.service: Failed with result 'exit-code'.
Dec 07 19:20:07 alarm systemd[1]: Failed to start A high performance web server>

[root@alarm ~]# journalctl -xe

-- The result is failed.
Dec 07 19:20:07 alarm audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4>
Dec 07 19:20:07 alarm kernel: audit: type=1130 audit(1544210407.811:51): pid=1 >
Dec 07 19:22:02 alarm systemd[1]: Starting A high performance web server and a >
-- Subject: Unit nginx.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit nginx.service has begun starting up.
Dec 07 19:22:02 alarm nginx[337]: 2018/12/07 19:22:02 [emerg] 337#337: unknown >
Dec 07 19:22:02 alarm systemd[1]: nginx.service: Control process exited, code=e>
Dec 07 19:22:02 alarm systemd[1]: nginx.service: Failed with result 'exit-code'.
Dec 07 19:22:02 alarm systemd[1]: Failed to start A high performance web server>
-- Subject: Unit nginx.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit nginx.service has failed.

-- The result is failed.
Dec 07 19:22:02 alarm audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4>
Dec 07 19:22:02 alarm kernel: audit: type=1130 audit(1544210522.724:52): pid=1 >

Start with the reported nginx.conf snippet and the nginx.service startup command. Check the complete nginx error output, which is truncated in the report, and verify whether the issue belongs to nginx-mod-headers-more rather than lua-nginx-module. Done means identifying a reproducible cause or confirming the configuration works with the relevant module and versions.