Revision history  [back]

I have a small network with a local database server (PostgreSQL) and 6 clients. It's all Windows.

Several times per day a timeout occurs when one of the clients sends SQL Queries to the server.

E.g. the client reports a 2022-04-01 15:24:06,959. tshark is running constantly on both ends and I looked for packets at about 15:23:51 (timeout is 15 seconds).

In the trace I see that the corresponding SQL query is not sent out to the server at 15:23:51.

The clients ip address is fe80::d9db:dcdf:58d3:2d03, fe80::d9db:dcdf:58d3:2d03, the server's ip address is fe80::804b:e959:60b:e90b.fe80::804b:e959:60b:e90b.

Client trace: https://1drv.ms/u/s!AphLkdj_V9pOqAE6We1pjs4KhzxA?e=adczjV

Server trace: https://1drv.ms/u/s!AphLkdj_V9pOqAB-RQCY7Z3BF3RK?e=raWUvD

My question is: does the trace show any hints why the server's response does not reach the client? Is it maybe a DNS issue?

EDIT: The traces are anonymized using TraceWrangler. Therefore no PGSQL queries are included in the trace and the DNS queries are cut down to UDP packets.

I have a small network with a local database server (PostgreSQL) and 6 clients. It's all Windows.

Several times per day a timeout occurs when one of the clients sends SQL Queries to the server.

E.g. the client reports a 2022-04-01 15:24:06,959. tshark is running constantly on both ends and I looked for packets at about 15:23:51 15:23:51 (timeout is 15 seconds).

In the trace I see that the corresponding SQL query is not sent out to the server at 15:23:51.

The clients ip address is fe80::d9db:dcdf:58d3:2d03, the server's ip address is fe80::804b:e959:60b:e90b.

Client trace: https://1drv.ms/u/s!AphLkdj_V9pOqAE6We1pjs4KhzxA?e=adczjV

Server trace: https://1drv.ms/u/s!AphLkdj_V9pOqAB-RQCY7Z3BF3RK?e=raWUvD

My question is: does the trace show any hints why the server's response does not reach the client? Is it maybe a DNS issue?

EDIT: The traces are anonymized using TraceWrangler. Therefore no PGSQL queries are included in the trace and the DNS queries are cut down to UDP packets.

I have a small network with a local database server (PostgreSQL) and 6 clients. It's all Windows.

Several times per day a timeout occurs when one of the clients sends SQL Queries to the server.

E.g. the client reports a 2022-04-01 15:24:06,959*2022-04-01 15:24:06,959 *. tshark is running constantly on both ends and I looked for packets at about 15:23:51 (timeout is 15 seconds).

In the trace I see that the corresponding SQL query is not sent out to the server at 15:23:51.

The clients ip address is fe80::d9db:dcdf:58d3:2d03, the server's ip address is fe80::804b:e959:60b:e90b.

Client trace: https://1drv.ms/u/s!AphLkdj_V9pOqAE6We1pjs4KhzxA?e=adczjV

Server trace: https://1drv.ms/u/s!AphLkdj_V9pOqAB-RQCY7Z3BF3RK?e=raWUvD

My question is: does the trace show any hints why the server's response does not reach the client? Is it maybe a DNS issue?

EDIT: The traces are anonymized using TraceWrangler. Therefore no PGSQL queries are included in the trace and the DNS queries are cut down to UDP packets.

I have a small network with a local database server (PostgreSQL) and 6 clients. It's all Windows.

Several times per day a timeout occurs when one of the clients sends SQL Queries to the server.

E.g. the client reports a *2022-04-01 15:24:06,959 *timeout at 2022-03-29 14:31:42,604. tshark is running constantly on both ends the server and I looked for packets at about 15:23:51 14:31:27 (timeout is 15 seconds).

In the trace I see is that the corresponding SQL query is notbeing received at No. 212 (14:31:27,452250) sent out to and responded immediately by the server at 15:23:51.server. But for any reason the response doesn't reach the client.

The clients ip address is fe80::d9db:dcdf:58d3:2d03, the fe80::cd78:c9cc:589c:e21b, server's ip address is fe80::804b:e959:60b:e90b.

Client trace: https://1drv.ms/u/s!AphLkdj_V9pOqAE6We1pjs4KhzxA?e=adczjV

Server trace: https://1drv.ms/u/s!AphLkdj_V9pOqAB-RQCY7Z3BF3RK?e=raWUvD

My question is: does the trace show any hints why the server's response does not reach the client? Is it maybe a DNS issue?client?

EDIT: The traces are anonymized using TraceWrangler. Therefore no PGSQL queries are included in Unfortunately I cannot publish the trace and the DNS queries are cut down to UDP packets.as it contains sensible data.

Therefore this thread can be closed.

I have a small network with a local database server (PostgreSQL) and 6 clients. It's all Windows.

Several times per day a timeout occurs when one of the clients sends SQL Queries to the server.

E.g. the client reports a timeout at 2022-03-29 14:31:42,604. tshark is running constantly on the server and I looked for packets at about 14:31:27 (timeout is 15 seconds).

In the trace I see is that the SQL query is being received at No. 212 (14:31:27,452250) and responded immediately by the server. But for any reason the response doesn't reach the client.

The clients ip address is fe80::cd78:c9cc:589c:e21b, server's ip address is fe80::804b:e959:60b:e90b.

My question is: does the trace show any hints why the server's response does not reach the client?

EDIT: Unfortunately I cannot publish the trace as it contains sensible data.

Therefore this thread can be closed.

I have a small network with a local database server (PostgreSQL) and 6 clients. It's all Windows.

Several times per day a timeout occurs when one of the clients sends SQL Queries to the server.

E.g. the client reports a timeout at 2022-03-29 14:31:42,604. tshark is running constantly on the server and I looked for packets at about 14:31:27 (timeout is 15 seconds).

In the trace I see is that the SQL query is being received at No. 212 (14:31:27,452250) and responded immediately by the server. But for any reason the response doesn't reach the client.

The clients ip address is fe80::cd78:c9cc:589c:e21b, server's ip address is fe80::804b:e959:60b:e90b.

My question is: does the trace show any hints why the server's response does not reach the client?

EDIT: Unfortunately I cannot publish Find the trace as it contains sensible data.

Therefore this thread can be closed.here: https://1drv.ms/u/s!AphLkdj_V9pOp3_OnbwtmwPoq75z