Changing certain engine settings get reset back to default values after a reboot with TIBCO LogLogic LMI
Article ID: KB0076951
Updated On:
| Products | Versions |
|---|---|
| TIBCO LogLogic Enterprise Virtual Appliance | 6.2.0 and higher |
Description
After changing a setting located in any of the following files in /loglogic/conf/:
capability.xml
my.cnf.LXVirtual
my.cnf.MXF
my.cnf.MXVirtual
my.cnf.STVirtual
you may find that after a reboot the setting reverts back to the previous value. This is because resource profiles were implemented starting with LMI 6.2.0. At boot time the appropriate profile is determined based on the resources of the system and then all 5 files listed above are copied from the profile directory (located at /loglogic/conf/vm_profiles) into the working directory, which is /loglogic/conf, just prior to mtask starting up the LMI engines. This copy operation overwrites any custom changes and occurs at boot time for every boot cycle.
Issue/Introduction
Starting with LMI 6.2.0 a user may encounter a situation where upon rebooting the appliance an engine setting's value that had been modified is reset. This article explains one potential cause for that.
Resolution
If you need to make a change to any of the 5 files listed above then you will need to implement the change by editing the profile's copy to make the change survive a reboot. To implement the change without a reboot you can edit the files in /loglogic/conf/ but that will still require an mtask restart to take effect. Applying changes to the profile's copy of these files does not require any further action. The customized values will automatically take effect upon the next reboot.
As a reminder, if you sufficiently change the memory or CPU core allocations for the EVA to cause another profile to be used then your custom changes will not be used. So you will need to apply your previous custom changes to the new profile that is in effect.
As a reminder, if you sufficiently change the memory or CPU core allocations for the EVA to cause another profile to be used then your custom changes will not be used. So you will need to apply your previous custom changes to the new profile that is in effect.
Additional Information
See article 35598 for more information about how resource profiles are designed.
Feedback
Yes
No
Powered by
