I realized the problem yesterday, when my discord bots instead of playing music started to join and leave the voicechannel rapidly. I checked the log and this error was spammed in there:
[JDA AudioWS-ConnectThread (guildId: 388969412889411585)] WARN net.dv8tion.jda.core.audio.AudioWebSocket - Failed to establish websocket connection: HOSTNAME_UNVERIFIED - The certificate of the peer (CN=*.discord.gg, OU=PositiveSSL Wildcard, OU=Domain Control Validated) does not match the expected hostname (eu-west791.discord.media)
Closing connection and attempting to reconnect.
My bots are running on a Raspberry Pi 3.
I haven't changed the code for about a week and after the last update the bots still worked. I haven't updated any software on my pi for a fair amount of time.
My best guess was restarting the pi and voilá, it worked. For about 10 minutes (I'm not exactly sure about this number) until it broke again.
After that I updated both JDA and Lavaplayer to the latest stable versions available (JDA to 1.8.3_464 and Lavaplayer to 1.3.18).
No changes, the problem still existed.
Then I tried updating java on my pi from
java version "1.8.0_65"
Java(TM) SE Runtime Environment (build 1.8.0_65-b17)
Java HotSpot(TM) Client VM (build 25.65-b01, mixed mode)
to
openjdk version "9-Raspbian"
OpenJDK Runtime Environment (build 9-Raspbian+0-9b181-4bpo9rpt1)
OpenJDK Server VM (build 9-Raspbian+0-9b181-4bpo9rpt1, mixed mode)
(I hope a didn't frick it up. I'm still relatively new to working with rpis and Ubuntu in general.)
Still not working.
(EDIT: The problem is definitely the pi, since I started the pi on my windows laptop and it worked fine.)
I would be glad if someone could explain to me what exactly went wrong with my bots and would show me a solution (I'm a beginner, if you provide a tutorial or explain something step-by-step I would be very pleased.)
Thanks in advance.
Related
I'm running Alpine 3.12 with the latest 64-bit kernel. Installed VS extension for remote server ssh connections and by trying to connect, I see that the process has downloaded a folder ".vscode-server" on my remote server, which means that the connection happened, but after loading for some time I receive this message "The remote host may not meet VS Code Server's prerequisites for glibc and libstdc++". I did some googling on this, and I see that a few people were having trouble as they didn't have enough space on their server storage to install some libraries, but this is not the case for me. The extension itself provides me with this link https://code.visualstudio.com/docs/remote/linux#_remote-host-container-wsl-linux-prerequisites explaining that there could be problems for Alpine based systems, but it should work anyways, but I can't quite find the problem. Maybe someone has faced this issue and can guide me to the solution?
I have MyEclipse Version: 2015 Stable 2.0. When i try to open WebBrowser on any site.. the following appears:
This document cannot be displayed while offline. To go online, uncheck Work Offline from the File menu.
I tried with
-vmargs
-Djava.net.preferIPv4Stack=true
and shows nothing..
java version "1.7.0_79"
OpenJDK Runtime Environment (IcedTea 2.5.6) (7u79-2.5.6-0ubuntu1.14.04.1)
OpenJDK Client VM (build 24.79-b02, mixed mode, sharing)
I had to change settings
image settings
any ideas
appreciate your vote for reputation
This seems to be a problem with certain Linux systems, where an internal browser view isn't available. See here for the requirements to run an internal browser.
If the requirements can't be met then you'd need to test on an external browser. The MyEclipse delivery log seems to be a related problem but can be viewed here (for the stable stream) or here (for the CI - continuous integration - stream).
I am working on my own, learning about Java servlets and JSPs. My machine configuration as follows is from NetBeans' About page.
Product Version: NetBeans IDE 8.0.1 (Build 201408251540)
Updates: NetBeans IDE is updated to version NetBeans 8.0.1 Patch 1.1
Java: 1.8.0_20; Java HotSpot(TM) 64-Bit Server VM 25.20-b23
Runtime: Java(TM) SE Runtime Environment 1.8.0_20-b26
System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
Tomcat 8.0.14 for Windows x64 is also installed as the web server.
I created a tiny web app yesterday, which was working as expected. When I went to the next exercise in the book, it was necessary to install MySQL. That seemed pretty straightforward, but alas, the install ran into a couple of problems. Unfortunately, I had not created a restore point right before that attempt, so I went back to the restore point created before the Tomcat install.
I re-installed Tomcat, and as a sanity check, started it, started NetBeans, tried to the run the tiny web app and after removing the server and re-adding it (because I got an error about the server) in NetBeans, got a message that I needed to set the build.dir.
For a tiny app, this is just annoying, but when working on a large app, it would be nice to avoid this problem. Another book author supplied app was working before, and is still working so...
Here are my questions:
1) Why/how would simply re-installing Tomcat cause a break in something that was working?
2) It seems as if the build.dir is set in build-impl.dir (in the app that is working) with a statement like (the opening and closing tags are missing so the statements would appear):
property location="${build.dir}/empty" name="empty.dir"
One post I read somewhere said that the above statement should be before the:
fail unless="build.dir">Must set build.dir
3) How/where is this build.dir set during the creation of a NetBeans web app? Is there some dialog box that I'm not completing correctly? If I miss it, is there a way to get back to it after the app gets "confused"?
Thanks in advance for any help on this.
I just installed GitHub for Windows on my 64-bit Windows 7 computer, and the GitHub always get the following two errors complaining about two components are 16-bit applications incompatible with the 64-bit Windows OS. The two error messages are attached below.
I think there should be many users running GitHub on 64-bit Windows, so could someone please provide some workaround for this issue?
1) The first error
Unsupported 16-Bit Application
The program or feature "\??\C:\Users\mikez\AppData\Local\GitHub\PortableGit_054f2e797ebafd44a30203088cd3d58663c627ef\bin\ssh-agent.exe" cannot start or run due to incompatibity with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available.
2) The second error
Unsupported 16-Bit Application
The program or feature "\??\C:\Users\mikez\AppData\Local\GitHub\PortableGit_054f2e797ebafd44a30203088cd3d58663c627ef\bin\ssh-keygen.exe" cannot start or run due to incompatibity with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available.
Give msysgit a try. I heard that this works fine.
I have a very strange issue that I'm hoping someone can help me with. I have various installations of Eclipse on my development machine at work. The one I primarily use is Weblogic WorkSpace Studio 10.2. This installation, along with a few Pulse installations I have set up works fine when I'm logged into my computer physically.
However, when I try to log into the computer using Microsoft's Remote Desktop Connection utility I get an error stating: "Could not create Java virtual machine." and then I get the lovely Eclipse error box which I personally can gather almost nothing from.
Even if you don't have the solution, any help would be greatly appreciated.
Justin
What ended up working for me was the memory settings for the JVM. Apparently the remote desktop connection, or some other setting in Windows, blocks off a fairly large amount of space. By reducing the heap size allocation for the JVM during Eclipse and server start-up I was able to get this working. As a side note, I had PLENTY of space that windows could have used, so I don't think blankly adding more memory would necessarily solve the issue. If you find another solution, please let me know.
• We came across an issue when user RDC’s to a remote system where the OS is Windows 10 and has a running Eclipse instance, the Eclipse instance terminates
• Eclipse is one of the IDE’s for Java
• The issue is because of Windows 10 Exploit protection
• Pre-requisite: You will need Administrative permissions for executing the below
• Navigate to Settings -> Update & Security -> Windows Security -> App & Browser Control -> Exploit Protection Settings
• Add the program to exclude as below
P.s. As of Window 10 1909 MS security advisory mentions we can disable some exploit protections by default.
Perhaps it is permission related. take a look at similar issue that symantec has:
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/8ea1593f1d1fcee68025759a003d8403?OpenDocument
Try to see if you have same patches installed that causes the security issue. Also refer to application log to see if there is a more specific error. Good luck :)
I think issue happens due to Windows, not Eclipse nor JVM. There is still open Bug report on the Eclipse side and one of the comments state that Microsoft is working on the issue.
I have tried Windows Remote Desktop-ing into my dev machine at work (which had only one version of eclipse installed on it). I had no troubles.
Is it possible that your problems stem from multiple versions of eclipse running at the same time?
Also, have you tried a fresh install of eclipse on your dev machine?
If the above two suggestions don't work, then the only thing that I can think of is what Mohammad said: you might need to check your permissions.
I would check the system log if I were you: Start > run > eventvwr
The first thing to look at is the .log file which is in your eclipse's metadata folder (found in your workspace at $WORKSPACE_ROOT/.metadata/.log). If you post the stack trace that it generates upon initialization, we can give a definitive answer.
I am now experiencing this in Eclipse (the Oxygen release and Java 1.8.0_181). I previously had the same problem with another Java-based program (Oxygen XML/XSL editor - the product name is coincidentally the same as the Eclipse version). Last year the Oxygen support team answered that it may be a known problem in Java.
Even without seeing a crash report, considering your sequence of
events, this seems like a known common cause of crash for the Java
runtime. Keeping Oxygen/Java running for a long time, until the screen
or video card enters sleep then connecting/disconnecting
screens/projectors or connecting/disconnecting RDP can trigger a crash
in the Java runtime. We keep updating the Java runtime (JRE) with each
new version of Oxygen, but so far the issue has not been resolved in
newer versions of the JRE.
e.g. Java VM logged issue:
https://bugs.openjdk.java.net/browse/JDK-8153389