I am trying to capture mysql queries. server run on localhost:8090 and database is running on localhost:3306.
Console log is:
INFO: Server startup in [938] milliseconds
Query is: select * from film where film_id = '123'.
CASABLANCA SUPER A Amazing Panorama of a Crocodile And a Forensic Psychologist who must Pursue a Secret Agent in The First Manned Space Station
When i send request to server wireshark captures only mysql login request.
How can i capture the actual query?
Related
For the past week, multiple SSIS packages running on SQL Server Agent that load data into Snowflake have started returning the follow message randomly.
"Failed to acquire connection "snowflake". Connection may not be configured correctly or you may not have the right permissions on this connection."
We are seeing this message across multiple jobs and each of the jobs is loading multiple tables and its not happening on each call to Snowflake within the projects, but just on one or two tasks in jobs that have 100s.
We are using the 2.20.2 drivers from Snowflake
We have ran the jobs while WireShark was capturing network traffic and were received by the network team. They didn't have much luck because the ACK messages were not being shown.
We also ran Process Monitor while the jobs ran and we did not find anything that alluded to any issues
We also dug though the logs from the Snowflake driver and found the calls right before and right after, but no messages for the task that failed. Since those logs bounce around on which file they are sending to, its a bit hard to track sequential actions when multiple task on a job are running together.
We also installed SnowCD and ran it and it returned a full success message.
The user that runs the jobs on SQL Server Agent is an Admin on the server and has SysAdmin rights on the Sql Sever instance.
The warehouse the drivers are connected to are a size Large with a max of 3 clusters (was at 1 when the issue started, but upped it to 3 to see if that helped)
Jobs are running on Windows Server 2016 DataCenter in Azure
SQL Server instance is Sql Sever 2016 13.0.4604.0
We cannot figure out why we are suddenly and randomly using connection to Snowflake.
Some ideas to help get these packages working:
Add a retry to the tasks that are failing. The task would move onto the next step only upon success:
https://www.mssqltips.com/sqlservertip/5625/how-to-retry-sql-server-integration-services-ssis-control-flow-tasks/
You can also combine the truncate and insert into one step using the insert overwrite into command which will allow your package to run quicker and have one less task for failure:
https://docs.snowflake.net/manuals/sql-reference/sql/insert.html#insert-using-overwrite
Once the SSIS packages are consistently completing, you can analyze the logs at the point of failure to see if there is any pattern to help you identify the root cause.
In MySQL DB server we have schema named test. The schema has table named users.
The table users not used in any place by rails application. The only place the entry for users found is in schema.rb.
The users tables has some data stored and data gets inserted by another java application which runs on some other server. The rails application makes API call to JAVA application via HTTPs and retrieves the data for usage if needed.
Daily the MySQL Master DB gets replicated to Slave server.
During replication the bellow query getting logged in slow logs and its making replication lag.
root localhost test Query 93 Sending data SELECT /*!40001 SQL_NO_CACHE */ * FROM `users`
root localhost test Query 62 Writing to net SELECT /*!40001 SQL_NO_CACHE */ * FROM `users`
This query is not fired from Rails application - we can see the user and host of the connection in logs is root and localhost.
I would be very grateful if someone helps me to identify origin of the query and how can or what can be done to avoid query.
I had the same problem. In my case it was due to calling mysqldump.
Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library.
Error: 17836, Severity: 20, State: 14. I am getting this error 5 times at the same time almost and want to know the reason for its occurrence.
See the solution here:
Since the SQL Server has Event ID 17836 logged, the SQL port is open.
It is more like authentication issue. Based on this articles
(Configuration for querying SQL database remotely –
http://www.howtonetworking.com/others/testsqlconnect2.htm ), we may
have 3 fixes:
creating SQL login ID (recommended)
join the computer to the domain
allow anonymous connections to SQL Server 2000 or to SQL Server 2005 (don’t recommend)
And this MSDN forum
Perform a nslookup of the CLIENT IP Address that is listed in the
error message and find out what computer it is that is connecting.
Then you need to check that machine and determine what specifically is
connecting to the SQL Server. You might get more infromation from
doing a SQL Trace for the Errors and Warnings Event Class and have the
ClientProcessID column in the trace data. When the error spikes, you
might get the PID for the process that is connecting from that
10.26.32.96 machine, and then you can find that process in Task Manager on that machine by adding the PID to the data displayed (View
-> Select Columns).
In my case, these events coincided with me doing telnet connectivity tests to our SQL Servers. We would see one entry in the Windows Event Log for each instance we successfully did a telnet to.
I am using SQL Server 2014 on a Windows 2012 server. I have several database instances on the server.
One of the instances has an error in the log every day at 2 AM.
Login failed for user MyDomain\SQLAgentAccount.
Reason: Could not find a login matching the name provided.
[CLIENT: ].
Error: 18456, Severity: 14, State: 5
This is the service account used for SQL Server Agent. The Agent service is running and all jobs run successfully. I was able to trace it back to see that it is coming from PowerShell.
If I add the account explicitly, the error goes away. But I did not need to do that on the other instances and don't think it would be best practices to do so here.
Does SQL Server has an external log file or internal table for attempted connections, or is that kind of info put somewhere in the Windows Event Log?
You can enable connection logging. For SQL Server 2008, you can enable Login Auditing. In SQL Server Management Studio, open SQL Server Properties > Security > Login Auditing select "Both failed and successful logins".
Make sure to restart the SQL Server service.
Once you've done that, connection attempts should be logged into SQL's error log. The physical logs location can be determined here.
Another way to check on connection attempts is to look at the server's event log. On my Windows 2008 R2 Enterprise machine I opened the server manager (right-click on Computer and select Manage. Then choose Diagnostics -> Event Viewer -> Windows Logs -> Applcation.
You can filter the log to isolate the MSSQLSERVER events.
I found a number that looked like this
Login failed for user 'bogus'. The user is not associated with a trusted SQL Server connection. [CLIENT: 10.12.3.126]
If you'd like to track only failed logins, you can use the SQL Server Audit feature (available in SQL Server 2008 and above). You will need to add the SQL server instance you want to audit, and check the failed login operation to audit.
Note: tracking failed logins via SQL Server Audit has its disadvantages. For example - it doesn't provide the names of client applications used.
If you want to audit a client application name along with each failed login, you can use an Extended Events session.
To get you started, I recommend reading this article: http://www.sqlshack.com/using-extended-events-review-sql-server-failed-logins/