Home of the Squeezebox™ & Transporter® network music players.
Results 1 to 3 of 3
  1. #1
    Junior Member
    Join Date
    Jan 2013
    Posts
    19

    Non-ANSI file names in server.log

    Logitech Media Server Version: 7.7.6 - 1521467459 @ Thu Mar 29 16:57:02 CEST 2018
    Operating system: Linux - EN - utf8
    Perl Version: 5.26.1 - arm-linux
    -----

    Hi All,

    When delete some files with non-ANSI characters and rescan, non-human readable logs are produced:
    [19-11-01 17:01:48.6549] Slim::Utils::Scanner::Local::deleted (582) Handling deleted audio file file:///DataVolume/Public/Shared%20Music/%D0%9A%D0%B8%D0%BD%D0%BE/2010_%D0%9B%D1%83%D1%87%D1%88%D0%B5%D0%B5_(CD3)/01._%D0%93%D1%80%D1%83%D0%BF%D0%BF%D0%B0_%D0%BA%D1 %80%D0%BE%D0%B2%D0%B8.flac

    The following logs are expected instead:
    [19-11-01 17:01:48.6549] Slim::Utils::Scanner::Local::deleted (582) Handling deleted audio file file:///DataVolume/Public/Shared Music/Кино/2010_Лучшее_(CD3)/01._Группа_крови.flac

    Is it possible to configure LMS to get human readable logs or do I miss anything?

    Thanks,
    Sergey

  2. #2
    Senior Member
    Join Date
    Aug 2012
    Location
    Austria
    Posts
    938
    Quote Originally Posted by tals View Post
    When delete some files with non-ANSI characters and rescan, non-human readable logs are produced:
    [19-11-01 17:01:48.6549] Slim::Utils::Scanner::Local::deleted (582) Handling deleted audio file file:///DataVolume/Public/Shared%20Music/%D0%9A%D0%B8%D0%BD%D0%BE/2010_%D0%9B%D1%83%D1%87%D1%88%D0%B5%D0%B5_(CD3)/01._%D0%93%D1%80%D1%83%D0%BF%D0%BF%D0%B0_%D0%BA%D1 %80%D0%BE%D0%B2%D0%B8.flac

    The following logs are expected instead:
    [19-11-01 17:01:48.6549] Slim::Utils::Scanner::Local::deleted (582) Handling deleted audio file file:///DataVolume/Public/Shared Music/Кино/2010_Лучшее_(CD3)/01._Группа_крови.flac

    Is it possible to configure LMS to get human readable logs or do I miss anything?
    LMS url-encodes paths (which is the correct way to handle them), and that's the representation you see in the logs.
    If you want to have the un-encoded version, here's a bash function:
    Code:
    urldecode(){
      echo -e "$(sed 's/+/ /g;s/%\(..\)/\\x\1/g;')"
    }
    then you can do this:
    cat server.log|urldecode
    Various SW: Web Interface | Playlist Editor / Generator | Music Classification | Similar Music | Announce | EventTrigger | LMSlib2go | ...
    Various HowTos: build a self-contained LMS | Bluetooth/ALSA | Control LMS with any device | ...

  3. #3
    Junior Member
    Join Date
    Jan 2013
    Posts
    19
    Quote Originally Posted by Roland0 View Post
    LMS url-encodes paths (which is the correct way to handle them), and that's the representation you see in the logs.
    If you want to have the un-encoded version, here's a bash function:
    Code:
    urldecode(){
      echo -e "$(sed 's/+/ /g;s/%\(..\)/\\x\1/g;')"
    }
    then you can do this:
    cat server.log|urldecode
    Thank you!
    Nice workaround.

Tags for this Thread

Posting Permissions

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