Copy link to clipboard
Copied
I'm having problems with the cfsetup.bat tool included with the zip installer of CF 2021. On a clean install, updated to Update 1 and installed the following packages: caching, debugger, mail, scheduler, sqlserver, zip, I encounter some problems exporting and reimporting settings using cfsetup.bat.
If I export METRIC using the command:
cfsetup.bat export METRIC c:\METRIC.json c:\ColdFusion\cfusion
And then immediately try to import it again with:
cfsetup.bat import METRIC c:\METRIC.json c:\ColdFusion\cfusion
It fails with the following error(s):
ERR: Invalid setting key (cfstatHost) for category: (METRIC).
ERR: Import of cfstatHost in METRIC is unsuccessful.
ERR: Import of METRIC is unsuccessful.
ExitStatus: FAIL
Why would this be the case? The default for this setting was unchanged from "127.0.0.1" and I can clearly see the setting in the UI so I know this must be a setting somewhere...
Additionally I have the same problems with the RUNTIME settings. Exporting those and then importing them again produces similar errors but for the following keys:
msic_settings/maxUnzip
template_settings/redisCacheStorageIsSSL
Any help would be appreaicated. Thanks.
Copy link to clipboard
Copied
I have two suggestions. (And to clarify, I did that export and import no problem, against a CF2021 deployed from the zip, and updated to update 1.)
First, since your problem is on the import, what do you see if you edit the file, c:\METRIC.json, once you create it? Since you're on Windows, while you're on the command line you can just do:
notepad c:\METRIC.json
Do you see the json in the file? And in it, do you see the cfstatHost that the error message refers to? I can confirm I do not. Here is what mine looked like:
{"METRIC":{"cfconnectorport":"8500","simpleLoad.sampleSize":"50","simpleLoad.sampleRate":"5","cfstat":"true","cfmetrics.pullfreq":"60.0","reqTimingWindow":"10","cfmetrics":"false","cfperfmon":"false","simpleLoad.maxRequests":"500","cfstatport":"7993","simpleLoad.constLoad":"200","cfperfmon.pullfreq":"1.0"}}
I am suspecting that you may find something interesting based on the above. (I can confirm that even if I make the file empty, I do not get the error you got, but instead just get "ExitStatus: Fail" in response to the import.)
But assuming that doesn't help, I'm curious what you see if you just do this:
cfsetup show metric c:\ColdFusion\cfusion
I see this:
Metric Settings:
cfconnectorport : 8500
cfmetrics : false
cfmetrics.pullfreq : 60
cfperfmon : false
cfstat : true
Do you see more? Less? I'm just trying to help you find where the problem may be, if your results of these things are quite different from mine.
Finally, yes, that "show" output is only 5 metrics, while the json file held 12. I have just filed a bug report for that, CF-4212175.
As for your issue, bcserverteam, let's hear what you may find. I would not think it's time to declare this a bug, since the same thing doesn't happen for me with the same setup. It would seem there's something distinctive about your situation, but we may be able to get to the bottom of it here.
Copy link to clipboard
Copied
Thanks Charlie,
The contents of the METRIC.json file are:
{"METRIC":{"cfconnectorport":"8500","simpleLoad.sampleSize":"50","simpleLoad.sampleRate":"5","cfmetrics":"false","simpleLoad.maxRequests":"500","cfstatHost":"127.0.0.1","cfperfmon.pullfreq":"1.0","cfstat":"true","cfmetrics.pullfreq":"60.0","reqTimingWindow":"10","cfperfmon":"true","cfstatport":"7993","simpleLoad.constLoad":"200"}}
The results of running cfsetup show METRIC are:
Metric Settings:
ExitStatus: FAIL
Clearly there is something that CF does not like about the neo-metric.xml file and the settings in it, I am assuming. The contents of the neo-metric.xml are:
<wddxPacket version='1.0'><header/><data><struct type='coldfusion.server.ConfigMap'><var name='cfstat'><string>true</string></var><var name='simpleLoad.maxRequests'><string>500</string></var><var name='simpleLoad.constLoad'><string>200</string></var><var name='cfconnectorport'><string>8500</string></var><var name='reqTimingWindow'><string>10</string></var><var name='cfperfmon'><string>true</string></var><var name='simpleLoad.sampleRate'><string>5</string></var><var name='cfstatport'><string>7993</string></var><var name='simpleLoad.sampleSize'><string>50</string></var><var name='cfstatHost'><string>127.0.0.1</string></var><var name='cfmetrics.pullfreq'><number>60.0</number></var><var name='cfperfmon.pullfreq'><number>1.0</number></var><var name='cfmetrics'><string>false</string></var></struct></data></wddxPacket>
Copy link to clipboard
Copied
In addition, I tested by starting from scratch. My results...
First time around
Seconds time around
Clearly the issue only shows up when changes are made to the METRIC data. I assume the same thing is happening with the RUNTIME export as well. Which in the end, kind of defeats the purpose of the cfsetup import/export. To me this looks like a bug, which is unfortunate.
Copy link to clipboard
Copied
Same here, on CF 2021.0.01.325996. I have added a comment to the bug Charlie reported.