New MYSQL Connection for Exiting Project Returns 'Connection attempt failed'

Scriptcase 9 Installation
#1

Hi.

I am using Scriptcase 9.2.003 on MacOS 10.12. I have an existing project where the DB connection was to MYSQL 5.7 running on another linux-based server. All was well.

Unfortunately I need to do some development while disconnected from that DB server. I installed MYSQL 5.7 on my Mac (used all defaults). MySQLWorkbench accesses the local DB fine (127.0.0.1 default socket 3306).

Logged onto local scriptcase as usual and created a new DB connection (127.0.0.1 / 3306) and set up the connection per usual - List Database retrieved the DB name and “test database” was successful.

Used Express Edit to change the DB connection on all the apps in my project which appear successful (the new connection is found under ‘connection’ in the SQL Settings tab of the app).

When I try to run an app (any I have tried so far) the I get “Connection attempt failed: SQLSTATE[HY000] [2002] Operation timed out”.

Any ideas where I have gone wrong, something I have forgotten to update other than the DB connection?

I am more of an application person than a platform (MAMP/LAMP) person, so please spell it out if I need to check or look at something.

Thanks in advance for any help.

Regards, Russell.

#2

I am adding some additional information to this thread in the hope that it may help someone help me isolate my issue. Some things are not adding for me, but again, I am a relative novice around platform issues.

When I look at the MySQL config using MySQLWorkbench, I note it states that the Socket is ‘/tmp/mysql.sock’ (it also confirms that the port is the default 3306).

When I run the command ‘php -i grep _socket’ command in my mac’s terminal window I get the following output:
mysql.default_socket => /var/mysql/mysql.sock => /var/mysql/mysql.sock
mysqli.default_socket => /var/mysql/mysql.sock => /var/mysql/mysql.sock
pdo_mysql.default_socket => /var/mysql/mysql.sock => /var/mysql/mysql.sock
default_socket_timeout => 60 => 60

Is it possible that the mis-match in the socket values are the source of my problem? (MySQL = /tmp/mysql.sock; php = /var/mysql/mysql.sock) If so, how do I get these aligned?

Note that I have already tried changing /Applications/Scriptcase/v9/components/php/php.ini by setting:
pdo_mysql.default_socket = /tmp/mysql.sock
mysql.default_socket = /tmp/mysql.sock
and restarted apache. Made no difference. Same issue. The output of php -i remains unchanged.

Is there another php.ini file or other means by which I should be telling php how to connect to the DB?

Happy to be told that I am going about this the wrong way and should give up because I don’t know what I am doing. :slight_smile:

#3

if you made your mysql connection on your db,
in principle the connection is correct and you must not change anything via express edit unless your tables, queries or views are modified

#4

Hi nsch2308. Thanks for your response.

I thought I needed to create a different connection because it is to MySQL on my local MacBook instead to a server (IE 127.0.0.1 instead of, say, 10.1.1.19). I did this to preserve the original connection when I needed to swap back at some future point in time. And given I created the new connection, don’t I need to change the DB connection for all the apps?

Or are you saying I should have just changed the existing connection to be IP 127.0.0.1?

In any event, what action should I take now? Revert the apps back to the original connection and change the IP address? Will this really fix my issue? I can’t help feeling the real problem is that script case / php is not finding MySQL on my MacBook??

#5

you simply connect through scriptcase by going to edit connection, you do a connection test, and that’s basically all you have to do to continue working with your applications
i don’t know mac but you can see maybe there
https://www.thoughtco.com/installing-mysql-on-mac-2693866

#6

Thank you for the reference nsch2306. I have been through the install. MySQL is working as evidenced by a) MySQLWorkbench working OK and b) the scriptcase edit connection ‘test database’ function says ‘success’. The applications generate OK. But still, applications are not connecting to the DB when run. So clearly something is not right. I am still looking for answers where to look.

#7

go into database menu, sql constructor, run and test a query on your database, you will already be certain to be correct in your config, then you can test through an app blank and check the operation of your request and select

#8

Thanks again nsch2308. To be sure, before I began I re-checked the “test database” function in edit connection and it still says “success”. Went into SQL builder and ran a query, results were returned, so I’ll call that success. Clicked on “new application” and before I had a chance to select any application type the “connection error” popup appeared. The accompanying “system error” dialog contains the following “an error occurred while connecting to the database. Connection attempt failed: SQLSTATE[HY000] [2002] Connection refused | Script: /Applications/Scriptcase/v9/wwwroot/scriptcase/devel/class/page/nmPageWizard.class.php linha: 5144”.

So how come “test database” and SQL builder work OK, but I get this error?

#9

UPDATE…

After I closed the “connection failed” popup, I was able to click on “blank” to create a blank application. First thing I did was make sure the connection under “SQL” was my new (local) connection. I then inserted code into the “onExecute” event to retrieve a row from the DB, saved and generated the app. I ran it and it worked perfectly.

Confused, I then went back and re-ran one of my existing apps… similar outcome as before… but now it says “connection refused” (IE, “An error occurred while connecting to the database:
Connection attempt failed: SQLSTATE[HY000] [2002] Connection refused”)

So to summarise where we are:

  • “test database” in edit connection returns success.
  • queries in SQL Builder are successful.
  • clicking on “New Application” produces a “connection failed” popup with “SQLSTATE[HY000] [2002] Connection refused |n Script: /Applications/Scriptcase/v9/wwwroot/scriptcase/devel/class/page/nmPageWizard.class.php linha: 5144”.
  • closing the “connection failed” popup and pushing ahead to build a blank application to access rows in the database results in success.
  • generating and running ANY of the exiting applications in my project results in “SQLSTATE[HY000] [2002] Connection refused”

Do I assume that the “connection timeout” issue seems to have been resolved and I now have a security issue? Why are some functions working and others not?

I have edited the php.ini several times - I have possibly fixed something but clearly not all the issues.

Any ideas?

#10

So I have been poking around. My original connection was called “conn_mysql_ontrax”. My new connection is called “conn_mysql_local”. When I look at the generated code for the new black application I can clearly see the reference for the new connection (“conn_mysql_local”). But when I look at the generated code for the exiting applications it still seems to reference the old connection as exhibited by the generated code snippet below (see “nm_db_conn_mysql_ontrax”). So while I have changed the connection in all the apps, is it possible that Scriptcase is still generating code for the original connection? Or do I have this completely wrong?

function NM_close_db()
{
if ($this->Db && !$this->Embutida_proc)
{
$this->Db->Close();
$this->Ini->nm_db_conn_mysql_ontrax->Close();
}
}

May be I should go back to the old connection and change the values to point to the local DB and test it?

#11

Mystery resolved.

I did exactly what I said (per your original suggestion) - I changed the original connection to values for the local MySQL instance. I went back into an existing app and reverted the connection under “SQL” back to the original connection name, saved and re-gened. Ran the existing app and it worked.

For completeness, I changed the connection in the new blank app and it worked. On checking the newly generated code for the blank app I note that it did change the connection name.

So I can only conclude that for forms and grids at least (noting that this is all I have tested), changing the connection name does not result in newly generated code for the new connection.

I would call this a fairly serious bug. Scriptcase is not picking up the change in connection for the app, and is not generating code for the new connection. It makes the ability to change the connection for existing apps (under SQL & express edit) completely redundant.

Happy to be told otherwise.

#12

happy for you that it is solved, sometimes it is enough to change the connection, then to leave scriptcase, to connect again and everything returns correctly, good continuation