bcgov / gwa

Gateway Administration
https://catalogue.data.gov.bc.ca/dataset/api-gateway-administration
Apache License 2.0
7 stars 3 forks source link

Kong Error in Prod Admin Interface #45

Closed Darv72 closed 6 years ago

Darv72 commented 6 years ago

I am receiving a "Kong server not available" error when clicking on the APIs tab in the GWA interface. As well I receive this error when clicking on the Users tab and scrolling down a ways. The other tabs seem to be working correctly. I noticed this behavior today, I believe I used the GWA without error early last week sometime.

pauldaustin commented 6 years ago

If you get these kind of errors check the Javascript console for your browser to see what the underlying error is and include that in the error report.

Also check to see if there is anything in the server side GWA error log and include that.

ll911 commented 6 years ago

strange thing is that there are no js console error in browser or server end error out it only happens immediately in apis tab and happens when scrolling on user tab, other tabs are fine.

screen shot 2018-02-21 at 6 12 35 pm
pauldaustin commented 6 years ago

In the browser chrome turn on the network tab under dev tools and see what responses are not 302 or 200 status

On Wed, Feb 21, 2018 at 18:15 Leo notifications@github.com wrote:

strange thing is that there are no js console error in browser or server end error out it only happens immediately in apis tab and happens when scrolling on user tab, other tabs are fine. [image: screen shot 2018-02-21 at 6 12 35 pm] https://user-images.githubusercontent.com/11949273/36516498-1a5bfeb6-1733-11e8-9652-e46369a3ac05.png

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/bcgov/gwa/issues/45#issuecomment-367544484, or mute the thread https://github.com/notifications/unsubscribe-auth/AAbMYQBRMn9xuViOMnxBHLAuK04Pm3rUks5tXM2kgaJpZM4SOhfv .

-- Paul Austin President/CEO Revolution Systems Inc.

+1 (604) 288-4304 x201 www.revolsys.com

ll911 commented 6 years ago

there are none,

screen shot 2018-02-21 at 10 27 20 pm
pauldaustin commented 6 years ago

You’ll have to grant me permission in prod so I can try it and see

On Wed, Feb 21, 2018 at 22:28 Leo notifications@github.com wrote:

there are none, [image: screen shot 2018-02-21 at 10 27 20 pm] https://user-images.githubusercontent.com/11949273/36523445-724ba914-1756-11e8-8ea7-f2605a2ea07b.png

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/bcgov/gwa/issues/45#issuecomment-367580616, or mute the thread https://github.com/notifications/unsubscribe-auth/AAbMYbTEDsK--E1N0Gmx4eN-s_HLVP5oks5tXQklgaJpZM4SOhfv .

-- Paul Austin President/CEO Revolution Systems Inc.

+1 (604) 288-4304 x201 www.revolsys.com

ll911 commented 6 years ago

granted.

pauldaustin commented 6 years ago

Leo,

That error is returned in 2 cases.

The http client on the GWA Servlet cannot connect to kong (e.g. timeout). If this were the case I write the stack trace as an DEBUG the logging system. As the log level is error you won't see this in the log. I didn't want to fill the logs if the kong server wasn't available. The kong server returned a 503 error in response to a request. If this were the case I write the stack trace as an error to the console log (e.g. catalina.out)

ll911 commented 6 years ago

no catalina.out created

/usr/local/tomcat/logs $ ls -lta                                                                                                                       
total 44                                                                                                                                               
drwxrwx---    2 tomcat   root          4096 Feb 21 22:39 .                                                                                             
-rw-r-----    1 10014300 root          1892 Feb 21 22:39 catalina.2018-02-21.log                                                                       
-rw-r-----    1 10014300 root          2029 Feb 19 17:55 catalina.2018-02-19.log                                                                       
-rw-r-----    1 10014300 root          2063 Feb 14 23:30 catalina.2018-02-14.log                                                                       
-rw-r-----    1 10014300 root          2064 Feb 13 17:33 catalina.2018-02-13.log                                                                       
-rw-r-----    1 10014300 root          1458 Feb  8 22:14 catalina.2018-02-08.log                                                                       
-rw-r-----    1 10014300 root          2401 Feb  1 22:26 localhost.2018-02-01.log                                                                      
-rw-r-----    1 10014300 root          1934 Jan 29 23:41 catalina.2018-01-29.log                                                                       
-rw-r-----    1 10014300 root          1856 Jan 28 21:00 catalina.2018-01-28.log                                                                       
-rw-r-----    1 10014300 root          5499 Jan 25 21:48 catalina.2018-01-25.log                                                                       
-rw-r-----    1 10014300 root             0 Jan 25 17:57 host-manager.2018-01-25.log                                                                   
-rw-r-----    1 10014300 root             0 Jan 25 17:57 localhost.2018-01-25.log                                                                      
-rw-r-----    1 10014300 root             0 Jan 25 17:57 manager.2018-01-25.log                                                                        
drwxrwx---   13 tomcat   root           220 Jan 25 17:57 ..                             

the only error I can grep -i from those log were invalid cookies, and ignored.

ll911 commented 6 years ago

also there no error logs from kong server for admin endpoint

zcat error.log-20180221.gz | grep -i "$kong_admin_gwa"
pauldaustin commented 6 years ago

Leo

Catalina date log

On Thu, Feb 22, 2018 at 12:51 Leo notifications@github.com wrote:

no catalina.out created

/usr/local/tomcat/logs $ ls -lta total 44 drwxrwx--- 2 tomcat root 4096 Feb 21 22:39 . -rw-r----- 1 10014300 root 1892 Feb 21 22:39 catalina.2018-02-21.log -rw-r----- 1 10014300 root 2029 Feb 19 17:55 catalina.2018-02-19.log -rw-r----- 1 10014300 root 2063 Feb 14 23:30 catalina.2018-02-14.log -rw-r----- 1 10014300 root 2064 Feb 13 17:33 catalina.2018-02-13.log -rw-r----- 1 10014300 root 1458 Feb 8 22:14 catalina.2018-02-08.log -rw-r----- 1 10014300 root 2401 Feb 1 22:26 localhost.2018-02-01.log -rw-r----- 1 10014300 root 1934 Jan 29 23:41 catalina.2018-01-29.log -rw-r----- 1 10014300 root 1856 Jan 28 21:00 catalina.2018-01-28.log -rw-r----- 1 10014300 root 5499 Jan 25 21:48 catalina.2018-01-25.log -rw-r----- 1 10014300 root 0 Jan 25 17:57 host-manager.2018-01-25.log -rw-r----- 1 10014300 root 0 Jan 25 17:57 localhost.2018-01-25.log -rw-r----- 1 10014300 root 0 Jan 25 17:57 manager.2018-01-25.log drwxrwx--- 13 tomcat root 220 Jan 25 17:57 ..

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/bcgov/gwa/issues/45#issuecomment-367763974, or mute the thread https://github.com/notifications/unsubscribe-auth/AAbMYb5AEBmFbBtO9Y25ktl2sOU5ekbtks5tXakFgaJpZM4SOhfv .

-- Paul Austin President/CEO Revolution Systems Inc.

+1 (604) 288-4304 x201 www.revolsys.com