Issues in Installing Servoy 5.2.1 on Amazon EC2

Classic Servoy
1

Hi all,

I have Servoy 4.6 running fine with Amazon EC2. After Installing Servoy 5.2.1, I have tried to create some databases and got some issues. The Repository Connection itself also not showing error on it. Please, find the screenshot in the attachment. Can anyone please, help me in this regard? Do I need to open the PostGreSql Default port, 54432, or anything else, I need to address and I am missing the same.

[attachment=0]Error_EC2.PNG[/attachment]

Thanks

Error_EC2.PNG
Error_EC2.PNG442×134 2.94 KB

2

Infop:
Hi all,

I have Servoy 4.6 running fine with Amazon EC2. After Installing Servoy 5.2.1, I have tried to create some databases and got some issues. The Repository Connection itself also not showing error on it. Please, find the screenshot in the attachment. Can anyone please, help me in this regard? Do I need to open the PostGreSql Default port, 54432, or anything else, I need to address and I am missing the same.

[attachment=0]Error_EC2.PNG[/attachment]

Thanks

Is PostgreSQL running ? Which is the database startup launcher property from servoy.properties ? Is it modified from original one ?

3

Hi lvostinar,

I think, the postgresql automatically start when starting the Servoy Developer. Or Do i need to start explicitly? If yes, How can Start the Database Explictly? This is not happening at my end on Windows XP box. The Database is starting up on the start up of the Servoy Developer.

I have never modified the servoy.properties file. It is just a fresh installation.

Thanks

4

It is not able to start the PostgreSql Service in Amazon EC2. Can anyone have any idea, why it is not able to start the PostgreSql Service? Have anyone tried to deploy Servoy 5.2.1 solution on Amazon EC2?

Thanks,

5

Hi Infop,
I tried to start Servoy Developer on Amazon EC2 with Windows 2008, but I found the PostgreSql start only if you are a normal user, not an Administrator! I think this is because PostgreSql “doesn’t like” DB changes by Administrators. (I found the same problem in my server with Windows 2003)
Another thing to check could be the Amazon EC2 firewall settings you choose during the first start-up of the AMI.

Bye

6

You can check the postgres log to see why it doesn’t start: application_server\postgres_db\postgres_log.txt