Member since
08-30-2019
14
Posts
0
Kudos Received
0
Solutions
12-20-2019
08:44 AM
Hi @AutoIN Hope doing great! We are planning to install cdsw 1.6.1 in new environment, just wanted to check if we still have to enable ipv6 as we did in 1.6.0. Thanks, Srinivas
... View more
10-24-2019
01:18 PM
@AutoIN just now observed issue with firefox as well after restart. attached screenshots in case.
... View more
10-24-2019
12:44 PM
@AutoIN it was nice talking to you! it will be good if we can narrow it down there will keep updated with firefox, IE outcome.Thanks for all your support
... View more
10-15-2019
06:06 PM
After opening websocket traffic at firewall level we are able to launch the sessions and run basic commands. But still not able to launch the session terminal, getting below error not sure where this is coming from. [..] 0/16/2019 12:52 AM 1 ERROR EngineInit.BrowserSvcs 4ubgvkai9lozx6q6 Finish apiGet, failed to parse resp body data = {"err":"invalid character '\u003c' looking for beginning of value","user":"cdsw"} 10/16/2019 12:52 AM 1 ERROR EngineInit.BrowserSvcs 4ubgvkai9lozx6q6 Finish isAuthorized, failed to get user permissions from API data = {"err":"invalid character '\u003c' looking for beginning of value","user":"cdsw"} 10/16/2019 12:52 AM 1 ERROR EngineInit.BrowserSvcs 4ubgvkai9lozx6q6 Error from memo.Get data = {"err":"invalid character '\u003c' looking for beginning of value","user":"cdsw"} 10/16/2019 12:52 AM 1 ERROR EngineInit.BrowserSvcs 4ubgvk
... View more
10-04-2019
04:56 PM
Hi , 1. We are still facing the issue,We have check with networks team they didn't see firewalls blocking this. when we check with cloudera even in their lab they see below error in session pod logs, but after clearing the cache its start working , though its not a perminant solution. In our case we are not able to access session/terminal even after clearing the cache but we didnt see below error in session pods. [..] fication error","user":"cdsw"} 2019-10-04 23:35:39.713 1 ERROR EngineInit.BrowserSvcs jv89ty4xw6v4tgkm Finish isAuthorized, failed to get auth cookie subject data = {"err":"crypto/rsa: verification error","user":"cdsw"} 2019-10-04 23:35:39.713 1 ERROR EngineInit.BrowserSvcs jv89ty4xw6v4tgkm Error from memo.Get data = {"err":"crypto/rsa: verification error","user":"cdsw"} 2019-10-04 23:35:39.713 1 WARNING EngineInit.BrowserSvcs jv89ty4xw6v4tgkm Rejecting unauthorized request data = {"scope":"session-like","status":401,"user":"cdsw"} 2019-10-04 23:35:41.966 1 ERROR EngineInit.BrowserSvcs jv89ty4xw6v4tgkm Error from memo.Get data = {"err":"crypto/rsa: verification error","user":"cdsw"} 2019-10-04 23:35:41.966 1 WARNING EngineInit.BrowserSvcs jv89ty4xw6v4tgkm Re [..] 2. after restarting cdsw we are seeing above error eventually after couple ours when we try to launch session we see different error as below in session pods..,wierd.. [..] 2019-10-01 17:37:20.248 1 ERROR EngineInit.BrowserSvcs uc1wc74ulb3xn7o5 Finish apiGet, failed to parse resp body data = {"err":"invalid character '\u003c' looking for beginning of value","user":"cdsw"} [..] Did you see any such behavour and any suggestions....please.. Thank You!
... View more
09-23-2019
08:28 AM
@AutoIN Yes you are right, this might be causing the issue let me check and update with the outcome! Thank you!
... View more
09-20-2019
10:50 AM
and i am not able to launch below urls from our browsers or unreachable " https://www.websocket.org/echo.html You can also use a chrome extension" as our browser is firewall protected (This site can’t be reached), can you please provide more details how to fix this... and we have no issue with the domain...we are able to dig..
... View more
09-20-2019
10:43 AM
@AutoIN yes, seems to be issue with websocket, i can see connection errors in the
... View more
09-20-2019
01:43 AM
@AutoIN This is a new installation with kerberos enabled but no tls.. Please see below engine container logs which leads to check live-log pod logs which show some failure(019-09-20 08:30:03.593 7 ERROR Livelog.Server message error data = {"addr":"100.66.0.29:51370","err":"websocket: close 1006 (abnormal closure): unexpected EOF"}) engine container logs : Livelog Open: Fri Sep 20 2019 08:30:22 GMT+0000 (UTC) 2019-09-20 08:30:22.431 1 INFO EngineInit.BrowserSvcs 76jt0ox8nexowxq5 Service port has become ready data = {"hostname":"ds-runtime-76jt0ox8nexowxq5.default-user-1.svc.cluster.local","port":8000,"user":"cdsw"} 2019-09-20 08:30:22.431 1 INFO EngineInit.BrowserSvcs 76jt0ox8nexowxq5 Emitting new UI status to LiveLog data = {"message":{"name":"terminal","url":"http://tty-76jt0ox8nexowxq5.chd6-cdsw.udl.net","status":true,"title":"GoTTY"},"user":"cdsw"} 2019-09-20 08:30:22.434 29 INFO Engine 76jt0ox8nexowxq5 Finish Authenticating to livelog: success data = {"secondsSinceStartup":0.271} 2019-09-20 08:30:22.434 29 INFO Engine 76jt0ox8nexowxq5 Start Searching for engine module data = {"secondsSinceStartup":0.272} 2019-09-20 08:30:22.670 29 INFO Engine 76jt0ox8nexowxq5 Finish Searching for engine module: success data = {"engineModule_path":"/usr/local/lib/node_modules/python2-engine"} 2019-09-20 08:30:22.671 29 INFO Engine 76jt0ox8nexowxq5 Start Creating engine data = {"secondsSinceStartup":0.508} PID of parser IPython process is 80 PID of main IPython process is 83 2019-09-20 08:30:22.812 29 INFO Engine 76jt0ox8nexowxq5 Finish Creating engine data = {"secondsSinceStartup":0.65} 2019-09-20 08:30:24.747 29 INFO Engine 76jt0ox8nexowxq5 Start Registering running status data = {"useHttps":false,"host":"web.default.svc.cluster.local","path":"/api/********/project1/dashboards/76jt0ox8nexowxq5/register-status","senseDomain":"***********} 2019-09-20 08:30:24.762 29 INFO Engine 76jt0ox8nexowxq5 Finish Registering running status: success 2019-09-20 08:30:24.763 29 INFO Engine 76jt0ox8nexowxq5 Pod is ready data = {"secondsSinceStartup":2.6,"engineModuleShare":2.092} -----------live logs----- 2019-09-20 08:30:03.593 7 ERROR Livelog.Server message error data = {"addr":"100.66.0.29:51370","err":"websocket: close 1006 (abnormal closure): unexpected EOF"} 2019-09-20 08:30:03.593 7 INFO Livelog.Server websocket disconnected data = {"addr":"100.66.0.29:51370"} 2019-09-20 08:30:03.593 7 INFO Livelog.Server unsubscribed on disconnect data = {"addr":"100.66.0.29:51370","stream":4,"topic":"2bkebt3msffbhihr_input"} 2019-09-20 08:30:20.408 7 INFO Livelog.Server websocket connected data = {"addr":"100.66.0.28:56216"} 2019-09-20 08:30:20.408 7 INFO Livelog.Server auth successful data = {"addr":"100.66.0.28:56216"} 2019-09-20 08:30:20.508 7 INFO Livelog.Server websocket connected data = {"addr":"100.66.0.28:56246"} 2019-09-20 08:30:20.509 7 INFO Livelog.Server auth successful data = {"addr":"100.66.0.28:56246"} 2019-09-20 08:30:21.512 7 ERROR Livelog.Server message error data = {"addr":"100.66.0.28:56246","err":"websocket: close 1006 (abnormal closure): unexpected EOF"} 2019-09-20 08:30:21.513 7 INFO Livelog.Server websocket disconnected data = {"addr":"100.66.0.28:56246"} 2019-09-20 08:30:22.423 7 INFO Livelog.Server websocket connected data = {"addr":"100.66.0.28:56288"} 2019-09-20 08:30:22.431 7 INFO Livelog.Server auth successful data = {"addr":"100.66.0.28:56288"} 2019-09-20 08:30:24.762 7 INFO Livelog.Server subscribe data = {"addr":"100.66.0.28:56288","stream":3,"topic":"76jt0ox8nexowxq5_input"} -----
... View more
09-19-2019
08:34 PM
i can see pod logs as below.. Error from server (BadRequest): a container name must be specified for pod 1256prl4sdxs0o6w, choose one of: [engine kinit ssh] or one of the init containers: [engine-deps]
... View more