Upgrade (today) to FreeNAS-9.3-STABLE-201512121950 broke MineOS.

Status
Not open for further replies.

Pops

Dabbler
Joined
Sep 19, 2015
Messages
24
Upgrade (today) to FreeNAS-9.3-STABLE-201512121950 broke MineOS.

(Moved to this forum at the request of Joshua R.)

I've been running a stable server (both freeNAS and MineOS plugin) for the past few months without problems. After updating to the latest stable build earlier today, I can no longer access MineOS interface from the WebUI. I have gone through everything with a fine-tooth comb and can not determine the reason for the problem, although I think this error is involved (freeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b).

Steps taken: reinstalled (manual) FreeNAS-9.3-STABLE-201512121950 which fixed several permission errors found during verification, but didn't allow access to the MineOS plugin/jail.

-Reconfigured the jail to different addresses.

-plexmediaserver plugin works without issue.

--->ifconfig from system shell: http://pastebin.com/xbthpuPy

--->ifconfig from jail: http://pastebin.com/uc6SD52V

--->server start (mesg): http://pastebin.com/Sh8wp7Bg

--->sockstat (jail): http://pastebin.com/nQUX9nZW

If I need to supply more information, please let me know.

Thanks!
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
in the jail try to run 'service mineos onestart'
 

Pops

Dabbler
Joined
Sep 19, 2015
Messages
24
in the jail try to run 'service mineos onestart'
Thanks for the reply.

In short, that didn't work.

When I entered the command: root@mineos_1:/ # service mineos onestart
Starting mineos.
Starting mineos daemon...
mineos daemon started. PID: 39352

This message popped up in console:
Dec 13 23:31:04 freeNAS kernel: epair0a: promiscuous mode enabled
Dec 13 23:31:04 freeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Dec 13 23:31:04 freeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b

(after 'onestart')
root@mineos_1:/ # ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:60:c9:00:0a:0b
inet 192.168.1.10 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
that kernel message has nothing to do with your problem. It is just a log message. So it looks like mineos has started and is working. Why don't you think it's working?
 

Pops

Dabbler
Joined
Sep 19, 2015
Messages
24
that kernel message has nothing to do with your problem. It is just a log message. So it looks like mineos has started and is working. Why don't you think it's working?
I can't access it through the webUI. I get the ol' "connecting" ball of infinite spinning....
 
Status
Not open for further replies.
Top