Ironing out some problems

[wishmeluck]

So i just went through the tutorial, Instructions: Installing CumulusMX on Raspberry Pi and I'm pretty happy with the results.

I'm not sure if I misunderstand the concept so please bear with me. I start Putty and log into the pi, start Cumulus, data is logged, when the pc gets turned off I lose connection. I was under the impression that I use my pc to control the pi and once I started logging data on the pi I could turn the pc off and pi would continue to log data.

I must be missing a step or something. Appreciate your help.

[billy]

I could turn the pc off and pi would continue to log data

How do you check that MX isn't running and logging data? Via the dashboard from another pc?

[wishmeluck]

I could turn the pc off and pi would continue to log data

How do you check that MX isn't running and logging data? Via the dashboard from another pc?

Either from my phone or when I check on the PC and check the dashboard there'll be a flat line in the data.

[billy]

Anything in the diag file that indicates why it has stopped?

[wishmeluck]

Anything in the diag file that indicates why it has stopped?

I don't know how to access this, can you assist with it please?

[billy]

In the folder mxdiags.

[water01]

I assume you are using SSH to log into your PI via Putty.

To leave processes running you have started using SSH you type Ctrl+A then Ctrl+D.

This should detach your screen but leave the processes running.

[ExperiMentor]

So i just went through the tutorial, Instructions: Installing CumulusMX on Raspberry Pi and I'm pretty happy with the results.

I'm not sure if I misunderstand the concept so please bear with me. I start Putty and log into the pi, start Cumulus, data is logged, when the pc gets turned off I lose connection. I was under the impression that I use my pc to control the pi and once I started logging data on the pi I could turn the pc off and pi would continue to log data.

I must be missing a step or something. Appreciate your help.

Your understanding is correct. But that behaviour assumes you continue with my tutorial to the end and make the RPi automatically run Cumulus in the background. If you start Cumulus as a foreground task (ie, from the command prompt via SSH from Putty), the Cumulus process will stop when you disconnect Putty (either using the exit commend or closing the PC window).

water01 has suggested a different method - I have never used that and cannot verify that it will work (though it should - just may be confusing and will mean your setup no longer matches the tutorial)

To leave processes running you have started using SSH you type Ctrl+A then Ctrl+D.

[wishmeluck]

Your understanding is correct. But that behaviour assumes you continue with my tutorial to the end and make the RPi automatically run Cumulus in the background. If you start Cumulus as a foreground task (ie, from the command prompt via SSH from Putty), the Cumulus process will stop when you disconnect Putty (either using the exit commend or closing the PC window).

Thanks for this, I've just attempted to finish the tutorial to the end. Hopefully I've done it correctly. As a completely new Linux user I have to say I feel quite intimidated that I'm going to do something catastrophically wrong that I won't be able to fix so thanks for the help again.

So after completing the tutorial, when I shut down the windows pc that I've been communicating via PuTTy with will keep the pi/WWL/Cumulus Mx connection intact?

Also one thing of interest to note, whenever I use the command

Code: Select all

sudo reboot

I get "PuTTy fatal error" remote side unexpectedly closed network connection". Is this because Pi reboots then I have to log in again via PuTTy to regain connectivity?

[malkie]

Also one thing of interest to note, whenever I use the command

Code: Select all

sudo reboot

I get "PuTTy fatal error" remote side unexpectedly closed network connection". Is this because Pi reboots then I have to log in again via PuTTy to regain connectivity?

The Pi has shut down/rebooted so has closed the connection, Putty is telling you this in a less than coherent way...

[wishmeluck]

Well I finished if the tutorial and about 4 hours later I list connection again. If anyone could give me the steps to pull the logs for info as to what happened that would be appreciated.

Or if you have a better idea that would be great also.

[water01]

If you are talking about the CumulusMx log they can be found in the MXDiags folder. They will be in date and time order so looking at the latest one will give you the info you want.

Did you try logging into the Pi with Putty, starting CumulsMX and then typing Ctrl+A then Ctrl+D to disconnect from the process and leave it running?

[wishmeluck]

If you are talking about the CumulusMx log they can be found in the MXDiags folder. They will be in date and time order so looking at the latest one will give you the info you want.

Did you try logging into the Pi with Putty, starting CumulsMX and then typing Ctrl+A then Ctrl+D to disconnect from the process and leave it running?

Haven't tried that yet, I guess I just wanted to stick to the tutorial but maybe I'll give it a try. Thanks

[wishmeluck]

Did you try logging into the Pi with Putty, starting CumulsMX and then typing Ctrl+A then Ctrl+D to disconnect from the process and leave it running?

Well this didn't work either unfortunately.
Edit: I just realized I wasn't running the latest version of Cumulus. Somehow I installed 3064, is there any way this could be the cause?

[mcrossley]

No, I think the Ctrl-A, Ctrl-D combination is talking about using "Screen" - which is what I use.

You first must install screen - https://raspi.tv/2012/using-screen-with ... sions-open

You start a new screen session, start Cumulus in the normal way, then use Ctrl-A, Ctrl-D to disconnect from the Cumulus session. You can then close your SSH session.

If you want to reconnect, establish a new SSH session, type screen -r and you will Cumulus back on your putty session.