Jupyterhub - Running as service Issue

64 views
Skip to first unread message

testb...@gmail.com

unread,
Mar 25, 2017, 12:01:42 PM3/25/17
to Project Jupyter
Hi,
Could anyone please help me? I'm trying to run JupyterHub as a service and created the jupyterub.service and have it under /etc/systemd/system in my Linux RedHat Server.
I'm using default configuration. When I access the Jupyterhub url from a different machine, I get 500 error after login. Could anyone please let me know how to resolve this issue? Thanks in advance!

Also, I have the few questions.

1. Is there a way to check the log file? If so, what is the default location of the log file?

2. If I run as a service, will the linux disk becomes full becox of many msgs. If so, how can check whether my disk is full?

Thanks again!

MinRK

unread,
Mar 27, 2017, 7:49:23 AM3/27/17
to Project Jupyter

On Sat, Mar 25, 2017 at 5:01 PM, <testb...@gmail.com> wrote:

Hi,
Could anyone please help me? I'm trying to run JupyterHub as a service and created the jupyterub.service and have it under /etc/systemd/system in my Linux RedHat Server.
I'm using default configuration. When I access the Jupyterhub url from a different machine, I get 500 error after login. Could anyone please let me know how to resolve this issue? Thanks in advance!

Also, I have the few questions.

1. Is there a way to check the log file? If so, what is the default location of the log file?

That’s up to the service runner and the service configuration where it puts output. It might be in syslog or /var/log/jupyterhub.log. If you are using systemd, you can access the logs with journalctl, e.g.

journalctl -u jupyterhub


2. If I run as a service, will the linux disk becomes full becox of many msgs. If so, how can check whether my disk is full?

This is up to your log rotation configuration. The default is usually to compress and archive old logs forever, but you can change logrotate’s configuration to throw away logs older than a certain age.

You can check if you disk is getting full with df -h.

-Min


Thanks again!

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/13aca6f7-b6ce-47a7-8883-0ce10d841b95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

testb...@gmail.com

unread,
Mar 30, 2017, 6:00:49 AM3/30/17
to Project Jupyter
Hi,
Thanks!
This helps.


On Monday, March 27, 2017 at 6:49:23 AM UTC-5, Min RK wrote:

On Sat, Mar 25, 2017 at 5:01 PM, <testb...@gmail.com> wrote:

Hi,
Could anyone please help me? I'm trying to run JupyterHub as a service and created the jupyterub.service and have it under /etc/systemd/system in my Linux RedHat Server.
I'm using default configuration. When I access the Jupyterhub url from a different machine, I get 500 error after login. Could anyone please let me know how to resolve this issue? Thanks in advance!

Also, I have the few questions.

1. Is there a way to check the log file? If so, what is the default location of the log file?

That’s up to the service runner and the service configuration where it puts output. It might be in syslog or /var/log/jupyterhub.log. If you are using systemd, you can access the logs with journalctl, e.g.

journalctl -u jupyterhub


2. If I run as a service, will the linux disk becomes full becox of many msgs. If so, how can check whether my disk is full?

This is up to your log rotation configuration. The default is usually to compress and archive old logs forever, but you can change logrotate’s configuration to throw away logs older than a certain age.

You can check if you disk is getting full with df -h.

-Min


Thanks again!

--
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+u...@googlegroups.com.

Reply all
Reply to author
Forward
0 new messages