LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only

  • 1.  Can't Connect to LAE Server

    Employee
    Posted 10-23-2014 09:34

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Leaner

    Hello All,

    I have wrestled all day with trying to connect from a Windows 7 BRE installation to a Linux LAE Server.

    The port used by LAE is 7721, so on the Linux Server the iptables are set to:
    $ sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:http-alt
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:7721
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:ssh
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:https
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:http
ACCEPT     udp  --  anywhere             anywhere             udp dpt:7721

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
    Still BRE tells me:
    1.png

    I press "Yes" and I get:
    2.png

    These are my farm settings:
    3.jpg

    So when I use nmap from a host to the server:
    $ nmap -A -T5 -v -p 7721 192.168.31.40

Starting Nmap 6.40 ( http://nmap.org ) at 2014-10-23 17:22 BST
NSE: Loaded 110 scripts for scanning.
NSE: Script Pre-scanning.
Initiating Ping Scan at 17:22
Scanning 192.168.31.40 [2 ports]
Completed Ping Scan at 17:22, 0.00s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 17:22
Completed Parallel DNS resolution of 1 host. at 17:22, 0.00s elapsed
Initiating Connect Scan at 17:22
Scanning dhouse.leaner.local (192.168.31.40) [1 port]
Completed Connect Scan at 17:22, 0.00s elapsed (1 total ports)
Initiating Service scan at 17:22
NSE: Script scanning 192.168.31.40.
Initiating NSE at 17:22
Completed NSE at 17:22, 0.00s elapsed
Nmap scan report for dhouse.leaner.local (192.168.31.40)
Host is up (0.00069s latency).
PORT     STATE  SERVICE VERSION
7721/tcp closed unknown

NSE: Script Post-scanning.
Read data files from: /usr/bin/../share/nmap
Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 0.23 seconds
    And when I try telnet from a host to the server:
    >telnet 192.168.31.40 7721
Connecting To 192.168.31.40...Could not open connection to the host, on port 7721: Connect failed
    Output from BRE's console:
    BRE is controller
Servers:
       192.168.31.40:7721 (1)
17:48:35 - Connecting to license control thread 192.168.31.40:7721#0
Connect failed 192.168.31.40:7721#LicenseControl
17:48:39 - Connecting to license control thread 192.168.31.40:7721#0
Connect failed 192.168.31.40:7721#LicenseControl
    On the Linux server, netstat -a:
    tcp6       0      0 Dhouse:7721             [::]:*                  LISTEN
    • On the Windows machine I disabled the firewall completely
    • No additional firewall/virus enabled on the Windows machine
    • LAE server is listening on port 7721 on the Linux server correctly
    • Same problem from other computers
    • tracert has only 1 hop (direct) so nothing between them, only a switch
    • Nothing on any of the LAE logs
    • Restarted both machines several times

    Can anyone please help? I am totally out of ideas.


  • 2.  RE: Can't Connect to LAE Server

    Employee
    Posted 10-23-2014 10:53

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: prashanth

    Not sure if this will help but confirm that:

    1. You are able to ping from the desktop to the server IP address and get a reply from the server.

    2. Run a 'ps -eaf | grep -i lae' command on the server and confirm that you can see something like this:
    laeadmn 6419 1 1 Sep30 ? 05:59:50 java -classpath /u01/app/brain/lavastorm/4.6.1/lib/java:/u01/app/brain/lavastorm/4.6.1/lib/java/liblmxjava.jar:/u01/app/brain/lavastorm/4.6.1/lib/java/log4j.jar:/u01/app/brain/lavastorm/4.6.1/lib/java/lsCore.jar:/u01/app/brain/lavastorm/4.6.1/lib/java/lae.jar: -Djava.ext.dirs=/u01/app/brain/lavastorm/4.6.1/lib/java/ext:/u01/app/brain/java/jdk1.7.0_40/jre/lib/ext -d64 -server -Xmx1024m com.lavastorm.brain.server.Server

    3. You have installed compatible versions of both desktop client and server. Something like a 4.6.1 on both etc.

    4. Any reason you are using only 1 thread? I typically use 6-8 threads for executing graphs but that is secondary.


    -Prashanth


  • 3.  RE: Can't Connect to LAE Server

    Employee
    Posted 10-24-2014 01:38

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Leaner

    Hi Prashanth,

    1. Yes, I can ping
    2. Yes, application is running
    3. They are both 5.0
    4. Changed it to 4 for now

    Any ideas?


  • 4.  RE: Can't Connect to LAE Server

    Employee
    Posted 10-24-2014 04:41

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: ejones

    When I see that type of error message in BRE, I press the F8 key (same as View -> Toggle Log) and look at what I'm seeing in the log window. I can then look through the errors and find out whether it is a network problem like you've investigated very well, or if it is a problem or if BRE is able to communicate with the LAE server and something else is the problem.


  • 5.  RE: Can't Connect to LAE Server

    Employee
    Posted 10-24-2014 04:56

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Leaner

    Hi Ejones,

    I already posted BRE Console's output in my original post under "Output from BRE's console:"

    UPDATE:
    I did a clean Debian install and followed the installation instructions step by step... no change, problem is the same. However, when I start the server (as stated exactly in the instructions), I get this:
    pablo@dwhouse:~$ sudo /home/pablo/Lavastorm/LAE5.0/bin/laeServer > /home/pablo/Lavastorm/LAE5.0/laeServer.log 2>&1 &
[3] 2173
pablo@dwhouse:~$ sudo /home/pablo/Lavastorm/LAE5.0/bin/startDatabase &
[4] 2175
[3]   Exit 1                  sudo /home/pablo/Lavastorm/LAE5.0/bin/laeServer > /home/pablo/Lavastorm/LAE5.0/laeServer.log 2>&1
pablo@dwhouse:~$ sudo /home/pablo/Lavastorm/LAE5.0/bin/startLavastormJettyServer &
[5] 2203
[4]   Exit 1                  sudo /home/pablo/Lavastorm/LAE5.0/bin/startDatabase
    Is that supposed to say 'exit'?

    Thanks again.


  • 6.  RE: Can't Connect to LAE Server

    Employee
    Posted 10-24-2014 06:27

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: ejones

    Thanks, I missed the Console output when I was looking for that information. Clearly BRE is not finding an LAE server to communicate with.

    So, to answer the next question, no you shouldn't see the "Exit 1" happen. I'm not very familiar with managing subprocesses in bash, but I believe the output you show on line 2 indicates that you started the LAE server and it was created as subprocess 3. Then on the 5th line it begins with the "[3]" indicating that the output that follows comes as a result of subprocess 3. The next part is "Exit 1" which means that the process finished running and has an exit code of 1. And, if the server isn't running, you would definitely not be able to connect to it.

    Instead, you should continue to see the LAE server process running using "ps -ef | grep brain.server".

    I have not heard of running LAE under Debian. I know it runs under RedHat and Centos.


  • 7.  RE: Can't Connect to LAE Server

    Employee
    Posted 10-24-2014 13:56

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: prashanth

    It is likely not a network or connection issue with the client and server then since the LAE server process dies with an error status (Exit 1) and the client is not able to make a connection to the server. It is just that this version seems not supported in Debian Linux as mentioned.

    This is the list of supported OS environments for 5.0:

    Supported Operating Systems

    LAE 5.0 is supported on the following operating systems:

    . For the BRE client and Lavastorm Desktop:
    o NEW! Windows 8 (32-bit and 64-bit)
    o Windows 7 (32-bit and 64-bit)—note that BRE and Desktop are 32-bit
    applications that run on either 32-bit or 64-bit versions of Windows 7
    o Windows XP (32-bit) with Service Pack 3 or higher.

    . For the LAE Server:
    Linux (x86; 32-bit and 64-bit)
    o Red Hat Enterprise Linux 5
    o Red Hat Enterprise Linux 6
    o Oracle Enterprise Linux 5
    o Oracle Enterprise Linux 6

    Oracle Solaris
    NEW! Solaris 11 (SPARC; 64-bit)
    Solaris 10 (SPARC; 64-bit)
    NEW! Windows Server 2008


    Prashanth


  • 8.  RE: Can't Connect to LAE Server

    Employee
    Posted 10-24-2014 14:39

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: stonysmith

    You need to check your log files.

    LAE: ..../log/server/server.7721.log
    Web: ..../jetty/logs/2014_10_24-113200725.start.log
    DB: ..../h2/log/dbLog.log

    There are any one of a number of reasons the server won't start (giving you the Exit 1 message), including missing temp directories, invalid trust configuration, network issues. We'd need to look thru the log(s) to see if anything is being recorded.

    ===
    I notice that your netstat says that you're using TCPIP v6.. I've had better luck with TCPIP v4
    Is your machine actually named "Dhouse"? I've often found that the netstat reports the actual IP address rather than a symbolic name.
    I've had a number of installations (OS versions) that required some kind of change to /etc/hosts

    ===
    There is also the condition where some kind of corporate firewall is blocking access to port 7721 regardless of what your Windows firewall settings are.
    Have you checked to see that linux itself is not blocking the ports?
    Once you can do ps -ef and see the LAE task running, then you can attempt connecting to that port with telnet (from windows)


    telnet dhouse 7721
    If it says "could not open connection on the host on port 7721: connect failed" the the LAE server task is either not running, or the port is blocked.
    If you DO connect, you'll get a blank window.. nothing exciting to see or do, but it won't give you and error message.


  • 9.  RE: Can't Connect to LAE Server

    Employee
    Posted 10-27-2014 03:43

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Leaner

    Shot-out to Suki and Sadat for solving the issue.

    Problems:
    1. I was never provided an installation guide (LAE 5.0 Enterprise Installation Guide.pdf), or knew one existed. Once it was provided I was able to install it as it needs to be installed(i.e. unique user for the server install, loading the profile, startup order, laeConfig Utility, etc).
    2. As usual, I sudo-ed the installation which according to the installation guide, you should not. This made the logs unusable by the LAE server even if it was started with sudo. As the services started, they died seconds later.

    Thank you to everyone who contributed.

    Notes:
    - Java errors were very helpful.
    - Even if iptables has the port open, telnet does not verify the port being open if no one is listening.
    - There should be no need to even modify the iptables as it accepts all established connections by default.
    - Adding a rule on Windows Firewall is necessary if it does not automatically ask you anyways.


  • 10.  RE: Can't Connect to LAE Server

    Employee
    Posted 10-27-2014 05:18

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: ejones

    Thank you Leaner,
    I'm so glad you have it working now. Thanks for closing the loop and pointing out the bits of information that were most helpful in solving this.