Cumulus Support

Well what started out today as a simple backup of one of my stations has turned into a bit of a nightmare. Shortly after completing the backup, I noticed the web pages weren't updating. I should declare at this point that I did forget to stop MX using the systemctl stop command before commencing the backup. Checking the diags file, ftp errors are showing. These have been reported previously but a stop and restart of MX seemed to fix the problem. Not in my case. after a restart, the errors were still there. I have re-installed the backup I just completed (no joy) and then gone back to the basic 3121 distribution and the errors remain. I suspect it is something outside of MX itself but is now beyond my capability to resolve. Hopefully someone can point me in the right direction. I wondered whether it is something to do with the MX service. My MXdiags file attached.
I am running MX on a raspberry pi version 2. OS is buster

Cheers
Steve

You are trying to SFTP to a computer in your local network. Is that what you intend to do? If not, you should check your Settings.

That is correct. It is in fact the same Rpi running MX which is also running an apache webserver. Has never given me an issue until today and I have a second station with the same setup that is running fine. The SFTP is to the /var/www directory on the Rpi.

Cheers
Steve

Then you have to check the SFTP-server on the RPi.

Thanks Steiner for your response. Unfortunately that is where my capability runs out. I'll do some googling to see what I can uncover. I do think this is an issue outside MX.

Cheers
Steve

Unless you have installed an SFTP server on your Pi, you should be connecting FileZilla using the SSH protocol (port 22), not SFTP.

Using FileZilla to look at your Cumulus files etc, would normally be done via SSH.

Hi Mark,
Thanks for your response. I do connect using bitvise ssh port 22 but my take on these errors was thinking they related to the ftp upload of the data to my web directory. When the problem started all ftp uploads stopped so no gauge page or web page update. I had seen this reported before (below) but the fix seemed to be a stop and restart of MX. In my case this didn't seem to work.
The problem seemed to fix itself last night and not sure what I did. Any insights as to why it might have happened would be useful for me to understand. Have I mis-interpreted the errors?

Cheers
Steve

viewtopic.php?f=40&t=19195&p=152523&hil ... le#p152523