dvd.collector

Members
  • Posts

    270
  • Joined

  • Last visited

Everything posted by dvd.collector

  1. OK.. so the issue may be where the stock folder is then.. as mine is under the "images" folder e.g. /boot/unmenu/images/stock ls -l /boot/unmenu/stock returns: root@Tower:~# ls -l /boot/unmenu/stock /bin/ls: cannot access /boot/unmenu/stock: No such file or directory I'm going to assume this may be a typo and you missed the images folder out of the command and continue with the other tests: ls -l /var/log returns: root@Tower:~# ls -l /var/log total 6912 -rw-r----- 1 root root 80 Dec 21 06:02 acpid -rw-r--r-- 1 root root 0 Dec 21 06:02 cron -rw-r--r-- 1 root root 30603 Dec 21 06:02 dmesg -rw-r--r-- 1 root root 53 Dec 21 06:02 go lrwxrwxrwx 1 root root 19 Dec 21 06:02 images -> /boot/unmenu/images/ drwxr-xr-x 2 root root 0 Dec 21 06:02 packages/ drwxr-xr-x 2 root root 0 Dec 21 06:02 removed_packages/ drwxr-xr-x 2 root root 0 Dec 21 06:02 removed_scripts/ drwxr-xr-x 3 root root 0 Dec 21 06:02 samba/ drwxr-xr-x 2 root root 0 Dec 21 06:02 scripts/ drwxr-xr-x 3 root root 0 Dec 21 06:01 setup/ -rw-r--r-- 1 root root 7036640 Dec 21 15:05 syslog rm /tmp/mymain_seq.txt I did this, and refreshed the mymain page, and unfortunately still no images! I must be doing something simple wrong, i'm sure of it!!
  2. ls -l /boot/unmenu/images (we expect the "images" directory to have been created and in it a "stock" sub-directory with most of the image files. The image directory is new with the new release of the myMain plugin. root@Tower:~# ls -l /boot/unmenu/images total 160 -rwx------ 1 root root 120047 Dec 6 10:45 MyServer.jpg* -rwx------ 1 root root 33072 Dec 6 10:45 MySlots.jpg* drwx------ 2 root root 4096 Dec 6 10:45 stock/ The older unmenu_install program had no concept of dealing with sub-directories. For that reason a new version had to be developed. To see if you have the new version, type: ls -l /boot/unmenu/unmenu_install root@Tower:~# ls -l /boot/unmenu/unmenu_install -rwx------ 1 root root 13168 Dec 19 08:54 /boot/unmenu/unmenu_install* and grep Revision /boot/unmenu/unmenu_install | grep RELEASE The output of the "grep" should look like this: #UNMENU_RELEASE $Revision: 186 $ $Date: 2010-12-04 14:58:29 -0500 (Sat, 04 Dec 2010) root@Tower:~# grep Revision /boot/unmenu/unmenu_install | grep RELEASE #UNMENU_RELEASE $Revision: 186 $ $Date: 2010-12-04 14:58:29 -0500 (Sat, 04 Dec 2010) $ I think, as the grep matches.. I don't need to follow the instructions in the rest of this post?
  3. Try entering the following URL: http://tower:8088/log/images/stock/myMainLogo.jpg Joe - This is probably unrelated - but appears that there is a directory called "images/slock" not "images/stock" that is being created by the install process. Here is what I see when accessing that url: 404 Not Found /var/log/images/stock/myMainLogo.jpg Not Found I assume that the 404 shows that the web server is up and running? (Rather than seeing a page cannot be displayed message). Have also tried clearing browser cache, and unless my router is playing up, there is no firewall in place.
  4. Hi Joe, yes I set it to autoinstall on reboot and i can see from the packages page it says install on reboot enabled too. Heres the output of the queries you asked for: Tower login: root Password: Linux 2.6.27.7-unRAID. root@Tower:~# ls -l /boot/packages/image_server.sh.auto_install -rwx------ 1 root root 2091 Dec 19 08:56 /boot/packages/image_server.sh.auto_ins tall* root@Tower:~# ls -l /usr/local/sbin/image_server.sh -rwxr-xr-x 1 root root 1103 Dec 19 09:03 /usr/local/sbin/image_server.sh* root@Tower:~# tail /boot/config/go echo nameserver 192.168.11.1 >/etc/resolv.conf echo 192.168.11.4 tower >>/etc/hosts echo "powerdown" | at 23:00 cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c /boot/custom/bin/cache_dirs -w -B # /boot/custom/bin/cache_user.shroot@Tower:~#
  5. Yes. You'll need to install, via the package manager in unMENU, the new image_server.sh package I created and set it to re-install on reboot. It is set to use port 8088. This is configurable if you need to change it if something else is already using that port, but for 99.99% of unRAID users, it will be unused and available for use by the image server. Then in the myMain config you need to set the image server field to tower:8088 (Click on the myMain Logo to open the configuration screen.) You can use an IP address as an alternative to the server name (for those using a MAC). In that case set the image server to xxx.xxx.xxx.xxx:8088 where the xxx.xxx.xxx.xxx = your specific IP address of your unRAID server. Joe L. I've installed the new package (and rebooted), and also updated myMain to try both "tower:8088" and IP:8088 and I'm still not seeing any images in Mymain. Is there anyway I can confirm that the image server is up and running? (Syslog snippet below, seems to suggest it is.. but also it is crashing?) Dec 19 09:04:17 Tower bash[2433]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:05:02 Tower bash[2480]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:05:27 Tower bash[2535]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:05:37 Tower unmenu[1589]: /boot/unmenu/uu: line 55: 1594 User defined signal 1 awk -W re-interval -f ./unmenu.awk 2>$stuff$1 </dev/null Dec 19 09:05:37 Tower unmenu-status: Exiting unmenu web-server, exit status code = 138 Dec 19 09:05:37 Tower unmenu-status: Starting unmenu web-server Dec 19 09:07:23 Tower bash[2603]: connect from 192.168.11.4 (192.168.11.4) (Routine) Dec 19 09:07:24 Tower bash[2613]: connect from 192.168.11.4 (192.168.11.4) (Routine) Dec 19 09:07:25 Tower bash[2623]: connect from 192.168.11.4 (192.168.11.4) (Routine) Dec 19 09:07:26 Tower bash[2633]: connect from 192.168.11.4 (192.168.11.4) (Routine) Dec 19 09:07:27 Tower bash[2643]: connect from 192.168.11.4 (192.168.11.4) (Routine) Dec 19 09:07:28 Tower bash[2653]: connect from 192.168.11.4 (192.168.11.4) (Routine) Dec 19 09:07:29 Tower bash[2663]: connect from 192.168.11.4 (192.168.11.4) (Routine) Dec 19 09:07:30 Tower bash[2673]: connect from 192.168.11.4 (192.168.11.4) (Routine) Dec 19 09:07:31 Tower bash[2683]: connect from 192.168.11.4 (192.168.11.4) (Routine) Dec 19 09:07:32 Tower bash[2693]: connect from 192.168.11.4 (192.168.11.4) (Routine) Dec 19 09:07:39 Tower bash[2783]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:07:39 Tower bash[2784]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:07:39 Tower bash[2785]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:07:39 Tower bash[2790]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:07:39 Tower bash[2794]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:07:39 Tower bash[2807]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:07:39 Tower bash[2831]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:07:39 Tower bash[2841]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:07:49 Tower bash[2871]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:07:54 Tower nss_wins[1298]: Listening on interface #2 eth0, 192.168.11.4#123 Enabled (Network) Dec 19 09:09:39 Tower bash[3199]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:09:39 Tower bash[3200]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:09:39 Tower bash[3198]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:09:39 Tower bash[3201]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:09:39 Tower bash[3202]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:09:39 Tower bash[3203]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:09:39 Tower bash[3264]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:09:39 Tower bash[3265]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:09:48 Tower bash[3398]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:09:57 Tower bash[3524]: connect from 192.168.11.97 (192.168.11.97) (Routine) Dec 19 09:10:06 Tower unmenu[1589]: /boot/unmenu/uu: line 55: 2552 User defined signal 1 awk -W re-interval -f ./unmenu.awk 2>$stuff$1 </dev/null Dec 19 09:10:06 Tower unmenu-status: Exiting unmenu web-server, exit status code = 138 Dec 19 09:10:06 Tower unmenu-status: Starting unmenu web-server
  6. whoops i copied from bjp's post! Shame on me being an englishman!
  7. Are you running lightpd web server? If yes, it would be pretty easy to get it to serve the images. If not, Joe L. has come up with an amazingly light Web server. I haven't tried it out yet, but will suggest that Joe L. send it to you as the guiney pig. (Acutally Joe was his own guiney pig and he says it works beautifully.) There is a value you can put in your local config file to change the image URL. I am going to make that a setting on the myMain config screen so that MAC users that need to put in IP address and others, like you, that want to serve images via lighttpd or Joe's Amazingly Light Image Server (JALIS ). But until that, you can still add the line manually: SetConstant(ImageHost, "tower") You should be able to add a port ... SetConstant(ImageHost, "tower:8088") BTW, this (Joe's image server) might be the best approach to handle users that have a password. I'm not running lightpd webserver, but am happy to be the guiney pig and try it
  8. Version 4.4.2 is roughly 30 versions old. The ability to serve images we are taking advantage of was added in version 4.5-beta2. (The version immediately after the one you are running) If you are not running that old 4.4.2 version for a specific reason, you might want to consider upgrading. It basically involves replacing two files on the flash drive and rebooting. (if you want the latest memory test program you can replace a third file too) If you're stuck on the version you are because you are using bubbaRAID... sorry. bjp999 and I are evaluating an alternative method of serving the images that might work for you too. I've dome some preliminary tests but it is not incorporated in any unMENU code yet. Joe L. Hi Joe, thanks for the reply. Actually the reason I'm still on 4.4.2. is that I can't see to get the shutdown script to work on any version past 4.4.2. I think the issue is related to cache_dirs holding open a drive as from memory the message in the syslog is that a drive is still in use when trying to unmount. I did post a question on this some time back, but i dont think you were able to solve the issue. Never mind, I'll live with the missing images
  9. Kyyspy & dvd.collector Yes the "log" is supposed to be there in the path to the images. The "other" web-server, used to serve images, is apparently not yet active on a reboot when you first attempt to access myMain. pressing "refresh" on the browser should fix it, as by then it should be active. Joe L. I've tried refreshing multiple times, as well as exiting the browser and going back in, and I still don't see the images. If I copy/paste the image url to the browser it doesnt find it either. Is there anything else I can check? What version of unRAID are you using? You must be using a recent version to see the images. In addition, you must run the update process twice. The first time it will download and install the new version of unmenu_install that can properly deal with the image subdirectory. The second time you run it, it will download the images into their sub-directory. Do you have a password on the "root" login. If you do log onto the normal unRAID web-interface and supply the password. The images will not display unless you have first logged in on the Stock unRAID Web-interface(if you have a root password) Joe L. Hi Joe, I'm using v4.4.2. I did run the update more than once, as the first time i got an error regarding the local_conf file being in use. Finally no, I dont have a password on root. I can see the images are there in the images\stock folder which hopefully the screenshot attached shows.
  10. Kyyspy & dvd.collector Yes the "log" is supposed to be there in the path to the images. The "other" web-server, used to serve images, is apparently not yet active on a reboot when you first attempt to access myMain. pressing "refresh" on the browser should fix it, as by then it should be active. Joe L. I've tried refreshing multiple times, as well as exiting the browser and going back in, and I still don't see the images. If I copy/paste the image url to the browser it doesnt find it either. Is there anything else I can check?
  11. I'm having problems with broken images too. In Firefox, the images seem to point to : http://tower/log/images/stock/myMainLogo.jpg is the "log" part of that url correct?
  12. You are correct. You need to stop the cache_dirs program first... (or any other program running currently accessing the disks) Once we get a true pre-shutdown trigger in version 5.0 of unRAID, we'll be able to more cleanly shut down processes like cache_dirs that we invoke. At that time, we'll all be making changes in how we start and stop add-on processes. Joe L. Hi Joe, It does kill the cache_dirs script, you can see it on the first line of the log above. I've simply added /boot/custom/bin/cache_dirs -q to the top of the powerdown script.. is that not enough? Add a line to give it time to stop. It only looks for the absence of the lock file (which the -q removes) once each time through the loop, and the loop runes every few seconds. If you are on 4.5final, you can invoke cache_dirs with the "-B" flag so it will not create the child processes it does otherwise to keep you from seeing the old "Unformatted" messages when attempting to stop the array.. So, after the cache_dirs -q in your powerdown sequence, add a line something like this: sleep 10 before it continues onward. Hi Joe thanks for the info, although i already have sleep 10 in the script, and am invoking using - B: /boot/custom/bin/cache_dirs -w -B However it doesnt seem to solve my issues stopping the array or using the powerdown script. Should I change to sleep 20, or longer?
  13. You are correct. You need to stop the cache_dirs program first... (or any other program running currently accessing the disks) Once we get a true pre-shutdown trigger in version 5.0 of unRAID, we'll be able to more cleanly shut down processes like cache_dirs that we invoke. At that time, we'll all be making changes in how we start and stop add-on processes. Joe L. Hi Joe, It does kill the cache_dirs script, you can see it on the first line of the log above. I've simply added /boot/custom/bin/cache_dirs -q to the top of the powerdown script.. is that not enough?
  14. Since upgrading to this version, I have problems (i assume) with Joe's powerdown script. Every morning now I have a parity check start when the server boots up. Dec 16 23:00:00 Tower cache_dirs: killing cache_dirs process 2033 Dec 16 23:00:10 Tower logger: Powerdown initiated Dec 16 23:00:10 Tower logger: Shutting down Samba Dec 16 23:00:10 Tower logger: Syncing the drives Dec 16 23:00:24 Tower logger: Killing active pids on the array drives Dec 16 23:00:24 Tower logger: root 4327 4313 0 22:57 ? 00:00:00 find /mnt/disk3/MP3 -noleaf Dec 16 23:00:24 Tower logger: Umounting the drives Dec 16 23:00:27 Tower logger: Stopping the Array Dec 16 23:00:27 Tower kernel: mdcmd (6128): stop Dec 16 23:00:27 Tower kernel: md: 2 devices still in use. Dec 16 23:00:28 Tower logger: cmdOper=stop Dec 16 23:00:28 Tower logger: cmdResult=failed Dec 16 23:00:28 Tower logger: Dec 16 23:00:29 Tower logger: Saving current syslog to /boot/logs/syslog.txt There was nothing accessing the drives at 23:00, other than I guess the cache_dirs script.
  15. Hi all, I thought I'd give this new version a try, however i seem to be having a problem when stopping the array. (Cache_dirs related?) The web interfaces shows the drives as "unmounting", and nothing i can do can seemingly get them to unmount. So I resorted to the power button. That of course started a parity check when it booted up, and uplon pressing "stop", i got the same situation. Is there any way to avoid this? Nov 26 15:09:04 Tower emhttp: shcmd (58): /etc/rc.d/rc.samba stop | logger Nov 26 15:09:04 Tower emhttp: shcmd (59): /etc/rc.d/rc.nfsd stop | logger Nov 26 15:09:05 Tower emhttp: Spinning up all drives... Nov 26 15:09:06 Tower emhttp: shcmd (60): sync Nov 26 15:09:11 Tower emhttp: shcmd (61): umount /mnt/user >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: shcmd (62): rmdir /mnt/user >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: shcmd (63): umount /mnt/user0 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: shcmd (64): rmdir /mnt/user0 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: shcmd (65): umount /mnt/disk1 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (65): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (66): rmdir /mnt/disk1 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (66): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (67): umount /mnt/disk2 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (67): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (68): rmdir /mnt/disk2 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (68): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (69): umount /mnt/disk3 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (69): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (70): rmdir /mnt/disk3 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (70): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (71): umount /mnt/disk4 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (71): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (72): rmdir /mnt/disk4 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (72): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (73): umount /mnt/disk5 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (73): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (74): rmdir /mnt/disk5 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (74): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (75): umount /mnt/disk6 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (75): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (76): rmdir /mnt/disk6 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (76): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (77): umount /mnt/disk7 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (77): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (78): rmdir /mnt/disk7 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (78): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (79): umount /mnt/disk8 >/dev/null 2>&1 The above just repeats forever.. [update] I disabled cache_dirs and the issue goes away.
  16. Wont mediabrowser be accessing the mymovies.xml files in each folder to verify it is current? If so, just caching the folder names isn't going to help with this.
  17. I see 80MB/s transferring Vista to Vista, but the best I see transferring to Unraid is 40-50MB/s (using a cache disk).
  18. As mentioned, you need to check if the graphics card supports hardware acceleration of the bluray codecs, namely VC1, AVC and MPG-2. I used a really old PC fitted with a new ATI AGP card that supported hardware acceleration of these codecs and could watch bluray movies in Powerdvd with very low cpu useage. Also if the graphics card isn't HDCP compatible you will need extra software to strip the protection from the bluray before you can watch it.. (I'm talking about bluray disks you bought and own here.. nothing illegal!) In the end I built a new HTPC, because not all types of video can be hardware accelerated currently.. namely MKV's. So for that you need a meaty processor. Cant you simply try playing a bluray movie on the PC as you have it and see if it works?
  19. I want this to be an externally available ftp server, that I can create users/passwords for and set specific folders to allow those users to download/upload from/to. Basically a normal ftp server you would find on any windows box. I currently use RaidenFTP for this task. For example, how do I setup PASV or am I limited to PORT? How do I create users, assign folders to those users etc..
  20. I read this on the release notes, but can't find any instructions on how to use it???
  21. I'd like to run an ftp server on unRaid. It would save me having to keep a windows pc running as well pointing at the files on the unRaid server. The posts I've read on here seem pretty complicated for a newbie, so is there an easier ftp server I can install on unRaid? Some requirements: I dont use user shares, but want to be able to restrict what folders each user sees on the ftp server Must be able to give write access to say an upload folder for specific users Preferably is will have some sort of anti-hammer feature, as my windows box is forever being hammered by people trying to brute force passwords. Thanks for any help.
  22. Thanks for all the replies, seems I have a lot to look at now Firstly the cpu is a P4 (socket 478) 2.8ghz. Can you still get socket 478 cpu's nowadays? I think I may be stuck with this setup unless I decide to buy a new mobo too. As I've just spent £££ on the parts for a HTPC, I think that may have to wait for a bit! I might try underclocking it and lowering the vCore though, see if that helps, as well as removing the video card. Also I'll look at the power supply. I have a feeling it's a generic 430w one, so perhaps buying a newer 80+ one will help. Although anything costing £££ will have to wait for a bit...
  23. Would underclocking the CPU help? How much does unRaid use the CPU?
  24. My unraid server is using 115watts when all the 6 drives are powered down. I'm assuming this is powering the mobo/cpu/fans. Is there any way to reduce this, other than using suspend or hibernate? Is there any way to switch off fans (specifically the ones cooling my hd's) when the drives power down?
  25. Thanks yeah I've added that tweak. The 40MB/s was writing btw.. haven't tested read yet.