Results 1 to 10 of 10

Thread: mt-daapd - memory issue

  1. #1
    Join Date
    Jun 2007
    Location
    Sweden
    Posts
    33

    mt-daapd - memory issue

    Hi, I have installed mt-daapd and get this message when I try to start it:
    Could not open songs database (/opt/var/mt-daapd/songs.gdb): Cannot allocate memory

    The mt-daapd doesn't start, does anyone have any idea why?
    I have had the package installed earlier on my 700gE but now it seems like it will not work.

    Appreciate any input on this problem.

    Regards, Rejan

  2. #2
    which user is configured to have r/w permissions on this file?

    change the permissions (temporary) to xrw (with unix cmd chmod 777 songs.db) to eliminate such problems

    ...

    greets

  3. #3
    Join Date
    Jun 2007
    Location
    Sweden
    Posts
    33
    Quote Originally Posted by eitsch View Post
    which user is configured to have r/w permissions on this file?

    change the permissions (temporary) to xrw (with unix cmd chmod 777 songs.db) to eliminate such problems

    ...

    greets
    No luck with that, still same problem.

    /Rejan

  4. #4
    Try running mt-daapd from command line with the following flags:
    /opt/sbin/mt-daapd -f -r -d 9 -c /opt/etc/mt-daapd/mt-daapd.conf

    -f Runs mt-daapd in forground, this way you can see all steps during execution to stdout
    -r rebuilds the song database - maybe it's corrupt?
    -d 9 turns debug logging on to level 9 (max level)
    -c path to configuration file. This assumes the default install of mt-daapd config file.

    Logging information is stored in /var/log/mt-daapd.log.

    X

  5. #5
    Join Date
    Jun 2007
    Location
    Sweden
    Posts
    33
    Quote Originally Posted by xmeister View Post
    Try running mt-daapd from command line with the following flags:
    /opt/sbin/mt-daapd -f -r -d 9 -c /opt/etc/mt-daapd/mt-daapd.conf

    -f Runs mt-daapd in forground, this way you can see all steps during execution to stdout
    -r rebuilds the song database - maybe it's corrupt?
    -d 9 turns debug logging on to level 9 (max level)
    -c path to configuration file. This assumes the default install of mt-daapd config file.

    Logging information is stored in /var/log/mt-daapd.log.

    X
    Got following result:
    Read web_root: /opt/share/mt-daapd/admin-root
    Read port: 3689
    Read admin_pw: mypassword
    Read db_dir: /opt/var/mt-daapd
    Read mp3_dir: /shares/MYVOLUME1/MYSHARE1/Music/iPod
    Read servername: NSLU2 Music
    Read runas: myuser
    Read playlist: /opt/etc/mt-daapd/mt-daapd.playlist
    Read extensions: .mp3,.m4a,.m4p
    Read rescan_interval: 600
    Read always_scan: 0
    Checking existence of /shares/MYVOLUME1/MYSHARE1/Music/iPod
    Checking existence of /opt/var/mt-daapd
    Starting rendezvous daemon
    Could not open songs database (/opt/var/mt-daapd/songs.gdb): Cannot allocate memory

    Did not get the logfil in the specified directory

    /Rejan

  6. #6
    Well, only other thing I can think of is to rename opt/var/mt-daapd/songs.gdb to something else so it can't find it and it might try and rebuild. How big is this file? Maybe it legitimitally can't open it.

    Also if it is some sort of permissions issue try changing your runas user in the mt-daapd.config file to root (only temporarily of course).

    X

  7. #7
    Join Date
    Jun 2007
    Location
    Sweden
    Posts
    33
    Quote Originally Posted by xmeister View Post
    Well, only other thing I can think of is to rename opt/var/mt-daapd/songs.gdb to something else so it can't find it and it might try and rebuild. How big is this file? Maybe it legitimitally can't open it.

    Also if it is some sort of permissions issue try changing your runas user in the mt-daapd.config file to root (only temporarily of course).

    X
    Done that, deleted the file and got it recreated, ran as root nothing seems to work. My guess is that the package dependencies has change since I had it installed earlier, perhaps gdbm? I have tried earlier packages of mt-daapd but no luck there either.

    /Rejan

  8. #8
    I got the same error.
    ipkg install gdbm -force-reinstall
    fixed it

  9. #9
    Thanks to tsp.
    I had the same problem like Rejan and your command resolved the problem.

    "ipkg install gdbm -force-reinstall"
    fixed it

    Thanks again

  10. #10
    I was wrong the first time.
    The solution is to remove mt-daapd and all dependencies first and than reinstall mt-daapd again. Reconfigure your confs or save them before

    Remove mt-daapd with dependencies:
    ipkg remove mt-daapd (Enter)
    ipkg remove gdbm -force-depends (Enter)
    ipkg remove libid3tag -force-depends (Enter)

    Reinstall mt-daapd:
    ipkg install mt-daapd (Enter)

    During the installation of mt-daapd you can see that it automatically reinstalls the removed dependencies.

    Good Luck

Similar Threads

  1. Memory exchange on WL-500g
    By Tamadite in forum WL-500g Q&A
    Replies: 4
    Last Post: 20-01-2007, 09:46
  2. WL-520g Wireless Network Encryption Issue
    By RULLe in forum WL-500g Q&A
    Replies: 0
    Last Post: 17-01-2007, 15:39
  3. Replies: 4
    Last Post: 02-08-2006, 11:02
  4. Replies: 3
    Last Post: 04-05-2006, 13:46

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •