errors in bdii-update.log after last config and startup script changes

Description

Errors of this kind show up in the bdii-update.log file after the latest changes in configuration, I believe related to runtime configuration but not limited to:

[2018-10-18 14:23:31] [InfosysHelper] [VERBOSE] [329775] New fifo created: /var/run/arc/infosys//ldif-provider.fifo
[2018-10-18 14:23:31] [InfosysHelper] [INFO] [329775] Start waiting for notification from A-REX's infoprovider
[2018-10-18 14:24:23] [InfosysHelper] [INFO] [329775] Notification received from A-REX's infoprovider
[2018-10-18 14:24:23] [InfosysHelper] [VERBOSE] [329775] Using ldif generator script: /var/run/arc/infosys//ldif-provider.sh
[2018-10-18 14:24:23] [InfosysHelper] [VERBOSE] [329980] New fifo created: /var/run/arc/infosys//ldif-provider.fifo
[2018-10-18 14:24:23] [InfosysHelper] [INFO] [329980] Start waiting for notification from A-REX's infoprovider
[2018-10-18 14:25:25] [InfosysHelper] [INFO] [329980] Notification received from A-REX's infoprovider
[2018-10-18 14:25:25] [InfosysHelper] [VERBOSE] [329980] Using ldif generator script: /var/run/arc/infosys//ldif-provider.sh
Can't exec "/etc/init.d/a-rex": No such file or directory at /var/tmp/arc/bdii/provider/arc-glue-bdii-ldif line 208.
Use of uninitialized value $glueservicestatusinfo in scalar chomp at /var/tmp/arc/bdii/provider/arc-glue-bdii-ldif line 209.
Use of uninitialized value $glueservicestatusinfo in concatenation (.) or string at /var/tmp/arc/bdii/provider/arc-glue-bdii-ldif line 642.
2018-10-18 14:25:25,098: [WARNING] ldap_add: Invalid syntax (21)
2018-10-18 14:25:25,098: [WARNING] additional info: glue2endpointhealthstateinfo: value #0 invalid per syntax
2018-10-18 14:25:25,098: [WARNING] ldap_add: Object class violation (65)
2018-10-18 14:25:25,099: [WARNING] additional info: object class 'GLUE2ExecutionEnvironment' requires attribute 'GLUE2ExecutionEnvironmentConnectivityIn'
[2018-10-18 14:25:35] [InfosysHelper] [VERBOSE] [330219] New fifo created: /var/run/arc/infosys//ldif-provider.fifo
[2018-10-18 14:25:35] [InfosysHelper] [INFO] [330219] Start waiting for notification from A-REX's infoprovider
[2018-10-18 14:26:26] [InfosysHelper] [INFO] [330219] Notification received from A-REX's infoprovider
[2018-10-18 14:26:26] [InfosysHelper] [VERBOSE] [330219] Using ldif generator script: /var/run/arc/infosys//ldif-provider.sh
[2018-10-18 14:26:26] [InfosysHelper] [VERBOSE] [330403] New fifo created: /var/run/arc/infosys//ldif-provider.fifo

The errors from arc-glue-bdii-ldif actually come from this line: https://source.coderefinery.org/nordugrid/arc/blob/master/src/services/a-rex/infoproviders/glue-generator.pl#L208 I guess this requires some magic to decide if to use systemd or not. @ellert ?

The GLUE2 warnings are new to me and I need to investigate more, these need to be fixed in ARC1ClusterInfo probably

This is on Centos7 with a minimalistic arc.conf:

[common]
x509_host_key = /etc/grid-security/testCA-hostkey.pem
x509_host_cert = /etc/grid-security/testCA-hostcert.pem
hostname = 158.37.63.12


[authgroup:dockertest]
subject= /DC=org/DC=nordugrid/DC=ARC/O=TestCA/CN=Test Cert 10171237

[mapping]
#unixmap = nobody:nobody authgroup zero
unixmap = grid:grid authgroup dockertest
#unixmap = dockerroot:dockerroot authgroup dockertest

[lrms]
lrms=condor
condor_bin_path=/usr/bin
[arex]
runtimedir = /var/spool/arc/runtime

[arex/ws]
[arex/ws/emies]
allowaccess = dockertest

[infosys]
[infosys/ldap]
[infosys/nordugrid]

[infosys/glue1]
resource_location=Oslo, Norway
resource_latitude=55.5555
resource_longitude=10.1111
cpu_scaling_reference_si00=2400
processor_other_description=Cores=3,Benchmark=9.8-HEP-SPEC06
glue_site_web=http://www.ndgf.org
glue_site_unique_id=Oslo Testing

[infosys/cluster]
[infosys/glue2]
[queue:fork]