Receiving “Legacy System Extension” Dialog Box After Upgrading To macOS Catalina 10.15.4+

USB Generic redirection is the main component utilizing kernel extensions. Apple is deprecating the use of Kernel extensions in upcoming releases of macOS.

The warning is to inform us before moving forward with the deprecation.

In the event Apple deprecates it in the next release, only Generic USB redirection will be affected, and will not allow the use of said feature.


  • No Related Posts

SEP smcd : tons of 8KB reads of logs (performance issue)

I need a solution

With SEP for Linux 14.2.1031.0100 on RHEL 7 we are seeing smcd nearly constantly reading/re-reading the multi-hundred-MB dated log data in /var/symantec/sep/Logs/MMDDYYYY.log in mere 8KB read() operations. We have seen this before on older versions of SEP 14 as well.

This happens even with smcd started with ‘-l warning’ instead of the default of ‘-l info’ What is the purpose of this and how do we stop it? It saturates a full CPU core on our VMs unless we stop smcd, deleted all of those logs, and start smcd again. That buys us some time until those logs get big again.

% sudo strace -f -p 28822


[pid 28822] read(14, "31050400343A,6,2,0,ourhost-linux"..., 8191) = 8191
[pid 28822] _llseek(14, -7976, [295662760], SEEK_CUR) = 0

<nearly constant stream of those system calls and 100% CPU usage>



Proxy unexpectedly got rebooted

I need a solution

Hi  Team,

Our both poxy got rebooted unexpectedly. One is last week and other is on this week.

I only can see software got rebooted. Please check below logs for more info and help me to find out the reason. 


Minicontext produced on: 2019-04-18 08:36:44+00:00UTC
Minicontext version: 1.5
ProxySG Appliance: Version
Architecture: x86_64
Kernel: Multiprocessor
System image flags: Customer, Optimized, Non-GDB, 64-bit

Hardware exception code: 0xe
Software exception code: 0x0
Page fault linear address: 0x1d
Process group: “PG_TCPIP”
Process: “HTTP CW 2071A91EA40” in “” at .text+0x566abb


Minicontext produced on: 2019-04-10 22:38:47+00:00UTC
Minicontext version: 1.5
ProxySG Appliance: Version
Architecture: x86_64
Kernel: Multiprocessor
System image flags: Customer, Optimized, Non-GDB, 64-bit

Hardware exception code: 0x0
Software exception code: 0x5a0000
Page fault linear address: 0x0
Process group: “PG_UNKNOWN”
Process: “Threshold_Monitor” in “” at .text+0x0






Installation of RTME disables Multimedia Redirection on Linux Receiver

Multimedia Redirection is disabled by RTME 2.7 (or older) to avoid Race condition between RTME and Receiver for Linux / Citrix Workspace app for Linux with Video Capturing devices.

“On Linux terminals, the RealTime Media Engine 2.7 (or older) installer disables multimedia redirection in Linux Receiver. Thus, avoiding the Optimization Pack and Linux/Unix Receiver getting into a conflict when accessing video devices. ”

Please note that any application in the virtual desktop that needs to access the webcam has to be 32-bit, since this is the only configuration supported by Citrix Workspace app for Linux at the moment.

You can use a 32 bit browser to verify webcam redirection online (e.g.

In Linux terminals, webcams are used in exclusive mode by the application.

For example, if Firefox is using the webcam and GoToMeeting needs to be launched, the Firefox tab has to be exited and then launch GoToMeeting to use the webcam.


Hyperledger introduces Fabric v1.4 LTS, the first long term support release

Hyperledger, an open source collaborative effort created to advance cross-industry blockchain technologies hosted by The Linux Foundation, today introduced Fabric v1.4 LTS, its first long term support release.

The Fabric developers have been working with network operators and application developers to deliver v1.4 with a focus on production operations and developer ease of use.

Key new production-focused features of Fabric fall into four key areas:

  • Serviceability and Operations: As more Hyperledger Fabric networks get deployed and enter a production state, serviceability and operational aspects are critical. Fabric v1.4 takes a giant leap forward with logging improvements, health checks, and operational metrics. Along with a focus on stability and fixes, Fabric v1.4 is the recommended release for production operations. Future fixes will be delivered on the v1.4.x stream, while new features are being developed in the v2.0 stream.
  • Improved programming model for developing applications: Writing decentralized applications has just gotten easier. Programming model improvements in the Node.js SDK and Node.js chaincode makes the development of decentralized applications more intuitive, allowing you to focus on your application logic. The existing npm packages are still available for use, while the new npm packages provide a layer of abstraction to improve developer productivity and ease of use. We have also provided a comprehensive business scenario and tutorial to get you started with the new developer experience.
  • Enhanced data privacy: Data and transaction confidentiality has been a key driver for Fabric development since v1.2. With this new release, we have added two new enhancements: 1) peers for organizations that are added to private data collections can now retrieve the private data for prior transactions to which they now are entitled, and 2) automatically enforce access control within chaincode based on the client organization collection membership without having to write specific chaincode logic.
  • Hand-on tutorials: Commercially focused training to help developers move up the Fabric learning curve quickly and efficiently to speed adoption and deployment.

Complete details of the new features can be found in Hyperledger’s What’s New documentation and release notes.

Hyperledger Fabric’s First Long Term Support Release.

Hyperledger Fabric v1.4 LTS marks the first long term support release. Hyperledger noted this as a critically important development for those beginning to deploy Hyperledger Fabric solutions into production and is a reflection of the confidence that the Fabric maintainers have in this latest release.

The policy to date has been to provide bug fix (patch) releases for its most recent major or minor release until the next major or minor release has been published. Hyperledger reports they plan to continue this policy for subsequent releases. However, for Hyperledger Fabric v1.4 LTS, the Fabric maintainers are pledging to provide bug fixes for a period of one year from the date of release (Jan 10). This will likely result in a series of patch releases (v1.4.1, v1.4.2, …), where multiple fixes are bundled into a patch release.

If running with Hyperledger Fabric v1.4 LTS, users can be assured that they will be able to safely upgrade to any of the subsequent patch releases. In the advent that there is a need for some upgrade process to remedy a defect, Hyperledge will provide that process with the patch release.


  • No Related Posts

RecoverPoint: ScaleIO Initialization not moving, host crash or stuck on highload

Article Number: 503004 Article Version: 3 Article Type: Break Fix

RecoverPoint,RecoverPoint CL,RecoverPoint EX,ScaleIO Product Family,ScaleIO Software

IOs to offsets greater than 1T are causing a short init on the CG. Host crash/stuck on high load.

Symptoms found in the logs:

ScaleIO host logs:

sdw1 kernel: attempt to access beyond end of device

sdw1 kernel: sdr: rw=33, want=2147483736, limit=1967000000


sdw4 kernel: NMI watchdog: BUG: soft lockup – CPU#40 stuck for 22s! [splDataPathExec:97896]

localhost kernel: INFO: task dd:3540 blocked for more than 120 seconds.

Splitter logs:

sdw1 kernel: 4967/4967: RPS:#0 – spl_kbox_end_io : offset = 2147483704, len = 16384, MajorMinor(65, 16), error status = -5

sdw1 kernel: 1351/1351: RPS:#1 – CommandIoSplit_KboxEndIo: Immediate MOH is true. Moving to Tracking. vol guid=0xe102395df73e4b67

RPA (Storage):

st_handle_write_atio: huge write !!! len=1048576 max_chunk_len=524288 (in bytes), ox_id=0x16, cd_remote_entity_id=0x6bca7c6343a4ccca, vlun=0x2c2d8

Splitter type(s): ScaleIO Splitter

Affected versions: 5.0.1,,

Splitter has no limitation on number of inflight IOs. Splitter’s RPA IO timeout flow is wrongly handled. Historically RPA supports IOs to addresses up to 1T.




Dell EMC engineering is currently investigating this issue. A permanent fix is still in progress. Contact the Dell EMC Customer Support Center or your service representative for assistance and reference this solution ID.


  • No Related Posts

Hyperledger Fabric 1.4 released with long term support

Today Hyperledger part of the Linux Foundation announced the release of the latest version of enterprise blockchain Hyperledger Fabric 1.4 LTS. The LTS stands for long term support and is Fabric’s first such release. Commonly with operating systems and major software distributions particular versions are badged as LTS which means security patches are released for that version even after new versions with added features become available.

This is important in a production environment when upgrading to new versions involves a lot of work to adapt code. Particularly if developers don’t necessarily want to take advantage of new features quite yet. Hence Hyperledger is committing to release patches for Hyperledger Fabric 1.4 until 10 January 2020. By LTS standards, a year is quite short, but blockchain is a fast moving sector. Linux versions are typically supported for five years and major software frameworks for roughly two years.

One area that Hyperledger has received a little flak is the serviceability for a production environment. Most servers store logs of key activities and the ability to interrogate these logs is critical for debugging issues. Hence Fabric 1.4 includes enhanced logging, health checks and operational metrics. The team referred to the serviceability as a “giant leap forward” in the announcement.

Previous versions of Fabric included an SDK and chaincode for Node.js the popular server-side javascript scripting framework. The programming model for both of these has a major upgrade so that developers can focus more on the application logic rather than needing to delve deep into the nitty-gritty.

Additionally, 1.4 features privacy enhancements. Latecomers added to private data collections can now retrieve private data for historical transactions which they’re entitled to see. And client access control is now automatically enforced within chaincode by a simple configuration without the need to write specific code.

The race is on

Hyperledger version 2.0 is expected in the Spring. It includes major features such as enhanced support for tokens and atomic swaps. Plus there’s an additional consensus mechanism – Raft – being added to existing consensus options Solo and Kafka.

Image Copyright: hyperledger


Information on Sophos SAVDI release 2.6.0

This article provides an overview of the main new features introduced with SAVDI 2.6.0.

Applies to the following Sophos product(s) and version(s)

SAV Dynamic Interface 2.6.0

SAV Dynamic Interface

SAVDI – SAV Dynamic Interface 2.6.0 – new features

  • Add TFT capability to SAVDI
  • SAVDI Stack Cookie implementation support
  • Remove libssp dependency from Linux builds

For more information please have a look at the Release Notes which are packaged with the product.

If you’ve spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article.

This is invaluable to us to ensure that we continually strive to give our customers the best information possible.


  • No Related Posts