Actions
Bug #14643
closedDebian/Ubuntu install fails to install rsyslog-pgsql
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Priority:
72
Name check:
Fix check:
Regression:
Description
... because postgresql has not yet been started.
Is it a mandatory to use a db with rsylog for rudder server? -> At this time I am not able to define the severity
Updated by François ARMAND over 5 years ago
- Translation missing: en.field_tag_list set to community
- Assignee set to Alexis Mousset
- Target version set to 5.0.10
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
- Effort required set to Very Small
- Priority changed from 0 to 79
Thank you for reporting. It is most likely a missing point on our documentation, we are going to enhance it to make clear what one should do to have that part of the installation works.
Updated by François ARMAND over 5 years ago
- Category changed from Packaging to Documentation
Updated by Nicolas CHARLES over 5 years ago
- Related to Architecture #14631: If we overwrite config file during upgrade, chaos happen added
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.10 to 5.0.11
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.11 to 5.0.12
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.12 to 5.0.13
- Priority changed from 79 to 77
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.13 to 5.0.14
- Priority changed from 77 to 75
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 5.0.14 to 5.0.15
- Priority changed from 75 to 73
Updated by Alexis Mousset about 5 years ago
- Status changed from New to Rejected
- Priority changed from 73 to 72
Nothing specific needs to be done, maybe it happened because you tried to configure de rsyslog-pgsql default database (which is not necessary as indicated in the docs), and even this should work (but if it doesn't it looks more like a bug in debian packaging).
If the problem occurs again, please reopen an issue, closing for now.
Actions