You are here: Home » Topic » How-to setup Firefly on a Synology disk station (powerpc)page 3

How-to setup Firefly on a Synology disk station (powerpc)

FireFly Media Server (formerly mt-daapd) Firefly Media Server Forums Firefly Media Server Setup Issues How-to setup Firefly on a Synology disk station (powerpc)

This topic contains 75 replies, has 19 voices, and was last updated by  Anonymous 9 years, 3 months ago.

Viewing 15 posts - 31 through 45 (of 76 total)
  • Author
    Posts
  • #14518

    cstern
    Participant

    For me I have a, maybe related, problem. If I copy new music to the DS107 Firefly will abort, and the web interface becomes unavailable – but I don’t even get the login box.

    In the log I can see that (the) Firefly crash landed after receiving a HUP signal.

    Also multiple requests at the same time to the server causes a crash. I think this is kind of well known with this release in combination with the sqlite database format.

    Maybe it works better with sqlite3 which can be selected in the web-interface. I tried it (sqlite3) once but had problems, and went back to sqlite. I will try again and see if stability improves. Perhaps you should try the same…

    #14519

    Anonymous

    @cstern wrote:

    For me I have a, maybe related, problem. If I copy new music to the DS107 Firefly will abort, and the web interface becomes unavailable – but I don’t even get the login box.

    In the log I can see that (the) Firefly crash landed after receiving a HUP signal.

    Also multiple requests at the same time to the server causes a crash. I think this is kind of well known with this release in combination with the sqlite database format.

    Maybe it works better with sqlite3 which can be selected in the web-interface. I tried it (sqlite3) once but had problems, and went back to sqlite. I will try again and see if stability improves. Perhaps you should try the same…

    Now I have another issue… Since this morning, I cannot log in to the web interface at all. Not even after 3 reboots of my DS-207…? Anyone tried this?

    #14520

    cstern
    Participant

    Try to log on to the box using telnet. Then check the last few lines of the log file:

    tail -20 /var/log/mt-daapd.log | more

    and see if this gives a clue to what is wrong

    #14521

    Anonymous

    @cstern wrote:

    Try to log on to the box using telnet. Then check the last few lines of the log file:

    tail -20 /var/log/mt-daapd.log | more

    and see if this gives a clue to what is wrong

    DiskStation> tail -20 /var/log/mt-daapd.log | more
    2007-12-04 21:00:37 (00004000): Updating playlists
    2007-12-04 21:00:37 (00004000): Updating playlists
    2007-12-04 21:00:46 (00004000): Updating playlists
    2007-12-04 21:00:46 (00004000): Updating playlists
    2007-12-04 21:00:46 (00004000): Updating playlists
    2007-12-04 21:00:46 (00004000): Updating playlists
    2007-12-04 21:00:46 (00004000): Updating playlists
    2007-12-04 21:00:47 (00004000): Updating playlists
    2007-12-04 21:00:47 (00004000): Scanned 4839 songs in 303 seconds
    2007-12-04 21:00:47 (00004000): Starting web server from /opt/share/mt-daapd/adm in-root on port 3689
    2007-12-04 21:00:47 (00004000): Registering rendezvous names
    2007-12-04 21:00:47 (00004000): Serving 4839 songs. Startup complete in 303 sec onds
    2007-12-04 21:02:26 (00008003): Thread 0: Entering ws_returnerror (401: Unauthor ized)
    2007-12-04 21:02:30 (0000c003): Thread 1: Entering ws_returnerror (302: Moved)
    2007-12-04 21:22:59 (00004000): Got HUP signal.
    2007-12-04 21:22:59 (003a4003): Auth: failed attempt to gain admin privs by fro m 192.168.0.18
    2007-12-04 21:22:59 (003a4003): Thread 231: Entering ws_returnerror (401: Unauth orized)

    Can anyone tell me what this means?

    #14522

    rpedde
    Participant

    @cstern wrote:

    For me I have a, maybe related, problem. If I copy new music to the DS107 Firefly will abort, and the web interface becomes unavailable – but I don’t even get the login box.

    In the log I can see that (the) Firefly crash landed after receiving a HUP signal.

    Also multiple requests at the same time to the server causes a crash. I think this is kind of well known with this release in combination with the sqlite database format.

    Maybe it works better with sqlite3 which can be selected in the web-interface. I tried it (sqlite3) once but had problems, and went back to sqlite. I will try again and see if stability improves. Perhaps you should try the same…

    Ah, the hup thing. yeah. On non-nptl pthreads machines (or maybe it’s ulibc machines, not sure) a sighup makes it crash. The thing is, the synology has a disk indexer that indexes any new media on the file system, and then HUPs mt-daapd to make it reindex. Sadly, that makes it die. 🙁

    The workaround is to kill the synology indexer thing. Can’t remember the process name, though, as I dont have a synology.

    At least until I can fix it to ignore hups.

    — Ron

    #14523

    SydneyGuy
    Participant

    What I did to get around the dreaded HUP problem was to rename /usr/syno/bin/synoindex to synoindex.old

    It’s a heavy handed approach but it stopped the damned indexing and the HUP problems haven’t been seen since.

    #14524

    cstern
    Participant

    @sydneyguy wrote:

    What I did to get around the dreaded HUP problem was to rename /usr/syno/bin/synoindex to synoindex.old

    It’s a heavy handed approach but it stopped the damned indexing and the HUP problems haven’t been seen since.

    Hi SydneyGuy – do you know what it is supposed to do? What services on the DS can be affected of the indexer not running?

    #14525

    SydneyGuy
    Participant

    It does the multimedia indexing so it would affect their multimedia services. Given how absolutely useless I found their multimedia service I certainly don’t miss it.

    Even with all the services disabled the indexer still runs. Synology support have said they may look at changing this so it only runs when ones of the services that require is enabled.

    Just rename the file as I did and make sure that everything that you need is still working. If not you can simply rename it back.

    #14526

    cstern
    Participant

    @sydneyguy wrote:

    It does the multimedia indexing so it would affect their multimedia services. Given how absolutely useless I found their multimedia service I certainly don’t miss it.

    Even with all the services disabled the indexer still runs. Synology support have said they may look at changing this so it only runs when ones of the services that require is enabled.

    Just rename the file as I did and make sure that everything that you need is still working. If not you can simply rename it back.

    Fine. I will put it in the “recipe”. Thanks.

    Edit: It is now updated.

    #14527

    Anonymous

    I trying to use the guide provided in the first post to get my Synology 207+ to work with a Soundbridge 1001 and I have gotten to point no. 4. then I get syntax errors. Can someone guide me and maybe tell me where I am going wrong. I dont have much(any) experience in working with telnet and these things so please be as specifik as You can. I have pasted the dialog from the telnet underneath.
    Thanks.
    /Rasmus

    BusyBox v1.1.0 (2007.11.01-13:20+0000) Built-in shell (ash)
    Enter ‘help’ for a list of built-in commands.

    Synology> cd /volume1/public
    Synology> sh ds101-bootstrap_1.0-4_powerpc.xsh
    DS-10x Bootstrap extracting archive… please wait
    bootstrap
    bootstrap/bootstrap.ipk
    bootstrap/ipkg.ipk
    bootstrap/openssl.ipk
    bootstrap/wget-ssl.ipk
    10009+1 records in
    10009+1 records out
    bootstrap/bootstrap.sh
    bootstrap/ipkg.sh
    Creating temporary ipkg repository… success
    Installing DS101(g)-bootstrap package…Unpacking bootstrap.ipk…Done.
    Configuring bootstrap.ipk…Regenerating dynamic linker cache…
    /opt/sbin/ldconfig: /opt/sbin/ldconfig: 1: Syntax error: “(” unexpected Done.
    success
    Installing IPKG package… (Ignore missing md5sum warning)
    Unpacking ipkg.ipk…Done.
    Configuring ipkg.ipk…./ipkg.sh: ./ipkg.sh: 1170: md5sum: not found
    Configuration file `/opt/etc/ipkg.conf’
    ==> File on system created by you or by a script.
    ==> File also in package provided by package maintainer.
    What would you like to do about it ? Your options are:
    Y or I : install the package maintainer’s version
    N or O : keep your currently-installed version
    D : show the differences between the versions (if diff is installed)
    The default action is to keep your current version.
    *** ipkg.conf (Y/I/N/O/D) [default=N] ? Y
    ./ipkg.sh: ./ipkg.sh: 1170: md5sum: not found
    Done.
    Removing temporary ipkg repository…
    Installing OpenSSL../opt/bin/ipkg: /opt/bin/ipkg: 1: Syntax error: “(” unexpecte
    d

    BusyBox v1.1.0 (2007.11.01-13:20+0000) Built-in shell (ash)
    Enter ‘help’ for a list of built-in commands.

    Synology> ipkg update
    /opt/bin/ipkg: /opt/bin/ipkg: 1: Syntax error: “(” unexpected

    #14528

    cstern
    Participant

    The 207+ is based on another chip – Marvell mv5281.

    To install FF on the 207+ you have to go this path:

    http://www.synology.com/wiki/index.php/Compiled_programs_for_Marvell_mv5281_ARM-based_Synology_Products#Firefly.2FMt-daapd_by_Mike

    Note the download link in the end of the article – you can get further help in the Synology forum on Marvell based boxes:

    http://www.synology.com/enu/forum/viewforum.php?f=55

    #14529

    Anonymous
    #14530

    Anonymous

    Thanks.

    Is it possible to get one of You guys to make a to-do list for me (and others) on what files to install and how to install it. Im pretty new to this, so that would be a great help! TIA

    /Rasmus

    #14531

    Anonymous

    Rasmus, please follow the link posted – it’s a kind of todo-list!

    You only need to know the type of your Diskstation (-> which CPU).

    Cheers, Martin

    #14532

    Anonymous

    I just wanted to post a huge thank you here to cstern for posting such clear and detailed instructions. Using them, I was able to get Firefly up and running on my Synology DS-106j quite easily.

    I did find that the latest nightly build (1696) had some stability issues and crashed when accessing large playlists, so I went back to 1586, and it seems to be working fine now. (You can install an earlier version by adding the “-force-downgrade” argument to the ipkg install command noted at the beginning of this thread.)

Viewing 15 posts - 31 through 45 (of 76 total)

The forum ‘Setup Issues’ is closed to new topics and replies.