So I'm using a Jetson Nano (lmk if you want specifics on image or jetpack version), but this is probably more of a Linux question.
When I boot I can't get in over the 8888 port, either headless or over wifi. I ssh to the Nano, run jupyter-notebook, then I can enter fine.
So I figure if I run jupyter-notebook on startup with systemd I'm good. I do that. When I ssh I can see that jupyter-notebook is running (as root) but I still can't connect until I run jupyter-notebook again.
My guess is that I am running the jupyter-notebook command before other appropriate daemons have started.
I tried to start jupyter notebook after some networking has been established by adding:
[Unit]
Description=Robot Service
Wants=network-online.target
After=network-online.target
to my robot.service file. But still no luck. So I guess I have two questions:
1) Is this the right approach to solve this?
2) How do I run jupyter-notebook later in the startup in hopes that all the required services have already started?
So I'm using a Jetson Nano (lmk if you want specifics on image or jetpack version), but this is probably more of a Linux question. When I boot I can't get in over the 8888 port, either headless or over wifi. I ssh to the Nano, run jupyter-notebook, then I can enter fine. So I figure if I run jupyter-notebook on startup with systemd I'm good. I do that. When I ssh I can see that jupyter-notebook is running (as root) but I still can't connect until I run jupyter-notebook again. My guess is that I am running the jupyter-notebook command before other appropriate daemons have started. I tried to start jupyter notebook after some networking has been established by adding:
[Unit] Description=Robot Service Wants=network-online.target After=network-online.target
to my robot.service file. But still no luck. So I guess I have two questions: 1) Is this the right approach to solve this? 2) How do I run jupyter-notebook later in the startup in hopes that all the required services have already started?
Thanks in advance. nmbike