Products > Storage
Linkstation Duo LS-WXL - how to access media server confguration page (port 9050)
axe:
I have done now a forced firmware update. Nothing changed http://<ip of linkstation>:9050 results in an empty page. But mediaserver is enabled and working. Only twonky config page can not be accessed. It seems you have a different version of firmware where enableweb in twonky config (firmware internal) is correctly set to 2 instead of 1 in latest firmware which can be downloaded through http://www.buffalotech.com/support/getfile/lswxl-124.zip Addtionally after today copying some hundred gigabyte to linkstation, it suddenly restarted and shows now raid 1 error: E13: error has occured at RAID 1 array 1E23: Disk 1 is removed from RAID array due to errors.I12: The raid array works under degrade mode I will return the device to the dealer. It seems it takes some more time for this model to become fully functional and stable.
axe:
another user having exactly same behaviour - twonkymedia web configuration page is not accessible: http://forums.buffalotech.com/t5/Storage/Linkstation-Duo-PS3-Help/m-p/29297# posting number 4 of "Gerald"
axe:
Ok, since no one of buffalo could help or wanted to help I had to help myself be analyzing in detail what linkstation / firmware is doing. 1. Linkstation with firmware 1.24 and 1.26 comes natively with twonkymedia 4.4.19_e2. with this twonky version access of webconfiguration on port 9050 is working. It is installed in directory /usr/local/twonky 2. Beneath twonky version mentioned above, firmware 1.24 and firmware 1.26 contains some very secret mechanism to do an automatic update of twonky to version 5.1.1. To do this, there is a program /usr/local/sbin/majishanzu which downloads twonky 5.1.1 from a https secured buffalo server using private certificates. In /var/log/messages and /var/log/linkstation.log one can see the behaviour of this majishanzu update tool: May 14 12:22:33 PLUTO majishanzu[1992]: download: --2010-05-14 12:21:20-- https://*****************/LS-WXL/en/firm_body/******************************.tgz
May 14 12:22:33 PLUTO majishanzu[1992]: download: Resolving *****************... ***************
May 14 12:22:33 PLUTO majishanzu[1992]: download: Connecting to *****************|***************|:443... connected.
May 14 12:22:33 PLUTO majishanzu[1992]: download: HTTP request sent, awaiting response... 200 OK
May 14 12:22:44 PLUTO majishanzu[1992]: download: Selecting previously deselected package *******.
May 14 12:22:44 PLUTO majishanzu[1992]: download: (Reading database ... 29779 files and directories currently installed.)
May 14 12:22:44 PLUTO majishanzu[1992]: download: Unpacking ******* (from .../******************************.deb) ...
May 14 12:22:44 PLUTO majishanzu[1992]: download: Setting up ******* (2.00_20090216) ...
May 14 12:22:46 PLUTO majishanzu[1992]: majishanzu success ps process of majishanzu (wget'ting the new twonky version 5.1.1) using top command: 6847 6818 root S 3240 3% 3% /usr/local/bin/wget -T 30 -U buffalonas-IMHTTP/ UPNP/1.0 DLNADOC/1.50 --ca-certificate=/tmp/ca --certificate=/tmp/...
Why obviously only some users / linkstations do this only update is not known currently. Buffalo developers should know the mechanism better! This new twonky 5.1.1 version is installed in directory /usr/local/twonky-alt. This majishanzu tool can be started manually, too. You will then see that /usr/local/twonky-alt will be created containing twonky version 5.1.1.In this twonky version access to web configuration on port 9050 is not possible as confirmed by different other users in this forum. Additionally with firmware 1.26 this autoupdated twonky version 5.1.1 does not work at all, /var/log/messages : May 14 16:36:49 PLUTO twonky: Media Server script is begun. type=start
May 14 16:36:50 PLUTO twonky: Media Server begins starting. contentbase=/mnt/array1/LS-Media/Media-Server diskinfo=/mnt/array1
May 14 16:36:58 PLUTO python: pam_unix(login:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=admin
May 14 16:37:02 PLUTO dbrescan[24383]: dbrescan: start sleep [600]
May 14 16:37:03 PLUTO twonky: Media Server does not start yet.[1] Retry call ...
May 14 16:37:05 PLUTO twonky: Media Server does not start yet.[2] Retry call ...
May 14 16:37:07 PLUTO twonky: Media Server does not start yet.[3] Retry call ...
May 14 16:37:10 PLUTO twonky: Media Server does not start yet.[4] Retry call ...
May 14 16:37:12 PLUTO twonky: Media Server does not start yet.[5] Retry call ...
May 14 16:37:14 PLUTO twonky: Media Server does not start yet.[6] Retry call ...
May 14 16:37:16 PLUTO twonky: Media Server does not start yet.[7] Retry call ...
May 14 16:37:18 PLUTO twonky: Media Server does not start yet.[8] Retry call ...
May 14 16:37:20 PLUTO twonky: Media Server does not start yet.[9] Retry call ...
May 14 16:37:22 PLUTO twonky: Media Server start was failed in the start. After this, the atomheartmother and initdx process is running, but mediaserver is not running. It seems that out of some unknown reason atomheartmother and initdx (probably two monitoring processes) could not start new twonkymediaserver process. 4. Downgrading back to firmware 1.24 does not work anymore if you are one of the "lucky" ones where twonky autoupdate mechnism has already started. After downgrading to version 1.24 in linkstation webconfig media server page, you will then always get an error box telling "During firmware update media server could not be updated. Connect to internet and restart mediasserver." This is because the "majishanzu" autoupdate tool tries to download twonky 5.1.1 from secret buffalo server. But there it only finds version for firmware 1.26 which can not be installed in firmware 1.24. In /var/log/message one can see error messages that firmware is too old / not matching. 5. In order to switch back from twonky 5.1.1 to twonky 4.4.19e in firmware 1.24. or 1.26. just rename /usr/local/twonky-alt. The start-script /etc/init.d/twonky.sh will then start the "old" twonky 4.4.19e version installed in /usr/local/twonky. This version is working. I do not know why Buffalo implemented such an auto update mechanism which provides users with a non-working twonky server 5.1.1 !?? Does Buffalo know the reason for this?? I would really appreciate if Buffalo could care about this topic !!! It is really ugly if user must repair linkstation firmware in order to get a linkstation with working twonky media server!! Best regardsAlexander
dongsheng:
Thanks Alexander Renaming fix the problem, I hope buffalo come up a proper fix.
chankartat:
dongsheng, how did you fix the problem? I'm using firmware 1.37.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version