Bug 37325 - Improve messages when failed.ldif import fails
Improve messages when failed.ldif import fails
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: LDAP
UCS 4.2
Other Linux
: P5 normal (vote)
: UCS 4.0-x
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-12-12 16:49 CET by Janis Meybohm
Modified: 2020-07-03 20:53 CEST (History)
3 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?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Error handling, External feedback, Troubleshooting
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Janis Meybohm univentionstaff 2014-12-12 16:49:15 CET
When a failed.ldif is automatically imported and that fails, a message like "You can find the failed modifications in /tmp/fileHE9KiB" is written to the listener.log.

We should include the first line of the temp-file into the message (or as a second one) as it contains a more detailed error message in most cases.

In addition we should change the name of the temp-file to something like /tmp/failed.ldif_HE9KiB. That would make customer communication easier (at the moment we need to ask the customer to look into the listener.log, check for the correct filename and send that file and the failed.ldif to us. "Please send the files /tmp/failed.ldif*" leaves less room for errors and is a lot faster :))
Comment 1 Ingo Steuwer univentionstaff 2020-07-03 20:53:32 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.