Bug 44383

Summary: OperationalError: FATAL: database "selfservice" does not exist
Product: UCS Reporter: Florian Best <best>
Component: Self ServiceAssignee: UMC maintainers <umc-maintainers>
Status: RESOLVED WONTFIX QA Contact: UMC maintainers <umc-maintainers>
Severity: normal    
Priority: P5 CC: troeder
Version: UCS 4.2   
Target Milestone: ---   
Hardware: Other   
OS: Linux   
See Also: https://forge.univention.org/bugzilla/show_bug.cgi?id=45531
What kind of report is it?: Bug Report What type of bug is this?: 6: Setup Problem: Issue for the setup process
Who will be affected by this bug?: 1: Will affect a very few installed domains How will those affected feel about the bug?: 4: A User would return the product
User Pain: 0.137 Enterprise Customer affected?:
School Customer affected?: ISV affected?:
Waiting Support: Flags outvoted (downgraded) after PO Review:
Ticket number: 2017040621001035, 2017042721000943 Bug group (optional): External feedback
Max CVSS v3 score:

Description Florian Best univentionstaff 2017-04-18 11:31:53 CEST
Version: 4.2-0 errata0 (Lesum)

Traceback(dd5fc069ea33b13d640a6ccd4d37bc04):

The initialization of the module failed: 

Traceback (most recent call last):
  File "%PY2.7%/univention/management/console/protocol/modserver.py", line 178, in _recv
    self.handle(msg)
  File "%PY2.7%/univention/management/console/protocol/modserver.py", line 178, in _recv
    self.handle(msg)
  File "%PY2.7%/univention/management/console/protocol/modserver.py", line 290, in handle
    self.__handler.init()
  File "%PY2.7%/univention/management/console/modules/passwordreset/__init__.py", line 212, in init
    self.db = TokenDB(MODULE)
  File "%PY2.7%/univention/management/console/modules/passwordreset/tokendb.py", line 53, in __init__
    self.conn = self.open_db()
  File "%PY2.7%/univention/management/console/modules/passwordreset/tokendb.py", line 120, in open_db
    db_name=DB_NAME, db_user=DB_USER, db_pw=password))
  File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 164, in connect
    conn = _connect(dsn, connection_factory=connection_factory, async=async)
OperationalError: The initialization of the module failed: Traceback (most recent call last):
  File "%PY2.7%/univention/management/console/protocol/modserver.py", line 178, in _recv
    self.handle(msg)
  File "%PY2.7%/univention/management/console/protocol/modserver.py", line 290, in handle
    self.__handler.init()
  File "%PY2.7%/univention/management/console/modules/passwordreset/__init__.py", line 212, in init
    self.db = TokenDB(MODULE)
  File "%PY2.7%/univention/management/console/modules/passwordreset/tokendb.py", line 53, in __init__
    self.conn = self.open_db()
  File "%PY2.7%/univention/management/console/modules/passwordreset/tokendb.py", line 120, in open_db
    db_name=DB_NAME, db_user=DB_USER, db_pw=password))
  File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 164, in connect
    conn = _connect(dsn, connection_factory=connection_factory, async=async)
OperationalError: FATAL:  database "selfservice" does not exist
Comment 1 Daniel Tröder univentionstaff 2017-04-18 11:33:46 CEST
selfservice join script didn't run?
Comment 2 Florian Best univentionstaff 2017-04-27 11:45:16 CEST
Reported again, 4.2-0 errata4 (Lesum)
Comment 3 Daniel Tröder univentionstaff 2017-04-28 11:38:22 CEST
Need to know on what server role this was installed on and have the installation/updater and the join log.
Comment 4 Florian Best univentionstaff 2017-04-28 11:39:16 CEST
Role: domaincontroller_master
Comment 5 Florian Best univentionstaff 2017-05-16 18:06:13 CEST
The postinst contains no error handling. Also I think we should do these things in the joinscript.
Comment 6 Daniel Tröder univentionstaff 2017-05-16 19:06:57 CEST
(In reply to Florian Best from comment #5)
> The postinst contains no error handling. Also I think we should do these
> things in the joinscript.
+1
The whole DB setup should be moved to a join script.
Comment 7 Ingo Steuwer univentionstaff 2020-07-03 20:51:42 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.