plugnmeet "suddenly" stopped working
jhjacobs81 opened this issue · comments
So today i was trying to login using my wordpress plugin when suddenly plugnmeet no longer works :(
I can access the page, enter my details, then it asks how i want to join, i click microphone, and after a while it says "Error: could not connect PeerConnection after timeout"
i tried rebooting the machine, disabling the firewall (and reboot), updating it, nothing works.
What would be my best approach to fix this issue?
Please check log from /opt/plugNmeet/log/plugNmeet.log. Also you can check logs of docker processes.
docker ps
docker logs -n 300 PLUGNMEET OR LIVEKIT CONTAINER ID
thank you :)
the log in opt/plugnmeet/log/plugnmeet.log says:
{"file":"/go/src/app/cmd/server/main.go:58","func":"main.startServer.func1","level":"info","msg":"exit requested, shutting down signal terminated","time":"2023-04-01T15:16:16Z"}
{"file":"/go/src/app/pkg/factory/mysqlDb.go:26","func":"github.com/mynaparrot/plugnmeet-server/pkg/factory.NewDbConnection","level":"fatal","msg":"dial tcp [::1]:3306: connect: connection refused","time":"2023-04-01T15:16:50Z"}
{"file":"/go/src/app/pkg/factory/mysqlDb.go:26","func":"github.com/mynaparrot/plugnmeet-server/pkg/factory.NewDbConnection","level":"fatal","msg":"dial tcp [::1]:3306: connect: connection refused","time":"2023-04-01T15:16:51Z"}
netstat says:
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 932/mariadbd
docker logs plugnmeet server:
working?
┌───────────────────────────────────────────────────┐
│ Fiber v2.41.0 │
│ http://127.0.0.1:8080 │
│ (bound on host 0.0.0.0 and port 8080) │
│ │
│ Handlers ............ 87 Processes ........... 1 │
│ Prefork ....... Disabled PID ................. 1 │
└───────────────────────────────────────────────────┘
docker logs livekit server:
[2023-04-01 15:16:50.894] [INFO] settings - All relative paths will be interpreted relative to the identified Etherpad base dir: /opt/etherpad-lite
[2023-04-01 15:16:51.002] [INFO] settings - settings loaded from: /opt/etherpad-lite/settings.json
[2023-04-01 15:16:51.003] [INFO] settings - No credentials file found in /opt/etherpad-lite/credentials.json. Ignoring.
[2023-04-01 15:17:01.867] [WARN] console - Admin username and password not set in settings.json. To access admin please uncomment and edit "users" in settings.json
docker logs mariadb:
2023-04-01 15:16:49+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.10.2+maria~ubu2204 started.
2023-04-01 15:16:50+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2023-04-01 15:16:50+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.10.2+maria~ubu2204 started.
2023-04-01 15:16:51+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
2023-04-01 15:16:51 0 [Note] mariadbd (server 10.10.2-MariaDB-1:10.10.2+maria~ubu2204) starting as process 1 ...
2023-04-01 15:16:51 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-04-01 15:16:51 0 [Note] InnoDB: Number of transaction pools: 1
2023-04-01 15:16:51 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2023-04-01 15:16:51 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2023-04-01 15:16:51 0 [Note] InnoDB: Using liburing
2023-04-01 15:16:51 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2023-04-01 15:16:51 0 [Note] InnoDB: Completed initialization of buffer pool
2023-04-01 15:16:51 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2023-04-01 15:16:51 0 [Note] InnoDB: 128 rollback segments are active.
2023-04-01 15:16:51 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2023-04-01 15:16:51 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2023-04-01 15:16:51 0 [Note] InnoDB: log sequence number 199774; transaction id 369
2023-04-01 15:16:51 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2023-04-01 15:16:51 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-04-01 15:16:51 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
2023-04-01 15:16:51 0 [Note] InnoDB: Buffer pool(s) load completed at 230401 15:16:51
2023-04-01 15:16:51 0 [Note] Server socket created on IP: '0.0.0.0'.
2023-04-01 15:16:51 0 [Note] Server socket created on IP: '::'.
2023-04-01 15:16:51 0 [Note] mariadbd: ready for connections.
Version: '10.10.2-MariaDB-1:10.10.2+maria~ubu2204' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
a docker ps shows everything running and healthy
when i run docker-compose up i can see the logs.. when i try to connect i get this:
livekit_1 | 2023-04-01T15:31:45.860Z INFO livekit service/twirp.go:120 API RoomService.ListRooms {"service": "RoomService", "method": "ListRooms", "room": ["2488719d-b799-4f79-961d-dac97c269bff"], "duration": "262.184µs", "status": "200"}
livekit_1 | 2023-04-01T15:31:48.916Z INFO livekit rtc/room.go:308 new participant joined {"room": "2488719d-b799-4f79-961d-dac97c269bff", "roomID": "RM_Jge247hRg9Bk", "pID": "PA_W67yfCEQLokF", "participant": "2", "protocol": 9, "options": {"AutoSubscribe":true}}
livekit_1 | 2023-04-01T15:31:48.924Z INFO livekit rtc/room.go:257 participant state changed {"room": "2488719d-b799-4f79-961d-dac97c269bff", "roomID": "RM_Jge247hRg9Bk", "state": "JOINED", "participant": "2", "pID": "PA_W67yfCEQLokF", "oldState": "JOINING"}
livekit_1 | 2023-04-01T15:31:48.941Z INFO livekit service/rtcservice.go:266 new client WS connected {"room": "2488719d-b799-4f79-961d-dac97c269bff", "roomID": "RM_Jge247hRg9Bk", "participant": "2", "pID": "PA_W67yfCEQLokF", "remote": false, "connID": "CO_HJ5vqMdoRAt3"}
livekit_1 | 2023-04-01T15:32:03.990Z INFO livekit service/rtcservice.go:236 finishing WS connection {"room": "2488719d-b799-4f79-961d-dac97c269bff", "roomID": "RM_Jge247hRg9Bk", "participant": "2", "pID": "PA_W67yfCEQLokF", "remote": false, "connID": "CO_HJ5vqMdoRAt3"}
livekit_1 | 2023-04-01T15:32:24.161Z INFO livekit rtc/transport.go:528 peer connection failed {"room": "2488719d-b799-4f79-961d-dac97c269bff", "roomID": "RM_Jge247hRg9Bk", "participant": "2", "pID": "PA_W67yfCEQLokF", "remote": false, "transport": "SUBSCRIBER"}
livekit_1 | 2023-04-01T15:32:24.164Z INFO livekit rtc/participant_signal.go:232 closing signal connection {"room": "2488719d-b799-4f79-961d-dac97c269bff", "roomID": "RM_Jge247hRg9Bk", "participant": "2", "pID": "PA_W67yfCEQLokF", "remote": false}
livekit_1 | 2023-04-01T15:32:39.169Z INFO livekit rtc/participant.go:1347 closing disconnected participant {"room": "2488719d-b799-4f79-961d-dac97c269bff", "roomID": "RM_Jge247hRg9Bk", "participant": "2", "pID": "PA_W67yfCEQLokF", "remote": false}
livekit_1 | 2023-04-01T15:32:39.173Z INFO livekit rtc/participant.go:614 participant closing {"room": "2488719d-b799-4f79-961d-dac97c269bff", "roomID": "RM_Jge247hRg9Bk", "participant": "2", "pID": "PA_W67yfCEQLokF", "remote": false, "sendLeave": true, "reason": "PEER_CONNECTION_DISCONNECTED"}
livekit_1 | 2023-04-01T15:32:39.176Z INFO livekit rtc/participant_signal.go:215 could not send message to participant {"room": "2488719d-b799-4f79-961d-dac97c269bff", "roomID": "RM_Jge247hRg9Bk", "participant": "2", "pID": "PA_W67yfCEQLokF", "remote": false, "messageType": "*livekit.SignalResponse_Leave"}
livekit_1 | 2023-04-01T15:32:39.178Z INFO livekit rtc/room.go:257 participant state changed {"room": "2488719d-b799-4f79-961d-dac97c269bff", "roomID": "RM_Jge247hRg9Bk", "state": "DISCONNECTED", "participant": "2", "pID": "PA_W67yfCEQLokF", "oldState": "JOINED"}
livekit_1 | 2023-04-01T15:32:59.704Z INFO livekit rtc/room.go:573 closing room {"room": "2488719d-b799-4f79-961d-dac97c269bff", "roomID": "RM_Jge247hRg9Bk"}
livekit_1 | 2023-04-01T15:32:59.709Z INFO livekit service/roommanager.go:110 deleting room state {"room": "2488719d-b799-4f79-961d-dac97c269bff"}
livekit_1 | 2023-04-01T15:32:59.725Z INFO livekit service/roommanager.go:427 room closed {"room": "2488719d-b799-4f79-961d-dac97c269bff", "roomID": "RM_Jge247hRg9Bk"}
Please use update script to update server. plugNmeet wasn't able to communicate with MySQL. You will require to check it manually to find the reason.
i did that before i created this ticket, want me to do it again?