• State Verified Answer
  • Replies 17 replies
  • Answers 1 answer
  • Subscribers 9 subscribers
  • Views 14733 views
  • Users 0 members are here
Related Discussions
Home » Discussions » General

Data-Server times out absolutely every time I try to start it, yet is still running

Dave Lewis
Certified Lead Developer

I'm running Quick Start local installation guide for Windows using Jboss for Appian 18.1

All the validations pan out, everything seems to work, but data-server always returns this error.

 

0 [main] INFO com.appian.data.TopologyFactory - Loading topology C:\appian181\appian\data-server\bin\..\conf\appian-topology.xml
347 [main] INFO com.appian.data.server.config.CustomPropertiesConfiguration - Configuration file custom.properties was loaded successfully. (Reload check = 30000 ms)
363 [main] INFO com.appian.data.server.Watchdog - Initializing log4j (processName=wd-5400, logsDir=C:\appian181\appian\data-server\bin\..\..\logs\data-server) from C:\appian181\appian\data-server\bin\..\conf\log4j.properties
2018-05-07 18:39:37,256 wd-5400 [main] INFO com.appian.data.server.JvmStarter - Starting JVM: C:\Program Files\Java\jdk1.8.0_171\jre\bin\java.exe -server -Duser.timezone=GMT -Xms64m -Xmx128m -Dds.home=C:\appian181\appian\data-server\bin\.. -cp C:\appian181\appian\data-server\bin\..\lib\appian-data-server-classpath-0.72.6.jar com.appian.data.server.Watchdog -f
2018-05-07 18:40:37,820 wd-5400 [main] ERROR com.appian.data.server.Watchdog - Shutting down with exit code 1...
com.appian.data.server.UnrecoverableError: Established WebSocket connection but failed to receive heartbeat from data-server:5400.
at com.appian.data.server.HeartbeatListener$SyncHeartbeatListenerBuilder.create(HeartbeatListener.java:157)
at com.appian.data.server.JvmStarter.startSync(JvmStarter.java:45)
at com.appian.data.server.Watchdog.main(Watchdog.java:697)
Caused by: java.util.concurrent.TimeoutException: Timeout waiting for task.
at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:269)
at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:96)
at com.google.common.util.concurrent.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:173)
at com.appian.data.server.HeartbeatListener$SyncHeartbeatListenerBuilder.create(HeartbeatListener.java:131)
... 2 more

 

I have seen absolutely NO posts about Heartbeat or HeartbeatListener or Watchdog.

 

I have verified PATH system variables are correct (%JAVA HOME%).

I have verified <REPO HOME> custom.properties.dev file multiple times.

I have verified <REPO HOME> \jboss\  appian-mysql-ds.xml.dev multiple times.

I have verified that the name of the datasource is correct and logged into said datasource using MySQL workbench to confirm.

I have verified numerous times that I've removed everything about cookies from web.war\WEB-INF\web.xml numerous times.

I have double-checked to delete everything from every path related to appian installation which has a .failed, .undeployed, or .isdeploying extension, even from my entire computer between each attempt.

I always shut down everything in the correct order and check to make sure no java is running at all before trying again.  I've even rebooted my machine to make sure there wasn't an existing jboss execution still running in the background.

 

What else could it possibly be?

 

Did I mention that I never get Jboss to run without error as well?  I don't know if it's related or not, so I'll ask a separate question why JBoss never runs properly.

  Discussion posts and replies are publicly visible

Parents Reply Children
  • 0
    Certified Lead Developer
     in reply to Justin Watts
    I renamed the FQDN from "localhost" back to what it was before, and nearly all the services came up PRIMARY mode. I shut down one straggler, started the one straggler up again, used status.bat to confirm all are up and running in PRIMARY mode, same error.

    I'm not being refused connection to 5400 now, I'm all the way back to having it timeout because it can't find heartbeat.

    Interesting thing, it times out, but it says it's running. Stop.bat on the data-server works fine. A few seconds and it's down like it never had an error.

    When I run netstat with all the services and the data server up, it still shows absolutely nothing about port 5400.
  • 0
    Certified Lead Developer
     in reply to Dave Lewis
    And I do have k4.lic at C:\appian181\repo\appian\data-server\engine\bin\q\w64

    This is Windows 10, 64 bit OS.
  • 0
    Certified Lead Developer
     in reply to Dave Lewis
    What do the data-server logs say? Maybe there is something useful in there
  • 0
    Certified Lead Developer
     in reply to Dave Lewis
    Status.bat in data-server folder does nothing. Just newline.
  • 0
    Certified Lead Developer
     in reply to Dave Lewis
    Where are the data-server logs? I've looked through the entire data-server folder and every subfolder and found no logs.
  • 0
    Certified Lead Developer
     in reply to Dave Lewis
    Under the main logs folder (docs.appian.com/.../Logging.html

    So something like ../appian/logs/data-server
  • 0
    A Score Level 1
     in reply to Dave Lewis
    So is the server running? But you are still worried about your license?
  • 0
    Certified Lead Developer
     in reply to Dave Lewis
    Found them.

    If I use "localhost" I get this error:

    0 [main] INFO com.appian.data.TopologyFactory - Loading topology C:\appian181\appian\data-server\bin\..\conf\appian-topology.xml
    301 [main] INFO com.appian.data.server.config.CustomPropertiesConfiguration - Configuration file custom.properties does not exist. Default settings will be used.
    314 [main] INFO com.appian.data.server.Watchdog - Initializing log4j (processName=wd-5400, logsDir=C:\appian181\appian\data-server\bin\..\..\logs\data-server) from C:\appian181\appian\data-server\bin\..\conf\log4j.properties
    2018-05-07 14:45:28,514 wd-5400 [main] INFO com.appian.data.server.replication.TopicManager - Connecting to Zookeeper: localhost:2181
    2018-05-07 14:45:59,639 wd-5400 [main] ERROR com.appian.data.server.Watchdog - Shutting down with exit code 1...

    If I use the other FQDN I get this error:

    0 [main] INFO com.appian.data.TopologyFactory - Loading topology C:\appian181\appian\data-server\bin\..\conf\appian-topology.xml
    293 [main] INFO com.appian.data.server.config.CustomPropertiesConfiguration - Configuration file custom.properties does not exist. Default settings will be used.
    306 [main] INFO com.appian.data.server.Watchdog - Initializing log4j (processName=wd-5400, logsDir=C:\appian181\appian\data-server\bin\..\..\logs\data-server) from C:\appian181\appian\data-server\bin\..\conf\log4j.properties
    2018-05-07 15:03:48,850 wd-5400 [main] INFO com.appian.data.server.replication.TopicManager - Connecting to Zookeeper: localhost:2181
    2018-05-07 15:03:49,185 wd-5400 [main] INFO com.appian.data.server.replication.TopicManager - Connecting to Zookeeper: localhost:2181
    2018-05-07 15:03:56,011 wd-5400 [main] INFO com.appian.data.server.Watchdog - Data Server is not configured to run on 'DESKTOP-063AN1L' according to the topology. It is configured to run on 'data-server'. DataServer is shutting down.
  • 0
    Certified Lead Developer
     in reply to Dave Lewis
    this is in the wd-5400 log

    2018-05-07 14:18:08,187 [main] INFO com.appian.data.server.JvmStarter - Starting JVM: C:\Program Files\Java\jdk1.8.0_171\jre\bin\java.exe -server -Duser.timezone=GMT -Xms64m -Xmx128m -Dds.home=C:\appian181\appian\data-server\bin\.. -cp C:\appian181\appian\data-server\bin\..\lib\appian-data-server-classpath-0.72.6.jar com.appian.data.server.Watchdog -f
    2018-05-07 14:18:09,641 [main] INFO com.appian.data.server.replication.TopicManager - Connecting to Zookeeper: localhost:2181
    2018-05-07 14:18:40,750 [main] ERROR com.appian.data.server.Watchdog - Shutting down with exit code 1...

    So when I use "localhost" it JUST shuts down with no explanation why it would want to do that. Exit code 1, whatever that is.
  • 0
    Certified Lead Developer
     in reply to Dave Lewis
    Fixed it!

    In the appian.topology.xml file i changed data server host to "localhost", then changed the FQDN in custom.properties to "localhost" as well, now data-server starts.

    I still don't have appian because of jboss errors, but we'll deal with that later.
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.