Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 03 Jul 2019 10:28:29 +0300
From:      wishmaster <artemrts@ukr.net>
To:        Eugene Grosbein <eugen@grosbein.net>
Cc:        freebsd-net@freebsd.org
Subject:   Re[2]: Network issues while jails are starting
Message-ID:  <1562138561.380322000.k6ndni22@frv50.fwdcdn.com>
In-Reply-To: <2deee082-1dca-b93f-39f7-33d4c4f5b09d@grosbein.net>
References:  <1562134249.868399000.r0je57so@frv50.fwdcdn.com> <2deee082-1dca-b93f-39f7-33d4c4f5b09d@grosbein.net>

next in thread | previous in thread | raw e-mail | index | archive | help

  

--- Original message ---
From: "Eugene Grosbein" <eugen@grosbein.net>
Date: 3 July 2019, 10:16:31

03.07.2019 14:08, wishmaster wrote:

> 
> Hi,
> 
> the office's server has 6 jails and 2 bhyve virtual servers.
> The problem is when I restart server, jails start for a long time (about 6 minutes). All this time the server does not acts as router, that is no packets between interfaces. From within the server packets are transmitted and received (ping works correctly), but from LAN - no.
> 
> I do not remember either this issue has appeared after upgrading to 12.0 or switching from STABLE to RELEASE branch, but this issue has been appearing for about half of year or little more.
> 
> Toggle sysctl net.inet.ip.forwarding while jails are starting don't help.
> 
> root@e-server: uname -a
> FreeBSD e-server 12.0-RELEASE-p3 FreeBSD 12.0-RELEASE-p3 GENERIC  amd64
> 
> jail_enable="YES"
> jail_parallel_start="NO"
> jail_list="basejail jdb jphp jwww jmail jdns"
> jail_reverse_stop="YES"
> Any advices?

Does your LAN use NAT service of the router and/or its DNS resolver?
You should uncomment /var/log/console.log in the /etc/syslog.conf,
create this file and reboot then read the file carefully and check whether
you NAT/DNS services start before jails.

Logging to the console log file is already enabled.
I check Internet connection w/o DNS services.

Some logs...

Jul  3 07:56:29 e-server kernel: Starting jails:
Jul  3 07:56:30 e-server kernel: Jul  3 07:56:30 e-server kernel: ng_ether_ifnet_arrival_event: can't re-name node epair999b
Jul  3 07:56:39 e-server kernel:  basejail
Jul  3 07:56:39 e-server kernel: Jul  3 07:56:39 e-server kernel: ng_ether_ifnet_arrival_event: can't re-name node epair7b
Jul  3 07:56:40 e-server kernel: wrmsr to register 0x10(0) on vcpu 0
Jul  3 07:56:40 e-server kernel: wrmsr to register 0x10(0) on vcpu 1
Jul  3 07:56:41 e-server kernel: wrmsr to register 0x10(0) on vcpu 2
Jul  3 07:56:41 e-server kernel: wrmsr to register 0x10(0x66e28bcf97) on vcpu 2
Jul  3 07:56:41 e-server kernel: wrmsr to register 0x10(0x66e28bcf97) on vcpu 1
Jul  3 07:56:41 e-server kernel: wrmsr to register 0x10(0x66e28bcf97) on vcpu 0
Jul  3 07:57:04 e-server kernel:  jdb
Jul  3 07:57:04 e-server kernel: Jul  3 07:57:04 e-server kernel: ng_ether_ifnet_arrival_event: can't re-name node epair8b
Jul  3 07:57:27 e-server kernel:  jphp
Jul  3 07:57:27 e-server kernel: Jul  3 07:57:27 e-server kernel: ng_ether_ifnet_arrival_event: can't re-name node epair6b
Jul  3 08:01:20 e-server kernel:  jwww
Jul  3 08:01:21 e-server kernel: Jul  3 08:01:21 e-server kernel: ng_ether_ifnet_arrival_event: can't re-name node epair5b
Jul  3 08:04:53 e-server kernel:  jmail
Jul  3 08:04:54 e-server kernel: Jul  3 08:04:54 e-server kernel: ng_ether_ifnet_arrival_event: can't re-name node epair4b
Jul  3 08:05:48 e-server kernel:  jdns
Jul  3 08:05:48 e-server kernel: Starting background file system checks in 60 seconds.
Jul  3 08:05:48 e-server kernel:
Jul  3 08:05:48 e-server kernel: Wed Jul  3 08:05:48 EEST 2019







Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1562138561.380322000.k6ndni22>