What version of openssl does .Q.hg require? - kdb

I am trying to use .Q.hg in kdb and I get the following error
q).Q.hg`$":https://www.google.com"
'conn. OS reports: Protocol not available
[0] .Q.hg`$":https://www.google.com"
^
q))
When I execute (-26!)[] I get the following output:
q).Q.hg`$":https://www.google.com"
'conn. OS reports: Protocol not available
[0] .Q.hg`$":https://www.google.com"
^
q))
I have downloaded different versions of openssl from the openssl website and built them from source, but nothing seems to work.
I have also downloaded the certificate as instructed on the kx website and defined the SSL_CA_CERT_FILE variables.
UPDATE:
output from (-26!)[]:
q))(-26!)[]
'Could not initialize openssl. Error was incompatible ssl version
[4] (-26!)[]
^
q))
Output from .z.k:
q)).z.K
3.6
q))
Distro version:
Static hostname:
Icon name: computer-laptop
Chassis: laptop
Machine ID:
Boot ID:
Operating System: Linux Mint 19.1
Kernel: Linux 4.15.0-20-generic
Architecture: x86-64

As per kx docs OpenSSL 1.1 is not supported, you need to use a 1.0.x version

Related

MariaDB messages when stopping/starting any service

We have:
Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster
x86_64
Linux 4.19.0-17-amd64 #1 SMP Debian 4.19.194-3 (2021-07-18) x86_64 GNU/Linux
mysql Ver 15.1 Distrib 10.6.4-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
When starting/stopping mariadb.service, the following message appears:
Failed to get properties: Unit name mariadb-extra#.socket is neither a valid invocation ID nor unit name.
Failed to get properties: Unit name mariadb#.socket is neither a valid invocation ID nor unit name.
The same messages pop up when starting/stopping any service.
What's wrong with mariadb user sockets? How can I remove these messages?
From MDEV-27715, the service implementation of Debian/Ubuntu is deficient in that it doesn't fully understand socket templated files of systemd.
Use systemctl.

CUDA_ERROR_COMPAT_NOT_SUPPORTED_ON_DEVICE when running guppy basecaller

I have tried to run the ONT basecaller guppy. I have run this code several times before without any issues. Now (following a reboot) it is producing the error message:
[guppy/error] main: CUDA error at /builds/ofan/ont_core_cpp/ont_core/common/cuda_common.cpp:203: CUDA_ERROR_COMPAT_NOT_SUPPORTED_ON_DEVICE [guppy/warning] main: An error occurred in the basecaller. Aborting.
Is this a compatibility problem, and if so what can I do to solve it?
I'm using Ubuntu 18.04.4 LTS (GNU/Linux 5.4.0-72-generic x86_64)
and Guppy Basecalling Software, (C) Oxford Nanopore Technologies, Limited. Version 4.0.14+8d3226e, client-server API version 2.1.0
Here is my guppy code:
guppy_basecaller -i fast5/pass -r --device cuda:0 -s hac_fastqs_demul -c /opt/ont/ont-guppy/data/dna_r9.4.1_450bps_hac.cfg --num_callers 4 --require_barcodes_both_ends --trim_barcodes --detect_mid_strand_barcodes --barcode_kits "EXP-PBC001"
This issue was fixed by rebooting.

Unable to run phantomJS on karma

I'm encountered a problem recently with PhantomJS library.
$ karma start
Log result:
Karma v0.13.15 server started at http://localhost:9876/ Starting
browser PhantomJS INFO [PhantomJS 1.9.8 (Mac OS X 0.0.0)]: Connected
on socket H1vRWOIqgBCUjb_bAAAA with id 36694801
PhantomJS 1.9.8 (Mac OS X 0.0.0) ERROR TYPE_MISMATCH_ERR: DOM Exception 17: The type of an object was incompatible with the expected
type of the parameter associated to the object. at
/Users/farman/.../tests.webpack.js:122637 <-
webpack:///~/crypto-browserify/rng.js:14:0
PhantomJS 1.9.8 (Mac OS X 0.0.0): Executed 0 of 0 ERROR (2.21 secs / 0
secs)
Module versions:
OSX: El Capitan 10.11.1
node: 5.0.0
Karma: 0.13.15
karma-phantomjs-launcher: 0.2.1
Phantomjs: 1.9.18
I've checked the forum, but still not solving the issue:
https://github.com/AngularClass/angular2-webpack-starter/issues/45
The crypto-browserify library is using Buffer which is buffer is a modified Uint8Array. PhantonJS apparently has a bug that rejects Buffer though and that's causing the issue you're seeing.
I've filed an issue here:
https://github.com/crypto-browserify/crypto-browserify/issues/143
You can also temporarily patch this by updating crypto-browserify/rng.js to replace this...
var bytes = new Buffer(size); //in browserify, this is an extended Uint8Array
...with this...
var bytes = new Uint8Array(size); //in browserify, this is an extended Uint8Array

NV-GLX missing extension in OS X Lion

I connect to a remote linux machine using "ssh -X machine", and then I run a graphical application, so its window is displayed on my local OS X Lion machine using X Window. I get the error
"Xlib: extension "NV-GLX" missing on display "localhost:11.0"."
The application moves very slow. Is it any way to use NV-GLX on OS X or to cimcurvent this problem?
I've encountered similar problem trying to connect from a laptop with AMD graphical card to a linux server with NVIDIA card and drivers installed.
If you have root access to your remote linux machine you could try to restart X server with default libglx.so, not the one from NVIDIA driver package. Appears that NVIDIA installer doesn't support partial installation (only driver, no GLX lib), so one needs to remove NVIDIA libglx.so from xorg modules path, but leave nvidia_drv.so. On Debian you could do
# update-alternatives --config glx # select mesa-diverted
# ln -s /usr/lib/nvidia/current/nvidia_drv.so /usr/lib/xorg/modules/drivers/
Be shure your remote /etc/Xorg.0.log has following parts
...
[ 1111.390] (II) LoadModule: "glx"
[ 1111.390] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 1111.390] (II) Module glx: vendor="X.Org Foundation"
...
[ 1111.391] (II) LoadModule: "nvidia"
[ 1111.391] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 1111.392] (II) Module nvidia: vendor="NVIDIA Corporation"
...
After that Xlib: extension "NV-GLX" missing on display "localhost:11.0" message should go away

What WinDbg version is compatible with NT 4.0 (SP 6a) for kernel debug?

I'm working with WinDbg 6.12 with both serial port connection and named pipe connection. Unfortunately I'm unable to connect my WinDbg with the target (NT 4 SP 6a) from the begining of the OS boot, autoreconnect doesn't work and I need to wait until NT 4 timeout for kernel connection is reached. Then NT continues with the startup process and only then I can connect...
Where I can get a version fully compatible with NT 4? (I have already checked the oldest version from Microsoft Debugging Tools website)
Also, where can I get the NT 4 symbols for debugging? I'm afraid the Microsoft Symbols Server doesn't provide these symbols anymore.
Thanks,
For futher details, the kd log is:
Opened \\.\pipe\com_1
Waiting to reconnect...
Connected to Windows NT 4 1381 x86 compatible target at (Tue Jan 24 16:32:17.010 2012 (UTC + 1:00)), ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: srv*b:\out*o:\out*http://msdl.microsoft.com/download/symbols
Executable search path is:
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
CS descriptor lookup failed
Windows NT 4 Kernel Version 1381 UP Free x86 compatible
Machine Name:
Kernel base = 0x80100000 PsLoadedModuleList = 0x80150b70
System Uptime: not available
The call to LoadLibrary(kdextx86) failed, Win32 error 0n2
"El sistema no puede hallar el archivo especificado."
Please check your debugger configuration and/or network access.
Unable to get program counter
WaitForEvent failed
Unable to get program counter
0008:497a 0010 add byte ptr [bx+si],dl
kd>
Works with http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.7.05.1.exe
From Windbg 6.12 help:
"Windows NT 4.0
Debugging Tools for Windows no longer supports the debugging of Windows NT 4.0 targets.
If you want to debug a Windows NT 4.0 target computer or perform user-mode debugging on Windows NT 4.0, you should use Debugging Tools for Windows version 6.7.5.1. You can install this package from the Debugging Tools for Windows Web site."