Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No map shown when using Umlaut in alias #152

Open
BertramVielsack opened this issue Oct 5, 2023 · 2 comments
Open

No map shown when using Umlaut in alias #152

BertramVielsack opened this issue Oct 5, 2023 · 2 comments

Comments

@BertramVielsack
Copy link

Hi,
after upgrade to jasonrivers/nagios:4.4.14 the ui no longer shows the "Map" while "Legacy" still worked.

This seems to be caused by using German umlauts within aliases.

The issue can be reproduced with the following files:

docker-compose.yml

services:
  nagios:
    image: jasonrivers/nagios:4.4.14
    ports: 
      - 80:80
    volumes:
      - ./localhost.cfg:/opt/nagios/etc/objects/localhost.cfg

localhost.cfg:

define host {
        use                     linux-server
        host_name               localhost
        alias                   localhost Büro
        address                 127.0.0.1
        }

define service {
        use                             local-service,graphed-service
        host_name                       localhost
        service_description             PING
	check_command			check_ping!100.0,20%!500.0,60%
        }

When I remove "Büro" from alias or use version 4.4.8 the issue does not occur.

Regards
Bertram

@Kolossi
Copy link

Kolossi commented Oct 5, 2023

Sounds like you've nailed it down.

But it appears to be an issue with actual Nagios rather than this Docker-packaging project, have you tried searching for it/raising it in the main Nagios repo?

@BertramVielsack
Copy link
Author

I have tried to search but was not able to find a similar issue.
I agree with you that its likely to be an issue in the nagios repo but I am not sure.
My hope is that you better know where and how to address the issue and finally provide a fixed docker image.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants