NLS
-
Posts
1415 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by NLS
-
-
14 minutes ago, JonathanM said:
How is it urgent? There is a workaround.
Not a showstopper, data loss, or server crash.
This is why I changed the priority.
But before finding the solution myself, it was urgent at least to me, as NethServer (which is a full small business server, so potentially important to some of us) was not running. No mail etc.
-
Changed Status to Open
Changed Priority to Other
Pity nobody actually reacted when priority was urgent.
-
NEWER UPDATE which seems to point UNRAID as the probem.
Attempting to install fresh does NOT find any usable disk and does NOT find any usable network!
Seems that with 6.12, CentOS7 does not recognise ANY virtio device!
So I changed vdisk to be SATA and network to be e1000 and it works!
Definitely an issue!
-
The issue seems to be UNRAID.
Aside from the attempts I have made (I can provide the details) to recover OS booting, I now tried a fresh install.
(the same I used when I originally set up NethServer inside UNRAID years ago)
The installer crashes, because seemingly of network issues, as it reports "couldn't open file /tmp-network-include".
Back on the existing installation, note that the qcow2 image itself is fine, I managed to connect it to UNRAID (host), see the partitions inside (including the lvm partitions root and swap), I managed to mount the root partition and see the files inside.
So the disk image is ok.
The problem started right after 6.12 reboot.
Something changed in kvm/libvirt/qemu/uefi that prohibits NS7 from running.
-
I hope 6.11 to 6.12 transparently migrates everything like always.
With all these fundamental changes, I wonder if 6.12 is the correct versioning. I can easily be named 6.20.
I am still confused on a few things:
1) Functionality of UNRAID WITHOUT using the new ZFS features. We are not loosing anything or getting forced to re-create anything?2) Functionality of UNRAID WITH new ZFS features AND ability to migrate easily (we need extra disks?).
3) Primary/Secondary storage vs. Array and Cache... I am still confused which is which and if anything really changes aside of the names (AND things really migrating the old to new).
-
Well obviously something is wrong...
(I now set it to "no", saved and then back to "yes" and saved again in case something got "stuck"?)
EDIT: Tried the above and rebooted.
AGAIN server started with the array offline and just needed me to click "start array".
This is weird and serious.One change I did a couple of days ago was this. I edited my syslinux config (using UNRAID GUI), and modified two entries:
label Unraid OS kernel /bzimage append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 label Unraid OS GUI Mode menu default kernel /bzimage append initrd=/bzroot,/bzroot-gui nvme_core.default_ps_max_latency_us=0
...because of a firmware issue with my M.2 cache.
(I added nvme_core.default_ps_max_latency_us=0)
But I don't see how this could be related...
EDIT #2: HOLD THE PRESS!
Cancel the above edit. The "turn setting off and then on and reboot" actually fixed the hiccup.
The problem right above was because some disk cable was needed reseating.
In less words:
System somehow mixed up the array auto start setting, after my last updates and edits.
It displayed "auto start yes" but did not autostart.
I switched to "auto start no", "apply", then back to "auto start yes" and "apply" and this seems to have reset the setting fine.
-
-
One more update and (somewhat) solution.
I rebooted. This showed the two plugins as needing an update (properly) and clicking to update them, updates them.
So something was stuck.
If you ask me, there is a bug somewhere and rebooting in not always a viable solution on a linux based system in production.
-
An update on the (still open) issue.
Community Apps DID update, because when going to "Apps" tab, it just reports that it is oudated (up in the title).
So clicking that, it DOES update.After that, going to plugins shows only two pending (Dynamix File Manager and Unassigned Devices), which I ave no way of changing their status OR removing (to re-add)!
So I am in a deadlock!
Again, clicking update all plugins, just pops that language pack thing I report above and nothing else.Also note, that the issue is present over more than one computers (and browsers), so it is not related to any stuck cookies or anything like that.
-
I say it right in the subject.
Yes I am in 6.11.3 since yesterday I think.
Didn't have that issue with older version.
No I don't see any banner in red (like an error?)... neither anything up in the top of the page (the new notification thing).
Also (don't know if it is related) scanning my dockers for updates takes FOREVER (several minutes - if it ever finishes).
Also note that the server is fresh from reboot (I rebooted for an unrelated reason).
-
Thanks for RC4.
If I can "cast a vote", I am against the new # links to menu items (that hide the proper URL path), because I can no longer use middle-buttun to add a new tab to another unRAID dashboard page.
(for example allow it to scan for plugin updates in a patch, but still see the main dashboard in another tab)
-
2
-
-
Not sure why RC cycle takes sooooo long this time around.
Wonder if they are waiting for something specific, or there is an issue that cannot yet be resolved (or reverted)... -
Why RC3 is not "open" for so long that is available?
In fact 6.10 should have probably be released already.Is there some serious issue pending?
-
1
-
-
Well log bar in dashboard does show 100%.
Attached are my diags.
root@quasar-ultima:/var/log# ls -l total 75236 -rw-r--r-- 1 root root 24200 Nov 11 09:21 Xorg.0.log -rw------- 1 root root 0 Oct 19 00:05 btmp -rw-r--r-- 1 root root 0 Apr 28 2021 cron -rw-r--r-- 1 root root 0 Apr 28 2021 debug -rw-r--r-- 1 root root 70702 Nov 11 09:20 dmesg -rw-r--r-- 1 root root 8192 Nov 22 22:40 docker.log -rw-r--r-- 1 root root 0 Feb 13 2021 faillog -rw-rw-rw- 1 root root 618 Nov 11 09:21 fluxbox.log -rw-r--r-- 1 root root 0 Apr 8 2000 lastlog drwxr-xr-x 3 root root 120 Nov 11 09:22 libvirt/ -rw-r--r-- 1 root root 4096 Nov 23 00:20 maillog -rw-r--r-- 1 root root 0 Nov 11 09:20 mcelog -rw-r--r-- 1 root root 0 Apr 28 2021 messages drwxr-xr-x 2 root root 40 Jun 15 21:38 nfsd/ drwxr-x--- 2 nobody root 80 Nov 13 04:40 nginx/ lrwxrwxrwx 1 root root 24 Oct 19 00:06 packages -> ../lib/pkgtools/packages/ drwxr-xr-x 5 root root 100 Nov 13 02:09 pkgtools/ drwxr-xr-x 2 root root 600 Nov 22 16:14 plugins/ drwxr-xr-x 2 root root 40 Nov 11 10:18 pwfail/ lrwxrwxrwx 1 root root 25 Oct 19 00:05 removed_packages -> pkgtools/removed_packages/ lrwxrwxrwx 1 root root 24 Oct 19 00:05 removed_scripts -> pkgtools/removed_scripts/ lrwxrwxrwx 1 root root 34 Nov 13 02:09 removed_uninstall_scripts -> pkgtools/removed_uninstall_scripts/ drwxr-xr-x 3 root root 160 Nov 11 09:21 samba/ lrwxrwxrwx 1 root root 23 Oct 19 00:06 scripts -> ../lib/pkgtools/scripts/ -rw-r--r-- 1 root root 0 Apr 28 2021 secure lrwxrwxrwx 1 root root 21 Oct 19 00:06 setup -> ../lib/pkgtools/setup/ -rw-r--r-- 1 root root 0 Apr 28 2021 spooler drwxr-xr-x 3 root root 60 Oct 11 19:01 swtpm/ -rw-r--r-- 1 root root 0 Nov 23 02:23 syslog -rw-r--r-- 1 root root 70582272 Nov 13 04:37 syslog.1 -rw-r--r-- 1 root root 6334751 Nov 12 03:22 syslog.2 -rw-r--r-- 1 root root 0 Nov 11 09:20 vfio-pci -rw-rw-r-- 1 root utmp 7680 Nov 11 09:21 wtmp root@quasar-ultima:/var/log# du -h -d 1 /var/log 0 /var/log/pwfail 0 /var/log/swtpm 20K /var/log/samba 0 /var/log/plugins 0 /var/log/pkgtools 55M /var/log/nginx 0 /var/log/nfsd 20K /var/log/libvirt 128M /var/logLooks like syslog is filling up the space?
I deleted syslog files and the VM fired up ok.But WHO is filling syslog and why syslog is not managed some way to not fill up the quota of the directory?
-
32 minutes ago, Squid said:
Hard to say exactly without more detail. Depending upon what the error was on the docker run command that would have showed up, the app could have simply refused to start or went and became orphaned (it will show up under advanced view)
I realize I provided no logs or anything to help.
Too late to check.
If it happens again, I might look deeper.My post above is mostly a pointer to an incident in case this happens to anybody else.
-
Weird thing just happened.
Among the many containers I have (although I have most stopped, 5-6 run all the time), I have "ddns-updater".(note this issue doesn't look to source from the container itself, but more from the docker backbone, this is why I report it here)
This container has a web interface only for info (to see if ddns registration is OK) and the configuration itself is during the container install including a simple manually edited file (ddns login details).Anyway, I saw the container running ok and casually clicked to see the web interface and see if i changed public IP (something that works and I have done before).
It reported that it cannot show me the web page.I naturally clicked Edit to see the container configuration in case I have new web port conflict or something. It didn't (the port was unique).
So I closed the Edit (DID NOT press to delete anything or even to update the container) to return to my dashboard and to click the "web" again to see if it was just a little "fart" from my server.
ONLY I COULDN'T FIND THE CONTAINER in the list!
I checked the dedicated docker page, not there.
So I went to apps and found it again. It didn't show as installed.I installed again with same parameters (I didn't even check if my manually edited file was in position, because I didn't delete it anyway)... it installed fine and run fine.
I clicked the web interface. Now it was working AND it even read my config file (and possibly it's own logs from previous install) as it reported my public IP is registered ok and hasn't changed for so many days.
What happened??????How can a container just disappear from existence?
-
...and it stopped working again.
I didn't do anything.
Damn.
I may need to make this reset into a script.
-
1 hour ago, bonienl said:
Because people like to run their own web server.
And this cannot be reused?
-
Yes this worked. Thanks.
Irrelevant:I didn't even know unRAID has nginx.
Why there are nginx containers for unRAID then... -
I understand, yet it is not possible right now.
I know this is RC but still my server is "production" (@home), so I cannot casually reboot it.
Even if I do, I cannot keep it in safe mode (no plugins) for days just to see if I can replicate the issue.
Last time it took 11 days between the two times this happened.
So again, is there a way to "reset" the web interface without rebooting the server?
(it will be interesting to see if this solves it anyway)
-
No I don't know how to replicate the issue. It just happens "some times" (in RC2).
I haven't connected this to anything I do.
NOTE that when this happens, it happens on every computer I access the dashboard from including the server itself!
Is there any service I could restart instead of rebooting the whole server?
-
Safemode for the browser? Or for unRAID?
I know the page will return to normal if I reboot the server, but will not reboot for such a minor thing. -
It happened again!
I think it might be related to adding or removing containers... I don't know.
Third row is again empty.
-
1 hour ago, johnwhicker said:
As I keep reflecting on your answer and position I actually don't like your tone and the way you threat you customers at all. You're the opposite of humble or grateful for our business / $$$ and you show no intention to listen or to find a work around. Is pretty much my way or the high way. Business 1:1 if I may, this tone of yours, one day will karma right back at you. I think I already know the outcome of this request or conversation so I give up but not before calling you out on this as I really really DON't LIKE IT...... Just for the record and for others to see
Since you mention "for others to see", I take it as giving me right to comment (after all it IS in a public forum). So let me comment on this after reading your original post too.
1) Disclaimer: I am not taking the side of Limetech. I don't care. I had my own rough times in the past (with Tom too IIRC)... many years ago. Don't even remember why any more. Back then I "voted" with my decision. I stopped using unRAID for years. Yet I returned because it became what I dreamt it should be before I stopped using it. So being first and foremost a consumer, not a fanboy nor a hater, I just returned. My original Pro license waited for me patiently.
2) Since you are talking about "tone"... Your tone in your first post and this post is quite a Karen. You are only ONE customer. Who made you our representative and the right to speak for us? Who told you we want this removed (even if we don't use it, I don't either). It doesn't bother me. It just stays there, who cares.
3) I don't see any threat whatsoever by LT. Maybe you mean "treat", but still, I don't see an issue.
4) LT is a business, as you said. They make things, we buy them, they support them indefinitely ON the price we originally bought them (no service fees). So why would they be grateful, or would we be grateful? $$$ = product. And I bet you have the product already. It is a transaction - as simple as that. Yet, they stand by their clients all right and do it for years (and this is not proven by removing something nobody else asked to remove than entitled-you).
5) Also, since they are a business, it is in the end their choice if they want to actively promote a new feature (their "cloud" system) if it is not too intrusive. So that login up in the corner and the OPTIONAL plugin, is not what I would call "intrusive".
6) Nobody is forcing you to update unRAID to next version. Stay on the current one. Remove unRAID for all we care.
7) If this login button and menu is (or was) a real problem, I am sure someone will step in with a tiny plugin (like the one that widens the interface for super-wide screens), that removes it. Or you can try making such a plugin.
8 ) Back to tone. I am sure if your original post was something like "this thing on the top right about logging in... could you please make hide-able, maybe by a toggle in the settings in some future version, for us OCD people?". This possibly would get a better reply.
Cheers.-
5
-
Serious issue with edited containers!
in Stable Releases
Posted
I can reply to my own bonus question:
If I edit the template and change default app data path to the correct one (i.e. /mnt/user/config to point to /mnt/user/appdata/technitium-dnsserver/config/), then I can add an extra path (I named it app data 2) and point /mnt/user to /mnt/user/appdata/technitium-dnsserver/. This solves the issue and the container can now auto-update!
(if I don't add the first path, the container doesn't assume that /mnt/user/config is under /mnt/user as it was supposed, but instead does NOT make it a bind path at all and points to the wrong path).
MY SOLUTION DOES NOT SOLVE THE BUG THOUGH! This is why I don't close this report.
I mean, I corrected the issue, so I don't hit the bug, but the bug is still there and can probably hit others.
The bug is that if container after update has an issue, something removes it from the container list!
I suspect the coolpit is somewhere in the update script where the script removes the "old" container, before verifying that indeed the "new" one can be deployed. If the deployment fails, we are left with a removed container!