Docs‎ > ‎Espresso Appliance‎ > ‎

Troubleshooting

The Espresso Logic Appliance virtual machine does not have an IP address after starting

After the Espresso Logic Appliance virtual machine has started the VMware Console's window will show the Appliance IP, such as 192.168.0.127 or whatever DHCP address your virtual machine has received from your network like the screen shot below:

if instead you see "Unable to get a valid DHCP address, please visit"...


Then VMware was not able to provide a DHCP address to the appliance. There can be multiple reasons for this:

Log into the Espresso Logic Appliance Virtual Machine's Operating System
First try:

# sudo ifup eth0

Device eth0 does not seem to be present, delaying initialization

If you see message "Device eth0 does not seem to be present, delaying initialization" what’s happening here is that VMware applied a new MAC Address to your network interfaces but didn't update the linux configuration files to mirror these changes and so the linux kernel can’t find or start the interface that matches it’s configuration (with the old MAC Address) and it finds a new interface (the new MAC Address) that it has no configuration information for. The result is that only your networking service can only start the loopback networking interface and eth0 is dead.

So here’s how to fix it:
Remove the kernel’s networking interface rules file so that it can be regenerated

# sudo rm ‐f /etc/udev/rules.d/70‐persistent‐net.rules
# sudo reboot 

If after rebooting, the problem persists: 

VMware (Player, Workstation and Fusion) supports three different networking strategies:
 Type Behavior
Bridged Bridged mode replicates another node on the physical network and your Virtual Machine will receive it's own unique IP address if DHCP is enabled in the network.
Network Address Translation (NAT) just like your home network with a wireless router, the VM will be assigned in a separate subnet, like 192.168.6.1 is your host computer, and VM is 192.168.6.3, then your Virtual Machine can access outside network like your host, but no outside access to your Virtual Machine  directly, it's protected.
Host only networking The Virtual Machine will be assigned one IP, but it's only accessible by the computer that the Virtual Machine is running on. No other computers can access it.

To change VMware network strategy:
  • Shut / power down the Espresso Logic Appliance Virtual Machine
  • In VMware Player for example
    • Click 'Player'
    • Click 'Manage'
    • Click 'Virtual Machine Settings'
    • Change 'Network Adapter' from 'NAT' to 'Bridged' (if it was already in 'Bridged' mode, try NAT)
A "Bridged" network strategy is the most flexible.

TCP/IP connection to the host database has failed 


Log into the Espresso Logic Appliance Virtual Machine's Operating System
  • Is your Domain Network Service (DNS) resolving hostnames properly?
    • ping google.com
      should see something like this:

      ping www.google.com (74.125.239.147): 56 data bytes
      64 bytes from iad23s08-in-f14.1e100.net (74.125.228.110): icmp_seq=1 ttl=46 time=1.33 ms

    • if this fails, try ping 74.125.239.147

    • if both fail try traceroute google.com
      You should see something like this or see where a firewall is blocking you:

      traceroute to google.com (74.125.228.105), 30 hops max, 60 byte packets

       1  100.100.48.193 (100.100.48.193)  0.984 ms  2.019 ms  2.325 ms
       2  100.88.105.3 (100.88.105.3)  0.782 ms  0.800 ms 100.88.105.0 (100.88.105.0)  0.865 ms
       3  100.88.105.33 (100.88.105.33)  0.773 ms 100.88.105.26 (100.88.105.26)  0.933 ms 100.88.105.32 (100.88.105.32)  0.998 ms
       4  * * *
       5  * * *
       6  100.67.134.3 (100.67.134.3)  2.561 ms 100.67.133.51 (100.67.133.51)  4.934 ms 100.67.130.27 (100.67.130.27)  16.338 ms
       7  100.67.143.90 (100.67.143.90)  3.602 ms 100.67.129.192 (100.67.129.192)  5.634 ms 100.67.142.8 (100.67.142.8)  0.846 ms
       8  100.67.159.128 (100.67.159.128)  0.579 ms 100.67.159.172 (100.67.159.172)  0.535 ms 100.67.159.208 (100.67.159.208)  0.687 ms
      9  100.64.38.29 (100.64.38.29)  1.437 ms 100.64.39.209 (100.64.39.209)  11.382 ms 100.64.38.11 (100.64.38.11)  2.234 ms|
      10  216.182.224.92 (216.182.224.92)  1.673 ms 216.182.224.78 (216.182.224.78)  1.743 ms 216.182.224.94 (216.182.224.94)  1.942 ms
      11  100.64.14.209 (100.64.14.209)  15.061 ms 100.64.8.121 (100.64.8.121)  1.172 ms 100.64.8.165 (100.64.8.165)  7.977 m
      12  100.64.0.100 (100.64.0.100)  1.029 ms 100.64.0.174 (100.64.0.174)  1.159 ms 100.64.0.218 (100.64.0.218)  1.417 ms
      13  100.64.16.17 (100.64.16.17)  0.819 ms 100.64.16.217 (100.64.16.217)  0.661 ms 100.64.16.1 (100.64.16.1)  0.863 ms
      14  205.251.245.64 (205.251.245.64)  0.925 ms 72.21.222.148 (72.21.222.148)  0.863 ms 205.251.245.67 (205.251.245.67)  0.504 ms
      15  72.21.222.34 (72.21.222.34)  0.792 ms 72.21.220.36 (72.21.220.36)  1.286 ms 72.21.222.148 (72.21.222.148)  0.987 ms
      16  72.14.215.157 (72.14.215.157)  1.051 ms  1.076 ms  0.935 ms
      17  72.14.215.157 (72.14.215.157)  0.924 ms  0.851 ms 209.85.252.80 (209.85.252.80)  16.425 ms
      18  209.85.252.80 (209.85.252.80)  1.074 ms 72.14.238.253 (72.14.238.253)  1.828 ms 209.85.252.80 (209.85.252.80)  16.080 ms
      19  72.14.238.253 (72.14.238.253)  1.989 ms  3.563 ms  3.446 ms
      20  iad23s08-in-f9.1e100.net (74.125.228.105)  1.047 ms  1.821 ms  1.617 ms

  • Can you connect to the database's port? for example:
    • telnet db-003.d.espressologic.com 1433
      should see:
          Trying 10.191.182.197...
          Connected to db-003.d.espressologic.com.
          Escape character is '^]'.


Microsoft SQL Server login failed for user ClientConnectionId

Connectivity:

Has TCP/IP protocol been enabled from SQL Server Management Server? Make sure that TCP/IP is enabled in SQL Server Configuration Manager and that IPAll (ignore the other ports, e.g. IP1, IP2, etc...) has an assigned TCP Port (note: this is TCP Port, not TCP Dynamic Ports).

Connecting to Microsoft SQL Server

Authentication:

The EspressoLogic appliance is hosted on a CentOS virtual machine which means that we can not use Window's Authentication to your Microsoft SQL Server database Therefore SQL Server Authentication is a requirement. Here is a Microsoft article concerning changing SQL Server and Windows Authentication mode
Here is a Microsoft Knowledge Base article on opening Windows Firewall Ports to allow database connectivity from the Espresso Logic appliance:

http://support.microsoft.com/kb/947709


No Tables, Views, Procedures, Foreign Keys nor Columns detected after successful database connection


This usually means that the "Schema Owner" specified in the Database Connection wizard is incorrect. In Microsoft SQL Server, the Schema Owner is usually "dbo", not "sa" for example.


Microsoft SQL Server 2005 hangs while reading in Foreign Keys

Under Integrate
Click Data Sources
Change Database URL from:
jdbc:sqlserver:
to
jdbc:jtds:sqlserver:


Isolating Database Connection and / or reading problems 

Log into the Espresso Logic Appliance Virtual Machine's Operating System

Test Connection and / or reading problems

cd  /usr/share/espresso/diagnostics

Usage ./MetaTest.sh <url> <db user name> <password>

example ./MetaTest.sh 'jdbc:sqlserver://db-003.d.espressologic.com:1433;databaseName=Northwind' northwind NorthwindPassword\!

********************************

Catalogs

********************************

TABLE_CAT:demo, 

TABLE_CAT:LivingRMS2.1.1, 

TABLE_CAT:master, 

.
.
.

********************************

Schemas

********************************

TABLE_SCHEM:db_accessadmin, 

TABLE_CATALOG:null, 

TABLE_SCHEM:db_backupoperator, 

.
.

.
********************************

Table types

********************************

TABLE_TYPE:SYSTEM TABLE, 

TABLE_TYPE:TABLE, 

TABLE_TYPE:VIEW, 

Test by running a SQL command

[tomcat@espresso diagnostics]$ ./JdbcTester.sh 

Usage ./JdbcTester.sh <url> <db user name> <password> [sql command]

example ./JdbcTester.sh 'jdbc:sqlserver://db-003.d.espressologic.com:1433;databaseName=Northwind' northwind NorthwindPassword\! 'select * from master..sysdatabases'

[tomcat@espresso diagnostics]$ ./JdbcTester.sh 'jdbc:sqlserver://db-003.d.espressologic.com:1433;databaseName=Northwind' northwind NorthwindPassword\! 'select * from master..sysdatabases'

Connection successful

*****Execute SQL Command:select * from master..sysdatabases

name:master, 

dbid:1, 

sid:[B@1e3bb60, 

mode:0, 

status:65544, 

status2:1090520064, 

crdate:2003-04-08 09:13:36.39, 

reserved:1900-01-01 00:00:00.0, 

category:0, 

cmptlevel:110, 

filename:D:\RDSDBDATA\DATA\master.mdf, 

version:706, 

.
.


I forgot my root password to mysql running on the appliance and need to reset it

sudo  su -
service mysqld stop
/usr/bin/mysqld --skip-grant-tables --user=root

mysql -u root
UPDATE mysql.user SET Password=PASSWORD('newpassword') WHERE User='root';
FLUSH PRIVILEGES;
quit

service mysqld restart


SELinux issue with mysql or httpd

ls -lZ /etc/httpd/conf.d
-rw-r--r--. root root system_u:object_r:httpd_config_t:s0 README
-rw-r--r--. root root unconfined_u:object_r:httpd_config_t:s0 ssl.conf
-rw-r--r--. root root system_u:object_r:httpd_config_t:s0 welcome.conf


 ls -lZ /var/lib/mysql
(ls is the selinux list function to detail the labels for each object.

This is the default directory and will list these objects.
drwx------. mysql mysql unconfined_u:object_r:mysqld_db_t:s0 mysql

-rw-rw----. mysql mysql unconfined_u:object_r:mysqld_db_t:s0 auto.cnf
drwx------. mysql mysql system_u:object_r:mysqld_db_t:s0 espresso_admin
drwx------. mysql mysql system_u:object_r:mysqld_db_t:s0 espresso_data
drwx------. mysql mysql system_u:object_r:mysqld_db_t:s0 espresso_demo
-rw-r-----. mysql root  unconfined_u:object_r:mysqld_db_t:s0 espresso.err
drwx------. mysql mysql system_u:object_r:mysqld_db_t:s0 espresso_sample
-rw-rw----. mysql mysql unconfined_u:object_r:mysqld_db_t:s0 ibdata1
-rw-rw----. mysql mysql system_u:object_r:mysqld_db_t:s0 ib_logfile0
-rw-rw----. mysql mysql system_u:object_r:mysqld_db_t:s0 ib_logfile1
drwx--x--x. mysql mysql unconfined_u:object_r:mysqld_db_t:s0 mysql
srwxrwxrwx. mysql mysql system_u:object_r:mysqld_var_run_t:s0 mysql.sock
drwx------. mysql mysql unconfined_u:object_r:mysqld_db_t:s0 performance_schema
-rw-r--r--. root  root  unconfined_u:object_r:mysqld_db_t:s0 RPM_UPGRADE_HISTORY
-rw-r--r--. mysql mysql unconfined_u:object_r:mysqld_db_t:s0 RPM_UPGRADE_MARKER-LAST
drwxr-xr-x. mysql mysql unconfined_u:object_r:mysqld_db_t:s0 test


I encountered a defect or want to update the Espresso Logic Appliance's Operating System, software and database

Log into the Espresso Logic Appliance Virtual Machine's Operating System

sudo yum -y update
sudo reboot


VMware console has grabbed cursor and keyboard focus

Default Hot-Key Combinations

You can use keyboard shortcuts to interact with Workstation and with virtual machines. Most of the available keyboard shortcuts for Workstation are listed next to their associated commands in Workstation menus.

Default Hot-Key Combinations

Shortcut

Action

Ctrl+G

Grab input from the keyboard and mouse.

Ctrl+Alt

Release the mouse cursor.

Ctrl+Alt+Insert

Shut down or, depending on the guest operating system, log out of the guest operating system. This command is received solely by the virtual machine.

Ctrl+Alt+Delete

Shut down or, depending on the operating system, log out of the guest operating system.

On a Windows host, if you do not use the enhanced virtual keyboard feature, both the host operating system and the virtual machine receive this command, even when Workstation has control of input. Cancel the ending of the host operating system session and return to the virtual machine to log out or shut down or perform administrative tasks.

Ctrl+Alt+Enter

Enter full screen mode.

Ctrl+Alt+spacebar

Send any command to the virtual machine so that Workstation does not process it. Hold down Ctrl+Alt as you press and release the spacebar, and continue to hold the Ctrl+Alt keys down as you press the next key in the combination.

Ctrl+Tab

Ctrl+Shift+Tab

(Windows hosts only) Switch among tabs.

Ctrl+Alt+right arrow

In full screen mode, switch to the next powered-on virtual machine.

Ctrl+Alt+left arrow

In full screen mode, switch to the previous powered-on virtual machine.

Ctrl+Shift+U

In Unity mode, give access to the virtual machine Start or Applications menu.

You can change the Unity hot-key combination by modifying Unity preference settings.

 


Comments