VMware Modern Apps Community
pcpaulh1
Contributor
Contributor

PhotonOS 4 and Lightwave DC

Good afternoon, hoping someone can help.

I'm testing using lightwave-server as a primary domain controller. I've followed the instructions but am constantly failing.

Here is the error I'm getting:

root@app01 [ /opt/likewise/bin ]# configure-lightwave-server --domain photon.local --password passwordRemoved
Deploying in standalone mode...
Starting service: eventlog
Starting service dependency: netlogon
Starting service dependency: lwio
Starting service dependency: rdr
Starting service: lsass
Starting service: lwio
Starting service: netlogon
Starting service dependency: dcerpc
Starting service: vmafd
Starting service: vmca
Starting service: vmdir
Starting service: vmdns
Error: LW_ERROR_SERVICE_UNRESPONSIVE (41203)
The service is not responding to requests
20220423115340:INFO:Setting up system as Infrastructure standalone node
20220423115340:INFO:Starting service [dcerpc]
20220423115340:INFO:Starting service [vmdns]
ic-promoteDomain controller setup failed. Error 41203: Unknown (private extension) error
20220423115343:ERROR:Domain controller setup failed. Error code: 41203
PSC Installation failed.
root@app01 [ /opt/likewise/bin ]#

hostfile looks like this:

127.0.0.1 localhost
192.168.26.128 app01.photon.local app01

This is the only server so far, so no DNS to point to, plan is to run unbound on here too-eventually.

Can anyone see anything I've missed?

Thanks in advance.

 

Reply
0 Kudos
4 Replies
DCasota
Expert
Expert

Hi,

did you double check the config eg. hosts file entries, unbound dns, ntp ? In https://github.com/vmware/lightwave see section ‚instantiating a domain controller‘. Check dmesg and journalctl as well.

Reply
0 Kudos
pcpaulh1
Contributor
Contributor

Hi, the lightwave server will be the DNS server too. I'll configure that and have another go.

Thanks.

Reply
0 Kudos
pcpaulh1
Contributor
Contributor

Morning, NTP and DNS seem to be working OK. I'm getting errors in journalctl which seem to point to vmdns being an issue. I've attached part of the log.

 

Thanks in advance

Reply
0 Kudos
DCasota
Expert
Expert

@pcpaulh1 I can reproduce a similar issue (vmdir) but haven't yet enough troubleshooting experience for an easy-to-use recipe. Anyone?  

Here some code snippets though.  

# support bundle
/usr/bin/lw-support-bundle.sh generates a support file .tar.gz.

# list services status
/opt/likewise/bin/lwsm list lists services status. example:  

lwreg running (standalone: 2823)
dcerpc running (standalone: 3053)
eventlog running (standalone: 2837)
lsass running (standalone: 2870)
lwio running (standalone: 2863)
netlogon running (standalone: 2857)
rdr running (io: 2863)
vmafd running (standalone: 3065)
vmca running (standalone: 3556)
vmdir dead
vmdns running (standalone: 3365)

 

# stop/start service <service> eg. lwsm start vmdir
/opt/likewise/bin/lwsm stop <service>
/opt/likewise/bin/lwsm start <service>

# get info <service> eg. lwsm info vmdir
/opt/likewise/bin/lwsm info <service>

# Show certs entries in stores (MACHINE_SSL_CERT, STORE TRUSTED_ROOTS, STORE TRUSTED_ROOT_CRLS)
for i in $(/usr/bin/vecs-cli store list); do echo STORE $i; /usr/bin/vecs-cli entry list --store $i --text;done

Reply
0 Kudos