Icinga / Icinga/icinga2

Ümläüts in identifiers fail config parsing with "EOF"

Open
#10,867 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
2.2k
Forks
616
Avg merge
5d 6h
Merged PRs (30d)
10

Description

Describe the bug

[2026-06-01 13:57:09 +0000] critical/config: Error: syntax error, unexpected end of file, expecting T_IDENTIFIER
Location: in /etc/icinga2/conf.d/services.conf: 39:26-39:26
/etc/icinga2/conf.d/services.conf(37):   check_command = "ping6"
/etc/icinga2/conf.d/services.conf(38):
/etc/icinga2/conf.d/services.conf(39):   assign where host.vars.äddress6
                                                                ^
/etc/icinga2/conf.d/services.conf(40): }
/etc/icinga2/conf.d/services.conf(41):
[2026-06-01 13:57:09 +0000] critical/cli: Config validation failed. Re-run with 'icinga2 daemon -C' after fixing the config.

To Reproduce

  1. Make a service apply rule with assign where host.vars.äddress6
  2. Run icinga2 daemon -C

Expected behavior

Error message says what's actually wrong, not "end of file" which is not true.

Additional context

I was testing https://github.com/Icinga/icingaweb2-module-director/pull/2972.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the apply rule with host.vars.äddress6 and run icinga2 daemon -C, using the diagnostic location in /etc/icinga2/conf.d/services.conf as the input. Trace the configuration parser's handling of the identifier and its syntax error reporting; done means invalid Unicode identifiers produce an accurate error instead of "unexpected end of file".

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
compilers
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.