Bug 2010992 - When ports that are in use are used to update a DS instance the error message is not helpful -use error that is in the logs
Summary: When ports that are in use are used to update a DS instance the error message...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: cockpit-389-ds
Version: 12.0
Hardware: Unspecified
OS: Linux
medium
unspecified
Target Milestone: ---
: dirsrv-12.3
Assignee: LDAP Maintainers
QA Contact: LDAP QA Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-05 18:00 UTC by Gilbert Kimetto
Modified: 2023-07-28 08:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gilbert Kimetto 2021-10-05 18:00:38 UTC
Description of problem:

When ports that are in use are used to update a DS instance the error message is not helpful -use error that is in the logs
Version-Release number of selected component (if applicable):


How reproducible:

Always

Steps to Reproduce:
1. Create 2 DS Instances on the Webconsole
2. Update the second instance to use the ports that are currently in use by the
   1st instance
3. Follow the prompt to restart the instance for the changes to take effect. 

Actual results:

The error is displayed which is not helpful:

Danger alert:
Error during instance restart operation - Command '['systemctl', 'start', 'dirsrv@dscre']' returned non-zero exit status 1.


Expected results:
The error that is logged should be displayed in the Web Console as its more helpful to the user

ERR - createprlistensockets - PR_Bind() on All Interfaces port 389 failed: Netscape Portable Runtime error -5982 (Local Network address is in use.)


Additional info:

the instance is irrecoverable the message 
This server instance is not running, either start it from the Actions dropdown menu, or choose a different instance

Is displayed unable to go back and update or change anything

Comment 1 Viktor Ashirov 2023-07-28 08:47:17 UTC
I think we should a check if the new port is already taken before we even attempt to change it.


Note You need to log in before you can comment on or make changes to this bug.