Page History

...

many people using "anatut" account simultaneously (others using their own SLAC accounts)

had to continually watch:

• memory usage on anatut server node (where all processes run)
• anatut disk usage
• watch for server moving to another node (killed by either user clicking "stop my server" or OOM killer?) and duplicate servers
• kept a "canary" anatut notebook running all the time

~stilton2 had weka shome issue on gpu107, which prevented him from starting/stopping notebooks
database locked (two issues): this error traced down to having to jupyterhub servers running on the same node for user "anatut"

...