Problem
I am trying to connect to client's remote mercurial repository. The error I get when connecting to it wit any command:
abort: error: [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:997)
I am on Macbook air M1 using mercurial version:
Mercurial Distributed SCM (version 6.0.1)
This is the latest version currently. Server with remote repository is a debian distribution using mercurial 4.8:
Mercurial Distributed SCM (version 4.8.2)
This version is the stable version for debian as it is stated on https://www.mercurial-scm.org/wiki/Download
I only get this problem on mac. On another windows computer mercurial version is 5.6 and it works fine.
How to solve this?
Related
I have a Debian linux server with glassfish 6.1 and JDK 11.
When configure the javamail session the server answer with a error javamail module not found.
I have installed the javamail with apt-get install, but it is not working.
How to configure the javamail module inside glassfish system ?
Thank you.
I had this error today after updating my IntelliJ IDEA on Windows machine and trying to access project on my remote Ubuntu virtual machine over SSH with JetBrains Gateway.
JetBrains Client 2022.1
JetBrains Gateway 2022.1
IntelliJ IDEA 2022.1 (Ultimate Edition)
TL/DR
I've removed whole /home/user/.cache/JetBrains folder.
Explanation
I've resolved my problem by checking logs:
#c.i.i.StartupUtil - JVM options: [-Djava.home=/home/user/.cache/JetBrains/RemoteDev-IU/...
Line 86164: 2022-04-25 09:40:57,760 [ 288] INFO - STDOUT - This
IDE build has expired. Please download a new build from JetBrains
official site
Since it was remote project on my Ubuntu 20.04 virtual machine.
I've removed whole /home/user/.cache/JetBrains folder.
Next time I started my remote project from JetBrains Gateway it downloaded client and other missing files automatically on my Ubuntu machine and then everything worked.
For some reason IDE on Ubuntu side didn't get updated when opening remote project on Ubuntu.
Try switching your login shell on the server to bash.
I am trying to create an Azure IoT Edge device on a Windows host, but running a module built as a Linux container. In a previous experiment, I was able to successfully create an Azure IoT Edge device on a Linux host, and successfully running this same Linux container module.
However, when I deploy the module onto the Windows host, the module shows that it is not running, and when I view the module's log using "iotedge logs camera-capture" I get the following error:
<6> 2019-12-02 13:32:56.016 -08:00 [INF] - Executing command: "Create module camera-capture"
<3> 2019-12-02 13:33:11.674 -08:00 [ERR] - Executing command for operation ["create"] failed.
Microsoft.Azure.Devices.Edge.Agent.Edgelet.EdgeletCommunicationException- Message:Error calling Create module camera-capture: Could not create module camera-capture
caused by: Could not pull image localhost:5000/camera-capture-opencv:1.1.128-amd64
caused by: image operating system "linux" cannot be used on this platform, StatusCode:500, at: at Microsoft.Azure.Devices.Edge.Agent.Edgelet.Version_2019_01_30.ModuleManagementHttpClient.HandleException(Exception exception, String operation) in C:\agent\_work\4\s\edge-agent\src\Microsoft.Azure.Devices.Edge.Agent.Edgelet\version_2019_01_30\ModuleManagementHttpClient.cs:line 194
I have found no results online, or through Microsoft forums, regarding this particular error that was able to resolve my problem. For the record, I have ensured:
I am running a compatible Windows 10 host (17763)
I have Hyper-V and Containers installed
I have VT enabled in the BIOS
I have configured my deployment.template.json to build as "amd64" platform
I have configured my Docker Desktop to run using Linux Containers (and also enabled Experimental mode)
I have tested the basic "hello-world" ubuntu example online, and it works when I run it from Powershell, which proves that a Linux container will run on my Windows host
Any help would be greatly appreciated!
After spending a few days stuck on this issue, I finally found the solution. The problem was with the IoT Edge runtimes on Windows were not configured to handle Linux containers!
As of this writing, the solution is documented here by Microsoft: https://learn.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-windows-with-linux
But in case of a future dead link, you basically have to add additional flags when you install your Azure IoT Edge runtimes to handle linux containers.
. {Invoke-WebRequest -useb aka.ms/iotedge-win} | Invoke-Expression; `
Deploy-IoTEdge -ContainerOs Linux
. {Invoke-WebRequest -useb aka.ms/iotedge-win} | Invoke-Expression; `
Initialize-IoTEdge -ContainerOs Linux
I changed Docker Desktop to Linux container mode and compiled in VSCode. It worked like magic.
when installing Zabbix v3.4 I get the following error message: http://imgur.com/a/xo3tg
Looks like an error in the yum repository. Do you have any suggestions for solutions or something similar?
Best regards
As you can see, there is just 2.2 version of Zabbix (agent, server, proxy, etc.) in that repository.
It seems Zabbix 2.2 (LTS) is the latest version supported by OpenSUSE using its repositories.
By the way, you can install older versions of Zabbix-agent (like 2.2) sending data correctly to newer server/proxy versions (like 3.0 or even 3.2).
I think the major item you will miss with using zabbix-agent older than 3.X is encryption. Other major features work very good.
I'm installing a v7.0.0 MobileFirst Server with Liberty 8.5.5.4 with Java 1.7.0 on RedHat in Nonadminstrator mode. Steps I have followed:
Successfully install Liberty, create a server and verify it starts with no errors in messages.log.
Install MFP Server.
Use the MFP Server Configuration Tool to create an MFP configuration using the Liberty server.
Bounce the Liberty server and verify it starts with no errors.
Create an MFP Runtime using the Server Configuration Tool.
Bounce the server and observe SSL errors in the log.
The SSL errors seem to be related to Liberty trying to talk to the JMX REST client - at least that is my assumption since I haven't even invoked an adapter yet.
The WAR file I am using for the Runtime comes from a project that builds and runs fine in the MFP Studio Liberty development server.
The full log can be found at https://www.dropbox.com/s/o1frf7pjszm46n6/messages.log?dl=0, but here's the relevant error:
[8/4/15 18:23:09:400 CDT] 00000050 com.ibm.ws.channel.ssl.internal.SSLHandshakeErrorTracker E CWWKO0801E: Unable to initialize SSL connection. Unauthorized access was denied or security settings have expired. Exception is javax.net.ssl.SSLException: Received fatal alert: certificate_unknown
at com.ibm.jsse2.o.a(o.java:6)
at com.ibm.jsse2.SSLEngineImpl.a(SSLEngineImpl.java:409)
at com.ibm.jsse2.SSLEngineImpl.a(SSLEngineImpl.java:469)
at com.ibm.jsse2.SSLEngineImpl.j(SSLEngineImpl.java:181)
at com.ibm.jsse2.SSLEngineImpl.b(SSLEngineImpl.java:176)
at com.ibm.jsse2.SSLEngineImpl.a(SSLEngineImpl.java:495)
at com.ibm.jsse2.SSLEngineImpl.unwrap(SSLEngineImpl.java:66)
at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:23)
at com.ibm.ws.channel.ssl.internal.SSLUtils.handleHandshake(SSLUtils.java:870)
at com.ibm.ws.channel.ssl.internal.SSLConnectionLink.readyInbound(SSLConnectionLink.java:531)
at com.ibm.ws.channel.ssl.internal.SSLConnectionLink.ready(SSLConnectionLink.java:304)
at com.ibm.ws.tcpchannel.internal.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:174)
at com.ibm.ws.tcpchannel.internal.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:83)
at com.ibm.ws.tcpchannel.internal.WorkQueueManager.requestComplete(WorkQueueManager.java:504)
at com.ibm.ws.tcpchannel.internal.WorkQueueManager.attemptIO(WorkQueueManager.java:574)
at com.ibm.ws.tcpchannel.internal.WorkQueueManager.workerRun(WorkQueueManager.java:929)
at com.ibm.ws.tcpchannel.internal.WorkQueueManager$Worker.run(WorkQueueManager.java:1018)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:906)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:929)
at java.lang.Thread.run(Thread.java:796)
Solved it. I went back to a system I knew worked and started looking for differences. The configuration was all the same, but I noticed the working system used
java version "1.7.0"
Java(TM) SE Runtime Environment (build pxa6470sr7fp1-20140708_01(SR7 FP1))
IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References 20140627_204598 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR7_20140627_0924_B204598
JIT - r11.b06_20140409_61252.04
GC - R26_Java726_SR7_20140627_0924_B204598_CMPRSS
J9CL - 20140627_204598)
JCL - 20140707_01 based on Oracle **7u65-b16**
The system that was throwing the SSL errors was running
java version "1.7.0"
Java(TM) SE Runtime Environment (build pxa6470sr6fp1ifix-20140220_01(SR6 FP1+IX90136+IX90137))
IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References 20140106_181350 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR6_20140106_1601_B181350
JIT - r11.b05_20131003_47443.02
GC - R26_Java726_SR6_20140106_1601_B181350_CMPRSS
J9CL - 20140106_181350)
JCL - 20140103_01 based on Oracle **7u51-b11**
I installed 7u65-b16 on the new system, restarted Liberty under that version of Java and all seems to be well now.