# Unable to run sample code for linux meeting SDK **URL:** \ **Category:** Meeting SDK\ **Tags:** sample-app\ **Created:** [November 27, 2023, 2:13pm UTC](https://devforum.zoom.us/t/unable-to-run-sample-code-for-linux-meeting-sdk/99072 "2023-11-27T14:13:10Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![cmr-anup](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/cmr-anup/32/50483_2.png) [@cmr-anup](https://devforum.zoom.us/u/cmr-anup)\ **Post date:** [November 27, 2023, 2:13pm UTC](https://devforum.zoom.us/t/unable-to-run-sample-code-for-linux-meeting-sdk/99072/1 "2023-11-27T14:13:11Z")
Hello I have encountered the following issue with the sample code for linux meeting SDK. **Meeting SDK Type and Version** Platform: Linux. Windows 10 Pro / Windows 11 with WSL2 running Ubuntu 22.04 MeetingSDKVersion: 5.16.0.8201 - downloaded the meeting-sdk-linux\_x86\_64-5.16.0.8201.tar file **Description** In short, I am unable to join a meeting as a bot, using the sample code provided. As soon as the docker container is run, it gives the error below. **Steps to Reproduce** Followed the README instructions for the sample code- [GitHub - zoom/meetingsdk-linux-raw-recording-sample](https://github.com/zoom/meetingsdk-linux-raw-recording-sample/tree/main) 1. Copied relevant files from meeting SDK to demo/ folder as instructed. 2. Built the docker container according to instructions for ubuntu 22.04 3. Made changes to withoutloginParam.userName as instructed. 4. Built the executable using make . 5. Had already created a meeting SDK app using one zoom account (free and pro both were tried) and copied the client\_id and secret to the config.txt file - lets call it account A. 6. Created a meeting through another account (account B). So account B is the host. 7. Now for obtaining the JWT token for the config.txt file, I used the ([GitHub - zoom/meetingsdk-auth-endpoint-sample: Generate a Meeting SDK JWT to join Zoom meetings and webinars with the Meeting SDK](https://github.com/zoom/meetingsdk-auth-endpoint-sample)) repository with the credentials from account A, passed the meeting\_id to the API endpoint and used the response. Started the meeting using a desktop zoom client through account B. Error: On running the docker container, I get the following- > sudo docker run -it --rm msdk-5.16.5-on-ubuntu-compact:0.20 > unix:path=/run/dbus/system\_bus\_socket,guid=43db63e6862f27e56c730a446564619c > Adding user `root' to group `pulse-access’ … > Adding user root to group pulse-access > Done. > Adding user `root' to group `audio’ … > Adding user root to group audio > Done. > cp: target ‘/root/.config/pulse/’ is not a directory > W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified). > 19 > mkdir: cannot create directory ‘/root/.config’: File exists > getpath > self path: /app/demo/bin > Readfile success. > Reading…meeting\_number: “77531321111” > Reading…token: “TOKEN” > Reading…meeting\_password: “11111” > Reading…recording\_token: “” > Reading…GetVideoRawData: “false” > Reading…GetAudioRawData: “false” > Meeting Number: 77531321111 > Token: TOKEN > meeting\_password: 11111 > recording\_token: > GetVideoRawData before parsing is : false > GetVideoRawData: 0 > GetAudioRawData before parsing is : false > GetAudioRawData: 0 > directory of config file: /app/demo/bin/config.txt > Init meetingSdk:success > AuthService created. > AuthServiceEventListener added. > AuthSDK:token extracted from config file TOKEN > Auth succeeded: JWT. > OnAuthenticationComplete > Joining Meeting > MeetingService created. > Settingservice created. > JWT token is TOKEN > Recording token is > Leaving recording token as NULL > join\_meeting:success > onLoginReturnWithReason: 0 > onMeetingStatusChanged: 1, iResult: 0 > Connect to the meeting server status. > onMeetingStatusChanged: 4, iResult: 0 > Disconnect the meeting server, leave meeting status. > onMeetingStatusChanged: 6, iResult: 63 > Failed to connect the meeting server. > onMeetingStatusChanged: 7, iResult: 0 > Meeting ends. **Troubleshooting Routes** On checking the linuxSDK documentation, I interpreted the above error as - > MEETING\_FAIL\_UNABLE\_TO\_JOIN\_EXTERNAL\_MEETING From [https://marketplacefront.zoom.us/sdk/meeting/linux/meeting\_\_service\_\_interface\_8h.html#af6483466bf33caf90bf3901c024780e4](https://marketplacefront.zoom.us/sdk/meeting/linux/meeting __service__ interface_8h.html#af6483466bf33caf90bf3901c024780e4) But I don’t know how to resolve this issue. Perhaps I’ve not understood how to run the sample code correctly. Could you please help me with this issue? Thank You. ---
**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\ **Post date:** [November 28, 2023, 3:49am UTC](https://devforum.zoom.us/t/unable-to-run-sample-code-for-linux-meeting-sdk/99072/2 "2023-11-28T03:49:17Z")
@cmr-anup , Your setup should be fine. However if you did not publish your Meeting SDK application (account A) yet, you won’t be able to join meeting hosted by external accounts (account B). To do a quick verification, try to create and join meeting with a user in the same account (both account A) as the Meeting SDK. ---
**Author:** ![cmr-anup](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/cmr-anup/32/50483_2.png) [@cmr-anup](https://devforum.zoom.us/u/cmr-anup)\ **Post date:** [November 29, 2023, 3:31am UTC](https://devforum.zoom.us/t/unable-to-run-sample-code-for-linux-meeting-sdk/99072/3 "2023-11-29T03:31:04Z")
@chunsiong.zoom Thank you for your reply. On trying your suggestion, I no longer get the error, however the terminal output remains stuck at “Joining meeting…” , while I don’t see the bot in the meeting. The last few lines of the terminal output are below- > Recording token is > Leaving recording token as NULL > join\_meeting:success > onLoginReturnWithReason: 0 > onMeetingStatusChanged: 1, iResult: 0 > Connect to the meeting server status. > onMeetingParameterNotification > Joining Meeting… Also, to ensure that it isn’t an issue with account permissions, I tried to join the same meeting using the windows sample code bot, and it worked successfully. ---
**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\ **Post date:** [November 29, 2023, 3:48am UTC](https://devforum.zoom.us/t/unable-to-run-sample-code-for-linux-meeting-sdk/99072/4 "2023-11-29T03:48:22Z")
@cmr-anup , I’ll PM you for the longer logs ---
**Author:** ![cmr-anup](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/cmr-anup/32/50483_2.png) [@cmr-anup](https://devforum.zoom.us/u/cmr-anup)\ **Post date:** [November 29, 2023, 4:20am UTC](https://devforum.zoom.us/t/unable-to-run-sample-code-for-linux-meeting-sdk/99072/5 "2023-11-29T04:20:39Z")
@chunsiong.zoom Sure! I can post it here too- > sudo docker run -it --rm msdk-5.16.5-on-ubuntu-compact:0.41 > unix:path=/run/dbus/system\_bus\_socket,guid=d438c1ed99122c49fa3fdfc66565e9d5 > Adding user `root' to group `pulse-access’ … > Adding user root to group pulse-access > Done. > Adding user `root' to group `audio’ … > Adding user root to group audio > Done. > cp: target ‘/root/.config/pulse/’ is not a directory > W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified). > 19 > mkdir: cannot create directory ‘/root/.config’: File exists > getpath > self path: /app/demo/bin > Readfile success. > Reading…meeting\_number: “83625711111” > Reading…token: “” > Reading…meeting\_password: “411111” > Reading…recording\_token: “” > Reading…GetVideoRawData: “false” > Reading…GetAudioRawData: “true” > Meeting Number: 83625711111 > Token: > meeting\_password: 411111 > recording\_token: > GetVideoRawData before parsing is : false > GetVideoRawData: 0 > GetAudioRawData before parsing is : true > GetAudioRawData: 1 > directory of config file: /app/demo/bin/config.txt > Init meetingSdk:success > AuthService created. > AuthServiceEventListener added. > AuthSDK:token extracted from config file > Auth succeeded: JWT. > OnAuthenticationComplete > Joining Meeting > MeetingService created. > Settingservice created. > JWT token is > Recording token is > Leaving recording token as NULL > join\_meeting:success > onLoginReturnWithReason: 0 > onMeetingStatusChanged: 1, iResult: 0 > Connect to the meeting server status. > onMeetingParameterNotification > Joining Meeting… ---
**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\ **Post date:** [November 29, 2023, 4:42am UTC](https://devforum.zoom.us/t/unable-to-run-sample-code-for-linux-meeting-sdk/99072/6 "2023-11-29T04:42:33Z")
@cmr-anup could you reply in the PM, I wanted to take a look at the token too ---
**Author:** ![cmr-anup](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/cmr-anup/32/50483_2.png) [@cmr-anup](https://devforum.zoom.us/u/cmr-anup)\ **Post date:** [November 29, 2023, 5:46am UTC](https://devforum.zoom.us/t/unable-to-run-sample-code-for-linux-meeting-sdk/99072/7 "2023-11-29T05:46:05Z")
@chunsiong.zoom I have replied to your PM. ---
**Author:** ![varun\_gadre](https://avatars.discourse-cdn.com/v4/letter/v/b9e5f3/32.png) [@varun\_gadre](https://devforum.zoom.us/u/varun_gadre)\ **Post date:** [December 1, 2023, 6:38pm UTC](https://devforum.zoom.us/t/unable-to-run-sample-code-for-linux-meeting-sdk/99072/8 "2023-12-01T18:38:44Z")
> [@cmr-anup](#): > > windows sample code bot, and it worked successfully. Hey Anup could you link me to this windows code bot. I am having a similar issue where I too am seeing the 63 error. Just trying to get a bot up and running. ---
**Author:** ![cmr-anup](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/cmr-anup/32/50483_2.png) [@cmr-anup](https://devforum.zoom.us/u/cmr-anup)\ **Post date:** [December 4, 2023, 1:15am UTC](https://devforum.zoom.us/t/unable-to-run-sample-code-for-linux-meeting-sdk/99072/9 "2023-12-04T01:15:37Z")
@varun_gadre Here’s the code I used- > **[GitHub - zoom/meetingsdk-win-raw-recording-sample: A patch of the Zoom...](https://github.com/zoom/meetingsdk-win-raw-recording-sample)** > > A patch of the Zoom Meeting SDK for Windows that enables raw recording - GitHub - zoom/meetingsdk-win-raw-recording-sample: A patch of the Zoom Meeting SDK for Windows that enables raw recording ---
**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\ **Post date:** [December 13, 2023, 3:48am UTC](https://devforum.zoom.us/t/unable-to-run-sample-code-for-linux-meeting-sdk/99072/11 "2023-12-13T03:48:04Z")
@varun_gadre error 63 is due to external meeting join. You will need to publish your meeting SDK app before you can join external meeting. meanwhile for dev / test, you can join meeting created by users in your account without publishing ---
**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\ **Post date:** [December 14, 2023, 4:12am UTC](https://devforum.zoom.us/t/unable-to-run-sample-code-for-linux-meeting-sdk/99072/12 "2023-12-14T04:12:06Z")