Merty's Blog

 

 

Well, just an update to let you all know I'm still alive and still working with the Disk Stations. I do have 2 now: DS408 and a DS1010. I realize you might haven't heard from me last months, but that is because of my other activities that are more important, like reconstructing rooms of my house and a new job, being a manager and architect at once, managing a very busy department of 30 people doing various development projects en dealing with several supplier of even more people working abroad. 

Anyway, back to Synology Disk Stations. 

First: Yes, I'm aware there are problems with the new DSM3.0 beta version. I'll look into it as soon as I have installed it myself on one of my Disk Stations. Looks like ssl library don't play "nice" with python ssl library for one, but maybe more is changed...

Second: Please, stop emailing me - or posting comments on this blog - with very common or very unclear errors. If you really need help, I'm probably not the best person to contact. Place question or problem in either english or dutch Synology forum, and other might help to answer your question. I'll drop by on those forums as well to see if I can help.  I'm sorry, but I don't have the time to answer all email.

So, what's in store for future, besides from fixes ? Well, I was working on getting Subversion server working on the Synology Diskstation. It is working (cross compiling all SVN stuff and solving all dependencies is a disaster, I can tell you know), but still need a GUI thingy for users to create new SVN repository and point to right logical volume. So, it might take some time...

 

A quick run into common questions:

Q1) Are you aware that sabnzbd+ doesn't work on DSM3.0 beta

A) Yup, I know, thank you telling me this (round about 60 persons emailed me about it..). I'm working on it..

Q2) When do you release with 5.3 version ?

A) Dunno, probably soon with fix for DSM3.0 bet. BUT YOU DON'T NEED TO WAIT ! You know, that is why I wrote the "SABnzbd+ helper" program, to upload the *sources* of SABnzbd+ and yourself, including the 5.3 version. You don't need a new package...

Q3)  How do I update to 5.3 version ?

A) Use SABhelper. If the package is installed, press "reload" of your browser screen. In admin screen on the left you have a pane with different options/programs. One of it is called "3rd party software", under this folder you'll find "SABnzbd+ helper", click on it to start.

Q4) Can't upload new version 

A) You are probably uploaded wrong version. You have to download the python sources of SABnzbd+ , nothing more or platform specific. To be correct, the file extension should be tar.gz or .tgz. Other files will give an error about not finding SABnzbd.py (extra check to prevent installing non-source code package). Download it from http://www.sabnzbd.org/download/ page, "Python source (linux etc.)" button.

Q5) Your program isn't working

A) To bad, however you didn't provide me any usefull information I can work with, starting with which program isn't working. Again give me more to work with, or better, try it again in one of the synology forums. I'm sorry, but if the only thing you can say is "it isn't working" without providing me about what you did, the version you use, what kind of DS you have, what you see in the "log" tab, I can't help you and don't have time for a long "try this" or "how about that" back-and-forth emailing scheme.

Q6) Can you make  <name or program>  for Disk Station ?

A) Nope, can do, no time besides other reasons why it isn't working at all, see previous posts.

Q7) SABNZBD+has  a bug

A) if it isn't platform related, please bug the SABnzbd+ developers about it..

 

 

 

 

Talking about errors... In the 2.3 firmware, the S97apache-user script (the script to start/stop user webserver) overwrites php.ini file with default values, making my WebShare Enabler program worthless. Fixed it, new version can be downloaded. Uninstall previous one.

Well, firmware 2.3 is out and I like the new features. However, there is a downside: several people report memory problems, not only with SABnzbd+ but almost all programs that needs memory from time-to-time. I think one of the new changes in the 2.3 firmware is leaking memory as hell... I don't see any strange memory usage when using SABnzbd+ on the 2.3 firmware - and why should it, it worked without problems under 2.2 and even beta). Hope Synology will fix this, in mean time, when you have memory problems, the only way to get rid of it is to reboot your Synology nas again. Also, try to prevent indexing of video/audio files, also a "usual" suspect of resource problems.

Further on, I do receive a lot - In the range of 20-30 messages a day - questions. It is hard for me to answer them all properly, I do have a normal day job, you know ;) . Also, a lot of questions do popping up in this blog. I urge everyone who has a technical problem to post it in the synology forums. Or better yet, check if this question has been answered already. I regarly check the international and dutch Synology forum. Doing this, there is better hope for an answer, if not from me it would be from somebody else and by doing this, you help others who might have the same question..

Oh, and talking about errors I do feel responsible for: yes, SABnzbdHelper can't fix strange characters in directorynames (yet)...

 Right, 0.5.0 Final. Although everyone should be able to just upload it via Sabhelper, lot of people still requested it. So, there you have it. I few minor fixes:

* Old firmware didn't have unzip, unrar, so included it in package for "old" Syno's. Although SAPhelper might not work, SABnzbd+ should work now.

* Open new page when clicking on SABnzbd+ instead of opening in frame  (thans for the tip Robbert!)

* Somehow, I managed to pack 2 SABhelpers in previous, old & new version...whoops.. This time the real, last one. Hopes it fixes some "not working" issues.

Short guide SABnzbd+ install & configuration for dummies:

1. download package (zip). Some Mac programs and Safari browser are a bit to eager to unpack *everything*, including contents of package itself. So, when on mac, use Firefox to download

2. unzip it, extract the *.spk out of it 

3. Go to packagemanager, click install (no, not upgrade) , point to package, choose a nice volume ...

4. After installation, click on the sab2 row. Click "run" button

5. Click on link that appears (or go to http://your-adress-of-your-nas:9200/)

6. Follow instructions to configure:

- don't check 'I want SABnzbd to be viewable from my pc only.'  (checking this would block any browser on the network to sabnzbd+ page)

- don't use "launch internet browser when..." (wouldn't work anyway, starting a browser on your nas)

7. WAIT before downloading anything: default configuration isn't right

8. configure filepermissions: 777 (read-write for everyone)

9. Go to SABnzbd+ helper, in your admin menu, bottom left, "3rd party software". Click on it

10. Choose share you want to have the SABnzbd+ on it

11. Press save configuration

12. Go back to SABnzbd+, configuration of folders should be changed to the "real" directories of the share you choose.

 

Have fun.

 

Remco

 

Finally ! At the moment, I'm uploading new packages for all recent diskstations (DSx06 and later) including the DS1010+ . As a happy owner of a brandnew DS1010+ I had to compile for this version to, of course. I will update download page tomorrow, but to give you an inside of what is changed:

* Included 3th party "SABhelper" this program wil help you with:

•   Upload the version of SABnzbd+ you want: just grab the sources tar.gz file and upload it via SABhelper ! Now you dont have to  wait 'till I have a new update version, just upgrade when SABnzbd+ is released !
•   Setting the right download directory/share, just click on what share you want your SABnzbd+ on.
•   Strange characters in filenames that prevents deleting or using the file
•   Setting file and directory permissions to everyone on all downloaded files and directories

*  python upgraded to version 2.5.4 (no, don't wanna use 2.6 there is no benefit in this)

*  ionice included (only supported on DSM firmware with kernel 2.6.13 or higher)

*  The Synology versions of unrar & zip that comes along with latest firmware version will be used.

*  SABnzbd+0.5.0RC3 is included in package (and of course, you can always up- or downgrade it via SABhelper)

*  Admin URL in packagemanager will go directy to SABnzbd url. No need for redirect script or specially crafted URLS. Even port configuration change will update admin url.

* New chipset: Intel Atom. It's good to see Synology pushing out a new crosscompiler kit that fast for the new DS1010+ and DS710 ..

*  Much improved & speeded up start and stop of services. Will not interfere with any other python processes

If you don't trust this new package yet, you can always use the "old" one, even next to eachother. Just beware that by default, they share the same portnumber: 9200. So, make sure only one of them is running at the same time, or configure one of them on another port then 9200 (9201). 

For those who can't wait, these are the download links to different version (check wiki or links in my download page if you don't know what kind of CPU you have and which file to download):

http://www.xs4all.nl/~merty/syno/SABnzbd-0.5RC3-arm88f5281-40-spk.zip

http://www.xs4all.nl/~merty/syno/SABnzbd-0.5RC3-arm88f6281-40-spk.zip

http://www.xs4all.nl/~merty/syno/SABnzbd-0.5RC3-ppc8241-40-spk.zip

http://www.xs4all.nl/~merty/syno/SABnzbd-0.5RC3-ppc8543-40-spk.zip

..and finally, the DS1010+ version:

http://www.xs4all.nl/~merty/syno/SABnzbd-0.5RC3-x86d510-40-spk.zip

Have fun..

  

 Just a quick update: working hard on new SABnzbd+ package and a "sabhelper" package. Still in progress. Will not help if you accidently remove your development directories . Anyway, for all people asking me about the alpha-beta version of SABnzbd+, here is an update package to try out beta version of SABnzbd+ (mind you, its still only an "update" of my "old" package):

http://www.xs4all.nl/~merty/syno/SABnzbd-UpdateTo0.5-beta6-All-24-spk.zip  

 

Ok, A small update. I really get 1 email per hour now because of the new DS210 models. At the moment there is the DS110j, DS210j and DS410j as far as I can see. They all have the same CPU/environment as the DSx09 model (without 'j' or '+').I've updated the downloadlinks for this models. Also, everything is zipped now. Some pesky browsers or operating systems did had the nasty habbit of 'recognizing' the spk format as tar.gz and unpacking it after download. So, to prevent this, all SPK files are zipped...

In the mean time, I'm working on a .psk package as an answer to all those people who are "misfortunate" to not read my instructions to CONFIGURE THE DOWNLOAD DIRECTORIES  TO AN ACCESSIBLE SHARE BEFORE DOWNLOADING SOMETHING. Some people don't understand telnet or ssh and I'm realy not in the mood for linux-commandline-tutorial-writing. So, this program should move the files into an accessible share and will "clean up" problems with read/write rights and strange characters in filenames. At the moment, I only have the AJAX part working (progress bars in Extjs are cool, you know), now the real stuff....

When browsing on the web looking for Synology info, I came accross this german wiki page "http://www.synology-wiki.de/index.php/%C3%9Cbersicht_%C3%BCber_verf%C3%BCgbare_3rd-Party-Apps_aus_unserer_Community". Besides from packages I didn't know about, it mentioned an interesting footnote: "Wenn es ihm gefällt, kann er als Urheber morgen sagen: "April, April ... ab jetzt dürft ihr nur noch damit spielen, wenn ihr bei mir eine Lizenz kauft." GLP schiebt einer solche Willkür einen Riegel vor ...". Well, my German is not that good, but what - I think - it says it that although I said it is free to use, I still have te ability to change the license of my packages and start asking licensemoney for it. Although I would never, never do such a thing and it will be questionable in court if I start asking money what I was previously giving away for free, the poster had a valid point.

So, thats why I will "changing" the license to an well-known opensoure one. I was thinking about GPL, but I think that is a bit to restrictive. I don't mind if someone alters my packages and rebrand them "closed source" or ask money for it (good luck !, doubt you will make any profit out of it if my version is still free). Actually, I don't mind at all what you will be doing with the stuff I provide, as long as you don't drag me into court because it is not doing exactly what you think it was. Therefore, I choosed the less-restricted "BSD" license. 

In the next coming updates of all packages, I will include this license into the programs. This will change not that much for you as end-user, but will give you the guarantee that I will keep this open source and will prevent me from nasty liability accusations..

Thank you for all your email ! Nowadays I get round about 25 emails a week about my Synology packages. So, I really appricated it, but don't be offended if I can't answer them all (-in time). But, I will always - and that I can promise you - read them. Believe me, I would, but don't have enough spare time for all my hobbies..

Often, I get the same questions over and over again (about SABnzbd+ download directory, for instance) but sometimes I do get requests to make packages. Most of the cases it's about running commercial package -- fill in name here -- on the DiskStation.  Most of the cases, the answer will be "no". Let me try to explain why:

1. Synology DiskStations are not intel/amd-linux computers. In fact, they run on different PPC or ARM CPU's with a  modified linux kernel and a "linux-like" environment but the simularity with your "average" linux-PC stops there. Don't presume any linux program will run out of the box on your DiskStation.

2. Unless you are extremely lucky, pre-compiled programs will not run on your Diskstation, unless Specifically compiled for your CPU & GlibC versions.BTW: there are differences in ARM en PPC CPU's too: don't expect a program compiled for one specific ARM CPU will run on all ARM CPU's..

3. CPU's of DiskStations don't have the same power as latest intel/AMD CPU's. Keep in mind that the CPU's in DiskStations do have enough power to do what they are supposed to do: serving files over a network. This requires less CPU power then a real full-fledged internet server. So don't expect the same power of a quad-core, more like an old "pentium III" if you are lucky.

No ventrillo, teamspeak, Oracle, dropbox ...

So with this in mind, I really can't create a package if I don't have access to the sources of the program you want. In most cases, commercial programs aren't open source, so, can't do anything about it. This means you might never get a Teamspeak or Ventrillo server package for your DiskStation, unless they release the sources (and then it still might be to much cpu consuming BTW).

No fancy java programs...

Also, lot of open source solutions do expect a full-fledged database, J2EE java application server and a full Java Virtual Machine. That again is too much consuming memory and CPU, besides from the program you want to run on it. Yes, there are "stripped/minimalistic" JVM's, but that will probably not run the java programs you are aiming for, unless specific adjusted for that kind of JVM. 

No Real-time Videoprocessing programs..

This is just to much for the processor to handle this in realtime. -a stripped version of- VLC is installed on the DiskStation to handle streaming video, but don't expect too much (intelligent upscaling, MPEG4 en+decoding and so on).

So, if you still find a program that does meet the above requirements and would be fun to have on your DiskStation, let me know...

 

Allright, a lot of people already asked for it, the 0.4.12 version is out. To get less confusion, I've changed the version of all packages to "0.20"..

 

Right, after a few comments came in about the new DSM2.2 beta, I decided to install it myself and took a look at it. Wel, so far, all my Synology programs works as they should be, so, hopefully none of the errors encountered "in the field" is the new DSM 2.2 to blame, I guess. Have to check further to be sure.

Anyway, new DSM looks fine. Firewall is handy, DLNA finally there, and updated versions of samba, php, MySQL and apache. Bad news is that the old "strange characters" bug is still there. Also, my browser keeps on crashing on the flash graph thingy's, although probably to do with the aggresive flash & javascript blocker I use with firefox. W'll see what future versions will bring.

I didn't made much updates lately, but I didn't do nothing. First of all, I'm writing my own blog software, I'm using LifeType for this and other blogs but I really hate the incapabilities of handling comment spam a fast and easy way. A lot of IP's are blocked by my webserver now, but I see 300 (!) requests being made from those automatic comment spammers a day (!). Also I'm working on updating all packages with the Ext2.2 Ajax toolkit, instead of the "old" version 1.0. It appears that with one one the latest DSM2.1 updates, Synology upgraded their Extjs toolkit they use internally (although, there *is* a 3.0 version now, *hint*). 

Last but not least, I'm trying to create a 3rd party program  alongside SABnzbd with the new 0.5.0 version, when it comes out. An easy GUI to setup basic things, since a lot of people still have problems understanding all options and configuration.

So a lot to do. Hope I will have free time enough to create the updates in the coming month...

Ok, too many people asks me the same question over and over again. I thought it was obvious, but most people do have a hard time understanding it. Most of the times, people download the package, installs it, fills in Newsserver properties and forget about the rest. After downloading a few files, they wonder where on earth the downloads are gone to and email me with that question. Well, I explained it on english forum on: http://forum.synology.com/enu/viewtopic.php?f=27&t=11307#p47829 and dutch forum: http://www.synology-forum.nl/viewtopic.php?f=85&t=2349#p9972. But let me try to explain it here again:

Don't confuse Shares and "real" directories

Everything you see in your windows explorer about the synology DiskStation is "shares". A share is a folder that is -hence the name- shared on the network by your Synology DiskStation. You might have a public share, a music share, a video share and so on. But, under its hood, the Synology uses a -linux like- filesystem. The shares you see are directories that belong to that filesystem, but are "exposed" to the outside world too. It is not that different with a windows machine in a windows network. If you have a directory - say "c:\stuff\documents" and want to share all content of that directory (including subdirectories), you can tell windows to make a share of "c:\stuff\documents" and give that share a name, say "SuperSecret". Now, everyone connected on your network will have acces to your computer, and if they do, they will see all shares on your computer, including "SuperSecret" share. So, "SuperSecret" isn't a real directory, it is just a name that links to a "real" directory (c:\stuff\documents). A "real" directory is only available if a share points to it. For example, C:\WINDOWS is a "real" directory, but as long as you didn't share that directory, no-one can access it on your computer from remote.

SABnzbd+ works with "real" directories

SABnzbd+ is made for a range of unix/linux/BSD, mac and windows machines that might or might not have windows file sharing. It "doesn't know" about the shares you have defined, it only knows about the "real directories" it works with. So every file and directory configuration option is about the "real" directory structure on the DiskStation itselves. Do not use the windows "UNC" notation (like "\\mydiskstation\sharename"). Again, SABnzbd+ will not understand that.

Without a full directory configured, SABnbzd+ will use a directory under installation directory

SABnzbd+ will be installed in /var/packages/sabnzbd/target/sab/. If you keep the default configuration, downloads points to "downloads/". That will result in '/var/packages/sabnzbd/target/sab/downloads', a directory that is not accessible via a share. Therefore it is important to change directory configuration before using SABnzbd+ !

Directory structure on DiskStations

So, when dealing with Synology WebAdmin or even Filemanager, you "see" only shares you can create and information about the disks. Therefore, you don't see the "real" directories that is under the hood of your DS. But, you want your SABnzbd+ download directory (or other directories) to be on a place that is accessible via a share, and therefore you need to translate disk & share info to the "real directory" info. However, that is not that difficult.

First of all, a share is always bound to one disk. If you don't know which share resides on which volume, check the 'Privileges' -> 'Shared Folders' info in the Web Admin page. Every disk do have its own "root directory". Disk 1 will be /volume1 , disk number two /volume2, disk 3 /volume3 , disk 4 ...well you got the idea.. So, that will be the beginning part of the directory.

Second, a share you create via the Synology WebAdmin will always be the sharename as directory under this /volume.. directory. 

Example: Say, you have a share "movies" on disk 1 of your diskstation, the "real" directory will be: /volume1/movies/ .

All directories created inside the share will come after this directoryname. 

Example: Say, you have a share "movies" on disk 1  and you created "downloads" and "failed" directory inside the share "movies" the directories will be : /volume1/movies/downloads and /volume1/movies/failed

Don't forget the '/' on the beginning of the path !

Note: If you accustomed of DOS or Windows directorynames, you'll note that the DiskStation directories, as any linux-like machine, will not use drive letters (like "C:" and "D:") but uses directorynames for disks as well (in this case /volume1, /volume2..). Also, be aware directory names are seperated by a slash '/' and not a backslash '\'.

What to do with the files downloaded in the "wrong" directory ?

If you are an experienced linux user, you might want to edit smb.conf to add manually a share to the "wrong" directory. However that is a bit complicated and not recommended, since the Synology WebAdmin programs might mess up your configuration the next time you reboot.

So, the best thing to do is to move the files to the right "real" directory on your syno.

1. log-in as root (same password as admin for Web Admin) using ssh or telnet. Don't log in as Admin because this user do have fewer rights on the command line.

2. On the command line type:

mv /whatever/directory/your/downloads/are/now/* /whatever/directory/your/downloads/should/be/.

<= dont forget the '.' here
(Example: mv /var/packages/sabnzbd/target/sab/downloads/complete/* /volume1/Downloads/SABdownloads/.

explanation: 'mv' command 'moves' files mentioned as first argument to the place mentioned in second argument. '*' on the end means  all files"

3. If you have an 'access denied' when trying to read them via the share type:

chmod -R 777 /whatever/directory/your/downloads/should/be/*

explanation: 'chmod' command alters the rights of files. '-R' means recursive, so also all files and directories below will get that right. '777' means read, execute, and write access for everyone.

4. logout, typing 'exit' or just pressing ctrl-d

Thats it.All it takes is a litle bit of linux/unix knowledge about files and directories, maybe the first step in learning linux command line :)

 

 

Ok, I admit, this bug is open too long, and Synology is only fixing it partly in some of the programs, but not where it should be. A few people mentioned this ( also in this blog, sorry for not giving an answer that soon), but it is not a SABnzbd problem, or a problem with my package, but still is frustrating.

I'm talking about filenames with 'strange' characters in them. 'Strange' characters are actually 'legal' characters used by many foreign languages, like the 'ë' we use in dutch or the 'ç' in spanish language. Files that do appear on your filestation without being put there via a share, cannot be read, moved or deleted. You see the file in your explorer or filemanager, but you can't do anything with it. Quite frustrating. This happens a lot if you download files directly to your Synology filestation. Synology tried to 'fix' it for their own download programs to automaticly rename files before writing them to disk. After every update, I hope Synology finally made it right, but they didn't. Sadly enough, it isn't easy one to fix. Handling with multiple codepages, unicode and native ascii handling of programs did give me a headache in the past, working as a teamlead for a messagebroker between mainframe, unix and windows machines.

Anyway, I can't find any 'clean & nice' solution and thinking of some kind of program to 'clean folders'. Just click on which folder has to be 'cleaned' and the program will rename the files without the nasty characters. Something like that. If some of the readers have a better idea, please let me know...

Allright, a new update for SABnzbd+ (0.4.11) - what happenend to 0.4.10 ? who knows..- . Seems like the toolchain I used to compile for the new NAS servers worked. Thank you all who tested it for me. So, I am quite sure my packages stays working on the new Synology models (DSx09 series). Would like to see some documentations and official toolchains from Synology though.

Still waiting for the official 0.5 version. Testing with beta for months now, but I think it is still too premature to release it.

Before everyone asks: No, I don't have a package yet for all DSxx9 models. In most of the time, none of the existing packages will work. Problem is that Synology didn't updated there documentation or toolchains, so I'm having trouble to figure out what kind of cpu/system-on-a-chip is used and the libraries they build on.

At the moment, we have:

• DS509+ (ppc8533 firmware)
• RS409+ (pp8533)
• RS409RP+ (pp8533)
• DS409+ (pp8533)
• DS209+ (pp8533)
• DS209 (88f6281)
• DS209j (ppc8241)
• DS109+ (pp8533)
• DS109 (88f6281)
• DS109J ("powerpc") 

 And I'm trying to get all info about these models. Synology states that the DS209+ should use the same toolchain as the one for DS/RS408,508 (pp8543), So I guess all new 9 models ending with '+' might use the existing packages for this one too. (if someone have tried this, please tell me)

The DS109J looks like a rebranded 101g+ , if you look at the output, also using the 8241. My bet the package for 101g+ will work on  this one too. Same goes for 209j. However, being a new model and firmware, I'll bet they use a new glibc. 

 And the 88f6281 models (109,209) , well we know for sure none of the packages will work. We need a new toolchain for this. Poking around in de NSLU2 optware feed, I came to the "cs08q1armel" toolchain, used - how ironic- by the QNAP NAS servers. I think this might create working binaries....

 

(Will continue)

• Main
• Archives
• Albums
• Links

«	September 2010					»
Mo	Tu	We	Th	Fr	Sa	Su
		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30

• Still Alive ...
• More errors
• Firmware 2.3, errors and questions
• 0.5.0 Final
• Complete new version of SABnzbd+ package with SABnzbd+ 0.5RC3 - or whatever version you like
• Beta
• New DSx10j models
• License
• Your emails...
• New version of SABnzbd is out

• General [1]
• Syno [17]

• RSS 0.90
• RSS 1.0
• RSS 2.0
• Atom