September 2022 Archives

Thu Sep 29 13:03:32 +07 2022

Some stuff related VMware and SSL certificates

Certificates are located in /etc/vmware/ssl rui.key is the private key mod 400 rui.crt is the certificate + the CA mod 644 The private key is installed once for all The certificate is generated/installed by ~on/letsencrypt/install_cert_virtual After installing the new certificates, restart the management agents: /etc/init.d/hostd restart /etc/initt.d/vpxa restart If that does not work, try to restart the agent manually from the console. Or try the command dcui from an ssh connection. I have not tried the solutions below. See also https://www.nakivo.com/blog/how-to-restart-management-agents-on-a-vmware-esxi-host/ 4. Use this command as an alternative, to restart all management agents on the ESXi host. services.sh restart &tail -f /var/log/jumpstart-stdout.log The progress of the VMware agents restart is displayed in the console output. VMware restart management agents with services.sh 5. You can also try to reset the management network on a VMkernel interface: esxcli network ip interface set -e false -i vmk0; esxcli network ip interface set -e true -i vmk0 The vmk0 interface is used by default on ESXi. If you have a different name for the management network interface, use the appropriate interface name in the command. This complex command consists of two basic commands separated by ; (semicolon). The vmk0 management network interface is disabled by the first part of the command. When this part is executed successfully and vmk0 is down, then the second part of the command is executed to enable the vmk0 interface. As a result, the ESXi management network interface is restarted. The authorized_keys file for root is in /etc/ssh/keys_root/authorized_keys It can be used from ufo sudo ssh -i /root/.ssh/id_rsa_virtual root@virtualX Crontab for root is in /var/spool/cron/crontab/root

Posted by Olivier | Permanent link

Thu Sep 29 12:47:49 +07 2022

chown error in slapd start

I would like to report a small inconvenient in the port of openldap26-server on FreeBSD. The startup script /usr/local/etc/slapd incudeds the line: chown -RL "$slapd_owner" "${DBDIR}" around the line 127 My DBDIR is a file system mounted to only contain LDAP data: fbsd63<root>334: mount -p |grep da1p1 /dev/da1p1 /var/db/openldap-data ufs rw 2 2 As such, it contains the file .sujournal that is not changeable" fbsd63<root>335: ll -o /var/db/openldap-data/.sujournal 4 65600 -r-------- 1 root wheel schg,sunlnk,nodump,opaque 33554432 Sep 20 12:02 /var/db/openldap-data/.sujournal The chown in the startup script throws an error: fbsd63<root>336: /usr/local/etc/rc.d/slapd restart Stopping slapd. Waiting for PIDS: 41425. chown: /var/db/openldap-data/.sujournal: Operation not permitted Performing sanity check on slap configuration: OK Starting slapd. The script still work, but it may be confusing for some users who have their DBDIR as an independant filesystem.

Posted by Olivier | Permanent link