Project

General

Profile

Bug #5906

After permanently changing jails hostname, the PBI control server does not get started anymore.

Added by Jordan Hubbard about 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Nice to have
Assignee:
Sean Fagan
Category:
Middleware
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Hi, i was playing around with the hostnames of the PBI-jails by adding "hostname=...." to the jails /etc/rc.conf. Soon after i found that all the jails i touched were not controllable via the web-interface anymore. I got the famous "HTTP Error 502: Bad Gateway" log message.

After some digging around i realized that the PBI-control-server just was not running for these jails.
This is confirmed by executing "service ix-plugins forcerestart". No instance gets started for all jails with a custom hostname.

I was looking into this and found the obvious problem.
The "ix-plugins" service tries to lookup the jid of the plugin-jail via its jail-name - which fails. "jail_get_jid()" in /etc/rc.freenas is looking at the output of "jls", which prints the hostname instead of the jail-name.

After fixing this, all PBI-control-server got started successfully
I attached the patch below.

rc.freenas.patch (487 Bytes) rc.freenas.patch Stephan Günther, 08/22/2014 04:33 PM

Related issues

Copied from FreeNAS - Bug #5889: After permanently changing jails hostname, the PBI control server does not get started anymore.Resolved2014-08-22

History

#1 Updated by Jordan Hubbard about 6 years ago

  • Copied from Bug #5889: After permanently changing jails hostname, the PBI control server does not get started anymore. added

#2 Updated by Sean Fagan about 6 years ago

  • Status changed from Screened to Fix In Progress

d48f8ed820145586f65f0fa1158cb3111026e117

Checked into 9.2.1-BRANCH. I think.

#3 Updated by Jordan Hubbard about 6 years ago

  • Status changed from Fix In Progress to Resolved

Also available in: Atom PDF