Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Problem when attempting to use the repl-monitor function embedded in the 389 Administration Express web GUI. #1550

Closed
389-ds-bot opened this issue Sep 12, 2020 · 2 comments
Closed

Problem when attempting to use the repl-monitor function embedded in the 389 Administration Express web GUI. #1550

389-ds-bot opened this issue Sep 12, 2020 · 2 comments
Labels
closed: duplicate Migration flag - Issue

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48219

Ticket was cloned from Red Hat Bugzilla (product Red Hat Directory Server): Bug 1241549

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem:
When run from the command line, "repl-monitor" works fine (in both "HTML" and
"text only" modes). The problem occurs only when attempting to use the
repl-monitor function embedded in the 389 Administration Express web GUI.

Version-Release number of selected component (if applicable):
RHDS-9.1.0

How reproducible:
Always.

Steps to Reproduce:
-------------------
STARTING ASSUMPTIONS: a server "server.example.com" with at least one replica
configured, and a valid "repl-monitor.conf" file located at
/etc/dirsrv/repl-monitor.conf.

The "Administration Server" is installed, configured, and running, on port
9830.

Go to:
http://server.example.com:9830/
  enter the "cn=Directory Manager" user name & password

  click "389 Administration Express" link on the main page

There should be a 3 sets of links for the "master" server: the "Administration
Server", the "config" directory ("slapd-config"), and the user directory
("slapd-serverName").  Click on the "Replication Status" link for the user
directory.

  Enter the "cn=Directory Manager" name & password again.

A form should be displayed with a box for "Configuration file", "Refresh
Interval" (defaults to 300 secs.), and OK / Reset / Help buttons.  Enter the
full path to a valid repl-monitor.conf file (I used
"/etc/dirsrv/repl-monitor.conf").

At this point, the stock "repl-monitor.pl" script will display an "Internal
Server Error" message in the browser.


Actual results:
---------------
The server will have logged the following error in
"/var/log/dirsrv/admin-serv/error":

[Mon Jun 01 17:06:22 2015] [error] [client X.X.X.X] malformed header from
script. Bad header=<!DOCTYPE HTML PUBLIC "-//W3C/: repl-monitor-cgi.pl,
referer: http://server.example.com:9830/admin-serv/tasks/configuration/MonRepli
cation?servhost=server.example.com&servport=389&admurl=http://server.example.co
m:9830

Expected results:
repl-monitor function embedded in the 389 Administration Express web GUI should
work.

Additional info:
----------------
This appears to be caused by the script (or whatever wrapper process calls it?)
not emitting a valid HTTP header (Content-type header plus at least one blank
line).

This can be corrected with 1-line patch.

From:           print "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML
3.2//EN\"><html>\n";
---
To:             print "Content-type: text/html\n\n\n<!DOCTYPE HTML PUBLIC
\"-//W3C//DTD HTML 3.2//EN\"><html>\n";
@389-ds-bot 389-ds-bot added the closed: duplicate Migration flag - Issue label Sep 12, 2020
@389-ds-bot
Copy link
Author

Comment from nkinder (@nkinder) at 2015-07-16 21:42:51

This bug was already fixed some time ago. Closing this ticket.

@389-ds-bot
Copy link
Author

Comment from nkinder (@nkinder) at 2017-02-11 22:48:41

Metadata Update from @nkinder:

  • Issue set to the milestone: N/A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed: duplicate Migration flag - Issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@389-ds-bot