5433 port was closed after write data 10000 times

Hi, I meet a problem when I use yugabyte.

I use C# Npgsql to write data and found that 5433 port was closed after write data 10000 times, thus I cannot write data again, and I have to restart yugabyte and then every thing is ok.

how can I solve this problem? fellow is that when I cannot write data ,and I found 5433 port is closed.

D:>docker exec -it yb-tserver-n1 /home/yugabyte/bin/ysqlsh
ysqlsh: could not connect to server: Connection refused
Is the server running on host “localhost” (127.0.0.1) and accepting
TCP/IP connections on port 5433?
could not connect to server: Cannot assign requested address
Is the server running on host “localhost” (::1) and accepting
TCP/IP connections on port 5433?

D:>

when SQL 5433 port was closed and I found that CSQL 9042 is ok, at the same time, I can write data with CSQL 9042。

Can you paste some logs ? Especially from .postgresql log.

where can I get yugabytedb logs, I use docker yugabytedb in my windows pc.

发自我的华为手机

发件人: Dorian Hoxha via Yugabyte Community Forum yugabyte@discoursemail.com
日期: 2021年7月9日周五 下午3:50
收件人: 13168098175@163.com
主 题: [Yugabyte Community Forum] [Design Discussions] 5433 port was closed
after write data 10000 times

Try running:

docker exec -it yugabyte /home/yugabyte/bin/yugabyted collect_logs

And upload the file somewhere and link to it.

[yugabyted collect_logs] 2021-07-12 02:28:35,024 INFO: | 0.0s | cmd = collect_logs using config file: /root/var/conf/yugabyted.conf (args.config=None)
[yugabyted collect_logs] 2021-07-12 02:28:35,024 INFO: | 0.0s | Found directory /home/yugabyte/bin for file yb-admin
[yugabyted collect_logs] 2021-07-12 02:28:35,029 INFO: | 0.0s | Logs are packaged into /root/yugabyted-2021-07-12-02:28:35.025092.tar.gz
[yugabyted collect_logs] 2021-07-12 03:49:00,496 INFO: | 0.0s | cmd = collect_logs using config file: /root/var/conf/yugabyted.conf (args.config=None)
[yugabyted collect_logs] 2021-07-12 03:49:00,496 INFO: | 0.0s | Found directory /home/yugabyte/bin for file yb-admin
[yugabyted collect_logs] 2021-07-12 03:49:00,500 INFO: | 0.0s | Logs are packaged into /root/yugabyted-2021-07-12-03:49:00.497066.tar.gz
[yugabyted collect_logs] 2021-07-12 06:47:32,527 INFO: | 0.0s | cmd = collect_logs using config file: /root/var/conf/yugabyted.conf (args.config=None)
[yugabyted collect_logs] 2021-07-12 06:47:32,531 INFO: | 0.0s | Found directory /home/yugabyte/bin for file yb-admin

D:>docker exec -it yb-tserver-n1 /home/yugabyte/bin/ysqlsh
ysqlsh: could not connect to server: Connection refused
Is the server running on host “localhost” (127.0.0.1) and accepting
TCP/IP connections on port 5433?
could not connect to server: Cannot assign requested address
Is the server running on host “localhost” (::1) and accepting
TCP/IP connections on port 5433?

D:>docker exec -it yb-master-n1 /home/yugabyte/bin/yugabyted collect_logs
Logs are packaged into /root/yugabyted-2021-07-12-06:47:32.531778.tar.gz

D:>docker cp yb-master-n1:/root/yugabyted-2021-07-12-06:47:32.531778.tar.gz 3.tar.gz

5433 port is closed now, then I collect yugabyte log, but I found the content of log is simple, maybe not useful for analysing.

Can you upload it somewhere and link to it still ?

this is log

发件人: Dorian Hoxha via Yugabyte Community Forum yugabyte@discoursemail.com
日期: 2021年7月12日周一 下午3:22
收件人: 13168098175@163.com
主 题: [Yugabyte Community Forum] [Design Discussions] 5433 port was closed
after write data 10000 times

(Attachment yugabyted-2021-07-12-06_47_32.531778.tar is missing)

sorry, I try and found that I cannot upload log as attachment, so can you email me 13168098175@163.com, then I reply you with log as attachment in my reply email.

Your file was empty. I literally just tried this guide to create a cluster: Create a local YugabyteDB cluster on Docker | YugabyteDB Docs

And then collected logs:

$ docker exec -it yugabyte /home/yugabyte/bin/yugabyted collect_logs
Logs are packaged into /root/yugabyted-2021-07-12-09:33:57.916847.tar.gz

And copied the file and it had the logs for yb-tserver,yb-master,yugabyted,postgresql:

docker cp yugabyte:/root/yugabyted-2021-07-12-09:33:57.916847.tar.gz docker_logs.tar.gz

Somewhere in there you did wrong that you got an ~empty file. Can you retry ?

Or you can get them manually, they should be inside the docker in /root/var/logs

Please explain how you deployed with docker containers including full commands that you ran (or guide that you followed).

As explained in the logs page, you can find logs inside the --fs_data_dir paths

  • When using the --fs_data_dirs flag with multiple directories, logs will be saved in the first directory in the list.

Can you try in a linux box/vm (centos,ubuntu) using the yugabyted cli for development ? Running on windows+docker isn’t totally supported. The program is running very slow and can’t even synchronize the clock between the containers (which have to look at how windows is doing the virtualization and any problems with ntp underneath).

I will try in centos or Ubuntu. thank you.

发件人: Dorian Hoxha via Yugabyte Community Forum yugabyte@discoursemail.com
日期: 2021年7月13日周二 傍晚6:02
收件人: 13168098175@163.com
主 题: [Yugabyte Community Forum] [Design Discussions] 5433 port was closed
after write data 10000 times