FreeNAS-11.1 with Rancher VM | losing Host after reboot

[vikozo6]

hello
i have the following strange behavior
i followed http://doc.freenas.org/11/vms.html#docker-rancher-vm
when in Rancher i add the Host and do a restart of the VM (in FreeNAS) the Host is not there anymore.
I also added kubernetes as management - this also is gone!

any suggestion what to check?

have a nice day
vinc

 

[vikozo6]

This happen again today, a reboot of FreeNAS the VM is running and after entering Rancher, there is no Host configured, why this happen?

 

[vikozo6]

and again my Host is away - but it is special because the Plex-Docker is still accessible which is on the Host

 

[KrisBee]

Rather than leaving people guessing, you'll have to give at least some details of your network setup before anyone might help.

1. FreeNAS , static ip or dhcp?
2. FreeNAS with FQDN and rancheros hostname added in global network config.
3. RancherOS, static ip or dhcp?
4. RacherOS, FQDN configured in same domain as FreeNAS host.
5. Is RancherOs accessible via ssh?

 

[vikozo6]

1) FreeNAS static 10.147.42.73 FQDN = NAS-04.kozo.ch
2) Rancher static 10.147.42.130 FQDN = rancher04.kozo.ch:8080
plex would be on 10.147.42.130:32400 (and works fine)

5) via terminal it is accessible with 10.147.42.130

Code:

rancheros hostname added in global network config

where should this be added?

 

[KrisBee]

5. See https://doc.freenas.org/11/network.html#global-configuration . Add rancher details in "hostname database" box and press save. It will add rancher details to FreeNAS /etc/hosts file and should avoid any possible problems with reverse DNS lookups on your kzo.ch domain.

I haven't used RancherUI enough to say what might be wrong. Incorrect rancher config and/or network problem and/or Rancher-server/Agent losing part of rancher config are all possible.

Once re-configured after the rancher host appears to be lost and everything is up and running can you pinpoint what fails on the rancher side after a FreeNAS VM reboot by looking at all the containers that should be running and interconnected.

There may be hints here about checking host registration, etc. :

http://rancher.com/docs/rancher/v1.6/en/faqs/agents/

Also have a look at recent posts on https://forums.rancher.com and https://github.com/rancher/rancher/issues for similar issues.

P.S. Just how extensive is your use of dockers? There are other possible implementations that might avoid these complexities.

 

[vikozo6]

@KrisBee
i did add the Information into the hostname database now.
it is not problem to access the Rancher UI - the problem is the rancher UI is loosing the Host, or at least the Information about it.
my
$ sudo system-docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
68e587e3dd65 rancher/os-console:v1.1.0 "/usr/bin/ros entrypo" 38 hours ago Up 38 hours console
783bd481870d rancher/os-docker:17.03.2 "ros user-docker" 11 days ago Up 38 hours docker
d6436f9de4f7 rancher/os-base:v1.1.0 "/usr/bin/ros entrypo" 11 days ago Up 38 hours ntp
9c4dd5969a0c rancher/os-base:v1.1.0 "/usr/bin/ros entrypo" 11 days ago Up 38 hours network
54ded1eda865 rancher/os-base:v1.1.0 "/usr/bin/ros entrypo" 11 days ago Up 38 hours udev
ac3e987f85d3 rancher/container-crontab:v0.1.0 "container-crontab" 11 days ago Up 38 hours system-cron
59f5a71b4d19 rancher/os-acpid:v1.1.0 "/usr/bin/ros entrypo" 11 days ago Up 38 hours acpid
368dbbafb01c rancher/os-syslog:v1.1.0 "/usr/bin/entrypoint." 11 days ago Up 38 hours syslog
[rancher@rancher ~]$


 

[KrisBee]

The running rancher-server/agent and their related containers can be viewed using docker ps. (Remember rancher server/agent etc can run on other linux distros as well as rancheros. ) . eg:

Code:

root@rancher:~# docker ps
CONTAINER ID		IMAGE							 COMMAND				  CREATED			 STATUS			  PORTS							  NAM
ES
3176a6077906		rancher/scheduler:v0.8.2		  "/.r/r /rancher-en..."   3 days ago		  Up About a minute									  r-s
cheduler-scheduler-1-7030b29a
8d23629722d9		rancher/storage-nfs:v0.8.5		"start.sh storage ..."   11 days ago		 Up About a minute									  r-n
fs-nfs-driver-1-00ec47cc
44213a15c28d		rancher/healthcheck:v0.3.3		"/.r/r /rancher-en..."   2 weeks ago		 Up About a minute									  r-h
ealthcheck-healthcheck-1-14795046
74d04ac0295c		rancher/net:v0.13.5			   "/rancher-entrypoi..."   2 weeks ago		 Up About a minute									  r-i
psec-cni-driver-1-b8e46d60
6cd01ac9ac24		rancher/dns:v0.15.3			   "/rancher-entrypoi..."   2 weeks ago		 Up About a minute									  r-n
etwork-services-metadata-dns-1-aede8559
b5381f05f099		rancher/network-manager:v0.7.18   "/rancher-entrypoi..."   2 weeks ago		 Up About a minute									  r-n
etwork-services-network-manager-1-7bcc510f
7fd18fc19e39		rancher/net:holder				"/.r/r /rancher-en..."   2 weeks ago		 Up About a minute									  r-i
psec-ipsec-1-987d5a01
3f60422fbf82		rancher/metadata:v0.9.5		   "/rancher-entrypoi..."   2 weeks ago		 Up About a minute									  r-n
etwork-services-metadata-1-3a5fc1ad
1379cbb07009		rancher/agent:v1.2.7			  "/run.sh run"			2 weeks ago		 Up 3 minutes										   ran
cher-agent
defcfa170620		rancher/server					"/usr/bin/entry /u..."   2 weeks ago		 Up 3 minutes		3306/tcp, 0.0.0.0:8080->8080/tcp   won
derful_varahamihira

I believe all the rancher config data is held internally, some of it in SQL tables. See here for further details: http://rancher.com/docs/rancher/v1.6/en/faqs/server/

You've not said if the host you've registered with the rancher-server, and whose details are being lost, is the same host that's actually running the rancher-server. Assuming this is true and you only have a single DockerVM running, then I have not encountered your problem in my limited use of rancher while testing in FreeNAS 11.1, nor using the same combination running in virtualbox on a linux desktop.

Other than looking at the references I gave you to troubleshoot your problem, the rancher system logs might provide some clues. I'm afraid I cannot advise further.

 

[abys]

Did you ever find out what happened? Facing the same issue, losing all my configuration after updating. Mixed with memory leak, I have to reboot every couple of days and lose all my config..