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

[dev.icinga.com #10460] A PgSQL DB for the IDO can't be created w/ UTF8 #3550

Closed
icinga-migration opened this issue Oct 26, 2015 · 5 comments
Closed
Milestone

Comments

@icinga-migration
Copy link
Member

@icinga-migration icinga-migration commented Oct 26, 2015

This issue has been migrated from Redmine: https://dev.icinga.com/issues/10460

Created by aklimov on 2015-10-26 10:38:21 +00:00

Assignee: jflach
Status: Resolved (closed on 2015-11-20 15:11:05 +00:00)
Target Version: 2.4.2
Last Update: 2016-02-23 10:25:00 +00:00 (in Redmine)

Icinga Version: 2.3.11
Backport?: Already backported
Include in Changelog: 1

On a fresh CentOS 6 x64 if you set up a PgSQL RDBMSd for I2+IDO as described here<http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/getting-started#setting-up-icinga2> the server won't start:

/var/lib/pgsql/data is missing. Use "service postgresql initdb" to initialize the cluster first.

When you do service postgresql initdb the template for all DBs is created w/ SQL_ASCII, not UTF8, so createdb -O icinga -E UTF8 icinga fails:

createdb: database creation failed: ERROR:  new encoding (UTF8) is incompatible with the encoding of the template database (SQL_ASCII)
HINT:  Use the same encoding as in the template database, or use template0 as template.

As an I2 admin I want to just copy&paste "all the things" from the doc without being stopped by some RDBMS-specific err msgs.

Changesets

2015-11-20 15:11:28 +00:00 by jflach acbbce9

Update docs

The semicolon is not required at all.
We also can expect an admin to be capable of fixing the problems
araising from locale problems by himself.

fixes #10460, #10458

2016-02-23 08:08:09 +00:00 by jflach 5ede586

Update docs

The semicolon is not required at all.
We also can expect an admin to be capable of fixing the problems
araising from locale problems by himself.

fixes #10460, #10458
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Nov 20, 2015

Updated by jflach on 2015-11-20 15:11:05 +00:00

  • Status changed from New to Resolved
  • Done % changed from 0 to 100

Applied in changeset acbbce9.

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Nov 20, 2015

Updated by jflach on 2015-11-20 15:23:17 +00:00

  • Target Version set to 2.5.0
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Nov 26, 2015

Updated by gbeutner on 2015-11-26 06:54:21 +00:00

  • Assigned to set to jflach
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Feb 23, 2016

Updated by gbeutner on 2016-02-23 09:58:16 +00:00

  • Backport? changed from Not yet backported to Already backported
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Feb 23, 2016

Updated by gbeutner on 2016-02-23 10:25:00 +00:00

  • Target Version changed from 2.5.0 to 2.4.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.