I’m trying to install Servoy Developer 7.0 / 7.1 / 7.2 on Ubuntu 12.10 / 13.04. I get a problem during installation with the bundled PostgreSQL database server, because the port 5432 is closed.
So you selected to install the Bundled PostgreSQL server. So you assume there is no PostgreSQL running or even installed yet (try ps -aux | grep postgres in the terminal).
Now, that ‘check availability’ button checks if the default Pg port is already in use. If it is it tries the next one, and so on. So somehow it seems to think that ports 5432 all the way to 65535 is already in use. I suggest you file this as a bug with Servoy because I find that hard to believe that this is the case.
To see if there is something listing on port 5432 you can use the following command:
sudo lsof -i -P | grep -i listen | grep 5432
I am pretty sure you will find no process there.
In that case you simply keep the ‘Database server port’ setting in the installer set to 5432 and install it.
ROCLASI:
So you selected to install the Bundled PostgreSQL server. So you assume there is no PostgreSQL running or even installed yet (try ps -aux | grep postgres in the terminal).
Yes, it’s a fresh Ubuntu installation, so there is no PostgreSQL running.
ROCLASI:
Now, that ‘check availability’ button checks if the default Pg port is already in use. If it is it tries the next one, and so on. So somehow it seems to think that ports 5432 all the way to 65535 is already in use.
I tried also the PostgreSQL install from the Ubuntu repository and then using the port 5432. It works.
ROCLASI:
I suggest you file this as a bug with Servoy because I find that hard to believe that this is the case.
Ok
ROCLASI:
To see if there is something listing on port 5432 you can use the following command:
sudo lsof -i -P | grep -i listen | grep 5432
I am pretty sure you will find no process there.
You are right.
ROCLASI:
In that case you simply keep the ‘Database server port’ setting in the installer set to 5432 and install it.
This bundled version should obviously work and it may be a Servoy bug or an operating system issue. But note that best practice is to use a stand alone postgresql installation, even with Servoy developer. The same version you use in production. It has saved us a few times.