Home of the Squeezebox™ & Transporter® network music players.
Page 97 of 107 FirstFirst ... 47879596979899 ... LastLast
Results 961 to 970 of 1065
  1. #961
    Member gonk's Avatar
    Join Date
    Aug 2005
    Location
    Linkeboda, Sweden
    Posts
    40
    I've been struggling with my server for several weeks with unexpected crashes several times every day, and in some cases automatic restarts. The only clue I had was the "GDResizer.pm", similar as cbondeson found in the logfiles. First thing I did was to install the 7.9 server, the previous version I used was many years old, but that did not solve anything. Failsafe mode or database rebuild from the control panel did not solve the issue.

    The solution that now seems to work was to clear the whole Cache-directory and let the server build this from scratch.

    The size of C:\ProgramData\Squeezebox\Cache was 6.4GB! I renamed the Cache directory and the server rebuilt everything, new size after build is now only 98MB...

    I guess there are better way to rebuild the Cache directory than removing it completely, but I didn't found any other way. Largest file before rebuild was "artwork.db" (5300MB). Some of the settings on the IRblaster plugin was lost.

    Hope this helps for others as well.

    Quote Originally Posted by cbondeson View Post
    16-09-03 19:37:43.8506] Slim::Utils::Misc::msg (1244) Warning: [19:37:43.8503] Perl interpreter failed at /<C:\PROGRA~2\SQUEEZ~1\server\SqueezeSvr.exe>Slim/Utils/GDResizer.pm line 165.

    Same error after every attempt to play.

    LogitechMediaServer-7.9.0-1472937447 @ Sat Sep 3 21:26:49 CUT 2016


    Same error with a previous version: LogitechMediaServer-7.9.0-1469176740

    Environment: Windows 10, 16 GB memory, Intel


    Rescanned music and error is gone.. Ah well


    Played for over an hour and then the same error..argh
    Does this unit has a bad motivator?

  2. #962
    Senior Member
    Join Date
    Jan 2010
    Posts
    537
    Quote Originally Posted by gonk View Post
    I guess there are better way to rebuild the Cache directory than removing it completely, but I didn't found any other way. Largest file before rebuild was "artwork.db" (5300MB). Some of the settings on the IRblaster plugin was lost.
    You could also delete/rename all *.db files in the cache folder.
    Usually the artwork.db will grow over time to cache the graphics in various resolutions.

  3. #963
    Senior Member DJanGo's Avatar
    Join Date
    Sep 2005
    Location
    Germany
    Posts
    2,524
    Quote Originally Posted by gonk View Post
    The only clue I had was the "GDResizer.pm"
    /snip
    \snap
    Largest file before rebuild was "artwork.db" (5300MB).
    GD Resizer is Artwork related.
    Since your artwork.db is huge - Please describe what you listen to and what kind of plugins you are using.
    Where is your Artwork? local embedded as file in folder?

  4. #964
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    19,872

    7.9 Problems/Bugs

    > I guess there are better way to rebuild the Cache directory than
    > removing it completely, but I didn't found any other way. Largest file
    > before rebuild was "artwork.db" (5300MB).


    Can you check the Settings in Advanced/Performance? There's an option
    which would list image formats LMS does pre-cache. What do you see there?

    I did fix an issue in 7.9 which could have caused massive growth for
    artwork.db. But it's an issue which requires the new creation of that
    file. Just running 7.9 would not have changed it. Therefore that growth
    problem might now be gone. Please let me know if that's not the case.

    --

    Michael

  5. #965
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    19,872

    7.9 Problems/Bugs

    > You could also delete/rename all *.db files in the cache folder.
    > Usually the artwork.db will grow over time to cache the graphics in
    > various resolutions.


    It should not grow infinitely. An old problem was that it wouldn't free
    the disk space recovered by wiping data. But it would re-use it over
    time. Therefore growth should stop at some point. Unless your collection
    grows, of course :-)

    --

    Michael

  6. #966
    Senior Member Webkemmi's Avatar
    Join Date
    May 2009
    Location
    Germany
    Posts
    167
    Michael,
    since I did a clean install, removed the unused plugins and replaced my SB Radio with a SB Touch and external speakers, LMS 7.9 ran stable since some days.
    Maybe the SB radio crashed the LMS service. Each time the problem appeared, the wifi icon on the SB radio was red while all SB Touch kept connected.
    I also cleaned up all unused players in mySB.com and the server.prefs now only contains real existing players.

    Nevertheless the server.log still shows these dispatching errors:

    Name:  not_dispatchable.JPG
Views: 136
Size:  240.8 KB

    Can they be ignored?

  7. #967
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    19,872

    7.9 Problems/Bugs

    > Nevertheless the server.log still shoes these dispatching errors:

    In future posting please copy/paste log entries as text, rather then
    uploading a screenshot. It's simpler, faster, and saves lots of bytes.
    And most of all I can read them in the mail and don't have to visit the
    web based forum :-).

    > Can they be ignored?


    I've mentioned this twice in this discussion: there must be some
    controller software running in your environment trying to control a
    player which is no longer connected. If this shows up after you've
    powered down a player, then this is totally normal. But as you've pasted
    this kind of log several times, I wonder how often you have players
    disappear.

    --

    Michael

  8. #968
    Senior Member Webkemmi's Avatar
    Join Date
    May 2009
    Location
    Germany
    Posts
    167
    Quote Originally Posted by mherger View Post
    > Nevertheless the server.log still shoes these dispatching errors:

    In future posting please copy/paste log entries as text, rather then
    uploading a screenshot. It's simpler, faster, and saves lots of bytes.
    And most of all I can read them in the mail and don't have to visit the
    web based forum :-).

    > Can they be ignored?


    I've mentioned this twice in this discussion: there must be some
    controller software running in your environment trying to control a
    player which is no longer connected. If this shows up after you've
    powered down a player, then this is totally normal. But as you've pasted
    this kind of log several times, I wonder how often you have players
    disappear.

    --

    Michael
    OK, I will paste text in the future.
    I use several iOS devices with iPeng as mobile players. Of course these devices are disconnected when I leave my home with my iPhone for example. Also the iPads disconnect from wifi when they are not in use.
    Can these iOS devices cause the log entries? Is there a way to switch on a kind of enhanced logging for identifying the player(s) causing these issues?

  9. #969
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    19,872

    7.9 Problems/Bugs

    > Can these iOS devices cause the log entries? Is there a way to switch on
    > a kind of enhanced logging for identifying the player(s) causing these
    > issues?


    Sounds like a reasonable request. I'll look into this.

    --

    Michael

  10. #970
    Senior Member Webkemmi's Avatar
    Join Date
    May 2009
    Location
    Germany
    Posts
    167
    Quote Originally Posted by mherger View Post
    Sounds like a reasonable request. I'll look into this.

    --

    Michael
    Great, thanks!

Posting Permissions

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