Like this, very cool.

I've been using a web based terminal for work by using the excellent chrome extension 'secure shell' might be worth a look for those of us that have to manage other distros as well as unraid.

Sent from my SM-G935F using Tapatalk

16 hours ago, limetech said:

We now have a web-based Terminal application available by clicking the Terminal button on the Menu bar.  Kudos to @eschultz for integrating the ttyd application with our nginx install.  This is using websockets and appears to be quite fast, give it a try!

 

Nano isn't working correctly on the terminal for me, when scrolling using the arrow keys it skips around.

8 hours ago, Ambrotos said:

 

I'm currently running 17b and am using multiple VLANs each with their own subnet in order to place various various dockers into different network segments. I'm curious how 17b killed your setup. Did performing the upgrade mess with your configuration, or did the configuration persist but stop working?

 

Cheers,

 

-A

He's referring to this: 

I had this same problem in 17b and did not have it when I upgraded to 18f. 

 

hih

 

 

I have s situation where my eth1 NIC has gotten hung.  I saw this on 17b also.

Dec 28 16:18:38 MediaServer kernel: veth7c17111: renamed from eth0
Dec 28 16:19:33 MediaServer kernel: eth0: renamed from veth9348bc7
Dec 28 16:19:33 MediaServer kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Dec 28 16:22:47 MediaServer emhttpd: req (1): csrf_token=****************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog
Dec 28 16:22:47 MediaServer emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog
Dec 28 16:38:05 MediaServer kernel: veth9348bc7: renamed from eth0
Dec 28 16:38:52 MediaServer kernel: eth0: renamed from veth108c16a
Dec 28 16:38:52 MediaServer kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Dec 28 16:57:24 MediaServer kernel: e1000e 0000:00:19.0 eth1: Detected Hardware Unit Hang:
Dec 28 16:57:24 MediaServer kernel:  TDH                  <1a>
Dec 28 16:57:24 MediaServer kernel:  TDT                  <60>
Dec 28 16:57:24 MediaServer kernel:  next_to_use          <60>
Dec 28 16:57:24 MediaServer kernel:  next_to_clean        <19>
Dec 28 16:57:24 MediaServer kernel: buffer_info[next_to_clean]:
Dec 28 16:57:24 MediaServer kernel:  time_stamp           <1002e2a1d>
Dec 28 16:57:24 MediaServer kernel:  next_to_watch        <1a>
Dec 28 16:57:24 MediaServer kernel:  jiffies              <1002e3300>
Dec 28 16:57:24 MediaServer kernel:  next_to_watch.status <0>
Dec 28 16:57:24 MediaServer kernel: MAC Status             <80083>
Dec 28 16:57:24 MediaServer kernel: PHY Status             <796d>
Dec 28 16:57:24 MediaServer kernel: PHY 1000BASE-T Status  <3800>
Dec 28 16:57:24 MediaServer kernel: PHY Extended Status    <3000>
Dec 28 16:57:24 MediaServer kernel: PCI Status             <10>

I have eth0 and eth1 bonded and set for transmit load balance.  It only happened once so far after the reboot for 18f.  Seems to have occurred after VMs were started.

 

mediaserver-diagnostics-20171229-0701.zip

Quote

emhttp: do not auto-invoke dockerupdate.php upon docker start

 

Now all we need is the ability to start libvirt before the docker daemon (i.e start VMs before dockere containers).

I had to create a plugin (and i hate php) that was able to disable Docker when the array starts and then re-enable it after libvirt has started (and my pfSense VM is up and running) all because of the auto-invoke of the check for updates for every single container (each one had to timeout in order to go onto the next).

I have an interesting problem I am not quite sure how to debug.  I have tried a few versions of 6.4 and all ended the same way. At first I thought maybe it was my USB but it only does this with 6.4.

 

My server gets turned off fully nightly as some days it doesn't get used so no need to run it all the time and the hardware doesn't have a sleep option. 

 

More often than not when I boot with 6.4 my USB drive drops off during plugin install and I have to take it out and fix the errors on a windows box.  It doesn't do it every time but almost always.  I go back to 6.3 and never see this issue. 

 

I can't run diagnostics since it tries to write to /boot but I suppose I could look into the code and modify it but not sure what else it tries to pull.

 

I have manually pulled some logs and will add the syslog.  Any ideas on how else to debug this?

 

*edit - started a new thread for this also*

 

 

syslog

Edited December 29, 20178 yr by jjslegacy

18 hours ago, limetech said:

emhttp/shfs: yet another btrfs free space calculation method

 

Seems to be much better, at least in a known situation where it was wrong previously, e.g., a 3 x 32GB raid1 pool:

 

before:

 

now:

 

3 minutes ago, jjslegacy said:

My server gets turned off fully nightly as some days it doesn't get used so no need to run it all the time and the hardware doesn't have a sleep option. 

 

Are you shutting down with the webUI?

1 minute ago, trurl said:

Are you shutting down with the webUI?

 

 

I use the dynamix sleep plugin to do it automatically.

Just updated, will report anything I find!

2 hours ago, Caedis said:

Now all we need is the ability to start libvirt before the docker daemon (i.e start VMs before dockere containers).

 

1) Why?

2) If we do that, who is going to post, "Hey now that you start VM's before Docker, I'm seeing <fill in the blank> issue now!"

10 minutes ago, limetech said:

 

1) Why?

2) If we do that, who is going to post, "Hey now that you start VM's before Docker, I'm seeing <fill in the blank> issue now!"

 

I was saying on the lines of an advanced option that would allow the order of execution in emhttpd to be changed.

I have not yet tested booting speeds on the new RC to see if the removing of dockerupdate.php when Docker is started with 0 internet access will cause each one to run until it timesout while trying to update, so that is probably all that was needed.

Since docker just released v17.12.0-ce

 

Will this make into unraid 6.40 or will be a point release after?

The Terminal! The Terminal! Thanks.

 

Upgraded without problems.

- Updated from 6.3.5 without incident

- All dockers work as before

- All plugins work as before, with sole exception of server-layout, which was fixed with a `sed` tweak

- Terminal works great, nice feature!

- Holding off on the https webgui and encrypted drives - excited for both, but running base 6.4 features before trying the new stuff

 

Since it is looking more and more like the RC series is coming to an end I had a question about moving to 6.4. If I use a 4Kn drive as a second parity drive and have to downgrade back to an earlier release, what will happen? I assume the array will still work with the single parity drive it can recognize. If later moving back to a 6.4 release will there be any conflict with the now out of date original 4Kn parity drive?

Edited December 29, 20178 yr by ssb201

11 hours ago, johnnie.black said:

 

Nano isn't working correctly on the terminal for me, when scrolling using the arrow keys it skips around.

 

After opening Terminal but before invoking nano, type this:

 

export TERM="linux"

I think that should work & we'll auto-add that in next release.

Call Traces are back when starting my Wi ndows VM.

 

servernas-diagnostics-20171229-1737.zip

7 minutes ago, greg2895 said:

Call Traces are back when starting my Wi ndows VM.

 

servernas-diagnostics-20171229-1737.zip

 

But VM works correctly right?

7 minutes ago, limetech said:

 

But VM works correctly right?

Everything appears to be fine.

1 hour ago, limetech said:

I think that should work & we'll auto-add that in next release.

It worked ?

9 hours ago, Dazog said:

Since docker just released v17.12.0-ce

 

Will this make into unraid 6.40 or will be a point release after?

 

We're sticking with v17.09.1 (released on 2017-12-07 to include recent bug fixes) for unRAID 6.4.

2 hours ago, eschultz said:

 

We're sticking with v17.09.1 (released on 2017-12-07 to include recent bug fixes) for unRAID 6.4.

 

Thank you for the info.

 

 

Upgraded with issue, only item is that the terminal does not show up in black and white themes only azure and grey themes, has anyone else seen this?

9 hours ago, ssb201 said:

Since it is looking more and more like the RC series is coming to an end I had a question about moving to 6.4. If I use a 4Kn drive as a second parity drive and have to downgrade back to an earlier release, what will happen? I assume the array will still work with the single parity drive it can recognize. If later moving back to a 6.4 release will there be any conflict with the now out of date original 4Kn parity drive?

 

The array won't start if you have a 4Kn disk assigned to any slot and an earlier version of unRAID. It fails silently - no error message, no log entry. (See here) So you'll need to unassign it from the second parity slot in order to start the array. When you later move up to 6.4 you'll be able to reassign the disk and start the array and then, of course, the parity will be rebuilt on that disk.

Edited December 30, 20178 yr by John_M
Added reference to my earlier experiment