| Author |
Message |
|
|
What would I add to the pg_hba.conf table to get that working correctly? As I mentioned, if I leave it at "@authmethod@", I get that SSL error:
|
 |
|
|
Yes, this is the correct hba.conf. It is not what was expected, probably because I had to change it from what it originally was:
However, when it was configured this way, the PostgreSQL 9.0 server for PEM failed to start:
So I switched it to the pg_hba.conf that I originally posted. Is that what is messing up the remote agents?
|
 |
|
|
|
|
 |
|
|
Ok, thanks for suggesting a look into those logs. The 101 logs look ok, but on every machine with an agent that PEM claims to be in status "UNKNOWN", there are hundreds of entries in /var/log/pemagent.log that look like this:
or, on a different machine that also has an agent hanging in UNKNOWN status,
Do you know what password is failing here? How do I specify or change that password?
Thanks so much for your help!
|
 |
|
|
I have two identical servers, 10.20.20.100 and 10.20.20.101.
PEM Server is installed and functioning as expected on 101. I installed PEM Agent on 100. I believe it correctly connected to the server on 101, as the installation process did not throw any errors about pg_hba.conf when I pointed it to 101. The Agent on 100 shows up in my PEM client as an available agent, and I can bind a database to it with the PEM client.
However, the agent remains as status UNKNOWN both from within the PEM Client and from the web interface. Any databases I bind to that agent also remain status UNKNOWN.
I'm not quite sure where to start looking to determine the cause of this. Any troubleshooting thoughts?
Thanks!
|
 |
|
|