java.lang.Exception: Server Key is empty, this is insecure, check config.

GitHub | beeedee | 3 months ago
  1. 0

    java.lang.Exception

    GitHub | 3 months ago | beeedee
    java.lang.Exception: Server Key is empty, this is insecure, check config.
  2. 0

    Cannot see Google Maps in signed application

    Stack Overflow | 3 years ago | suja
    java.lang.Exception: Keystore file exists, but is empty: C:\Users\PC8\De sktop\Sign Key
  3. 0

    Java Server Toolkit and services ...

    Google Groups | 2 decades ago | ash
    java.lang.Exception: Server EchoServiceHandler has no property directory. Please check that the server name is correct.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    We've recently upgraded to Hudson ver. 1.358 and upgraded our Hudson plugins (CheckStyle, FindBugs, Emma, etc). Since taking the upgrades, we're noticing that slave agents are terminating after building our 'code checking' project, which consists of: - CheckStyle (now on 3.6) - FindBugs (now on 4.8) - Emma coverage reports (now on 1.20) We've narrowed the problem down to the Emma plugin; the Hudson slave does not terminate when I deactivate the "Record Emma coverage report" step in my Hudson project. When I re-enable the Emma coverage report step, the Hudson slave starts dying again. Slave agents are happily building our other builds (junit tests, end-2-end tests). Here's some logging below: (please let me know, if you need more details) ============================== When this happens, his is the logging we see on the: 1) Hudson server log file: 17-May-2010 12:49:29 hudson.TcpSlaveAgentListener$ConnectionHandler run INFO: Accepted connection #36 from /xx.xx.xx.xx:38048 17-May-2010 12:49:29 hudson.TcpSlaveAgentListener$ConnectionHandler error WARNING: Connection #36 is aborted: cislave3 is already connected to this master. Rejecting this connection. 2) Hudson slave agent log file: 17-May-2010 12:49:19 hudson.remoting.Engine$2 onDead INFO: Ping failed. Terminating the socket. 17-May-2010 12:49:19 hudson.remoting.Channel$ReaderThread run SEVERE: I/O error in channel channel java.net.SocketException: Socket closed at java.net.SocketInputStream.read(SocketInputStream.java:162) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2542) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2552) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at hudson.remoting.Channel$ReaderThread.run(Channel.java:856) 17-May-2010 12:49:19 hudson.remoting.jnlp.Main$CuiListener status INFO: Terminated 17-May-2010 12:49:29 hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among [http://ccmain.xx.com:8080/] 17-May-2010 12:49:29 hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to ccmain.xx.com:44477 17-May-2010 12:49:29 hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking 17-May-2010 12:49:29 hudson.remoting.jnlp.Main$CuiListener error SEVERE: The server rejected the connection: cislave3 is already connected to this master. Rejecting this connection. java.lang.Exception: The server rejected the connection: cislave3 is already connected to this master. Rejecting this connection. at hudson.remoting.Engine.run(Engine.java:191)

    Jenkins JIRA | 7 years ago | saipatel
    java.lang.Exception: The server rejected the connection: cislave3 is already connected to this master. Rejecting this connection.
  6. 0

    Hello, I've vSphere slaves witch are "reverted" to a snapshot for each build. Those slaves are used to test the installation of our products. Some builds wait a long time at the beginning of the build before to crash with the following message: Remote build on slave-seven64 (x86_64 seven uiTest java7 autoRestored win x86)FATAL: channel is already closed hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:541) at hudson.remoting.Request.call(Request.java:129) at hudson.remoting.Channel.call(Channel.java:739) at hudson.EnvVars.getRemote(EnvVars.java:404) at hudson.model.Computer.getEnvironment(Computer.java:927) at jenkins.model.CoreEnvironmentContributor.buildEnvironmentFor(CoreEnvironmentContributor.java:29) at hudson.model.Run.getEnvironment(Run.java:2248) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:905) at hudson.matrix.MatrixRun$MatrixRunExecution.decideWorkspace(MatrixRun.java:175) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:517) at hudson.model.Run.execute(Run.java:1740) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.io.IOException at hudson.remoting.Channel.close(Channel.java:1027) at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:110) at hudson.remoting.PingThread.ping(PingThread.java:120) at hudson.remoting.PingThread.run(PingThread.java:81) Caused by: java.util.concurrent.TimeoutException: Ping started on 1411030796694 hasn't completed at 1411031036694 ... 2 more The problem happens very often but it is not 100% reproducible. I've this problem with 2 different sets of computers. My slave configuration was working properly in a not so far past (about 6 months), but I don't know at witch jenkins update the problem appeared. Sometimes a blocked build is running in slave (according to the Jenkins UI) whereas the computer hosting the slave is down (according to the "vSphere Client"). I also found the following message in a log of a running slave on which a build was waiting before to crash: sept. 18, 2014 3:30:59 PM hudson.remoting.jnlp.Main$CuiListener error SEVERE: The server rejected the connection: ntedtop-seven64 is already connected to this master. Rejecting this connection. java.lang.Exception: The server rejected the connection: ntedtop-seven64 is already connected to this master. Rejecting this connection. at hudson.remoting.Engine.onConnectionRejected(Engine.java:286) at hudson.remoting.Engine.run(Engine.java:261) Is there a workaround for this problem. Regards, Grégoire

    Jenkins JIRA | 2 years ago | Grégoire Dupé
    java.lang.Exception: The server rejected the connection: ntedtop-seven64 is already connected to this master. Rejecting this connection.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.Exception

      Server Key is empty, this is insecure, check config.

      at com.plugish.woominecraft.WooMinecraft.validateConfig()
    2. com.plugish.woominecraft
      WooCommand.onCommand
      1. com.plugish.woominecraft.WooMinecraft.validateConfig(WooMinecraft.java:103)
      2. com.plugish.woominecraft.WooMinecraft.check(WooMinecraft.java:117)
      3. com.plugish.woominecraft.Commands.WooCommand.onCommand(WooCommand.java:31)
      3 frames
    3. Bukkit
      SimpleCommandMap.dispatch
      1. org.bukkit.command.PluginCommand.execute(PluginCommand.java:44)
      2. org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:140)
      2 frames
    4. org.bukkit.craftbukkit
      CraftServer.dispatchServerCommand
      1. org.bukkit.craftbukkit.v1_10_R1.CraftServer.dispatchCommand(CraftServer.java:626)
      2. org.bukkit.craftbukkit.v1_10_R1.CraftServer.dispatchServerCommand(CraftServer.java:612)
      2 frames
    5. net.minecraft.server
      MinecraftServer.run
      1. net.minecraft.server.v1_10_R1.DedicatedServer.aL(DedicatedServer.java:398)
      2. net.minecraft.server.v1_10_R1.DedicatedServer.D(DedicatedServer.java:362)
      3. net.minecraft.server.v1_10_R1.MinecraftServer.C(MinecraftServer.java:643)
      4. net.minecraft.server.v1_10_R1.MinecraftServer.run(MinecraftServer.java:547)
      4 frames
    6. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:745)
      1 frame