I currently have developed a server in node.js (and respective client) which works without hassle. It uses socket.io and communicates with a mysql database to retrieve some info for certain messages.
The problem is that I tried uploading it online using Nodejitsu. The communication works without problem but when it's the the server's turn to send a query for the database nothing happens, the client just sits there.
Is there and issue with nodejitsu? Seeing that all other modules work except the communication with the a mysql database I had setup.
Note that when running the server in my computer and communicating via localhost everything works flawlessly.
Related
My app seems to run fine sometimes, and other times it says it cannot connect to any of the MySQL servers.
I started out with the MySQL server being hosted in azure as well, but I moved it external due to connectivity issues.
I finally moved the ASP.Net app to a real VM instead of being hosted as a website. I tested a manual connection to the MySQL server when it became unresponsive and it failed as well. I then did a trace route to the server and it failed as well.
Is this a known issue? Is this a duplicate of: Classic ASP site on Azure web site, remote mysql database
I am currently running a virtualized environment for my web and db server. When I access the web server or the MySQL server individually, they are both fast. I also have websites running on the web server that do not require the db server and those all load quickly. However, when I access my hosted website that requires the web server to call from the db server, there is about a 5-7 second latency for every page load. This has been confirmed with both a very simple site and with a Word Press setup as well. Here is the config:
Web server - CentOS 6.5, Apache 2.2.15
DB server - CentOS 6.5, MySQL 5.1.73
My question is, are the servers continuously authenticating with one another (and thus causing latency) on every single db call? If that is the case, does anyone know how to permanently authenticate between the two?
I might be way off on this assumption and authentication could have nothing to do with it. I am completely open to any and all ideas at this point. Thank you very much.
V/R,
Tony
To me it seems to be a network issue.
and obviously the db-server will need authentication every time there is a hit.
I got stuck in deployement of my website built using ASP.Net, C# and using sql server 2008 database. The problem is that website is working perfectly fine on localhost but it is not connecting with database when I hosted it on web, I know that the problem is in Sql server database in giving permission or something but I don't know exactly because the connection and user which I have created is exactly the same as I used while development and as soon as I deployed it on web the part which is not using database is working fine that is login page but when I enter username and password in the interface and hit login it does not go into database and pull the data, I mean it does not connect to database at all.
My question is that does it matters in accessing database from localhost and from web, Though I am still using My local computer for Coding and using the company"s database through VPN. This is first time I am deploying the website on web and I need some help, I know my way of asking question might ambiguous but please try to understand and if you have some question than please ask don't just ignore.
Many thanks in advance.
Most frequent solutions:
Enable TCP/IP protocol for sql server instance.
Enable SQL Server Browser service.
Open firewall ports.
More information:
http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/
I am designing the backend of my ios application. The backend has separate database and application server running mysql and django separately in different machines. Till now, I have connected my application server with my database server in simple way: I changed the database host in application server settings to point to remore database server and created a new remote host in database server configuration files allowing remote application server to access the database. All works fine and I have decided to go with this setup for production. Then when I was reading Instagram engineering blog, I saw them mentioning 'Pgbouncer' to pool connection to their postgresql database server. What is the need for something like this? Has this got something to do with only performance, or is this a production friendly approach to use something like this for communication between database and application server. Is my general approach mentioned too amateur?
Your approach is not amateur at all. The purpose of bouncer in your case would be to eliminate connection time that happens on each request django handles. For example, on Heroku, which is hosted on AWS servers, this could eat up 40-50ms of each request.
Now, if you had a master/slave setup or something like that, a connection pool would also provide you a failover functionality (just an example)
We have an android app that currently sends data to a php script which writes to a mysql DB on the same server. We are thinking of using a scalable DB server e.g. FathomDB (which is just based on amazon RDS & rackspace) so that we can handle load increases easily.
The question is how does our android app write to these remote DBs? Do they have some kind of rest API, or allow you to have a php script similar to the one we have in place at the moment?
I'd say most of services like these have a connector running on the web, like the one you are using. But some of the services you mention (for example amazon rds) have a native mysql connection. So you can connect using mysql to the server and run queries like you currently do in php. You can use ACL to ensure security in your application :)