New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 671019 link

Starred by 2 users
Status: Assigned
Owner:
█ cernekee@chromium.org
Last visit > 30 days ago
Cc:
derat@chromium.org
█ ejcaruso@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

arc-networkd aborts at CHECK(arc_ip_config_->Init());

Project Member Reported by derat@chromium.org, Dec 4 2016 
http://crash/5334ff2300000000, but originally came up in issue 661656.
Chrome OS 8992.0.0

Thread 0 CRASHED [SIGABRT @ 0x00000000 ]
0x00007fc4f1c5ab82	(libc-2.19.so -raise.c:56 )	raise
0x00007fc4f1c5c89f	(libc-2.19.so -abort.c:89 )	abort
0x00007fc4f23f6104	(libbase-core-395517.so -debugger_posix.cc:249 )	base::debug::BreakDebugger()
0x00007fc4f240d977	(libbase-core-395517.so -logging.cc:755 )	logging::LogMessage::~LogMessage()
0x00007fc4f252b3e3	(arc-networkd -manager.cc:39 )	arc_networkd::Manager::OnInit()
0x00007fc4f24c9442	(libbrillo-core-395517.so -daemon.cc:25 )	brillo::Daemon::Run()
0x00007fc4f252ae6e	(arc-networkd -main.cc:34 )	main
0x00007fc4f1c45fb5	(libc-2.19.so -libc-start.c:292 )	__libc_start_main
0x00007fc4f2524719	(arc-networkd + 0x00006719 )	_start
0x00007ffd2c457117		
0x00007fc4f25246f0	(arc-networkd -iostream:74 )	<name omitted>

manager.cc:
 37 int Manager::OnInit() {
 38   arc_ip_config_.reset(new ArcIpConfig(int_ifname_, con_ifname_, con_netns_));
 39   CHECK(arc_ip_config_->Init());

Comment 1 by cernekee@chromium.org, Dec 4 2016

Cc: derat@chromium.org
Is this happening after the ARC container crashes?

arc-networkd gets invoked with --con_netns=<PID> on its command line so that it knows which namespace to attach to.  |PID| is passed through upstart.  If the container crashes and is restarted, the arc-networkd upstart job will need to be stopped and restarted with the new $CONTAINER_PID, otherwise arc-networkd will try to attach to a nonexistent namespace and hit that check.

Comment 2 by derat@chromium.org, Dec 5 2016 

Not sure. This was from a user, and the only crash reports from their system are this one and an unrelated Chrome crash.

Comment 3 by benhenry@chromium.org, Aug 1

Status: Assigned (was: Untriaged)
►

Sign in to add a comment