Re: [jupyter] Running Jupyterlab on multiple servers with DNS round robin

2020-05-21 Thread Rishikesh Bhalerao
Hello Jason

Thanks for your reply. I am using Jupyterlab integrated with Jupyterhub.
 I have below four configs added in my jupyterhub_config.py. This is the
single config file I am maintaining, I had installed jupyterhub and
jupyterlab using anaconda3.


c.ConfigurableHTTPProxy.auth_token = ''

c.NotebookApp.token = ''


Attached is the jupyterhub_config.py.

Thanks
Rishikesh

On Thu, 21 May 2020, 03:28 Jason Anderson, 
wrote:

> Hi Rishikesh,
>
> It sounds like an issue where each server is generating its own
> authentication or encryption token. Are you specifying the authentication
> token manually[1], and is it the same value for all servers?
>
> If you’re using JupyterHub (it does not sound like it based on your
> question), the same would apply for the crypto key, which is used to
> encrypt the session cookie.
>
> Hope that helps,
> /Jason
>
> [1]:
> https://jupyter-notebook.readthedocs.io/en/stable/security.html#alternatives-to-token-authentication
>
> On May 20, 2020, at 12:48 AM, Rishikesh Bhalerao 
> wrote:
>
> Hello Team,
>
> We have jupyterlab instances running on 5 different servers. These servers
> have NFS home directories, i.e. same content under user's home directory is
> available on all the servers.
> We have created a URL(hostname) to access jupyterlab in DNS Round Robin by
> creating 5 A records of 5 IPs with same FQDN.
>
> We are facing the issue of AUTH Token Expiry when user lands on a new node
> and this is leading to auto-save fail issue.
> Auto Save interval is of 5 minutes.
>
> Could you please help how efficiently this can be configured to run on 5
> servers?
>
> Thanks in advance!
>
> Thanks & Regards
> Rishikesh
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CAMw24Y95ac0hdyM-eE%3D7zPZm%2B_PPXjfDKwhE0Opv3y-_xDscEQ%40mail.gmail.com
> 
> .
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/8C154258-2DDC-4F0C-83D5-2AA16F093673%40uchicago.edu
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAMw24Y-ZTsPQGv6esQxYF4b%3DXFt0vYq5vixBEY3rF4M%2BpKkOGQ%40mail.gmail.com.


jupyterhub_config.py
Description: Binary data


Re: [jupyter] Running Jupyterlab on multiple servers with DNS round robin

2020-05-20 Thread Jason Anderson
Hi Rishikesh,

It sounds like an issue where each server is generating its own authentication 
or encryption token. Are you specifying the authentication token manually[1], 
and is it the same value for all servers?

If you’re using JupyterHub (it does not sound like it based on your question), 
the same would apply for the crypto key, which is used to encrypt the session 
cookie.

Hope that helps,
/Jason

[1]: 
https://jupyter-notebook.readthedocs.io/en/stable/security.html#alternatives-to-token-authentication

On May 20, 2020, at 12:48 AM, Rishikesh Bhalerao 
mailto:rlbhalera...@gmail.com>> wrote:

Hello Team,

We have jupyterlab instances running on 5 different servers. These servers have 
NFS home directories, i.e. same content under user's home directory is 
available on all the servers.
We have created a URL(hostname) to access jupyterlab in DNS Round Robin by 
creating 5 A records of 5 IPs with same FQDN.

We are facing the issue of AUTH Token Expiry when user lands on a new node and 
this is leading to auto-save fail issue.
Auto Save interval is of 5 minutes.

Could you please help how efficiently this can be configured to run on 5 
servers?

Thanks in advance!

Thanks & Regards
Rishikesh

--
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jupyter+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAMw24Y95ac0hdyM-eE%3D7zPZm%2B_PPXjfDKwhE0Opv3y-_xDscEQ%40mail.gmail.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/8C154258-2DDC-4F0C-83D5-2AA16F093673%40uchicago.edu.


[jupyter] Running Jupyterlab on multiple servers with DNS round robin

2020-05-19 Thread Rishikesh Bhalerao
Hello Team,

We have jupyterlab instances running on 5 different servers. These servers
have NFS home directories, i.e. same content under user's home directory is
available on all the servers.
We have created a URL(hostname) to access jupyterlab in DNS Round Robin by
creating 5 A records of 5 IPs with same FQDN.

We are facing the issue of AUTH Token Expiry when user lands on a new node
and this is leading to auto-save fail issue.
Auto Save interval is of 5 minutes.

Could you please help how efficiently this can be configured to run on 5
servers?

Thanks in advance!

Thanks & Regards
Rishikesh

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAMw24Y95ac0hdyM-eE%3D7zPZm%2B_PPXjfDKwhE0Opv3y-_xDscEQ%40mail.gmail.com.