Blank screen, weird errors with Jupyter

Get Help
21

You probably need to do sudo httpd -V.

I’m not sure it’s an issue of configuration. If anything I’m thinking maybe it’s a performance issue.

I can regularly get a Jupyter instance with 1 core and 4 GB of memory, so it’s hard to say it’s an issue with the compute node’s resources. I would imagine your Jupyter jobs have as much resources, if not more.

I feel like there’s something obvious that we’re missing maybe? Is the OnDemand server under high load?

OK - strange :laughing: I would not have pinned this to some configuration issue. I’d ask if this is consistent. I.e., you can always get a Jupyter instance running and it always runs smoothly.

22

Yea very strange indeed that this appears to be a configuration issue.

I should leave well enough alone, I just hope that the issue wasn’t solved by a coincidence and will pop back up again.

If it does, I guess just reach out again? If it consistently works well, then I suppose there’s nothing to do? :man_shrugging:

Glad to hear it got solved, just a little puzzled on how…

23

All right, I will do some testing today and see if it is solved for real. There was one other change on the server at the time, where and admin set up ood.cori.ncsa.cloud to redirect to localhost.

ood.cori.ncsa.cloud {
  import tls
  route {
    respond /robots.txt 200 {
      body "User-agent: *
Disallow: /"
      close
    }
    reverse_proxy https://127.0.0.1:18080 {
      transport http {
        tls_insecure_skip_verify
      }
    }
  }
}

That was done before I redid certs. But I pretty much kept everything in the ood_portal file the same. servername is currently still localhost. If I go to that address, it ends up on localhost:18080. I can’t think of anything else I did on this, but I’m not the only one with admin privileges.

I was in sudo su mode when I was looking at httpd -V.

24

When i redid the certificate, I changed the command from what was run previously. That’s the only thing I think I really did differently.

25

OK well, all’s well that ends well I suppose.

Just reach out again if you have any other issues!

1 Like