Issue install new rancher-server:v0.32.0

Hi everyone,

I got the following error when trying to install a new rancher server:
Steps to reproduce:

  1. sudo docker create --name rancher-data rancher/server:latest true
  2. sudo docker run --volumes-from rancher-data --restart=always --name=rancher-server rancher/server:latest

Then the following output occurs and hangs at the last log message:

150818 14:15:28 [Note] /usr/sbin/mysqld (mysqld 5.5.44-0ubuntu0.14.04.1-log) starting as process 23 ...
Uptime: 3  Threads: 1  Questions: 2  Slow queries: 0  Opens: 33  Flush tables: 1  Open tables: 26  Queries per second avg: 0.666
Setting up database
CATTLE_CATTLE_VERSION=v0.75.0
CATTLE_DB_CATTLE_DATABASE=mysql
CATTLE_DB_CATTLE_MYSQL_HOST=localhost
CATTLE_DB_CATTLE_MYSQL_NAME=cattle
CATTLE_DB_CATTLE_MYSQL_PORT=3306
CATTLE_DB_CATTLE_USERNAME=cattle
CATTLE_GRAPHITE_HOST=
CATTLE_GRAPHITE_PORT=
CATTLE_HOME=/var/lib/cattle
CATTLE_HOST_API_PROXY_MODE=embedded
CATTLE_LOGBACK_OUTPUT_GELF_HOST=
CATTLE_LOGBACK_OUTPUT_GELF_PORT=
CATTLE_RANCHER_COMPOSE_VERSION=beta/latest
CATTLE_RANCHER_SERVER_IMAGE=v0.32.0
DEFAULT_CATTLE_API_UI_INDEX=//releases.rancher.com/ui/0.40.0
DEFAULT_CATTLE_MACHINE_EXECUTE=true
DEFAULT_CATTLE_RANCHER_COMPOSE_DARWIN_URL=https://releases.rancher.com/compose/beta/latest/rancher-compose-darwin-amd64.tar.gz
DEFAULT_CATTLE_RANCHER_COMPOSE_LINUX_URL=https://releases.rancher.com/compose/beta/latest/rancher-compose-linux-amd64.tar.gz
DEFAULT_CATTLE_RANCHER_COMPOSE_WINDOWS_URL=https://releases.rancher.com/compose/beta/latest/rancher-compose-windows-386.zip
[BOOTSTRAP] Starting Cattle
[BOOTSTRAP] CATTLE_HOME=/var/lib/cattle
[BOOTSTRAP] CATTLE_LIB=/var/lib/cattle/lib/0.5.0-SNAPSHOT-08247e2354761cd579bb810745473fe8eefcf32b-2615904b-dc5e-432e-bcc9-e82276949d4d
[BOOTSTRAP] Running first time extraction
0% 10% 20% 30% 40% 50% 60% 70% 80% 90%
[BOOTSTRAP] Done
[BOOTSTRAP] Launching Cattle from [file:/var/lib/cattle/lib/0.5.0-SNAPSHOT-08247e2354761cd579bb810745473fe8eefcf32b-2615904b-dc5e-432e-bcc9-e82276949d4d/]
[MAIN] Scanning [etc/cattle] for extensions
14:15:54.935 [main] WARN  o.e.jetty.security.SecurityHandler - ServletContext@o.e.j.w.WebAppContext@46d872fe{/,file:/var/lib/cattle/lib/0.5.0-SNAPSHOT-08247e2354761cd579bb810745473fe8eefcf32b-2615904b-dc5e-432e-bcc9-e82276949d4d/,STARTING}{file:/var/lib/cattle/lib/0.5.0-SNAPSHOT-08247e2354761cd579bb810745473fe8eefcf32b-2615904b-dc5e-432e-bcc9-e82276949d4d/} has uncovered http methods for path: /
14:15:58.230 [main] INFO  ConsoleStatus - [1/6] [1ms] [0ms] Loading config-bootstrap
14:15:58.660 [main] INFO  ConsoleStatus - [2/6] [432ms] [422ms] Loading base-config
14:15:59.288 [main] INFO  ConsoleStatus - [3/6] [1060ms] [627ms] Loading config
14:15:59.306 [main] INFO  ConsoleStatus - [4/6] [1078ms] [17ms] Starting config-bootstrap
14:15:59.778 [main] INFO  ConsoleStatus - [5/6] [1550ms] [472ms] Starting base-config
14:15:59.778 [main] INFO  ConsoleStatus - [6/6] [1550ms] [0ms] Starting config
2015-08-18 14:16:00,419 INFO    [main] [ConsoleStatus] [1/102] [0ms] [0ms] Loading bootstrap
2015-08-18 14:16:00,575 INFO    [main] [ConsoleStatus] [2/102] [156ms] [156ms] Loading config-defaults

docker version:

    Client:
 Version:      1.8.1
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   d12ea79
 Built:        Thu Aug 13 02:35:49 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.8.1
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   d12ea79
 Built:        Thu Aug 13 02:35:49 UTC 2015
 OS/Arch:      linux/amd64

docker info:

Containers: 2
Images: 42
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 46
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.16.0-45-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 2
Total Memory: 3.362 GiB
Name: rancher-master
ID: LNYN:YHWO:GSZL:BXWS:MNEV:FYKI:VXAM:5KSG:LZU5:3XYA:KHAK:FIUJ
WARNING: No swap limit support

Did you give it “a while”? Initial startup has to create the database and go through every revision of it so that along with the rest of startup takes at least several minutes the first time, depending on the CPU and disk speed.

Yep tried it about 5-10 times always the same sometimes i get the following output, sometimes the container exits.

2015-08-18 14:40:11,698 ERROR [:] [] [] [] [igurationSource] [c.n.config.AbstractPollingScheduler ] Error getting result from polling source java.sql.SQLSyntaxErrorException: Table 'cattle.setting' doesn't exist
	at org.mariadb.jdbc.internal.SQLExceptionMapper.get(SQLExceptionMapper.java:138) ~[mariadb-java-client-1.1.7.jar:na]
	at org.mariadb.jdbc.internal.SQLExceptionMapper.throwException(SQLExceptionMapper.java:106) ~[mariadb-java-client-1.1.7.jar:na]
	at org.mariadb.jdbc.MySQLStatement.executeQueryEpilog(MySQLStatement.java:264) ~[mariadb-java-client-1.1.7.jar:na]
	at org.mariadb.jdbc.MySQLStatement.execute(MySQLStatement.java:288) ~[mariadb-java-client-1.1.7.jar:na]
	at org.mariadb.jdbc.MySQLStatement.executeQuery(MySQLStatement.java:302) ~[mariadb-java-client-1.1.7.jar:na]
	at org.mariadb.jdbc.MySQLPreparedStatement.executeQuery(MySQLPreparedStatement.java:112) ~[mariadb-java-client-1.1.7.jar:na]
	at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) ~[commons-dbcp-1.4.jar:1.4]
	at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) ~[commons-dbcp-1.4.jar:1.4]
	at com.netflix.config.sources.JDBCConfigurationSource.load(JDBCConfigurationSource.java:107) ~[archaius-core-0.5.14.jar:na]
	at com.netflix.config.sources.JDBCConfigurationSource.poll(JDBCConfigurationSource.java:88) ~[archaius-core-0.5.14.jar:na]
	at io.cattle.platform.archaius.sources.LazyJDBCSource.poll(LazyJDBCSource.java:31) ~[cattle-framework-archaius-0.5.0-SNAPSHOT.jar:na]
	at com.netflix.config.AbstractPollingScheduler$1.run(AbstractPollingScheduler.java:163) ~[archaius-core-0.5.14.jar:na]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_79]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) [na:1.7.0_79]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) [na:1.7.0_79]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.7.0_79]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_79]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_79]
	at java.lang.Thread.run(Thread.java:745) [na:1.7.0_79]
Caused by: org.mariadb.jdbc.internal.common.QueryException: Table 'cattle.setting' doesn't exist
	at org.mariadb.jdbc.internal.mysql.MySQLProtocol.getResult(MySQLProtocol.java:942) ~[mariadb-java-client-1.1.7.jar:na]
	at org.mariadb.jdbc.internal.mysql.MySQLProtocol.executeQuery(MySQLProtocol.java:991) ~[mariadb-java-client-1.1.7.jar:na]
	at org.mariadb.jdbc.MySQLStatement.execute(MySQLStatement.java:281) ~[mariadb-java-client-1.1.7.jar:na]
	... 15 common frames omitted

I tried the same commands and had no issues with starting Rancher server.

How big is the machine that you are running rancher server on?

Hi @denise,

It`s an Azure Standard A2 with 2 Cores, 3,5 GB RAM and 135 GB Disk space.

Maybe another issue??
docker images -a

REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
rancher/server      latest              84fbca2b610d        10 days ago         502.6 MB
rancher/server      v0.32.0             84fbca2b610d        10 days ago         502.6 MB
<none>              <none>              e55174d49486        10 days ago         502.6 MB
<none>              <none>              2bc90226ab86        10 days ago         502.6 MB
<none>              <none>              490819b6a8ec        10 days ago         471.1 MB
<none>              <none>              c0edaa8af9f2        10 days ago         458.2 MB
<none>              <none>              cd59668ef7ac        10 days ago         458.2 MB
<none>              <none>              8562839614d1        10 days ago         458.2 MB
<none>              <none>              0812ee9489ec        10 days ago         458.2 MB
<none>              <none>              3d6ac100e6b7        10 days ago         458.2 MB
<none>              <none>              fc6f3394d121        10 days ago         458.2 MB
<none>              <none>              a5f973025539        10 days ago         458.2 MB
<none>              <none>              8a52d61ef533        11 days ago         458.2 MB
<none>              <none>              8ed81a7c9042        11 days ago         458.2 MB
<none>              <none>              d7d75b602486        11 days ago         458.2 MB
<none>              <none>              cc82d3bd6136        11 days ago         458.2 MB
<none>              <none>              bf7c65b534bc        11 days ago         458.2 MB
<none>              <none>              adaec60c7377        11 days ago         458.2 MB
<none>              <none>              36e4eb90d480        11 days ago         453.9 MB
<none>              <none>              11dd4ef5cfe1        12 days ago         452.3 MB
<none>              <none>              7b7c86cb816b        12 days ago         452.3 MB
<none>              <none>              c95c73f0d6d6        12 days ago         452.3 MB
<none>              <none>              a6bd0b531e15        12 days ago         452.3 MB
<none>              <none>              e88a86f9bd45        12 days ago         452.3 MB
<none>              <none>              cc8bacf87e73        2 weeks ago         452.3 MB
<none>              <none>              859cd88d9cb8        2 weeks ago         452.3 MB
<none>              <none>              0b87eef0f43b        2 weeks ago         188.4 MB

Can you do a docker ps -a?

Here you go:

ONTAINER ID        IMAGE                   COMMAND                  CREATED             STATUS                     PORTS               NAMES
8791d059017a        rancher/server:latest   "/usr/bin/s6-svscan /"   35 minutes ago      Exited (0) 9 minutes ago                       rancher-server
db3806335e72        rancher/server:latest   "true"                   36 minutes ago      Created

Honestly I’m stumped because it works for me on a fresh install of a machine. And I copy and pasted your commands.

Yeah looks strange. I´ll try to reinstall the base server and try it again.

Thanks.

Hi @denise @vincent,

I`ve deployed a completely fresh install of Ubuntu on Azure, but still have the same issue except the container stays in running state.

Kernel Version: 3.19.0-25-generic
Operating System: Ubuntu 14.04.3 LTS

Don`t know where the problem is.

Here`s the complete log file:

150818 20:55:52 [Note] /usr/sbin/mysqld (mysqld 5.5.44-0ubuntu0.14.04.1-log) starting as process 24 ...
Uptime: 3  Threads: 1  Questions: 2  Slow queries: 0  Opens: 33  Flush tables: 1  Open tables: 26  Queries per second avg: 0.666
Setting up database
CATTLE_CATTLE_VERSION=v0.75.0
CATTLE_DB_CATTLE_DATABASE=mysql
CATTLE_DB_CATTLE_MYSQL_HOST=localhost
CATTLE_DB_CATTLE_MYSQL_NAME=cattle
CATTLE_DB_CATTLE_MYSQL_PORT=3306
CATTLE_DB_CATTLE_USERNAME=cattle
CATTLE_GRAPHITE_HOST=
CATTLE_GRAPHITE_PORT=
CATTLE_HOME=/var/lib/cattle
CATTLE_HOST_API_PROXY_MODE=embedded
CATTLE_LOGBACK_OUTPUT_GELF_HOST=
CATTLE_LOGBACK_OUTPUT_GELF_PORT=
CATTLE_RANCHER_COMPOSE_VERSION=beta/latest
CATTLE_RANCHER_SERVER_IMAGE=v0.32.0
DEFAULT_CATTLE_API_UI_INDEX=//releases.rancher.com/ui/0.40.0
DEFAULT_CATTLE_MACHINE_EXECUTE=true
DEFAULT_CATTLE_RANCHER_COMPOSE_DARWIN_URL=https://releases.rancher.com/compose/beta/latest/rancher-compose-darwin-amd64.tar.gz
DEFAULT_CATTLE_RANCHER_COMPOSE_LINUX_URL=https://releases.rancher.com/compose/beta/latest/rancher-compose-linux-amd64.tar.gz
DEFAULT_CATTLE_RANCHER_COMPOSE_WINDOWS_URL=https://releases.rancher.com/compose/beta/latest/rancher-compose-windows-386.zip
[BOOTSTRAP] Starting Cattle
[BOOTSTRAP] CATTLE_HOME=/var/lib/cattle
[BOOTSTRAP] CATTLE_LIB=/var/lib/cattle/lib/0.5.0-SNAPSHOT-08247e2354761cd579bb810745473fe8eefcf32b-2615904b-dc5e-432e-bcc9-e82276949d4d
[BOOTSTRAP] Running first time extraction
0% 10% 20% 30% 40% 50% 60% 70% 80% 90%
[BOOTSTRAP] Done
[BOOTSTRAP] Launching Cattle from [file:/var/lib/cattle/lib/0.5.0-SNAPSHOT-08247e2354761cd579bb810745473fe8eefcf32b-2615904b-dc5e-432e-bcc9-e82276949d4d/]
[MAIN] Scanning [etc/cattle] for extensions
20:56:16.833 [main] WARN  o.e.jetty.security.SecurityHandler - ServletContext@o.e.j.w.WebAppContext@62158e60{/,file:/var/lib/cattle/lib/0.5.0-SNAPSHOT-08247e2354761cd579bb810745473fe8eefcf32b-2615904b-dc5e-432e-bcc9-e82276949d4d/,STARTING}{file:/var/lib/cattle/lib/0.5.0-SNAPSHOT-08247e2354761cd579bb810745473fe8eefcf32b-2615904b-dc5e-432e-bcc9-e82276949d4d/} has uncovered http methods for path: /
20:56:20.179 [main] INFO  ConsoleStatus - [1/6] [0ms] [1ms] Loading config-bootstrap
20:56:20.676 [main] INFO  ConsoleStatus - [2/6] [500ms] [490ms] Loading base-config
20:56:21.256 [main] INFO  ConsoleStatus - [3/6] [1080ms] [580ms] Loading config
20:56:21.267 [main] INFO  ConsoleStatus - [4/6] [1091ms] [10ms] Starting config-bootstrap
20:56:21.788 [main] INFO  ConsoleStatus - [5/6] [1612ms] [521ms] Starting base-config
20:56:21.789 [main] INFO  ConsoleStatus - [6/6] [1612ms] [0ms] Starting config
2015-08-18 20:56:22,330 INFO    [main] [ConsoleStatus] [1/102] [0ms] [0ms] Loading bootstrap
2015-08-18 20:56:22,469 INFO    [main] [ConsoleStatus] [2/102] [139ms] [139ms] Loading config-defaults
2015-08-18 20:56:37,811 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,812 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,812 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,812 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,812 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,812 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,812 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,812 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,812 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,813 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,813 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,813 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,813 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,813 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,813 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,813 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,813 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,814 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,814 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,814 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,814 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,814 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,814 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,814 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,814 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,815 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,815 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,815 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,821 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,821 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,821 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,821 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,821 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,821 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,821 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,821 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,822 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,822 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,822 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,822 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,822 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,822 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,822 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,822 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,822 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,822 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,822 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,823 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,823 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,823 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,823 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,823 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,823 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,823 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,823 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,823 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,823 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,823 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,823 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,824 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,824 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,824 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,824 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,824 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,824 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:37,830 WARN  [:] [] [] [] [main           ] [liquibase                           ] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2015-08-18 20:56:51,166 ERROR [:] [] [] [] [igurationSource] [c.n.config.AbstractPollingScheduler ] Error getting result from polling source java.sql.SQLSyntaxErrorException: Table 'cattle.setting' doesn't exist
	at org.mariadb.jdbc.internal.SQLExceptionMapper.get(SQLExceptionMapper.java:138) ~[mariadb-java-client-1.1.7.jar:na]
	at org.mariadb.jdbc.internal.SQLExceptionMapper.throwException(SQLExceptionMapper.java:106) ~[mariadb-java-client-1.1.7.jar:na]
	at org.mariadb.jdbc.MySQLStatement.executeQueryEpilog(MySQLStatement.java:264) ~[mariadb-java-client-1.1.7.jar:na]
	at org.mariadb.jdbc.MySQLStatement.execute(MySQLStatement.java:288) ~[mariadb-java-client-1.1.7.jar:na]
	at org.mariadb.jdbc.MySQLStatement.executeQuery(MySQLStatement.java:302) ~[mariadb-java-client-1.1.7.jar:na]
	at org.mariadb.jdbc.MySQLPreparedStatement.executeQuery(MySQLPreparedStatement.java:112) ~[mariadb-java-client-1.1.7.jar:na]
	at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) ~[commons-dbcp-1.4.jar:1.4]
	at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) ~[commons-dbcp-1.4.jar:1.4]
	at com.netflix.config.sources.JDBCConfigurationSource.load(JDBCConfigurationSource.java:107) ~[archaius-core-0.5.14.jar:na]
	at com.netflix.config.sources.JDBCConfigurationSource.poll(JDBCConfigurationSource.java:88) ~[archaius-core-0.5.14.jar:na]
	at io.cattle.platform.archaius.sources.LazyJDBCSource.poll(LazyJDBCSource.java:31) ~[cattle-framework-archaius-0.5.0-SNAPSHOT.jar:na]
	at com.netflix.config.AbstractPollingScheduler$1.run(AbstractPollingScheduler.java:163) ~[archaius-core-0.5.14.jar:na]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_79]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) [na:1.7.0_79]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) [na:1.7.0_79]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.7.0_79]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_79]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_79]
	at java.lang.Thread.run(Thread.java:745) [na:1.7.0_79]
Caused by: org.mariadb.jdbc.internal.common.QueryException: Table 'cattle.setting' doesn't exist
	at org.mariadb.jdbc.internal.mysql.MySQLProtocol.getResult(MySQLProtocol.java:942) ~[mariadb-java-client-1.1.7.jar:na]
	at org.mariadb.jdbc.internal.mysql.MySQLProtocol.executeQuery(MySQLProtocol.java:991) ~[mariadb-java-client-1.1.7.jar:na]
	at org.mariadb.jdbc.MySQLStatement.execute(MySQLStatement.java:281) ~[mariadb-java-client-1.1.7.jar:na]
	... 15 common frames omitted

Any update on this ??

I have exactly the same issue with the latest rancher build.
I have the same issue with the v0.34.0 build also.

root@rancher-server:~# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
be6eaaa75ac1 rancher/server “/usr/bin/s6-svscan /” 4 minutes ago Up 4 minutes

root@rancher-server:~# docker logs be6eaaa75ac1 | grep http
DEFAULT_CATTLE_RANCHER_COMPOSE_DARWIN_URL=https://releases.rancher.com/compose/beta/latest/rancher-compose-darwin-amd64.tar.gz
DEFAULT_CATTLE_RANCHER_COMPOSE_LINUX_URL=https://releases.rancher.com/compose/beta/latest/rancher-compose-linux-amd64.tar.gz
DEFAULT_CATTLE_RANCHER_COMPOSE_WINDOWS_URL=https://releases.rancher.com/compose/beta/latest/rancher-compose-windows-386.zip
16:30:02.192 [main] WARN o.e.jetty.security.SecurityHandler - ServletContext@o.e.j.w.WebAppContext@2e56c4eb{/,file:/var/lib/cattle/lib/0.5.0-SNAPSHOT-1ae5249f09d3960a771f3ca1a7d267a840b066e3-4a06a64b-2392-46e1-aef7-256ba68a3afa/,STARTING}{file:/var/lib/cattle/lib/0.5.0-SNAPSHOT-1ae5249f09d3960a771f3ca1a7d267a840b066e3-4a06a64b-2392-46e1-aef7-256ba68a3afa/} has uncovered http methods for path: /

rancher server container is up. I can ping. But http fails.

Thanks,
Farhad.

Might be an arb observation, but I dont see the port mapping -p 8080:8080 being parsed in the start-up, not sure if it may be the total issue, but certainly could be if http is failing.

Hi @fsunaval,
I got it working on installing v.0.28 and then updated the rancher-server to version v0.34.
And then point you SSL or HTTP Proxy to that container. That works for me.
Maybe you can try that aswell.

1 Like

Interesting. Did you have to roll through old versions one release at a time? I tried 0.34, then 0.32, then 0.31, until I got fed up with this and tried v0.28 but then Docker Hub hanged.

Leaving my terminal there and let’s see how it goes when I wake up :(.