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. 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. It seems that out of some unknown reason atomheartmother and initdx (probably two monitoring processes) could not start new twonkymediaserver process.Ĥ. May 14 16:37:22 PLUTO twonky: Media Server start was failed in the start.Īfter this, the atomheartmother and initdx process is running, but mediaserver is not running. May 14 16:37:20 PLUTO twonky: Media Server does not start yet. May 14 16:37:18 PLUTO twonky: Media Server does not start yet. May 14 16:37:16 PLUTO twonky: Media Server does not start yet. May 14 16:37:14 PLUTO twonky: Media Server does not start yet. May 14 16:37:12 PLUTO twonky: Media Server does not start yet. May 14 16:37:10 PLUTO twonky: Media Server does not start yet. May 14 16:37:07 PLUTO twonky: Media Server does not start yet. May 14 16:37:05 PLUTO twonky: Media Server does not start yet. May 14 16:37:03 PLUTO twonky: Media Server does not start yet. May 14 16:37:02 PLUTO dbrescan: dbrescan: start sleep May 14 16:36:58 PLUTO python: pam_unix(login:auth): authentication failure logname= uid=0 euid=0 tty= ruser= rhost= user=admin contentbase=/mnt/array1/LS-Media/Media-Server diskinfo=/mnt/array1 May 14 16:36:50 PLUTO twonky: Media Server begins starting. May 14 16:36:49 PLUTO twonky: Media Server script is begun.
In this twonky version access to web configuration on port 9050 is not possible as confirmed by different other users in this forum.Īdditionally with firmware 1.26 this autoupdated twonky version 5.1.1 does not work at all, /var/log/messages : You will then see that /usr/local/twonky-alt will be created containing twonky version 5.1.1. This majishanzu tool can be started manually, too. This new twonky 5.1.1 version is installed in directory /usr/local/twonky-alt. Buffalo developers should know the mechanism better! Why obviously only some users / linkstations do this only update is not known currently. Ps process of majishanzu (wget'ting the new twonky version 5.1.1) using top command:Ħ847 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/. May 14 12:22:46 PLUTO majishanzu: majishanzu success May 14 12:22:44 PLUTO majishanzu: download: Unpacking ******* (from. 29779 files and directories currently installed.) May 14 12:22:44 PLUTO majishanzu: download: (Reading database. May 14 12:22:44 PLUTO majishanzu: download: Selecting previously deselected package *******. May 14 12:22:33 PLUTO majishanzu: download: HTTP request sent, awaiting response. In /var/log/messages and /var/log/linkstation.log one can see the behaviour of this majishanzu update tool: 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. 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. It is installed in directory /usr/local/twonkyĢ. with this twonky version access of webconfiguration on port 9050 is working. Linkstation with firmware 1.24 and 1.26 comes natively with twonkymedia 4.4.19_e2. 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.ġ. Is there any current firmware with "enableweb=2" for Linkstation LS_WXL? etc/init.d/twonky.sh creates a default twonky configuration ini file with enableweb=1 !!:Įcho "contentbase=$ I have downloaded latest Firmware 1.24 and extracted it.
0 kommentar(er)
