-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blank Screen when accessing one (out of three) clusters #4018
Comments
having same issue in MacOS
|
Same for me. Installed lens about 2 weeks ago. Worked well for a while and now i just can't use it. Tried to reinstall the app, remove and add the cluster, still not able to do anything with the app. I'm on Linux, Zorin OS
|
If you turn off "Download kubectl binaries matching the Kubernetes cluster version" in preferences does this problem resolve itself? |
@Nokel81 No |
You have to restart lens currently for that option to be picked up. Including the tray icon |
@Nokel81 Yeah, did restart, the problem doesn't look to be a the kubectl level. At least it's not between kubectl and the cluster. Might be between Lens and kubectl 🤷♂️. |
@Nokel81 Disabled "Download kubectl binaries matching the Kubernetes cluster version" in prefs, quit out of Lens, started it again. No change. |
Here is more details about the error message
|
Yes thanks, that is a unrelated issue, sorry about the noise. |
I have the same problem. On mac, I need to delete |
Thanks @Doraemoe--that worked for me. |
@Doraemoe also worked for me, thanks! |
Not here ... I needed to delete wider on my macbookpro: |
Hi all, Having the same problem. @Doraemoe 's fix works for me. BUT IT IS REPETITIVE. Cannot tell what causes it, but in many cases, I had a VPN (over which I reach out to Kubernetes with Lens) drop out. Reconnecting didn't fix the problem. Could this be a cause? Cheers, B. |
Would you mind providing files under |
Hi @Nokel81, I'm on MacOS, Big Sur 11.6. For now, it's working and I don't have the contents anymore. Will provide them next time the problem occurs. Cheers, B. |
Okay thanks, the path will be |
Hi @Nokel81, I turned the VPN off and on again, but that in itself did not cause the problem. Overnight, the computer fell into stand-by modus and the VPN timed out. Now I have the problem again. |
Thanks for the information, I will investigate. Thanks for the information about when it occurred. I will delete your information once I am done. |
@Bezz242 Thanks for the files but unfortunately they don't seem to have the cause... will continue investigating. |
@Nokel81 FYI this issue also occurs while I was using VPN, usually I left my laptop in stand-by mode over the night, and the next day this issue might happen, after VPN drop and reconnect (not sure it always happen everytime, I can make some observation later), the situation looks similar to what @Bezz242 was having. And I'm running MacOS 10.15.6 I can send some file for your investigation, but is there some private channel I can share file? |
My work email in smalton @ mirantis.com if that works for you |
@Nokel81 sent, thanks |
Could people please try
And see if the variety of fixes we have merged resolves this issue for people. |
It seems to be working now! |
I only ran into the issue once. I was never able to reproduce it reliably, so I can't say that |
On launch of |
The latest beta seems to solve the issue I had in #4408 |
same here |
I have found the cause of why this happens. It happens when we set state within a render function, thus causing react never to render anything and go into a hot loop before crashing on OOM. #4376 should fix this for some of the cases, but I will need to do a thorough check in all of our components to make sure that we are not doing that anymore |
Closing as this has been fixed in master. |
Thanks @Nokel81 |
command + r solved my issue. |
I'm still having this issue, with the following warnings in devtools:
I've already tried clearing the whole Cmd+R does solve the problem temporarily, but it resets my namespace selection and I have to do this every time I start up Lens which is quite annoying. |
I have 3 clusters on Digital Ocean under various accounts.
I have always been able to connect to them with Lens.
About a week ago, I suddenly couldn't connect to one of the clusters.
I've tried deleting and re-adding the config in kubectl, I've tried deleting and re-adding it to Lens.
I just get a blank screen. kubectl works fine, it's just Lens that isn't showing anything.
Lens has no trouble with the other clusters. They are all running the same version.
Here's a screenshot of Lens and the terminal I launched it from when I try to connect to the cluster that Lens is having issues with:
This is a screenshot of the developer console in Lens when it can't connect:
![Screenshot from 2021-10-12 09-51-15](https://user-images.githubusercontent.com/158380/136997624-eeef82a4-8dff-4ca3-b1e0-2251199a70c5.png)
The text was updated successfully, but these errors were encountered: