SHOUTcast DNAS 2 (Build 29) 07/31/2011

[MikeRiverra]

Originally Posted by DrO

-daz

Hi Dro,

I've sent you one PM regarding one auth hash, please help me ... because my station is down since yesterday and i'm loosing listeners ...

I don't know what happened, but now it does not recognize my auth key for one of my stations.

Later Edit: sorry for posting here this problem, I have solve it right now by searching the answers on forum

Best Regards,
Cosmin

[DrO]

MikeRiverra: i'll check out your pm's in the next few hours (along with all of the other ones i've received from being on holiday all of last week - had hoped my signature change made that obvious).

---------------------------------------

@anyone else who posted in this thread in the last few days: the posts made by / relating to the user 'pools' have been removed. said user has a lifetime forum ban (*) (and i will not personally help after previous run-ins) and should not be replied to unless you're happy to do so privately. and just to note, this user has caused the same issue on other forums, even causing the codemasters forum to stop accepting new user registrations for a while due to his anti-social behaviour.

(*) the only reason for keep this account alive is bryan007/pokemons/pools/insert 100+ other ban evasion, will just keep posting / making new accounts and wasting everyone's time - hence one of the reasons there is no specific eta on a new v2 DNAS release.

-daz

[rsg]

Hello,

I have been experimenting with the 64-bit V2 DNAS and Transcoder 2. I am able to broadcast and things will generally run smoothly - that is until people begin to connect from external IPs, which then crashes the server. The crash, however, is never immediate, and I have been unable to finger the culprit.

I do not believe it is my ISP, as V1 works fine.

I do not think it has to do with the audio files, as I ran through a long playlist with V2 yesterday while connected via 127.0.0.1 with Winamp and there were no problems.

I do not think it is the transcoder because, again, no problems with V1 DNAS + transcoder 2.

I have tried a great number of config options and these made no difference.
The only thing that appears to be somewhat related is that the crashes seem to begin when people connect with the SHOUTcast web player. I have spent days reading through the forum and numerous posts, as well as Googling the tips of my fingers off, but all to no avail.

I will attach the transcoder and server logs for the last crash event.

Thanks

Win7 64-bit/Intel Core II Duo/6 gig ram

[DrO]

rsg: can you confirm what versions of the tools you are using please (i.e. that you're on DNAS build 29 and Transcoder build 54 - the current versions at the time of this reply).

i assume you are referring to the DNAS crashing? also as you're using Win7, i'd hope there's something in the system event logs about the crash since there's nothing of use in the log file to do with any sort of crash.

-daz

[rsg]

Hi DrO,

DNAS build 29 / Transcoder build 54 affirmative.

Yes, it appears to be the DNAS crashing first.

There are a number of items in the system event logs pertaining to both the DNAS and Transcoder. I will go through and see if there is anything revealing. However, scanning such things is not my area of expertise, so to speak. Is there anything in particular that you might want me to send/post?

I will be trying a few other ideas in the meantime.

Thanks for your reply - I know you are busy.

Cheers,

rsg

[DrO]

rsg: pm sent with a link to a test build to try out.

-daz

[WHITELIONX]

Nevermind I got everything working as to exactly how I want/need it to work

[GeorgeT]

Hi I have a problem, the client cannot connect to the server. The program writes a bad password Even if the password is correct. When you enter the ip and port to the browser indicates that the server is ok. What is it?
Sorry for my english :-)
sc_serv.log

2012-01-03 00:19:35 I msg:[MAIN] Logger updating log file to use
2012-01-03 00:19:35 I msg:[MAIN] Loaded config from sc_serv.conf
2012-01-03 00:19:35 I msg:[MAIN] Calculated CPU count is 2
2012-01-03 00:19:35 I msg:[MAIN] Starting 2 network threads
2012-01-03 00:19:35 I msg:[MICROSERVER] Listening for connection on port 9040
2012-01-03 00:19:35 I msg:[MICROSERVER] Listening for connection on port 9041
2012-01-03 00:19:49 I msg:[SRC 92.243.xxx.xxx:31433 sid=1] SHOUTcast 1 source connection.
2012-01-03 00:19:49 E msg:[SRC 92.243.xxx.xxx:31433 sid=1] connection denied. Bad password.
2012-01-03 00:19:58 I msg:[SRC 92.243.xxx.xxx:31435 sid=1] SHOUTcast 1 source connection.
2012-01-03 00:19:58 E msg:[SRC 92.243.xxx.xxx:31435 sid=1] connection denied. Bad password.
2012-01-03 00:19:59 I msg:[SRC 92.243.xxx.xxx:31438 sid=1] SHOUTcast 1 source connection.
2012-01-03 00:19:59 E msg:[SRC 92.243.xxx.xxx:31438 sid=1] connection denied. Bad password.
2012-01-03 00:20:00 I msg:[SRC 92.243.xxx.xxx:31440 sid=1] SHOUTcast 1 source connection.
2012-01-03 00:20:00 E msg:[SRC 92.243.xxx.xxx:31440 sid=1] connection denied. Bad password.
2012-01-03 00:20:00 I msg:[SRC 92.243.xxx.xxx:31442 sid=1] SHOUTcast 1 source connection.
2012-01-03 00:20:00 E msg:[SRC 92.243.xxx.xxx:31442 sid=1] connection denied. Bad password.
2012-01-03 00:20:00 I msg:[SRC 92.243.xxx.xxx:31444 sid=1] SHOUTcast 1 source connection.
2012-01-03 00:20:00 E msg:[SRC 92.243.xxx.xxx:31444 sid=1] connection denied. Bad password.
2012-01-03 00:20:01 I msg:[SRC 92.243.xxx.xxx:31446 sid=1] SHOUTcast 1 source connection.
2012-01-03 00:20:01 E msg:[SRC 92.243.xxx.xxx:31446 sid=1] connection denied. Bad password.

[DrO]

well the DNAS keeps getting the wrong password from the source which is trying to connect (clarification of what you are using as the source would be useful), so either it is wrong in the source you're using or you've found a new bug in the DNAS (which i doubt).

-daz

[GeorgeT]

Originally Posted by DrO

well the DNAS keeps getting the wrong password from the source which is trying to connect (clarification of what you are using as the source would be useful), so either it is wrong in the source you're using or you've found a new bug in the DNAS (which i doubt).

-daz

I uninstalled the shoutcast server, cleared the registry and deleted the remaining files, but it still writes bad password :-(

[DrO]

i can only go on what you've posted and without _any_ of the information i've asked for in my prior reply, there is _nothing_ i can do to aid in tracking down your issue which i still think is due to the wrong details being entered in the source (whatever that is) that you are using.

-daz

[GeorgeT]

I'm sorry :-) So I use Virtual DJ 7 PRO

sc_serv.conf

code:
;DNAS configuration file

;Made with the SHOUTcast 2 Configuration Builder



password=f3ntM2Cx

adminpassword=administrator

portbase=9040

requirestreamconfigs=1

logfile=sc_serv.log

w3clog=sc_w3c.log

publicserver=never

banfile=sc_serv.ban

ripfile=sc_serv.rip



streamid=1

Sorry, but I do not understand. What source? :-(

[DrO]

Originally Posted by GeorgeT

Sorry, but I do not understand. What source? :-(

Originally Posted by GeorgeT

So I use Virtual DJ 7 PRO

that would be the source you're using. Not one i'm frequented with so i'd have to assume that it's working as a v1 source.

from the config file, it should just require 'f3ntM2Cx' to be set as the password and that should be it. if not, remove the requirestreamconfigs=1 part from the file as that will lessen some of the checks made when a source connects.

-daz

[dz0ny]

Hi, am using monit to monit shoutcast server service status for client. However when performin http request to stat file I've got error indicating that http response is malformed.

HTTP error: Illegal Content-Length response header 'Content-Length:549'

Using browser it works just fine(no error there).

Host uses SHOUTcast Server v2.0.0.29/posix(bsd).

monit code

check host shoutcast with address stream.xxxxxxxxx.xx
if failed url http://stream.xxxxxxxxx.xx:8000/stats?sid=1
and content != ".*<STREAMSTATUS>0<\/STREAMSTATUS>.*"
timeout 10 seconds for 1 cycles then alert

status page xml is(its nonexistent stream for purpose of testing, however it also does't work for proper stream)

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?><SHOUTCASTSERVER><CURRENTLISTENERS>0</CURRENTLISTENERS><PEAKLISTENERS>0</PEAKLISTENERS><MAXLISTENERS>60</MAXLISTENERS><UNIQUELISTENERS>0</UNIQUELISTENERS><AVERAGETIME>0</AVERAGETIME><SERVERGENRE></SERVERGENRE><SERVERURL></SERVERURL><SERVERTITLE></SERVERTITLE><SONGTITLE></SONGTITLE><NEXTTITLE></NEXTTITLE><STREAMHITS>0</STREAMHITS><STREAMSTATUS>0</STREAMSTATUS><STREAMPATH>/stream/2/</STREAMPATH><BITRATE>0</BITRATE><CONTENT></CONTENT><VERSION>2.0.0.29 (posix(bsd))</VERSION></SHOUTCASTSERVER>

[DrO]

never having heard of monit before, i can only assume from what you've posted it doesn't like how things are returned since if it's ok in a browser then it cannot be completely broken. would probably say this is more something to direct towards monit to better advise than here (as it's not something i'm in a position to look into for some time to come).

-daz

[endrogeri]

Hi!

Please help me, I have Segmentation fault at more then 500 user. Last msgs this:

2012-02-24 11:54:05 D msg:[YP2] pvt_update key=1
2012-02-24 11:54:05 D msg:[YP2] pvt_update key=2
then connect and die:
2012-02-24 11:54:05 I msg:[YP2] Connecting to yp.shoutcast.com

I use linux, stable debian version. I can send debug if you need. 64bit version, 1.8 core2duo and 4gb ram.

[DrO]

all i can direct you at is the suggestions made in point #4 at http://forums.winamp.com/showthread.php?p=2790357#known (which is the first post of this thread...) and set the maxuser limit to ~500 and run a secondary DNAS instance until the issue is fully investigated and fixed (i.e. when i get the proper time to look into a fix for whatever is going on).

-daz

[DrO]

as people seem to have a complete issue with reading the log files and / or noticing the error (and warning) messages, i'm considering making the console output like in the attached screenshot (at least for the Windows builds - still need to sort out changes for the non-Windows builds).

my point really is, is this going to really annoy people (since it won't be able to toggled on/off) or is it actually going to make things easier to identify if there is a problem when using console output? since it passed the gf test as she's little knowledge about such things but at least recognised there was an issue even without knowing what things meant.

-daz

[MrSinatra]

do u mean a wrapper like v1 was? i liked the way i could watch connections in v1.

[DrO]

this is just showing the output shown in the Windows console window. i've no plans to bring back a v1 wrapper like the Windows build had. the emphasis now is more on using the web interfaces for the management and viewing of information about what is going on.

not saying there isn't a chance of an external wrapper but as i've not done linux gui programming in years, it's not too high up on things i want to work on since i'd prefer to provide something which is consistent across all platforms as is done with the v2 DNAs in it's console form now.

-daz

[zetaf]

am just curious, when can we see a stable release of this script?

[DrO]

what script?

-daz

[NitrofishRadio]

LOL @ DrO... Pretty stable once you get it setup correctly. My server does not come down unless I shut it down.

I did have some problems at first, but this was due to bad ID3 tags and invalid configuration. With the help of these forums and some pretty nice people, it's all sorted out and running rock solid delivering my stream.

[smfrockstation]

Originally Posted by GeorgeT

Hi I have a problem, the client cannot connect to the server. The program writes a bad password Even if the password is correct. When you enter the ip and port to the browser indicates that the server is ok. What is it?
Sorry for my english :-)
sc_serv.log

I found same error when I start DNAS 2 B.29 64bit

Shoutcast Log :
********************************
2012-06-20 17:09:15 I msg:[DST 61.63.39.74:59109 sid=1] SHOUTcast 1 client connection accepted. Java/1.6.0_29
2012-06-20 17:09:16 E msg:[DST 61.63.39.74:59109 sid=1] Socket error while waiting to send data. err=Broken pipe(32)
2012-06-20 17:09:16 I msg:[DST 61.63.39.74:59109 sid=1] SHOUTcast 1 client connection closed (1 seconds) [Bytes: 13032] Agent: `Java/1.6.0_29'
2012-06-20 17:09:16 I msg:[DST 61.63.39.74:59130 sid=1] SHOUTcast 1 client connection accepted.
2012-06-20 17:09:16 I msg:[DST 61.63.39.74:59129 sid=1] SHOUTcast 1 client connection accepted. Lavf53.13.0
2012-06-20 17:09:16 I msg:[DST 61.63.39.74:59131 sid=1] SHOUTcast 1 client connection accepted. NSPlayer/4.1.0.3856
2012-06-20 17:09:16 I msg:[SRC 61.63.39.74:59133 sid=1] SHOUTcast 1 source connection.
2012-06-20 17:09:16 E msg:[DST 61.63.39.74:59131 sid=1] Socket error while waiting to send data. err=Connection reset by peer(104)
2012-06-20 17:09:16 E msg:[SRC 61.63.39.74:59133 sid=1] connection denied. Bad password.

********************************

messages log :
********************************
Jun 20 17:09:16 metal kernel: sc_serv[7141]: segfault at 0000000000000000 rip 000000320dc60694 rsp 0000000042a4c7b0 error 4
********************************

Then my shoutcast will crashed and stopped. It crashed twice a day.
Please help !!!

My Machine > CentOS 5.x 64bit

[DrO]

/me bangs head on desk

smfrockstation: this has been covered in you previous thread -> http://forums.winamp.com/showthread.php?t=345581 though at least you've now provided actual information which confirms it as issue #6 from the known issues.

the fix is to block 61.63.39.74 by doing something like is described in http://forums.winamp.com/showpost.ph...90&postcount=5 until an updated DNAS is released.

-daz

[smfrockstation]

Thank you very much.
Now I have just blocked the ip 61.63.39.74 from iptables.

[nwgator]

It's done something like this for the past couple days... is it a metadata issue causing it to do this? The server connection isn't dropping when this happens.

Edit:

This is when using the most up-to-date version of sc_serv and sc_trans.

I looked in the sc_trans log as well, but there's not really anything of interest in there.

PHP Code:

AOL_logger::message&) Error writing to console - write issue
2012-07-20 21:42:41    D    msg:gotResponseRequest key=13 cmd=2
Response body=***91;
<yp version="2"><resp seq="1"><updatefreq>600</updatefreq><publicip>199.15.252.149</publicip></resp></yp>
***93;
Response code=***91;200***93;
2012-07-20 21:42:41    E    msg:virtual void AOL_logger::consoleLogger_element::log(const AOL_logger::message&) Error writing to console - write issue
2012-07-20 21:43:25    D    msg:***91;YP2***93; pvt_update key=15
<?xml version="1.0" encoding="utf-8"?>
<yp version="2">
<cmd op="update" seq="1">
<id>122123</id>
<authhash>HIDDEN</authhash>
<source>Promo Only</source>
<stats>
<listeners>0</listeners>
<avglistentime>0</avglistentime>
<newsessions>0</newsessions>
<connects>0</connects>
</stats>
<metadata>
    <title seq="1">The Cab - La La (Feelgud Remix)</title>
    <title seq="2">Shelly E. Johnson - All Things Beautiful</title>
    <title seq="3">Travis Ryan - Fearless</title>
    <title seq="4">City Harbor - Somebody Tell Them (Radio Version - Cold Ending)</title>
    <soon>Shelly E. Johnson - All Things Beautiful</soon></metadata>
</cmd>
</yp>
2012-07-20 21:43:25    E    msg:virtual void AOL_logger::consoleLogger_element::log(const AOL_logger::message&) Error writing to console - write issue
2012-07-20 21:43:45    E    msg:***91;YP2***93;  ***91;YP2***93;  Could not resolve host address yp.shoutcast.com Restarting in one minute
2012-07-20 21:43:45    E    msg:virtual void AOL_logger::consoleLogger_element::log(const AOL_logger::message&) Error writing to console - write issue
2012-07-20 21:45:05    E    msg:***91;YP2***93;  ***91;YP2***93;  Could not resolve host address yp.shoutcast.com Restarting in one minute
2012-07-20 21:45:05    E    msg:virtual void AOL_logger::consoleLogger_element::log(const AOL_logger::message&) Error writing to console - write issue
2012-07-20 21:45:30    D    msg:***91;SRC 199.15.252.149:50313 sid=1***93; Cacheable metadata received
2012-07-20 21:45:30    E    msg:virtual void AOL_logger::consoleLogger_element::log(const AOL_logger::message&) Error writing to console - write issue
2012-07-20 21:45:30    D    msg:***91;SRC 199.15.252.149:50313 sid=1***93; Cacheable metadata reset due to span change
2012-07-20 21:45:30    E    msg:virtual void AOL_logger::consoleLogger_element::log(const AOL_logger::message&) Error writing to console - write issue
2012-07-20 21:45:30    I    msg:***91;SRC 199.15.252.149:50313 sid=1***93; Got complete metadata message type=3902 ***91;780 bytes***93; id=1 span=1 content=
<?xml version="1.0" encoding="UTF-8" ?>
<metadata>
<COMM language="eng">Promo Only - www.promoonly.com - Distribution of this file is strictly prohibited.</COMM>
<TALB>Contemporary Christian July 2012</TALB>
<TBPM>73</TBPM>
<TCON v1="12"></TCON>
<TENC>Promo Only</TENC>
<TIT2>All Things Beautiful</TIT2>
<TMED>008058</TMED>
<TPE1>Shelly E. Johnson</TPE1>
<TPUB>Maranatha!</TPUB>
<TRCK>9</TRCK>
<W000>nolan@wnolfm.com______________</W000>
<extension>
    <title seq="1">Shelly E. Johnson - All Things Beautiful</title>
    <title seq="2">Travis Ryan - Fearless</title>
    <title seq="3">City Harbor - Somebody Tell Them (Radio Version - Cold Ending)</title>
    <title seq="4">Kaci Battaglia - Body Shots (feat. Ludacris)</title>
    <soon>Travis Ryan - Fearless</soon>
</extension>
</metadata>

[DrO]

nwgator: what am i meant to be looking at in the above log snippet? the 'Error writing to console - write issue' messages?

-daz

[DrO]

attached (with my details removed, heh) is something i'm toying with for Windows users (it will not officially be part of the DNAS).

as something which will start / stop a v2 DNAS and show the different messages highlighted according to their level (which the console output on internal DNAS builds has been doing for a few months) then it's doing what is needed.

there are other things which need to be implemented (like tracking of the source connections and configuration of the DNAS to use, the ability to filter by message type, etc) which is why i'm not putting out a test / preview build until a) i'm happy with it not going to blow up and cause me complaints (this is unofficial so is done off my own back) and b) needs the newer v2 DNAS since it expects the slimmer log output it provides.


i may also look into a non-Windows version but that is low on my priorities and seems to be less of a 'complaint' compared to the wonderfully vocal Windows users who've repeatedly complained.

and in all honesty, i'd be more tempted to try to make a Windows 8 / Metro style interface though i really don't know if that even allows for redirection of console output (i doubt it) so that may not be viable / requires a different way of trying to do things.

-daz

[MrSinatra]

dumb question:

is this the v1 style terminal wrapper? will it have easy access to edit config txt?

[DrO]

Originally Posted by MrSinatra

is this the v1 style terminal wrapper?

it's an equivalent of what the v1 DNAS natively provided but is targeted at the v2 DNAS only (is no point in trying to develop something for a DNAS which is not under development).

it's no more different than the few other wrappers which have been created, just i'm aiming for something which is small and just does what it's supposed to do i.e. just embeds the DNAS's output in a Windows themed window with similar log output highlighting to the DNAS's upcoming output and allows for starting / stopping it without having to use the (seemingly deemed evil) command-line.

Originally Posted by MrSinatra

will it have easy access to edit config txt?

i still haven't decided what i am or am not going to implement in it (especially for starting off on things). though making it open the config file in the associated text editor is just a one line call (and is what the v1 wrapper did anyway - when it worked). i am toying with the idea of an integrated editor (well just embedding an edit control) so then things can maybe be a bit more automated.

as so far the only thing other than start / stop actions is a menu action which allows for going directly to the DNAS's server admin summary page (/admin.cgi?sid=0) since that seems to be one of those things which keeps coming up as something people struggle to find (especially from Windows users).

-daz

[nwgator]

Originally Posted by DrO

nwgator: what am i meant to be looking at in the above log snippet? the 'Error writing to console - write issue' messages?

-daz

Not exactly sure... I set all the log files to 777 and see if the stream disconnects. It seems at times almost if the shoutcast server times out for a few seconds and is inaccessible, then comes back later... I know it's not the server dropping connection, because on the same box, I have an IRC eggdrop that doesn't lose connection throughout the process.

EDIT: The only thing of interest in the log I posted really was

PHP Code:

2012-07-20 21:43:25    E    msg:virtual void AOL_logger::consoleLogger_element::log(const AOL_logger::message&) Error writing to console - write issue 
2012-07-20 21:43:45    E    msg:***91;YP2***93;  ***91;YP2***93;  Could not resolve host address yp.shoutcast.com Restarting in one minute 


Not exactly sure why it would do that.

[DrO]

it could be the DNAS maxing out on the file descriptors it's able to use (if you're getting more than 300 concurrent clients then things can get a bit 'quirky' in relation to "the shoutcast server times out for a few seconds and is inaccessible, then comes back later".

with the yp resolution issue, it's not ideal but try setting ypaddr=64.12.96.225 and see if that makes a difference (it should resolve but either the DNAS is caching something incorrectly or the host isn't getting the correct DNS record for things).


and with the logger write error, setting screenlog=0 will sort that out as the shell the DNAS was started to run in seems to have expired so it'll keep spamming that out.

-daz

[nwgator]

I've turned on debugging for everything and if it happens again I'll let you know.
The problem doesn't happen that often.

[DrO]

in all honesty i don't think that's going to help out too much in trying to determine the cause but hopefully i'll be proved wrong (though will be fun if it does happen especially in trying to match a b29 log output to what the internal builds generate).

-daz

[nwgator]

I'm seeing a few of these as I look through the log... any ideas? This is on Debian 64-bit.

PHP Code:

2012-07-24 01:59:25    E    msg:***91;DST 186.89.69.88:57071 sid=1***93; Socket error while waiting to send data. err=Connection reset by peer(104)
2012-07-24 02:09:27    E    msg:***91;DST 208.20.225.130:53615 sid=2***93; Socket error while waiting to send data. err=Connection reset by peer(104) 


[DrO]

that is generally normal when a connection ends, without context of what those messages relate to it's hard to say if it's a true error or not, though it is most likely not.

most of those sort of messages will be hidden away whenever the next release happens since they are mainly for debugging and are just the raw codes reported when the underlying socket connections close (hence why it is normal to see them).

-daz

[nwgator]

Originally Posted by DrO

that is generally normal when a connection ends, without context of what those messages relate to it's hard to say if it's a true error or not, though it is most likely not.

most of those sort of messages will be hidden away whenever the next release happens since they are mainly for debugging and are just the raw codes reported when the underlying socket connections close (hence why it is normal to see them).

-daz

I went back in the logs when I noticed the problem that I had mentioned up there occurred again. Those were the only things in the log that were errors.. weird. the content surrounding them looked normal to me. I don't have 300 clients connected at one point, but I am using port 80... could that pose any problems?

You were right about having debugging turned on for everything not helping. Now I just have a massive log file lol.

It's stable for the most part, just these little hiccups every once in a while are irritating. Could something like this be fixed with an update to the DNAS?

[DrO]

Originally Posted by nwgator

I went back in the logs when I noticed the problem that I had mentioned up there occurred again. Those were the only things in the log that were errors.. weird. the content surrounding them looked normal to me. I don't have 300 clients connected at one point, but I am using port 80... could that pose any problems?

it shouldn't make a difference what port things are running on unless there's some external aspect affecting how things like DNS resolution are happening. i've never directly seen the issue happen let alone for anyone to have it happen reliably that it could be debugged against so i'm really not sure what is the cause. it could even just be the timing of the those connections to the YP coincided with us doing updates on it or the load balancer not handling things properly, just don't know.

Originally Posted by nwgator

You were right about having debugging turned on for everything not helping. Now I just have a massive log file lol.

that's why so much is hidden via the debugging options, though i think i've almost halved the amount of log output that happens under normal usage for what will become the next public build.

Originally Posted by nwgator

It's stable for the most part, just these little hiccups every once in a while are irritating. Could something like this be fixed with an update to the DNAS?

i'm aware that a new public build needs to be released (if only to stop the insane number of new authhash that people keep re-making because they've not read the docs / example configs), but doing that has been dependent upon initially a whole slew of YP updates making it publically (which is now done). but there are some remaining issues which need to be resolved (mainly against relaying and the associated backupurl handling) as well as the documentation + setup process being re-done (the docs alone is a weeks work).

since in all honesty there's no point from my side of the fence in giving out what is a notably improved build (as there are a lot of newer builds being used out in the wild via our partners which has validated that being the case) when people still cannot install it or have the doc updates to know what can be done with the new features or get their heads around editing 2 things in an example config file and going to one page at the most basic to get things up and listed (hence having to make a more integrated setup UI for it).

yes there probably should have been more incremental updates instead of what is now at a 101 line changelog (and that's me being frugal on what i've added to it). but then most people seem to be adverse to frequent updates and actually it's probably worked out better in this case to just wait longer so that i do catch and fix all of the issues which i can and provide one large update addressing them all in one go so it is more appealing as something for people to install or actually use to update a v1 setup and without needing people to keep updating their DNAS (as i've been repeatedly told from a lot of people that they don't like doing since they then loose their peak numbers and uptime).

-daz

[nwgator]

Thanks for the response. I understand. Let me know if I can help out in any way, especially if you need more testers

It's sad that people are ignorant of the documentation/examples. I understood them fine.