IncludeMoonImage and MoonImageEnabled get reset to 0

[martinu]

I've just updated to v3.6.8 (3084), having been on 3.4.4 for ages, and I notice that Cumulus now has the ability to generate a moon image based on the phase of the moon. Up to now I'd used 29 different images of the moon "borrowed" from somewhere on the web, and I selected the correct one using <img src="images/moon<#MoonAge>.png">.

So I've edited the relevant lines to IncludeMoonImage=1 and MoonImageEnabled=1 in the relevant sections of Cumulus.ini. I do this while Cumulus is stopped. The modified file is definitely being saved.

[FTP site]
IncludeMoonImage=1

[Graphs]
MoonImageEnabled=1
MoonImageSize=100
MoonImageFtpDest=images/moon.png

But when I start Cumulus, the time stamp on the file changes to the time when Cumlus is started, and the keywords are set back to 0. I wondered why I was never getting an images/moon.png !

This is on a Raspberry Pi running Raspbian Stretch.

Has anyone else seen this problem?

[mcrossley]

As stated many times, if you edit the Cumulus.ini file you *must* do it with Cumulus stopped.

But why edit the ini file anyway? Just enable the settings via the admin interface, which you can obviously do with Cumulus still running.

[martinu]

I had edited Cumulus.ini with CumulusMX stopped. It was the act of restarting it which set the values back to zero.

I'd looked for the menu items in the admin interface, and hadn't found them - I was looking on Station Settings rather thna Internet Settings. With Cumulus running, having made the changes from the admin interface, everything is working OK: the moon.png file is generated.

In general, should it be possible to hand-edit Cumulus.ini with Cumulus stopped and the restart it to pick up the changes, or havw you seen othewr cases where a hand-edited file (with Cmuous stopped) reverts to its old state when Cumlus is started?

[water01]

That usually happens when you have accidentally started 2 copies of CumulusMX and even though you thought you had stopped the running one, there was one still running in the background.

This can be stopped by ticking "Stop Second Instance" in Settings / Station Settings / Options.