Cumulus Support

A couple of days ago, the web server provider I use (Siteground) changed the administration interface from cPanel to "Site tools". A result was the need to change my FTP and MySQL usernames. Having done this, all works well - with one exception

The MySQL uploads I have set are:
1. Monthly log file upload
2. Dayfile.txt upload
3. A custom upload at 1 minute intervals (this is for my "enhanced" realtime table)

And the standard files and graphs are also ftp'ed up (yes I know this seems redundant!) as are a few custom ones.

All of these work except #1 - the upload to MySQL of the monthly log file. According to the diags file, for that upload (only) it is using the OLD username - tillyspa - ie the one used before the siteground administration changes. The first few lines are included to show the Dayfile upload to MySQL worked, so must have had the new credentials.


Nowhere can I find a reference to this old username - except in the diag . The FTP and MySQL usernames in Cumulus.ini have been changed to reflect the new name in the Site Tools. And this is of course necessary for the other uploads to work, and I would have expected for the monthly one too.

Any ideas gratefully received.

can you confirm you did restart Cumulus when you made the ftp username changes?

yes - many times while trying to get this darn thing to work!

It's hard to image how that can happen as all the MySQL connections use the same variable for the username.

that's what I assumed. There seems to be only two places in cumulus where username can be set - ftp settings and mysql settings (well and noaa settings, which I often overlook when I make such changes until I realize that's not uploading)

... and why would the dayfile mysql upload work and not the monthly? Do they not have the same user name?

Silly question but you don't by any chance have two CumulusMX's running one in an old directory and the other in a new one, hence why old settings could be picked up?

no such thing as a silly question. But I don't think so - at least not intentionally! I have "stop second instance" checked. Out of interest, how would I check this more directly? (I'm not a linux wiz by any stretch of the imagination)

The cumulus restart has been answered, but did you also restart the linux machine? Shutdown, poweroff and powerup?

billy wrote: ↑Tue 09 Feb 2021 10:10 am no such thing as a silly question. But I don't think so - at least not intentionally! I have "stop second instance" checked. Out of interest, how would I check this more directly? (I'm not a linux wiz by any stretch of the imagination)

In a terminal window:
You should only have one process listed.

HansR wrote: ↑Tue 09 Feb 2021 10:18 am The cumulus restart has been answered, but did you also restart the linux machine? Shutdown, poweroff and powerup?

Is this necessary? Shutdown of Cumulus will release all existing resources.

@freddie: true but the MySql subsystem is totally independent of Cumulus so you never know what is in there. The only thing we know is things go wrong somewhere. Why not in the MySql subsystem?

HansR wrote: ↑Tue 09 Feb 2021 10:18 am The cumulus restart has been answered, but did you also restart the linux machine? Shutdown, poweroff and powerup?

hmm ... I did in the earlier phases of trying to solve this but there were some other authentication issues at that stage so I will test now. I cmx as a service and have to remind myself how to stop the service auto starting at the reboot too

I think the reboot will organise the shutdown and restart of cmx automatically when configured correctly (at least it does with me)

@HansR true - I hadn't realised the database was on the same host. Even so, I would do a database process restart rather than a reboot. Also, the old username was being logged in the MX log file, so will be obtained from MX config rather than the database.