I have MQ 7.5 installed on a ubuntu machine.
From the terminal I can run the runmqsc command this takes me into a shell.
I run a few commands,
then when I try to exit runmqsc by typing quit, i get a error message.
Only end seems to work.
Why is this happening? Have I changed some setting inadvertently?
Update 1:
Below is the output of the dspmqver command.
user1#ubuntuvm-5:~$ /opt/mqm/bin/dspmqver
Name: WebSphere MQ
Version: 7.5.0.2
Level: p750-002-130704
BuildType: IKAP - (Production)
Platform: WebSphere MQ for Linux (x86-64 platform)
Mode: 64-bit
O/S: Linux 4.4.0-96-generic
InstName: Installation1
InstDesc:
Primary: No
InstPath: /opt/mqm
DataPath: /var/mqm
MaxCmdLevel: 750
quit and exit were added to runmqsc at V8.0. Prior to that release there was only end.
See Knowledge Center: runmqsc (V8.0.0) and IBM Tech note: New features added to the runmqsc command in IBM MQ Version 8.0.
Related
I am testing a known working Redhat Kickstart procedure on upgraded Vmware software.
Our KS process uses two CDRom's. the RH ISO is attached to CD 1 and KS ISO attached to CD 2.
the KS process fails with many messages such as
localhost dracut-initqueue[1118]: Warning: dracut-initqueue timeout - starting timeout scripts
In addition the following message appears in the rdsosreport file:
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.
I have successfully used the vscode's extension Remote-SSH on a few remote linux servers. However, I cannot get past the "Acquiring lock" message in my vscode terminal on one particular server and would like to know how to. The terminal displays the "Acquiring Lock" line in the terminal and nothing else follows. I have even let this connection try to resolve itself overnight and it just will not go any further.
The output I am receiving appears as follows (I have replaced some real values/hash with generic text wrapped in angle brackets):
[13:48:34.210] Log Level: 3
[13:48:34.218] remote-ssh#0.49.0
[13:48:34.218] win32 x64
[13:48:34.221] SSH Resolver called for "ssh-remote+<hash>", attempt 1
[13:48:34.221] SSH Resolver called for host: DEV
[13:48:34.221] Setting up SSH remote "DEV"
[13:48:34.291] Using commit id "<hash>" and quality "stable" for server
[13:48:34.292] Install and start server if needed
[13:48:34.296] Checking ssh with "ssh -V"
[13:48:34.347] > OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
[13:48:34.348] Running script with connection command: ssh -T -D 55214 DEV bash
[13:48:34.354] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[13:48:34.502] >
[13:48:34.503] Got some output, clearing connection timeout
[13:48:34.626] > <User>#<HostName>'s password:
[13:48:34.626] Showing password prompt
[13:48:42.869] Got password response
[13:48:42.869] "install" wrote data to terminal: "***********"
[13:48:42.908] >
>
[13:48:42.969] > <hash>: running
>
[13:48:43.009] > Acquiring lock on /<path to commit id hash>/vscode-remote-lock.<User>.<hash>
>
>
Vscode version
Version: 1.42.1 (user setup)
Commit: c47d83b293181d9be64f27ff093689e8e7aed054
Date: 2020-02-11T14:45:59.656Z
Electron: 6.1.6
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.17763
Remote - SSH version 0.49.0
Thank you for taking a look at my issue!
Update
The attempt appears to have finally timed out. The message that was left is:
[15:48:54.081] "install" terminal command done
[15:48:54.082] > Connection reset by <ip address> port 22
>
[15:48:54.084] Install terminal quit with output: Acquiring lock on <vscode-remote-lock file>
[15:48:54.085] Received install output: Acquiring lock on <vscode-remote-lock file>
[15:48:54.090] Stopped parsing output early. Remaining text: Acquiring lock on <vscode-remote-lock file>
[15:48:54.090] Failed to parse remote port from server output
[15:48:54.092] Resolver error:
[15:48:54.108] ------
I brought this issue up on the Remote-SSH Github project: https://github.com/microsoft/vscode-remote-release/issues/2472
After putting this issue in on Stackoverflow, the extension developers have developed a fix for this on their Nightly version of the extension. The fix will be in the Remote-SSH version 0.50.
Appium Server version: 1.7.1
OS: Windows 8
While running the code I got
org.openqa.selenium.WebDriverException:
An unknown server-side error occurred while processing the command.
Original error:
Error executing adbExec.
Original error:
'Command 'D\:\\Android\\android-sdk\\platform-tools\\adb.exe -P 8080 -s ------ install C\:\\Users\\resi\\AppData\\Local\\Programs\\appium-desktop\\resources\\app\\node_modules\\appium\\node_modules\\appium-unlock \\bin\\unlock_apk-debug.apk' exited with code 1';
Stderr: 'Failed to install C:\Users\resi\AppData\Local\Programs\appium-desktop \resources\app\node_modules\appium\node_modules\appium-unlock\bin\unlock_apk-debug.apk:
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE:
Package io.appium.unlock signatures do not match the previously installed version; ignoring!]'; Code: '1'
error and Appium Setting page is opened and instant closed in real Android device instead of opening app (.apk file)
You need to cleanup the device you are using:
Go to Settings -> Apps
Delete you application under test using Uninstall for all users menu
Delete Appium Settings app
Restart your test and it should work
Here is a summary:
Objective: Debug a dynamic web application
Environment: MacOS 10.6.8 / Eclipse Helios 20110218-0911 / Tomcat 7
Error: Failed to connect to remote VM. Connection refused.
Story line:
Doing some research on this matter, I found out that the possible problem to this is that I need to start tomcat7 in debug mode which usually acts on port 8000. The command I'm using is ./catalina.sh jpda start which didn't work (it starts tomcat but doesn't start debug mode). So I tried other things like adding this
variables to the system:
declare -x CATALINA_HOME="/Library/Tomcat"
declare -x JPDA_ADDRESS="8000"
declare -x JPDA_TRANSPORT="dt_socket"
and the problem keeps happening.
this is the return of the command: ./catalina.sh jpda start
Using CATALINA_BASE: /Library/Tomcat
Using CATALINA_HOME: /Library/Tomcat
Using CATALINA_TMPDIR: /Library/Tomcat/temp
Using JRE_HOME: /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home
Using CLASSPATH: /Library/Tomcat/bin/bootstrap.jar:/Library/Tomcat/bin/tomcat-juli.jar
can anyone help ?
thank you in advance.