Weird bug/error in /usr/local/apnscp/resources/playbooks/roles/mail/rspamd/defaults/main.yml

Bug reports
1

Here are some helpful considerations when filing a bug:

  • What version of apnscp are you running?
    [root@cpanel2 playbooks]# cpcmd misc_cp_version
    revision: 8232125102b820206a1ebdc8e285584f00b2c8dd
    timestamp: 1769988959
    ver_maj: 3
    ver_min: 2
    ver_patch: 0
    ver_pre: 823212510-dirty
    dirty: true
    debug: false

  • Which version of RHEL or CentOS are you using?
    Rocky Linux 10

[root@cpanel2 ~]# cd /usr/local/apnscp/resources/playbooks && env ANSIBLE_LOG_PATH=/root/apnscp-bootstrapper.log BOOTSTRAP_SH=/root/resume_apnscp_setup.sh ansible-playbook -l localhost -c local bootstrap.yml
ERROR! We were unable to read either as JSON nor YAML, these are the errors we got from each:
JSON: Expecting value: line 1 column 1 (char 0)

Syntax Error while loading YAML.
found unacceptable key (unhashable type: ‘AnsibleMapping’)

The error appears to be in ‘/usr/local/apnscp/resources/playbooks/roles/mail/rspamd/defaults/main.yml’: line 383, column 23, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

        BAYES_SPAM:
          score: {{ rspamd_scores_bayes_spam }}
                  ^ here

We could be wrong, but this one looks like it might be an issue with
missing quotes. Always quote template expression brackets when they
start a value. For instance:

with_items:
  - {{ foo }}

Should be written as:

with_items:
  - "{{ foo }}"

I for sure did not change this file. I ran this as I am having some other oddities on this new install and thought maybe something missed. (dig / nslookup not working in vps shell error "dlg: error while loading shared libraries: libuv.so.1: cannot open shared object file: No such file or directory)

2

You beat me… :wink:

Came here to report the same.

Mine is a fresh AlmaLinux 10.1 install. I just wiped out the system and tried again without my edits to the /root/apnscp-vars.yml file, same result.

Minimal AlmaLinux install and then this command…

curl https://raw.githubusercontent.com/apisnetworks/apnscp-bootstrapper/master/bootstrap.sh | bash


Do you wish to edit initial configuration? Installation resumes in 30 seconds automatically. [y/n] /usr/local/apnscp/resources/playbooks /usr/local/apnscp ~
ERROR! We were unable to read either as JSON nor YAML, these are the errors we got from each:
JSON: Expecting value: line 1 column 1 (char 0)

Syntax Error while loading YAML.
  found unacceptable key (unhashable type: 'AnsibleMapping')

The error appears to be in '/usr/local/apnscp/resources/playbooks/roles/mail/rspamd/defaults/main.yml': line 383, column 23, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

            BAYES_SPAM:
              score: {{ rspamd_scores_bayes_spam }}
                      ^ here
We could be wrong, but this one looks like it might be an issue with
missing quotes. Always quote template expression brackets when they
start a value. For instance:

    with_items:
      - {{ foo }}

Should be written as:

    with_items:
      - "{{ foo }}"
ERR: Stage 2 bootstrap failed
Run 'cd /usr/local/apnscp/resources/playbooks && env ANSIBLE_LOG_PATH=/root/apnscp-bootstrapper.log BOOTSTRAP_SH=/root/resume_apnscp_setup.sh  ansible-playbook -l localhost -c local bootstrap.yml' to resume
Installation failed

That error is exactly as it says though…

Edit /usr/local/apnscp/resources/playbooks/roles/mail/rspamd/defaults/main.yml line 383 and add the quotes.

3

I added the quotes, ran upcp -a and the quotes didnt go away so he may have fixed it already.

4

Built off the wrong branch. Give it a go now. Install will automatically loop and pull down new code if it hasn’t been manually stopped yet.

5

I can confirm this has been fixed.

System still won’t install but it at least tries/starts to install now.

2026-02-02 08:37:15,688 p=8496 u=root n=dnf.plugin.[fork.9543] | Etckeeper plugin: pre-install
2026-02-02 08:37:17,182 p=8496 u=root n=dnf.[fork.9543] | Cleaning up.
2026-02-02 08:37:17,183 p=8496 u=root n=dnf.[fork.9543] | Plugins were unloaded.
2026-02-02 08:37:17,195 p=8493 u=root n=ansible | ok: [localhost]
2026-02-02 08:37:17,228 p=8493 u=root n=ansible | TASK [Record PostGIS version] **************************************************
2026-02-02 08:37:17,263 p=8493 u=root n=ansible | skipping: [localhost]
2026-02-02 08:37:17,290 p=8493 u=root n=ansible | TASK [pgsql/install : Symlink include/pgsql] ***********************************
2026-02-02 08:37:17,351 p=8493 u=root n=ansible | ok: [localhost]
2026-02-02 08:37:17,380 p=8493 u=root n=ansible | TASK [pgsql/install : alias pgsql] *********************************************
2026-02-02 08:37:17,440 p=8493 u=root n=ansible | ok: [localhost]
2026-02-02 08:37:17,473 p=8493 u=root n=ansible | TASK [Override postgresql.service] *********************************************
2026-02-02 08:37:17,705 p=8493 u=root n=ansible | TASK [systemd/override-config : set_fact] **************************************
2026-02-02 08:37:17,749 p=8493 u=root n=ansible | ok: [localhost]
2026-02-02 08:37:17,778 p=8493 u=root n=ansible | TASK [systemd/override-config : set_fact] **************************************
2026-02-02 08:37:17,809 p=8493 u=root n=ansible | skipping: [localhost]
2026-02-02 08:37:17,837 p=8493 u=root n=ansible | TASK [systemd/override-config : set_fact] **************************************
2026-02-02 08:37:17,874 p=8493 u=root n=ansible | ok: [localhost]
2026-02-02 08:37:17,905 p=8493 u=root n=ansible | TASK [systemd/override-config : set_fact] **************************************
2026-02-02 08:37:17,958 p=8493 u=root n=ansible | ok: [localhost]
2026-02-02 08:37:17,989 p=8493 u=root n=ansible | TASK [systemd/override-config : fail] ******************************************
2026-02-02 08:37:18,020 p=8493 u=root n=ansible | skipping: [localhost]
2026-02-02 08:37:18,048 p=8493 u=root n=ansible | TASK [systemd/override-config : file] ******************************************
2026-02-02 08:37:18,111 p=8493 u=root n=ansible | ok: [localhost]
2026-02-02 08:37:18,143 p=8493 u=root n=ansible | TASK [systemd/override-config : set_fact] **************************************
2026-02-02 08:37:18,184 p=8493 u=root n=ansible | ok: [localhost]
2026-02-02 08:37:18,213 p=8493 u=root n=ansible | TASK [systemd/override-config : Override {{__systemd_service_name}}] ***********
2026-02-02 08:37:18,281 p=8493 u=root n=ansible | included: /usr/local/apnscp/resources/playbooks/roles/common/tasks/write-config.yml for localhost => (item={'group': 'Service', 'vars': {'RuntimeDirectory': 'postgresql'}})
2026-02-02 08:37:18,323 p=8493 u=root n=ansible | TASK [systemd/override-config : Edit /etc/systemd/system/postgresql-16.service.d/override.conf] ***
2026-02-02 08:37:18,435 p=8493 u=root n=ansible | ok: [localhost] => (item=Set Service => RuntimeDirectory = postgresql)
2026-02-02 08:37:18,489 p=8493 u=root n=ansible | TASK [pgsql/install : stat] ****************************************************
2026-02-02 08:37:18,549 p=8493 u=root n=ansible | ok: [localhost]
2026-02-02 08:37:18,581 p=8493 u=root n=ansible | TASK [pgsql/install : Initialize PostgreSQL data dictionary] *******************
2026-02-02 08:37:19,062 p=8493 u=root n=ansible | fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["/usr/pgsql-16/bin/postgresql-16-setup", "initdb"], "delta": "0:00:00.415214", "end": "2026-02-02 08:37:19.046487", "msg": "non-zero return code", "rc": 1, "start": "2026-02-02 08:37:18.631273", "stderr": "", "stderr_lines": [], "stdout": "Initializing database ... ", "stdout_lines": ["Initializing database ... "]}
2026-02-02 08:37:19,065 p=8493 u=root n=ansible | PLAY RECAP *********************************************************************
2026-02-02 08:37:19,065 p=8493 u=root n=ansible | localhost                  : ok=134  changed=1    unreachable=0    failed=1    skipped=98   rescued=0    ignored=0
6

PM me login details to take a look at this server. Once resolved, wipe and reinstall.

7

Per initdb:

# tail -n50 /var/lib/pgsql/16/initdb.log
/usr/pgsql-16/bin/initdb: CPU ISA level is lower than required

via /proc/cpuinfo:

model name      : Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx rdtscp lm constant_tsc arch_perfmon nopl xtopology tsc_reliable nonstop_tsc cpuid tsc_known_freq pni pclmulqdq vmx ssse3 cx16 pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm pti ssbd ibrs ibpb stibp tpr_shadow ept vpid fsgsbase tsc_adjust smep arat vnmi md_clear flush_l1d arch_capabilities
vmx flags       : vnmi invvpid ept_x_only tsc_offset vtpr mtf ept vpid unrestricted_guest ple ept_violation_ve
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit retbleed bhi spectre_v2_user its

You’ll need a CPU launched within the last decade to run PostgreSQL 16. E5-2670 was released in 2012.

1 Like