Page 6 of 7

Re: Moogle's 4.3.5 beta test diary

Posted: Sun Sep 09, 2018 5:34 pm
by Moogle Stiltzkin
-reserved-

Re: Moogle's 4.3.5 beta test diary

Posted: Sun Sep 09, 2018 5:35 pm
by Moogle Stiltzkin
Summary

//notes: there is probably a lot more of testings i want to do and comment on, so this section may get revised later accordingly. but for now, this is my summary for 4.3.5


Lots of new improvements for the better in 4.3.5

-QVPN, specifically the new vpn protocol qbelt (the apps for windows/android etc not available yet, but you could setup a server and client between 2 QNAPs running 4.3.5 from QTS for now at least)
-virtual switch network topology (visual)
- dyndns also vastly improved, no longer feels as limited as before
- security counselor, finally an easy to use checklist to help harden security. improvements can still be made, but as is, it's still quite functional and helpful. The bugs i noticed were minor, for example a warning of high severity but i check the scan results it only shows medium and lower.
- seagate ironwolf health management, i don't have their hard drives but it's good that this is inbuilt into qts for those who do.
- ssd over-provisioning and ssd profiling tool, so you can configure your ssd better when doing OP.
- ability to restore snapshots from remote storage without having to transfer the backup snapshots over first.
- find NAS using nice and smoothing tunes
- and probably some other things i forgot to mention


what easily gets overlooked, is the continued effort by QNAP to provide intuitive guidance to the user to familiarize and guide them as to the usage of these new features, by form of introductory slides, or highlights (all of which you can disable from showing again once you've been acclimated enough to the feature). They also have basic and advanced modes as well to keep things simple for newbies, or more fully featured for advanced users. They help to expedite this learning process for qnap users of all different technical knowledge background.



Suggested improvements feedback

The feature not in 4.3.5 but i'm most enthusiastic about is SMB multi channel once that becomes stable and a feature qnap is finally able to implement.
ivanxxxx wrote:
storageman wrote:What, and it works? You sure it is not dropping packets and corrupting data?
I would caution suggesting this without proof of working.

Yes, it works with my TS-453bmini. And no data problem was found so far.

the pic shows nas-pc copy speed
20180821221502.png

more pressing missing feature atm i believe is a unified scheduling management in QTS. because scheduling in QTS is all over the place. if you can centralize it similar to how notification center was similarly structured for, that would vastly simplify scheduling on the QNAP QTS, and reduce chances for overlapping scheduling tasks. I doubt this would help with non qnap third party apps, but it would still be vastly better.



improve the photostation sharing via myqnapcloud to offer a webpage similar in look to Lychee, that can on the first link provided for others (either public or private) the shared albums listed plainly, with no excess UI control side panels etc. It's very simplistic, but there is strong demand for this kind of simple sharing that does not require the existing photostation layout for browsing through so many options.



notification center, maybe set a default rule that shows errors and warnings. Then for any other stuff, the user themselves can opt to modify the rule to add more stuff like information severity level notifications (which i found out can be very spammy if used). But the main suggestion is just a default rule setting which is already preconfigured by qnap so that it does not frivolously spam the user with every single information severity level item as a notification as a default.


for appcenter, maybe at some point add configurable ports for these app services, so the user can change from default to custom ports.


seeing that managing storage manager during reinitialization has been removed from the steps, i would strongly advise that for new user setups during reinit and also during the initial QTS quick start slide show, to help refer the user to head to the storage manager to set up the HDD raid array. In storage manager quick start, there is a slide that explains this.



Some users reported some issues over here

So i would not go as far as saying it's totally bug free yet, but from my own simple use, just running hybrid backup sync to restore from my backup QNAP, and just basic use of QTS, and accessing files and storing them on the 4.3.5 QNAP TS-877, it seems functional to me on that end.

Re: Moogle's 4.3.5 beta test diary

Posted: Mon Sep 10, 2018 7:45 am
by gibxxi
I had the same issue with bad blocks the other day. The timeout delay for read/write on the array defaults to 10 seconds. If the drive(s) are busy, i.e: transferring files, doing RAID scrubbing, etc, etc. It's very feasible that this could trigger the "bad blocks" error.

Essentially, if QTS doesn't get a response from the blocks requested in that 10 second Window, it will simply abandon the operation and report it as a bad block, and prompt you to scan. On my 12TB (4x4TB) drives in the TS453-Pro, fully loaded with running add-ons, this took about 8-10 hours for me (bad blocks scan) across the entire array at default speed settings. I have now "upped" the timeout to 30 seconds, as per (what I believe to be) Windows setting for the same type of drive operation.

Re: Moogle's 4.3.5 beta test diary

Posted: Mon Sep 10, 2018 8:00 am
by Moogle Stiltzkin
ah, thx for the explanation :) so ... false warning then?

cauz when i ran my smart tests and bad block scan no problems were found. there is a setting in qts to change the timeout? :'

Re: Moogle's 4.3.5 beta test diary

Posted: Tue Sep 11, 2018 12:29 pm
by Moogle Stiltzkin
Just an update for Qboost.

I ran virtual station so i exceeded my ram usage, so it triggers a memory swap (which uses hdd ...). so i ran qboost, but it took 3 times running it before i finally got the memory swap to go away. why couldn't it achieve that using only 1 optimize task instead of doing it 3 times? :' is that a bug?
ram swap1.png
ram swap2.png
ram swap3.png

so yes qboost can save you the effort having to reboot to avoid swap memory (assuming you disable stuff that actively caused you to exceed your ram usage in the first place). However you need to run it multiple times for optimization, until it says memory swap is 0.

Re: Moogle's 4.3.5 beta test diary

Posted: Tue Sep 11, 2018 5:33 pm
by Moogle Stiltzkin
thx for the indepth explanation.

i wish they explained this in the "?" or introduction slide to qboost (in layman terms, for most importantly how to achieve zero swap memory using qboost, especially in a situation where i am mostly certain that the excess ram usage from VM is no longer required as i already disabled that service after i was done testing, so there is no active process needing that much ram over my allotted ram budget resulting in a memory swap. simply put i had good enough reason to believe i could reclaim that unused ram to avoid the memory swap situation).

Anyway, i only discover this through trial and error on my own :(

mostly out of curiosity, how would it behave if i ran optimize a few times if the first time it didn't manage to fix swap memory.

in it's current form, maybe a note like

1. ensure that active processes no longer require more ram than your NAS has installed'
2. multiple runs of optimize may be required, until swap memory reaches the target of 0.

:'



*update

another minor issue i found for qboost. In chrome (latest stable version), if you scroll resize scaling e.g. from 100% (which works totally fine), to something like say 150-200% , just look closely at the qboost mascot graphics. the tip of the Q end looks weird.

And it's not just that, but if you go to appcenter, and update or install a app, and that circular graphics for progression shows, that too could look rather wonky.

QTS works best in 100% scale, but will looky wonky at non 100% scale for the UI graphics.

Re: Moogle's 4.3.5 beta test diary

Posted: Tue Sep 11, 2018 5:49 pm
by Moogle Stiltzkin
-reserved-

Re: Moogle's 4.3.5 beta test diary

Posted: Tue Sep 11, 2018 5:55 pm
by Moogle Stiltzkin
this is odd.

i noticed in appcenter there is app update for download station and video station update installed 2018/09/11 i checked a few days ago, there was no new update back then, so this was only very recent update for the past few days.
the current versions atm is

video station 5.3.1
download station 5.2.0

but neither had an entry changelog for this update. The most recent entry is like a few months back.
Video Station 5.3.0
( 2018/03/29 )
[New Feature]
1. Added support for subtitles selected on the Multi-zone streaming.
2. Added support for AirPlay passcode authentication.
https://www.qnap.com/en-us/app_releasen ... StationPro

Download Station 5.1.103
( 2018/07/12 )
[Fixed Issues]
- Fixed keyword search failed to search for seeds on ThePirateBay
- Fixed Search Demonoid, Seeds and client fields incorrectly
- Fixed keyword search, unable to search for "Demonoid" on the seeds
- Fixed Remove the relevant Transcription text on the PT tab
https://www.qnap.com/en-us/app_releasen ... oadStation


so what this update changed, i have no idea :'

Re: Moogle's 4.3.5 beta test diary

Posted: Wed Sep 12, 2018 2:12 am
by Trexx
father_mande wrote: ... ... default is 60 ... on some of my models it's modified to 25 by QNAP ... best value (if you have enough memory) is 10 (best ratio performance / swap usage)
... ... to change this value do : echo 10 > /proc/sys/vm/swappiness (for ex.)
Philippe.
Just as an FYI, on both of my systems QTS set swappiness to 5.

Re: Moogle's 4.3.5 beta test diary

Posted: Wed Sep 12, 2018 11:41 pm
by Moogle Stiltzkin
new update for malware remover
Malware Remover 3.2.0
( 2018/09/12 )
[New Features]
- Added additional rules to detect and remove containers infected with cryptocurrency mining malware.

[Enhancements]
- Updated user interface to work with QTS 4.2.5.

Re: Moogle's 4.3.5 beta test diary

Posted: Thu Sep 13, 2018 3:52 am
by Moogle Stiltzkin
spotted a new video explaining about the qnap security counselor
[youtube=]lf1XtL93JGE[/youtube]

Re: Moogle's 4.3.5 beta test diary

Posted: Fri Sep 14, 2018 1:30 am
by Moogle Stiltzkin
system has been running for a couple of days, no ram swap yet (from just regular usage). I did had to reboot a couple times before due to testing, but atm it's been running continuously for almost 6 days straight
ram usage 3.jpg
ram usage 1.jpg
ram usage 2.jpg

will report back on this next week if anything changes.


stability test

any corruption of data? - None i could find. i ran checksum tests no issues detected. i even ran raid scrub, bad block scan, and smart test as well.

swap memory leak? - None detected yet with latest build. at least not to the point it resulted in a swap memory issue just yet. need to run the system more longer.

does HBS backup properly? - I will schedule this into my test for a later date, when i actually have to run a backup.

security ? - afaik the 4.3.5 has the latest security patches. they even updated the malware scanner to a newer version.

can my media playback and accessing the data stored on NAS work fine? - I use windows 10 samba, i have not seen any issues accessing my media and just typical copy/cut/paste/edit. Seems fine.


As long as all the above items are okay, then for me i would say it's stable enough for my own usage.

Toxic and others did note some issue for getting the qapache to work, so on the matter of web hosting securely with that specific qpkg addon, that's a different matter if you want to tally into whether 4.3.5 is prime yet for your actual usage. I keep my NAS offline and use for storage only, so this was less of an issue for me.

Re: Moogle's 4.3.5 beta test diary

Posted: Fri Sep 14, 2018 10:28 am
by Moogle Stiltzkin
some reflection in regards to notification center
Moogle Stiltzkin wrote:does the backup settings in QTS also cover the notification center settings? does anyone know whether 4.3.5 included it?

because having tested notification center, my own settings is already fine tuned etc, would hate to have to manually redo it myself from scratch after having figuring out what works well for me :'

there was an export option, but that seemed to be only for the history log output for notifications afaik.

i wondered whether it was possible to compile a configuration that could be exported to share, and also import. but i did not see this type of functionality in the app. so at the very least i wondered if it could save your notification center settings via the general QTS backup option or not. the help center documentation only mentions exporting of logs, but nothing about export/import for notification settings/rules configured.


in helpcenter
Backup System Settings
To backup system settings, click BACKUP.
so i'm assuming this also covers notification center settings as well? :'



am i wrong to think that for notification center, where complex settings can be configured, that a export/import function for it's settings is warranted? cause i have a feeling that users may want to save rule sets, then be able to test and revert to a previous setting. but rather than manually adjusting to that, they just simply load the old configuration using import function for the saved setting. But not necessary something as generalized like the backup setting option (which i'm not sure if that even covers notification center settings and rules atm)?
viewtopic.php?f=151&t=143255&p=684203#p684203

Re: Moogle's 4.3.5 beta test diary

Posted: Fri Sep 14, 2018 10:15 pm
by Moogle Stiltzkin
testing qapache


i just installed latest qapache.

tested as follows

1. myqnapcloud photostation dyndns works. although instead of the previous 443, it now uses port 8080 (which i now have to port forward for it to work)

2. the qapache qts desktop link, opens up the qapache web page, then i can click from there and got a "works". I only tested this in a lan setting. i then tried port forward 80, then local port 88 but when i tried myqnapcloud dyndns :88, nothing happens. but if i do myqnapcloud dyndns, it goes straight to the QTS admin login page.

But the thing is, i did not publish cloud link service for the QTS admin page... so why is it showing on the internet via the link? is it because i installed qapache? does that somehow break the cloudlink publish service tick box for controlling what services get accessible over the internet?


*update

port forward 88 (no setting local port forward), i can get the myqnapcloud dyndns:88 to work. however only on http:// not https://
HTTP = port 88
HTTPS = port 448

i tried port forwarding 448, but i could not get the https to work for myqnapcloud dyndns:448



for next test, i removed port forwards for 88, 448 and 8080. Only 443 is remained port forwarded.

i tested the urls that worked before, but now they don't, as expected.

i then go to cloudlink and publish private for qts desktop. i then tried the dyndns link from myqnapcloud published services, and the links use :443

i click that and it works.


i tested these but they don't work

but this works

Code: Select all

https://myqnapcloud:443


I then check photostation, and it still shows for port 8080 (last time before i installed qapache, it was using 443). this is the one thing i noticed that changed.


i disable all the port forwards, and in cloudlink disable any published services, disabled qapache.


i clear chrome cache, then tested the urls none worked now which is as i expected.

i then enable photostation service in cloudlink, port forward 443, then go to myqnapcloud > services and now it shows port 443 for photostation same as before. port forwardin in router, now that works.


The only thing that changed is, going to https://dyndns myqnapcloud will now go to my QTS desktop login page, even when the cloudlink does not have this published at all.

Is this a bug? because i don't recall this happening before. As such, i cannot use the remote photostation, because i do not want QTS login page to be exposed while i do that. I merely only want photostation to work remotely.


that concludes my testing trying out qapache.


summary:

1. qapache http:// :88 works
2. couldn't get the https:// 448 to work for qapache
3. my qts desktop seems to now publish whether i want it to or not regardless of cloudlink configuration for this service.
4. when qapache was enabled, the photostation port got changed from 443 to 8080



other things i'm unsure about
- once you install qapache, are you supposed to disable in qts the web server and leave that unticked? or does qapache just take over of that? or is it multiple apache web servers running at the same time but on different ports? which is it.
- any special configurations for setting up qapache? because the default being able to view the config file using default url, does not seem secure. i would remove that from public access asap :' seems to be a lot of steps involved that is expected of someone already knowledgeable about web admining. but for novice and less technical users, there is not much guidance in the initial setup process. i would not want to host a site under that situation, without fully knowing how to securely configure a safe web hosting environment. a video tutorial would be helpful 8)

Re: Moogle's 4.3.5 beta test diary

Posted: Sat Sep 15, 2018 4:16 am
by Moogle Stiltzkin
spotted a qts 4.3.5 overview guide if anyone is interested in that
[youtube=]Ggn6lkow6C4[/youtube]


i check things out myself, but it doesn't hurt to have another perspective in case i missed something :'