Bug 36513 - no packages found matching ldapacl_66univention-appcenter_app.acl
no packages found matching ldapacl_66univention-appcenter_app.acl
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: LDAP
UCS 4.0
Other Linux
: P5 normal (vote)
: UCS 4.0-x
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-07 08:37 CET by Stefan Gohmann
Modified: 2020-08-05 13:22 CEST (History)
7 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2014-11-07 08:37:34 CET
We often see this message, for example during the nagios app installation: 

06.11.14 18:30:19.268  MODULE      ( PROCESS ) : dpkg-query: no packages found matching ldapacl_66univention-appcenter_app.a
Comment 1 Arvid Requate univentionstaff 2015-09-14 15:55:41 CEST
This may originate in the ucs_registerLDAPExtension function in univention-lib/shell/ldap.sh where we try to determine the pacakge name from either postinst or joinscript name.
Comment 2 Florian Best univentionstaff 2017-06-28 14:52:41 CEST
There is a Customer ID set so I set the flag "Enterprise Customer affected".
Comment 3 Stefan Gohmann univentionstaff 2019-01-03 07:17:10 CET
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.
Comment 4 Christian Völker univentionstaff 2020-08-05 12:40:26 CEST
While updating from 4.4-4 to 4.4-5 (with OX installed):

Setting up univention-management-console (11.0.4-96A~4.4.0.202007291436) ...
Processing triggers for univention-config (14.0.0-18A~4.4.0.202007200731) ...
dpkg-query: no packages found matching ldapacl_66oxforucs.acl
dpkg-query: no packages found matching ldapacl_66univention-appcenter_app.acl
Traceback (most recent call last):
  File "/usr/sbin/univention-pkgdb-scan", line 37, in <module>
    univention.pkgdb.main()
  File "/usr/lib/python2.7/dist-packages/univention/pkgdb.py", line 579, in main
    connection = open_database_connection(config_registry, pkgdbu=False)
  File "/usr/lib/python2.7/dist-packages/univention/pkgdb.py", line 561, in open_database_connection
    connection = pgdb.connect(database=connectstring)
  File "/usr/lib/python2.7/dist-packages/pgdb.py", line 1615, in connect
    cnx = _connect(dbname, dbhost, dbport, dbopt, dbuser, dbpasswd)
pg.InternalError: FATAL:  password authentication failed for user "home$"


Is the traceback related (how comes authentication failure)?
Comment 5 Philipp Hahn univentionstaff 2020-08-05 13:22:18 CEST
(In reply to Christian Völker from comment #4)
> Processing triggers for univention-config (14.0.0-18A~4.4.0.202007200731) ...
> dpkg-query: no packages found matching ldapacl_66oxforucs.acl
> dpkg-query: no packages found matching ldapacl_66univention-appcenter_app.acl

This ist not the real bug; the real bug is that your machine account is probably no longer valid for PostgreSQL for the server to update the pkgdb:

> Traceback (most recent call last):
>   File "/usr/sbin/univention-pkgdb-scan", line 37, in <module>
                    ^^^^^^^^^^^^^^^^^^^^^
>   File "/usr/lib/python2.7/dist-packages/pgdb.py", line 1615, in connect
>     cnx = _connect(dbname, dbhost, dbport, dbopt, dbuser, dbpasswd)
> pg.InternalError: FATAL:  password authentication failed for user "home$"
> 
> Is the traceback related (how comes authentication failure)?

See Bug #50937 or Bug #48677