System update broke LMS

Collapse
X
Collapse
 
  • Page of 3
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 template Next
  • barrymcl
    Junior Member
    • Dec 2020
    • 17
    #1

    System update broke LMS

    > then, 'create an issue' (https://github.com/Logitech/slimserver/issues),
    > asking for the the modules for perl 5.32 to be re-built without this
    > dependency.

    Would you have any idea why that would happen? Or even how this could be
    influenced at build time? I usually build binaries on the target
    platform, using a 64 bit linux to build for that platform.

    --

    Michael
    Tags: None
    • barrymcl
      Junior Member
      • Dec 2020
      • 17
      #2
      System update broke LMS

      Hi all - I've been running LMS 8.0.1 successfully on my Linux box (running the openSUSE Tumbleweed distro), up until today, when I did a system update. Among the many packages that were updated, I believe Perl went from v. 5.30.3 to 5.32.0. Now when I attempt to start LMS, it fails with the message "The following modules failed to load: EV YAML::XS Sub::Name". I tried updating LMS to 8.1.0 in the hope that it would resolve the problem, but it didn't.

      I suppose I need to download and build the EV module and figure out where to put it so LMS can find it, but I'm not clear on the details about how to do that. The version of EV on the CPAN site is 4.33, but I see that GitHub page for Logitech/slimserver-vendor/tree/public/8.0/CPAN has the file EV-4.03.tar.gz. I'm not sure how to proceed... anyone?

        Comment

        • mherger
          Babelfish's Best Boy
          • Apr 2005
          • 24643
          #3
          System update broke LMS

          > Hi all - I've been running LMS 8.0.1 successfully on my Linux box
          > (running the openSUSE Tumbleweed distro), up until today, when I did a
          > system update. Among the many packages that were updated, I believe
          > Perl went from v. 5.30.3 to 5.32.0. Now when I attempt to start LMS, it
          > fails with the message "The following modules failed to load: EV
          > YAML::XS Sub::Name".

          What platform are you running your LMS on? We only have binaries for
          x86_64 for Perl 5.32.

          --

          Michael
          Michael

          "It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
          (LMS: Settings/Information)

            Comment

            • barrymcl
              Junior Member
              • Dec 2020
              • 17
              #4
              Originally posted by mherger
              >

              What platform are you running your LMS on? We only have binaries for
              x86_64 for Perl 5.32.
              My system is x86_64 - since openSUSE is RPM-based, I install the RPM noarch package. Since that normally works fine, I've never tried building LMS from the Unix tarball package.

                Comment

                • mherger
                  Babelfish's Best Boy
                  • Apr 2005
                  • 24643
                  #5
                  System update broke LMS

                  >> What platform are you running your LMS on? We only have binaries for
                  >> x86_64 for Perl 5.32.
                  >
                  > My system is x86_64 - since openSUSE is RPM-based, I install the RPM
                  > noarch package. Since that normally works fine, I've never tried
                  > building LMS from the Unix tarball package.

                  Hmm... could you please add --d_startup to the runtime parameters
                  (/etc/sysconfig/squeezeboxserver or similar). Then post the resulting
                  server.log.

                  --

                  Michael
                  Michael

                  "It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
                  (LMS: Settings/Information)

                    Comment

                    • barrymcl
                      Junior Member
                      • Dec 2020
                      • 17
                      #6
                      Originally posted by mherger
                      Hmm... could you please add --d_startup to the runtime parameters
                      (/etc/sysconfig/squeezeboxserver or similar). Then post the resulting
                      server.log.
                      I've done that, but it still is not creating a server.log file when I attempt to start it. Here's the contents of my /etc/sysconfig/squeezeboxserver file:

                      # Edit this to suit your setup
                      SQUEEZEBOX_USER="squeezeboxserver"
                      SQUEEZEBOX_HOME="/usr/libexec"
                      SQUEEZEBOX_CFG_DIR="/var/lib/squeezeboxserver/prefs"
                      SQUEEZEBOX_LOG_DIR="/var/log/squeezeboxserver"
                      SQUEEZEBOX_CACHE_DIR="/var/lib/squeezeboxserver/cache"
                      SQUEEZEBOX_CHARSET="utf8"
                      SQUEEZEBOX_ARGS="--d_startup --daemon --prefsdir=$SQUEEZEBOX_CFG_DIR --logdir=$SQUEEZEBOX_LOG_DIR --cachedir=$SQUEEZEBOX_CACHE_DIR --charset=$SQUEEZEBOX_CHARSET"

                      I have older server.log and scanner.log files in /var/log/squeezeboxserver, but nothing new. The last server.log before my system update says:

                      [20-11-28 14:46:40.9334] main::init (388) Starting Logitech Media Server (v8.0.1, 1606059084, Sun Nov 22 16:40:47 CET 2020) perl 5.030003 - x86_64-linux-thread-multi

                      but apparently the startup is now failing before it reaches the point of creating a log file.

                      Barry

                        Comment

                        • mherger
                          Babelfish's Best Boy
                          • Apr 2005
                          • 24643
                          #7
                          System update broke LMS

                          > I've done that, but it still is not creating a server.log file when I
                          > attempt to start it. Here's the contents of my
                          > /etc/sysconfig/squeezeboxserver file:

                          But where did you get the "The following modules failed to load: EV
                          YAML::XS Sub::Name"?

                          --

                          Michael
                          Michael

                          "It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
                          (LMS: Settings/Information)

                            Comment

                            • barrymcl
                              Junior Member
                              • Dec 2020
                              • 17
                              #8
                              Originally posted by mherger
                              > I've done that, but it still is not creating a server.log file when I
                              > attempt to start it. Here's the contents of my
                              > /etc/sysconfig/squeezeboxserver file:

                              But where did you get the "The following modules failed to load: EV
                              YAML::XS Sub::Name"?
                              That came from the system log (/var/log/messages)... curiously, when I just tried to start the server now, the syslog contained much more detailed error messages. Here's the first part of it:

                              2020-12-03T11:19:58.701155-05:00 topazdesigns systemd[1]: Starting LSB: Startup script for the Logitech Media Server...
                              2020-12-03T11:19:58.774437-05:00 topazdesigns squeezeboxserver[27326]: Starting Squeezebox Server:
                              2020-12-03T11:19:58.774548-05:00 topazdesigns squeezeboxserver[27337]: Module [DBI] failed to load:
                              2020-12-03T11:19:58.774569-05:00 topazdesigns squeezeboxserver[27337]: Can't load '/usr/share/squeezeboxserver/CPAN/arch/5.32/x86_64-linux-thread-multi/auto/DBI/DBI.so' for module DBI: libperl.so.5.32: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.32.0/x86_64-linux-thread-multi/DynaLoader.pm line 193.
                              2020-12-03T11:19:58.774583-05:00 topazdesigns squeezeboxserver[27337]: at /usr/share/squeezeboxserver/CPAN/arch/5.32/DBI.pm line 277.
                              2020-12-03T11:19:58.774756-05:00 topazdesigns squeezeboxserver[27337]: BEGIN failed--compilation aborted at /usr/share/squeezeboxserver/CPAN/arch/5.32/DBI.pm line 277.
                              2020-12-03T11:19:58.774770-05:00 topazdesigns squeezeboxserver[27337]: Compilation failed in require at (eval 12) line 1.
                              2020-12-03T11:19:58.774782-05:00 topazdesigns squeezeboxserver[27337]: BEGIN failed--compilation aborted at (eval 12) line 1.
                              2020-12-03T11:19:58.777276-05:00 topazdesigns squeezeboxserver[27337]: Module [EV] failed to load:
                              2020-12-03T11:19:58.777297-05:00 topazdesigns squeezeboxserver[27337]: Can't load '/usr/share/squeezeboxserver/CPAN/arch/5.32/x86_64-linux-thread-multi/auto/EV/EV.so' for module EV: libperl.so.5.32: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.32.0/x86_64-linux-thread-multi/DynaLoader.pm line 193.
                              2020-12-03T11:19:58.777310-05:00 topazdesigns squeezeboxserver[27337]: at /usr/share/squeezeboxserver/CPAN/EV.pm line 127.
                              2020-12-03T11:19:58.777321-05:00 topazdesigns squeezeboxserver[27337]: BEGIN failed--compilation aborted at /usr/share/squeezeboxserver/CPAN/EV.pm line 127.
                              2020-12-03T11:19:58.777332-05:00 topazdesigns squeezeboxserver[27337]: Compilation failed in require at (eval 13) line 1.
                              2020-12-03T11:19:58.777344-05:00 topazdesigns squeezeboxserver[27337]: BEGIN failed--compilation aborted at (eval 13) line 1.
                              2020-12-03T11:19:58.783670-05:00 topazdesigns squeezeboxserver[27337]: Module [XML::Parser::Expat] failed to load:
                              2020-12-03T11:19:58.783692-05:00 topazdesigns squeezeboxserver[27337]: Can't load '/usr/share/squeezeboxserver/CPAN/arch/5.32/x86_64-linux-thread-multi/auto/XML/Parser/Expat/Expat.so' for module XML::Parser::Expat: libperl.so.5.32: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.32.0/x86_64-linux-thread-multi/DynaLoader.pm line 193.
                              2020-12-03T11:19:58.783705-05:00 topazdesigns squeezeboxserver[27337]: at (eval 14) line 1.
                              2020-12-03T11:19:58.783716-05:00 topazdesigns squeezeboxserver[27337]: Compilation failed in require at (eval 14) line 1.
                              2020-12-03T11:19:58.783728-05:00 topazdesigns squeezeboxserver[27337]: BEGIN failed--compilation aborted at (eval 14) line 1.
                              2020-12-03T11:19:58.787441-05:00 topazdesigns squeezeboxserver[27337]: Module [HTML::Parser] failed to load:
                              2020-12-03T11:19:58.787464-05:00 topazdesigns squeezeboxserver[27337]: Can't load '/usr/share/squeezeboxserver/CPAN/arch/5.32/x86_64-linux-thread-multi/auto/HTML/Parser/Parser.so' for module HTML::Parser: libperl.so.5.32: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.32.0/x86_64-linux-thread-multi/DynaLoader.pm line 193.
                              2020-12-03T11:19:58.787661-05:00 topazdesigns squeezeboxserver[27337]: at (eval 15) line 1.
                              2020-12-03T11:19:58.787676-05:00 topazdesigns squeezeboxserver[27337]: Compilation failed in require at (eval 15) line 1.
                              2020-12-03T11:19:58.787687-05:00 topazdesigns squeezeboxserver[27337]: BEGIN failed--compilation aborted at (eval 15) line 1.
                              2020-12-03T11:19:58.791562-05:00 topazdesigns squeezeboxserver[27337]: Module [JSON::XS] failed to load:
                              2020-12-03T11:19:58.791583-05:00 topazdesigns squeezeboxserver[27337]: Can't load '/usr/share/squeezeboxserver/CPAN/arch/5.32/x86_64-linux-thread-multi/auto/JSON/XS/XS.so' for module JSON::XS: libperl.so.5.32: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.32.0/x86_64-linux-thread-multi/DynaLoader.pm line 193.
                              2020-12-03T11:19:58.791596-05:00 topazdesigns squeezeboxserver[27337]: at (eval 16) line 1.
                              2020-12-03T11:19:58.791607-05:00 topazdesigns squeezeboxserver[27337]: Compilation failed in require at (eval 16) line 1.
                              2020-12-03T11:19:58.791618-05:00 topazdesigns squeezeboxserver[27337]: BEGIN failed--compilation aborted at (eval 16) line 1.
                              2020-12-03T11:19:58.793848-05:00 topazdesigns squeezeboxserver[27337]: Module [Digest::SHA1] failed to load:
                              2020-12-03T11:19:58.793874-05:00 topazdesigns squeezeboxserver[27337]: Can't load '/usr/share/squeezeboxserver/CPAN/arch/5.32/x86_64-linux-thread-multi/auto/Digest/SHA1/SHA1.so' for module Digest::SHA1: libperl.so.5.32: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.32.0/x86_64-linux-thread-multi/DynaLoader.pm line 193.
                              2020-12-03T11:19:58.793887-05:00 topazdesigns squeezeboxserver[27337]: at (eval 17) line 1.
                              2020-12-03T11:19:58.793898-05:00 topazdesigns squeezeboxserver[27337]: Compilation failed in require at (eval 17) line 1.
                              2020-12-03T11:19:58.793910-05:00 topazdesigns squeezeboxserver[27337]: BEGIN failed--compilation aborted at (eval 17) line 1.
                              2020-12-03T11:19:58.796161-05:00 topazdesigns squeezeboxserver[27337]: Module [YAML::XS] failed to load:
                              2020-12-03T11:19:58.796182-05:00 topazdesigns squeezeboxserver[27337]: Can't load '/usr/share/squeezeboxserver/CPAN/arch/5.32/x86_64-linux-thread-multi/auto/YAML/XS/LibYAML/LibYAML.so' for module YAML::XS::LibYAML: libperl.so.5.32: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.32.0/x86_64-linux-thread-multi/DynaLoader.pm line 193.

                                Comment

                                • mherger
                                  Babelfish's Best Boy
                                  • Apr 2005
                                  • 24643
                                  #9
                                  System update broke LMS

                                  > /usr/share/squeezeboxserver/CPAN/arch/5.32/x86_64-linux-thread-multi/auto/XML/Parser/Expat/Expat.so'
                                  > for module XML::Parser::Expat: libperl.so.5.32: cannot open shared
                                  > /usr/lib/perl5/5.32.0/x86_64-linux-thread-multi/DynaLoader.pm line 193.

                                  Can you confirm these three files exist? And that permissions would
                                  allow the application to read them?

                                  --

                                  Michael
                                  Michael

                                  "It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
                                  (LMS: Settings/Information)

                                    Comment

                                    • barrymcl
                                      Junior Member
                                      • Dec 2020
                                      • 17
                                      #10
                                      Originally posted by mherger
                                      > /usr/share/squeezeboxserver/CPAN/arch/5.32/x86_64-linux-thread-multi/auto/XML/Parser/Expat/Expat.so'
                                      > for module XML::Parser::Expat: libperl.so.5.32: cannot open shared
                                      > /usr/lib/perl5/5.32.0/x86_64-linux-thread-multi/DynaLoader.pm line 193.

                                      Can you confirm these three files exist? And that permissions would
                                      allow the application to read them?
                                      The first file (Expat.so) exists and has universal read permissions.

                                      The third file (DynaLoader.pm) exists, but is only readable by group root... not sure that's a problem, though.

                                      The second file, libperl.so.5.32, does not exist on my system. I assume that the file needed here is:
                                      /usr/lib/perl5/5.32.0/x86_64-linux-thread-multi/CORE/libperl.so
                                      which exists and has universal read permissions.

                                      Does that clarify things, or muddy the waters further?

                                        Comment

                                        • mherger
                                          Babelfish's Best Boy
                                          • Apr 2005
                                          • 24643
                                          #11
                                          System update broke LMS

                                          > The second file, libperl.so.5.32, does not exist on my system. I
                                          > assume that the file needed here is:
                                          > /usr/lib/perl5/5.32.0/x86_64-linux-thread-multi/CORE/libperl.so
                                          > which exists and has universal read permissions.

                                          Could you try with a symlink to that file?

                                          --

                                          Michael
                                          Michael

                                          "It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
                                          (LMS: Settings/Information)

                                            Comment

                                            • barrymcl
                                              Junior Member
                                              • Dec 2020
                                              • 17
                                              #12
                                              Originally posted by mherger
                                              > The second file, libperl.so.5.32, does not exist on my system. I
                                              > assume that the file needed here is:
                                              > /usr/lib/perl5/5.32.0/x86_64-linux-thread-multi/CORE/libperl.so
                                              > which exists and has universal read permissions.

                                              Could you try with a symlink to that file?
                                              That seems like a good plan, but at the moment it is completely unclear to me where to put the symlink so that it will be found during the loading process.

                                              Barry

                                                Comment

                                                • mherger
                                                  Babelfish's Best Boy
                                                  • Apr 2005
                                                  • 24643
                                                  #13
                                                  System update broke LMS

                                                  > That seems like a good plan, but at the moment it is completely unclear
                                                  > to me where to put the symlink so that it will be found during the
                                                  > loading process.

                                                  No educated idea, tbh. But I'd start by putting it right next to the
                                                  original file.

                                                  --

                                                  Michael
                                                  Michael

                                                  "It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
                                                  (LMS: Settings/Information)

                                                    Comment

                                                    • barrymcl
                                                      Junior Member
                                                      • Dec 2020
                                                      • 17
                                                      #14
                                                      Originally posted by mherger
                                                      > That seems like a good plan, but at the moment it is completely unclear
                                                      > to me where to put the symlink so that it will be found during the
                                                      > loading process.

                                                      No educated idea, tbh. But I'd start by putting it right next to the
                                                      original file.
                                                      That didn't help. I'll have to keep digging, and maybe try to consult with someone who is familiar with the intricacies of this particular distro and its filesystem.

                                                      Barry

                                                        Comment

                                                        • agt
                                                          Member
                                                          • Oct 2020
                                                          • 38
                                                          #15
                                                          Same here.

                                                          Originally posted by barrymcl
                                                          That didn't help. I'll have to keep digging, and maybe try to consult with someone who is familiar with the intricacies of this particular distro and its filesystem.

                                                          Barry
                                                          Hi Barry, I have similar symptoms to you after a recent tumbleweed update, and am happy to work together to solve it.
                                                          The good news is that I have two instances:
                                                          My home server hasn't updated OS for a few weeks and is working fine, while I updated the OS on my office NUC last weekend, which left LMS unable to start.
                                                          This might let us track down file locations in the working instance that Michael is unsure of, and figure out what we need to fix.

                                                          Please advise if you have made any more progress since your last post.
                                                          Thanks, Alex

                                                            Comment

                                                            Previous 1 2 3 template Next
                                                            Working...

                                                            We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

                                                            By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

                                                            I Agree