Epicor Eclipse is aware of the Meltdown-Spector vulnerabilities affecting many modern microprocessors from Intel, AMD, POWER and ARM chips that could allow hackers to access a computer’s memory and steal passwords, encryption keys and other private information from open applications.
Because it’s a vulnerability in the CPU hardware implementations, not a bug in the Eclipse application program, there is no “patch” from Eclipse.
We recommend that customers to check with their hardware and Operating System (OS) vendors for applicable patches as the solution for Meltdown and Spectre.
- Apply the firmware update via BIOS update
- Apply the operating system (RHEL, Windows and AIX) patch
- Apply hypervisor patches where applicable
Recommended Customer Actions
We recommend that customers to open a service request with Eclipse Systems support team and deploy patches on their platform and underlying infrastructure on a mutually agreed schedule.
Frequently Asked Questions
Q: How do I patch my system?
A:Install Red Hat updates.
A:Install Dell Firmware Update.
Q: Will these fixes slow down my server?
A: Yes, there is performance impact caused by additional overhead required for security hardening, but the actual performance degradation that customers see may vary considerably based on the nature of their workload, hardware configuration and system constraints.
Q: Can I disable these fixes?
A: Yes, you can disable the kernel patches if you fell confident that your systems are well protected by other means. Please see this article from Red Hat for a step by step instructions.
UniVerse Database Replication
Data replication frequency: typically “real time”
Time to recovery: typically a few minutes
Eclipse customers that want “real time” replication can use UniVerse’s native replication functionality. The software is configured to capture writes to the database and replicate them to a secondary server while preserving the integrity of the database. Recovery is also quick, since the Eclipse software is already up and running on the secondary server. This solution is implemented and supported directly by the database vendor, Rocket Software, so please contact your account manager for more details.
NOTE: these steps must be performed on the same LAN as the device.
- Record the MAC address of the Digi device (located on the label side (bottom) of the unit)
- Manually update the workstation’s ARP table using the Digi device’s MAC using one of the commands below, substituting the new Digi’s IP address and MAC address:
arp -s 192.168.2.2 00-00-9d-22-23-60
arp -s 192.168.2.2 00009d222360
- Ping the Digi device using the IP address just assigned:
The Eclipse PD team has identified JBoss running on RHEL 5.x with Java 7u131 may crash when the Solar Eclpse SSL interface (i.e Connection Pool, Session manager and etc..) is accessed from a browser.
This is an Oracle bug, and it is expected to be fixed with java 7u141 release.
The Work-around is to not use java 7u131. Do not install java update or downgrade to an older version if java 7u131 has already been installed.
To downgrade java to older version, 7u95:
yum downgrade java-1.7.0-openjdk-22.214.171.124-126.96.36.199.el5_11
To exclude java updates when manually installing the RHEL updates:
yum update --exclude=java-1.7.0-openjdk-188.8.131.52*
If your system is setup with RHEL automatic update you may temporarily disable it and run manual updates until a fix is available.
To disable RHEL auto update:
chkconfig yum-updatesd off
service yum-updatesd stop
If your system is configured to perform an rsync backup as part of the standard snapshot script, simply run the following command:
at now -f /u2/UTILS/bin/snapsave_linux.sh
To schedule the backup at specific date and time, for example at 11PM today, change now to 23:00.
at 23:00 -f /u2/UTILS/bin/snapsave_linux.sh
This script will suspend your database, take snapshots of the database files and create a full tape backup. You will not see any output in your console session, because the script creates a separate log file under /tmp/snapsave.log.
If you have already created the snapshot filesystem, but you want to perform a separate manual tape backup:
rsync -avz --delete --stats /snap/u2/ /mnt/nas/rsync/
If there are no snapshots present, but no users are on the system and you want to perform a manual rsync backup:
rsync -avz --delete --stats /u2/ /mnt/nas/rsync/
How to use the at command
How to use rsync