1 00:00:00,560 --> 00:00:02,420 Hello and welcome back. 2 00:00:02,450 --> 00:00:07,340 In this video we will go through the solution for application trouble shooting 3 00:00:10,140 --> 00:00:18,300 so in this quest we have six questions and there is an architecture diagram associated with each question 4 00:00:18,300 --> 00:00:26,310 which is quite similar in nature and for each test the application is read applied in a different namespace 5 00:00:26,750 --> 00:00:35,430 with the specific issue which prevents the app tab to be opened properly for the application configured. 6 00:00:35,520 --> 00:00:39,960 So our goal is to correct whatever is wrong with the deployment. 7 00:00:40,040 --> 00:00:50,050 The servers depart and make sure that the web application works properly so to start off let's click 8 00:00:50,050 --> 00:00:52,500 on the app tab. 9 00:00:53,790 --> 00:00:57,100 And as you can see by default it's in a failed state. 10 00:00:57,620 --> 00:01:03,500 So for the first question we will have to figure out what exactly is wrong and try to fix it. 11 00:01:04,540 --> 00:01:12,910 So let's straight to the question troubleshooting test 1 a simple app is deployed in the alpha namespace 12 00:01:13,030 --> 00:01:21,610 it's a two tier application it must display green that page on success click on the app tab at the top 13 00:01:21,610 --> 00:01:27,190 of your terminal to view your application it is currently field troubleshoot and fix the issue. 14 00:01:27,730 --> 00:01:35,830 So we have already seen that in our case it's displaying a red coloured team here and a bit of statement 15 00:01:35,830 --> 00:01:42,670 that it's filled and you can see the environmental variables that is being used here and the exact nature 16 00:01:42,670 --> 00:01:43,570 of the failure. 17 00:01:43,990 --> 00:01:53,770 So here it says that it's not able to connect to the My School so or on the name of the DV holes which 18 00:01:53,770 --> 00:02:02,550 is my sequel hyphen service on board 3 3 0 6 and if we check the architecture diagram we can see that 19 00:02:02,550 --> 00:02:07,660 there is a mikes equal pod which exposes the port. 20 00:02:07,680 --> 00:02:18,060 3 3 0 6 and there is a service which was of plus IP and exposing the 3 3 0 6 again and that is consumed 21 00:02:18,060 --> 00:02:20,530 by the thereby Python my sequel. 22 00:02:21,360 --> 00:02:29,390 Which runs on board 80 80 and this is the one which the user is accessing using Node port 3 0 0 8 1. 23 00:02:30,180 --> 00:02:36,800 So let's check the alpha namespace and list all the components which is inside this namespace. 24 00:02:36,870 --> 00:02:44,340 So let's go back to the terminal and we can do this by running the command cube CTO hyphen and how far 25 00:02:44,920 --> 00:02:55,970 and get all to the show you the port the deployment the replica set and these services so let's go back 26 00:02:55,970 --> 00:02:57,970 to the architecture diagram. 27 00:02:58,260 --> 00:03:05,360 The part should be my sequel the service name should be my sequel service the deployment name should 28 00:03:05,360 --> 00:03:16,620 be there are by then my sequel and that exposes where Python's service so here the port has my sequel. 29 00:03:16,630 --> 00:03:20,540 There was a deployment there as apart from the deployment. 30 00:03:20,540 --> 00:03:27,890 The service name here is called My sequel whereas it should be called my sequel hyphen service. 31 00:03:28,250 --> 00:03:36,790 And if you go back to the app the variable used for the B horses my sequel hyphen service. 32 00:03:37,190 --> 00:03:41,870 So straight away we can see that the name here is incorrect. 33 00:03:41,870 --> 00:03:51,980 So to fix the scenario we can recreate the service with the correct name so to do this first I'll export 34 00:03:51,990 --> 00:03:56,650 the contents of the current my sequel service to. 35 00:03:56,730 --> 00:03:58,050 Yeah no definition file. 36 00:03:58,060 --> 00:04:11,440 Call my sequel hyphen service knock em now alt delete the service called my sequel. 37 00:04:13,880 --> 00:04:20,000 And I will recreate it using the definition far before that. 38 00:04:20,000 --> 00:04:24,640 Let me rename the service to my sequel hyphen service. 39 00:04:35,260 --> 00:04:44,570 So now if I run the same command again cube C2 hyphen then Alpha get all it shows that the service has 40 00:04:44,570 --> 00:04:45,650 been re created 41 00:04:48,870 --> 00:04:57,870 so now let's rephrase the speech and see if it works and you're getting a green theme right now and 42 00:04:57,870 --> 00:04:59,130 it's successful. 43 00:04:59,760 --> 00:05:02,090 So let's change the result. 44 00:05:04,070 --> 00:05:05,000 So that was correct. 45 00:05:05,000 --> 00:05:07,220 Let's go to the second question. 46 00:05:09,460 --> 00:05:15,150 So for the second question we have a very similar architecture diagram as that of the first question 47 00:05:15,790 --> 00:05:21,720 but we can see that the application has now deployed in the beta namespace. 48 00:05:22,000 --> 00:05:29,680 And just as before we had to make sure that the display is providing green where patients are for red. 49 00:05:29,680 --> 00:05:32,740 So let's refresh the app tab. 50 00:05:32,920 --> 00:05:36,500 And as you can see it's gone back to its field state. 51 00:05:36,790 --> 00:05:41,650 And in this case we can see that the error is connection refused. 52 00:05:42,850 --> 00:05:49,600 So we'll again go back to the terminal and check the competence of the beta namespace 53 00:05:52,530 --> 00:05:59,710 a huge deal my friend and Lena get all. 54 00:05:59,850 --> 00:06:02,970 In this case you can see that the mice equal services correct too. 55 00:06:03,150 --> 00:06:12,490 The problem is with something else let's quickly check the service which is created and thus namespace 56 00:06:27,860 --> 00:06:28,470 so. 57 00:06:28,520 --> 00:06:37,100 We check the service here we can see that the mice equal service has the target endpoint as 1880 and 58 00:06:37,100 --> 00:06:43,160 now if we go back to the architecture diagram this is incorrect because the target endpoint should be 59 00:06:43,160 --> 00:06:44,970 3 3 0 6. 60 00:06:45,290 --> 00:06:54,410 So as before we have to recreate the service but now in the beta namespace so as before. 61 00:06:54,450 --> 00:06:59,170 Let us export the current service into a general definition file 62 00:07:05,170 --> 00:07:06,100 real again. 63 00:07:06,100 --> 00:07:16,490 Delete the my sequel servers and recreate it after editing the Live Nation file. 64 00:07:17,350 --> 00:07:25,010 So here I'm going to change the target put 2 3 3 0 6. 65 00:07:25,210 --> 00:07:32,600 Let's now recreate the service. 66 00:07:32,650 --> 00:07:40,850 Now if Iran describe again a should should the target put as 3 3 0 6. 67 00:07:41,140 --> 00:07:46,500 Let to see if that would and we caught up rain. 68 00:07:46,550 --> 00:07:47,050 Team 69 00:07:49,960 --> 00:07:59,150 let's seek the solution that has failed so let's wait for the question 3 And scenario number 3 to load 70 00:07:59,150 --> 00:08:07,460 up so for the troubleshooting shooting scenario 3 the same two tier application has now deployed on 71 00:08:07,460 --> 00:08:13,730 the gamma namespace and the rest of the question are similar for the other two questions. 72 00:08:15,870 --> 00:08:18,130 And we have the exact same architecture. 73 00:08:18,210 --> 00:08:22,050 So let's go back and refresh the application 74 00:08:24,760 --> 00:08:28,270 and then this case looks like it's not even loading up. 75 00:08:28,560 --> 00:08:37,170 So then again there is something wrong with the service as you can see if I refresh it. 76 00:08:37,440 --> 00:08:39,730 The application as not loading. 77 00:08:40,050 --> 00:08:51,010 So let's go and check the deployments and the objects created in the game on him space as before cube 78 00:08:51,060 --> 00:08:53,710 CTO in Gama. 79 00:08:53,950 --> 00:08:54,870 Again all 80 00:08:58,060 --> 00:08:58,840 in here. 81 00:08:58,930 --> 00:09:00,490 Before this my sequel. 82 00:09:00,560 --> 00:09:02,040 Exactly as before. 83 00:09:02,060 --> 00:09:10,130 There is a web app my sequel pod and a deployment created and let's inspect these services. 84 00:09:11,240 --> 00:09:19,160 Before that we can also inspect the endpoints for these services and the first thing that you will see 85 00:09:19,160 --> 00:09:27,660 here is that the my sequel service does not have an end point and this is supposed to point to the Y 86 00:09:27,660 --> 00:09:29,760 sequel pod. 87 00:09:29,760 --> 00:09:35,570 So let's check what's wrong with the heart as well as the service. 88 00:09:35,770 --> 00:09:48,580 So Cube CTO get service Y sequel reference service pay phone n no ammo. 89 00:09:51,820 --> 00:09:56,370 Now if you look here the port is correct the target port is correct. 90 00:09:56,370 --> 00:10:01,640 There is a selector here by the name of sequel 0 0 0 0 1. 91 00:10:02,280 --> 00:10:09,360 Let's see if this matches what is provided in the port definition for my sequel. 92 00:10:14,620 --> 00:10:19,480 If you go here the label is name is equal to my sequel. 93 00:10:19,560 --> 00:10:21,230 So that is incorrect. 94 00:10:21,360 --> 00:10:27,300 Which is why you see no end points created for the mice equal service. 95 00:10:27,300 --> 00:10:39,010 So to fix this we can delete the current service or my sequel service and I can use imperative command 96 00:10:40,880 --> 00:10:57,300 cube CTO iPhone in the nano expos poured my sequel for never name was equal to my sequel service. 97 00:10:57,780 --> 00:11:08,820 From here on cube CTO hyphen n Gama kit in points we see that we have one single endpoint for the my 98 00:11:08,820 --> 00:11:11,610 sequel service. 99 00:11:11,660 --> 00:11:18,380 So now if we try to refresh this we should get a successful screen. 100 00:11:18,990 --> 00:11:24,170 That's sick and that is complete as well. 101 00:11:24,170 --> 00:11:26,890 So let's not wait for scenario number 4. 102 00:11:29,230 --> 00:11:36,640 For scenario number 4 we have the exact same architecture with one exception. 103 00:11:36,640 --> 00:11:42,110 We now have the environment variables as part of the architecture diagram here. 104 00:11:42,250 --> 00:11:50,080 So the DP whose should be my sequel hyphen service db user should be root and DV password should be 105 00:11:50,680 --> 00:11:54,400 password spelled as P as W R D. 106 00:11:54,400 --> 00:12:00,220 The rest of the question is the same as before except for the fact that the objects are deployed in 107 00:12:00,220 --> 00:12:01,780 the Delta namespace 108 00:12:04,290 --> 00:12:11,420 Let's reload the application tab and see what the error is here. 109 00:12:11,520 --> 00:12:19,620 The environment variables are VB on the score hostess my sequel service there's no database said the 110 00:12:19,620 --> 00:12:30,870 db user the sequel user DV password as B is w arty and it says that access is denied for the sequel 111 00:12:30,870 --> 00:12:32,700 user fee. 112 00:12:32,700 --> 00:12:38,400 Compare that with the architecture diagram you can see that the db user should be a route not equal 113 00:12:38,400 --> 00:12:38,820 user. 114 00:12:39,750 --> 00:12:43,880 So the first thing that we have to change is the. 115 00:12:44,010 --> 00:12:45,440 And one went really well. 116 00:12:46,020 --> 00:12:48,150 So now let's see where is the set 117 00:13:12,170 --> 00:13:21,170 so when we're not describe on the deployment forum where about Python mice equal we can see that the 118 00:13:21,170 --> 00:13:25,610 DV user which is set as an environment variable is equal user. 119 00:13:26,150 --> 00:13:28,160 So this is what we need to change 120 00:13:32,200 --> 00:13:33,300 as usual. 121 00:13:33,340 --> 00:13:43,080 Let's get a poor definition file or in this case a deployment definition using your CTO hyphen and Delta 122 00:13:44,440 --> 00:13:53,650 get deployment up I from my sequel national animal country daring to fight 123 00:13:57,300 --> 00:14:09,480 we can now delete the deployment web app I see in the tower namespace 124 00:14:12,220 --> 00:14:24,430 let's edit the file here and update the correct TB user name it should be ruled 125 00:14:28,510 --> 00:14:30,190 let's recreate the deployment. 126 00:14:35,420 --> 00:14:43,710 As you can see the new port has been recreated and the old port with the incorrect db user is terminating 127 00:14:45,520 --> 00:14:51,710 so if you reload the browser we should get a successful screen. 128 00:14:56,220 --> 00:14:58,110 Let's move on to question number 5 129 00:15:01,770 --> 00:15:10,590 so for Scenario Number 5 we have the exact same architecture but again we have a new namespace called 130 00:15:10,620 --> 00:15:17,110 Epsilon do the same thing as before and reload the browser. 131 00:15:18,670 --> 00:15:26,860 In year he can see that the access has again denied for a user sequel user using password as yes. 132 00:15:26,890 --> 00:15:29,420 So let's go back and check the deployment 133 00:15:32,830 --> 00:15:38,080 in this case we have to change the namespace to Epsilon 134 00:15:59,480 --> 00:16:08,880 let's quickly check the deployment for web app for my sequel and the Epsilon namespace and the orienting 135 00:16:08,890 --> 00:16:11,620 in the db user is set to sequel user. 136 00:16:13,620 --> 00:16:21,570 So let's exploit this and rewrite the verb GMO quickly update the animal file. 137 00:16:23,600 --> 00:16:27,230 Before a value should be rude 138 00:16:35,980 --> 00:16:38,440 Let's delete the deployment 139 00:16:45,950 --> 00:16:47,190 and tree created 140 00:16:56,170 --> 00:17:05,470 as before we have the new port which is running and let's see if that fixes this looks like we still 141 00:17:05,470 --> 00:17:06,860 have an error. 142 00:17:08,740 --> 00:17:15,630 Although we achieve the db user to root let's say what else could be wrong. 143 00:17:17,530 --> 00:17:24,310 Let's describe the part of my sequel in the Epsilon namespace 144 00:17:29,430 --> 00:17:29,870 here. 145 00:17:29,900 --> 00:17:38,110 If you see the my sequel root password which is used as an environmental variable for my sequel container 146 00:17:39,910 --> 00:17:48,490 we can see that the password has said incorrectly the password should be password spelled as P as W 147 00:17:48,490 --> 00:17:53,730 R D and this is something which is described in the architecture diagram as well. 148 00:17:54,550 --> 00:17:59,370 So in this case we'll have to recreate this pod 149 00:18:03,990 --> 00:18:09,320 it's updated but first let's create a poor definition file 150 00:18:16,460 --> 00:18:17,010 here. 151 00:18:17,110 --> 00:18:21,640 Let's update the value decree expelling 152 00:18:33,550 --> 00:18:34,890 Let's delete the current. 153 00:18:34,890 --> 00:18:38,280 My sequel pod and recreate it. 154 00:18:49,690 --> 00:18:53,080 As you can see the why sequel part is in our running state. 155 00:18:53,120 --> 00:18:55,380 So let's refresh the screen. 156 00:18:58,970 --> 00:19:02,890 Now that that's fixed let's move on to the next question. 157 00:19:07,340 --> 00:19:15,050 So for this final question we have to do the same exercise one more time and the application is now 158 00:19:15,050 --> 00:19:17,020 deployed in the z namespace 159 00:19:20,790 --> 00:19:30,030 so in this case we are not even reaching the application on board 3 0 0 8 1 which is the node board 160 00:19:30,810 --> 00:19:33,990 used by the users to access the application 161 00:19:37,160 --> 00:19:40,860 so this gives us a clue on what we need to check. 162 00:19:40,890 --> 00:19:47,310 So if we go back to the architecture diagram we can see that the web service which listens on board 163 00:19:47,370 --> 00:19:54,330 1880 on for the target board is exposed as a node put on 3 0 8 1. 164 00:19:54,960 --> 00:20:07,240 So let's check the status of the service in the 0 namespace for the web service and if you look here 165 00:20:08,380 --> 00:20:10,470 the node board is wrong. 166 00:20:10,510 --> 00:20:16,060 It should be treasonous 0 8 1 and not treasonous 0 8 8. 167 00:20:16,060 --> 00:20:19,330 So let's update the service 168 00:20:29,020 --> 00:20:34,610 and here we're going to change the node put 2 3 0 0 8 1. 169 00:20:36,270 --> 00:20:41,690 Let's delete the current service and we've created 170 00:20:45,830 --> 00:20:48,470 now they no put us updated 171 00:20:53,160 --> 00:20:54,450 and still. 172 00:20:54,510 --> 00:20:56,940 Now we got a radar screen. 173 00:20:57,000 --> 00:21:03,070 So it is loading up properly but looks like there are other fields that we need to fix. 174 00:21:03,090 --> 00:21:10,370 So here the db user is again set to equal user so the access is denied. 175 00:21:10,570 --> 00:21:13,300 So let's make sure that that's corrected as well. 176 00:21:28,280 --> 00:21:36,150 Now let's inspect both the deployment as well as the my sequel pod. 177 00:21:36,180 --> 00:21:38,320 So in this case the deployment is incorrect. 178 00:21:38,320 --> 00:21:51,640 We have to change the value for the db user too rude and let's recreate it. 179 00:21:51,830 --> 00:21:58,610 Let's also check the in my sequel part and see if anything else needs to be changed here. 180 00:21:58,770 --> 00:22:01,260 And as you can see the password is still incorrect. 181 00:22:01,270 --> 00:22:05,430 So let's change it to be as W R D. 182 00:22:06,590 --> 00:22:09,340 And let's now recreate the port as well. 183 00:22:25,450 --> 00:22:28,230 And now we've got everything in our running state 184 00:22:32,210 --> 00:22:34,400 so let's rephrase the screen. 185 00:22:34,550 --> 00:22:38,380 And now you caught us a school application. 186 00:22:39,690 --> 00:22:46,030 Let's check and we have successfully completed this practice test. 187 00:22:46,030 --> 00:22:48,520 Thank you for joining me in this lecture. 188 00:22:48,520 --> 00:22:49,680 See you on the next one.