blasadmin -s _pxe set pxe password <new-password>
will fix the ka.
Thanks. We ran "blasadmin -s _pxe set pxe password <new-password>" and now the DB account doesn't get locked out.
Now the problem is PXE won't start and I can't find any errors in the logs. There's nothing being logged to pxe.log when we try to start the service. Where else might these PXE startup errors show up?
if it's linux you can create a NSH/br/pxeconsole.log if it doesn't exist and see what shows up there.
if it's windows there should be a pxeservice.exe (whatever the service calls) that you can rung w/ a 'debug' argument that will run in the console (there is for the appserver at least)
Sorry for the slow response......
We got this one working by editing the password in pxe/br/golbal.properties. Updating the _pxe deployment wasn't enough.Nothing helpful showed up in the pxe debug output when the connection failed. Pxe debug showed lots of information when the connection worked.
PXE is working now, but I'm not sure how to handle future password changes. The manual global.properties update doesn't seem like something we should have to worry about. Any idea what we might have missed here?
When you ran blasadmin were you root or in a ‘run as administrator’ cmd shell ?
Yes, we are in a 'run as administrator' shell. (Windows appserver).
I tried it again this morning just to make sure and got the same results. pxe/br/deployments/global.properties did not get updated. Blasadmin didn't report any errors.
This is working now. The problem was we have PXE installed on the same host as the app server, and we weren't running blasadmin from the PXE install location bin directory.