<TIMESTAMP> <int> lb WARNING lbconf-repo is failed: Command '['cat', '/var/log/lb/lbconf-repo/lbconf-config']' returned non-zero exit status 1.<TIMESTAMP> <int> lb ERROR Traceback (most recent call last): File "/opt/vmware/nsx-edge/bin/lbconf_gen.py", line 3331, in main repo.read_config() File "/opt/vmware/nsx-edge/bin/lbconf_gen.py", line 3149, in read_config output = subprocess.check_output(['cat', lbconf_repo.lbconf_config]) File "/usr/lib/python3.10/subprocess.py", line 421, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 526, in run raise CalledProcessError(retcode, process.args,subprocess.CalledProcessError: Command '['cat', '/var/log/lb/lbconf-repo/lbconf-config']' returned non-zero exit status 1.VMware NSX 4.1.x
VMware NSX 4.2.x
lbconf-repo is a debugging feature implemented in 4.1.0 to store loadbalancer config history. NSX Edge VM creates the lbconf-repo directory at installation.
In upgrade scenario, NSX Edge VM does not create the lbconf-repo directory and modification to the directory fails.
Currently there is no resolution.
These error / warning messages are harmless and ignored.
To workaround this issue, either:
mkdir /var/log/lb/lbconf-repochmod 0770 /var/log/lb/lbconf-repochgrp nsx /var/log/lb/lbconf-repotouch /var/log/lb/lbconf-repo/repo.lockchmod 0770 /var/log/lb/lbconf-repo/repo.lockchgrp nsx /var/log/lb/lbconf-repo/repo.lockecho "1 102400 1024000 7" > /var/log/lb/lbconf-repo/lbconf-configchmod 0770 /var/log/lb/lbconf-repo/lbconf-configchgrp nsx /var/log/lb/lbconf-repo/lbconf-configmkdir /var/log/lb/lbconf-repo/cur-repochmod 0770 /var/log/lb/lbconf-repo/cur-repochgrp nsx /var/log/lb/lbconf-repo/cur-repogit -C /var/log/lb/lbconf-repo/cur-repo init