Bug 36047 - Sorting pupils by class results in an error
Sorting pupils by class results in an error
Status: RESOLVED DUPLICATE of bug 35407
Product: UCS@school
Classification: Unclassified
Component: UMC - Password reset
UCS@school 3.2 R2
Other Linux
: P5 normal (vote)
: ---
Assigned To: Bugzilla Mailingliste
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-06 09:49 CEST by Tim Petersen
Modified: 2014-10-06 10:01 CEST (History)
1 user (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?:
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 Tim Petersen univentionstaff 2014-10-06 09:49:33 CEST
Reported at #2014093021000693 and #2014091521000159.

If sorting the user list in the pupil wizard by class you'll receive an error message in UMC ("An error occured...").

Unfortunately the module logfiles with debuglevel 4 are not very helpful - see the tickets for full logs:

"
[...]
06.10.14 09:19:51.843  MODULE      ( PROCESS ) : UDM object uid=username,cn=schueler,cn=users,ou=schoolou,ldap_base is not User, but actually Student
<normal stuff...>
06.10.14 09:19:51.845  ADMIN       ( INFO    ) : values are identical: pwdChangeNextLogin:1
06.10.14 09:19:51.845  ADMIN       ( INFO    ) : values are identical: CtxBrokenSession:0000
06.10.14 09:19:51.845  ADMIN       ( INFO    ) : values are identical: CtxReconnectSession:0000
06.10.14 09:19:51.900  PROTOCOL    ( INFO    ) : Sending UMCP RESPONSE 141257998688385-13
"

Perhaps the connection breaks due to a sizelimit or something like that. I wasn't able to reproduce it till now.
Comment 1 Florian Best univentionstaff 2014-10-06 10:01:09 CEST
This is an error directly in UMC (See Bug #35407).

*** This bug has been marked as a duplicate of bug 35407 ***