The reporting of --file errors differs from how other errors are reported. The --file errors are not logged to a file as other errors are. This can give a false impression of the root cause of an error, as only the later errors are shown in the log file.
Command:
/usr/sbin/setup-ds.pl --file=nonexistent.ldif --silent
STDERR
Error: could not open inf file nonexistent.inf: No such file or directory
STDOUT
Either ServerPort or ldapifilepath must be specified. The server must listen to something. Error: Could not create directory server instance 'minion'. Exiting . . . Log file is '/tmp/setupfa3U2i.log'
File /tmp/setupfa3U2i.log
[15/03/10:11:29:06] - [Setup] Info Either ServerPort or ldapifilepath must be specified. The server must listen t. [15/03/10:11:29:06] - [Setup] Fatal Error: Could not create directory server instance 'devserver'. [15/03/10:11:29:06] - [Setup] Fatal Exiting . . . Log file is '/tmp/setupfa3U2i.log'
attachment 0001-Ticket-48119-setup-ds.pl-does-not-log-invalid-file-p.patch
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1240404
e4d83c9..6306fc4 master -> master commit 6306fc4 Author: Mark Reynolds mreynolds@redhat.com Date: Mon Jul 6 15:55:43 2015 -0400
Pushed to 389-ds-base-1.3.4: b513a50..5bd7119 389-ds-base-1.3.4 -> 389-ds-base-1.3.4 commit 5bd7119
Does that mean if you run setup as root, and you do not specify a SuiteSpotUser, it will install and run the server as root?
Replying to [comment:12 rmeggins]:
Yes
Replying to [comment:13 mreynolds]:
Replying to [comment:12 rmeggins]: Does that mean if you run setup as root, and you do not specify a SuiteSpotUser, it will install and run the server as root? Yes
I'll revise the patch to error out in this case.
That's bad. We do not want to run the server as root. That's why that check was in there.
attachment 0001-Ticket-48119-Silent-install-needs-to-properly-exit-w.patch
New patch attached.
6dce81e..5363898 master -> master commit 5363898 Author: Mark Reynolds mreynolds@redhat.com Date: Mon Jul 13 12:24:19 2015 -0400
6d177bf..eeddc9f 389-ds-base-1.3.4 -> 389-ds-base-1.3.4 commit eeddc9f
Metadata Update from @mreynolds: - Issue assigned to mreynolds - Issue set to the milestone: 1.3.4.2
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1450
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.