#50165 dscreate throwing errors
Closed: wontfix 3 years ago by mreynolds. Opened 3 years ago by mreynolds.

Issue Description

[root@localhost ~]# dscreate from-file /data/dssetup.inf

Starting installation...
Created symlink /etc/systemd/system/multi-user.target.wants/dirsrv@localhost.service → /usr/lib/systemd/system/dirsrv@.service.
port 636 already in [389, 636, 3268, 3269, 7389], skipping port relabel
lstat(/root/backup_dir) failed: No such file or directory
lstat(/root/cert_dir) failed: No such file or directory
lstat(/root/config_dir) failed: No such file or directory
lstat(/root/db_dir) failed: No such file or directory
lstat(/root/ldif_dir) failed: No such file or directory
lstat(/root/lock_dir) failed: No such file or directory
lstat(/root/log_dir) failed: No such file or directory
lstat(/root/run_dir) failed: No such file or directory
lstat(/root/schema_dir) failed: No such file or directory
lstat(/root/tmp_dir) failed: No such file or directory
port 389 already in [389, 636, 3268, 3269, 7389], skipping port relabel

The message about the port labelling should be a debug message not an error. Not sure what the lstat errors are all about, but they need to go


Metadata Update from @mreynolds:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None

3 years ago

commit 9408b94 master

9290997..0036226 389-ds-base-1.4.0 -> 389-ds-base-1.4.0

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

3 years ago

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/3224

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

2 years ago

Login to comment on this ticket.

Metadata