I have a question about the dashboard configuratio...
# fusion-reactor
b
I have a question about the dashboard configuration. I have a lucee instance running with a configured password of
passwordX
. I have confugured that instance to start and run with commandbox. I can access that fusion-reactor instance at
<http://localhost:8088>
I register that instance at a windows installation of fusion-reactor with that url and password. That works fine. After I restart the lucee instance, the dashboard wil show a
pwd
on the instance icon. If I go to the instance URL I can log in with the configured password. I have to go to the server manager of the dashboard and edit the monitored instance and put in the same password and save the instance. Then monitoring is fine again... until the next restart. What is happening here? Why would the monitoring page lose access after a restart of the monitored instance?
m
@birdy1980 did you upgrade the version of FusionReactor atall?
what version are these instances running
b
ow sorry... the windows install was upgraded from 8.7.7 to 8.8.0. the lucee instance uses the 8.8.0 package from forgebox.
m
if you upgrade the FR of the dashbaord you may need to reset the password because of the new algorithm
but restarting it after that should be fine
b
I also tried removing and adding the registered instance. I also reset the password of the main (windows) instance
m
when you start the box server, does that spring up a new instance?
or reuse the old one
b
that reuses the old one. Althoug I have tried "forgetting" the server and start a clean instance. that didn't help
should the password of the main fr instance be the same as the fr of the lucee instance?
I have removed and installed fusion-reactor 8.8.0 on windows. And gave that fr-instance a adminpassword of
x
. I have given the fr instance of the lucee server a password of
y
. I can open the fr url of the lucee server and log in with
y
. I register the lucee server with the dashboard of the fr-instance on windows. That is successful. Then I restart the lucee server and the
pwd
icon appears on the dashboard. So I have tried to do a clean install of fr 8.8.0 but the pwd problem persists. I'm going to try to reproduce this problem on a new virtual machine, and record every action that I do. I can share that with you when I have finished that.
m
i suspect i know the issue
when you restart, the instance gets a new unique entity, which since 8.8.0 will have it's own unique password hash
meaning you can't use the same ED server for 2 instance as the hash will be unique, whereas in FR 8.7.x and below the password would always result in the same hash
b
ah, that makes sense.
m
so what you want to do instead is use the auto registration
b
is there a way to solve this?
m
so that your CB image will automatically register with your static dashboard
b
thanks. I will thy this.
m
I don't belive right now CB supports these new args as commandbox params
so you will need to set them as JVM args
b
I don't belive right now CB supports these new args as commandbox params
Yes, I had already noticed that.
m
@bdw429s are these something you can add in the module? https://commandbox.ortusbooks.com/embedded-server/fusionreactor#additional-jvm-args the ones you have here aere depricated since 7.1..x
b
I might even create a pull request for commandbox-fusionreactor to add the new settings.
how do I add this setting to the windows instance of fusion-reactor? fr.ed.ds.enable=true
m
what instance is the dashboard on?
if it's fram edit the vmoptions file and add -Dfr.ed.ds.enable=true as an arg to it
👍 1
b
the dashboard is on the windows instance that I installed with the .msi installer
m
i'm guessing thats FRAM then
b
thanks. I tried adding a system environment variable...
yes, it is FRAM
cool, I have the first server autoregistered with the dashboard 🙂
👍 1
question about the paramter "fr.ed.ds.groups" what should I put in the list? The names of the groups or the Id?
m
the names of the groups you want it in
👍 1
production,group2,myApp something like that
b
If a lucee server restarts or is stopped, it disappears from the dashboard. Is there a way to keep the instance on the dashboard, so you can see it is offline?
m
not with the auto registration, if it goes offline it unregisters itself
b
ah... can't have both 😉
thanks for the help today
@mflewittintergral which of these parameters are deprecated? https://commandbox.ortusbooks.com/embedded-server/fusionreactor#additional-jvm-args
m
all of those
message has been deleted
b
Thanks. The new options for EDS are added to the commandbox-fusionreactor package. A PR to update the documentation is waiting on approval. 🙂
b
merged
🎉 1