Home of the Squeezebox™ & Transporter® network music players.
Page 86 of 87 FirstFirst ... 367684858687 LastLast
Results 851 to 860 of 865
  1. #851
    Senior Member jasell's Avatar
    Join Date
    May 2008
    Posts
    310
    By the way, I have som trouble running QLMS from Putty.
    And starting QLMS service takes a really long time know, or finishing the script takes long the service starts quickly.
    But if I end Putty before finishing the script then LMS stops/crash.

    I get a bunch of warnings that the commands are using the wrong operators and some line are missing formatting.
    I run a QTS 4.2 (the latest version compatible with my system).
    Do I miss some packages to be installed or do I need some language settings as that will adjust the command lines and formatting errors?


    When starting QLMS I get this message repeating 3 times, in quick sequences...
    Code:
    /bin/grep: invalid option -- w
    BusyBox v1.01 (2021.03.27-04:02+0000) multi-call binary
    
    Usage: grep [-ihHnqvs] PATTERN [FILEs...]
    
    Search for PATTERN in each FILE or standard input.
    
    Options:
            -H      prefix output lines with filename where match was found
            -h      suppress the prefixing filename on output
            -i      ignore case distinctions
            -l      list names of files that match
            -n      print line number with output lines
            -q      be quiet. Returns 0 if result was found, 1 otherwise
            -v      select non-matching lines
            -s      suppress file open/read error messages
    Then we look for the last nightly, which works fine.
    NOTICE the bad formatting on the last line...
    Code:
    [.....] Checking is there is a update for LogitechMediaServer.
    Preparing the system to run LogitechMediaServer. 
    Fixing owner/rights for squeezeboxserver on SlimServer/ !
    Fixing owner/rights for squeezeboxserver on SlimServer/ the old way !
    Starting LogitechMediaServer in the Background.
    \e[41mWaiting for LogitechMediaServer to become ready, can take a few minutes!\e
    Then I get the same message as above, repeating 90 times, and it takes a long time...
    When it is finally done I get this new error...
    Code:
    /sbin/log_tool: invalid option -- G
    Usage: /sbin/log_tool [OPTION]...
    Manipulate event logs in system.
    
            -h, --help              Display this help and exit.
            -v, --verbose           Enable verbose output.
            -c, --initdb            Initialize the table for event logs.
            -r, --rmdb              Remove the table for event logs.
            -f, --flushdb           Flush all data in the table for event logs.
            -y, --modifydb          Modify column in the table for event logs.
            -b, --maxlog N          Set the max number of logs to N.
            -a, --append MSG        Append MSG into the event log.
                    -t, --type [0-2]        Specify the event type.
                    -u, --user USER         Specify the username.
                    -p, --ip IP             Specify the IP.
                    -m, --comp NAME         Specify the computer name.
                    -x, --msgid MSGID               Specify the mesage id.
            -q, --query             Query the data of event logs.
                    -s, --sort [0-17]       Set the sort type.
                    -l, --lower NUM         Set the lower bound.
                                             (NUM >= 0, NUM <= upper)
                    -o, --upper NUM         Set the upper bound.
                                             (NUM >= 0, NUM >= lower)
                    -e, --filter [0-3]      Specify the filter type.
                    -i, --group [0-9]       group by TBL_FIELD.
                    -d, --date1 DATE1               Specify the date1 - date2.
                    -g, --date2 DATE2               Specify the date1 - date2.
                    -u, --user USER         Specify the username.
                    -p, --ip IP             Specify the IP.
                    -m, --comp NAME         Specify the computer name.
                    -k, --keyword KEYWORD           Filter the keyword in log.
    
    Event types:
            0 = Information
            1 = Warning
            2 = Error
    
    Sort types:
            0 = Sort by date in ascending order.
            1 = Sort by date in descending order.
            2 = Sort by time in ascending order.
            3 = Sort by time in descending order.
            4 = Sort by event type in ascending order.
            5 = Sort by event type in descending order.
            6 = Sort by user in ascending order.
            7 = Sort by user in descending order.
            8 = Sort by IP in ascending order.
            9 = Sort by IP in descending order.
            10 = Sort by computer name in ascending order.
            11 = Sort by computer name in descending order.
            12 = Sort by id in ascending order.
            13 = Sort by id in descending order.
            14 = Sort by msgid in ascending order.
            15 = Sort by msgid in descending order.
            16 = Sort by timet in ascending order.
            17 = Sort by timet in descending order.
    
    Report bugs to <nas_rd@qnap.com>
    /sbin/log_tool: invalid option -- N
    Usage: /sbin/log_tool [OPTION]...
    Manipulate event logs in system.
    
            -h, --help              Display this help and exit.
            -v, --verbose           Enable verbose output.
            -c, --initdb            Initialize the table for event logs.
            -r, --rmdb              Remove the table for event logs.
            -f, --flushdb           Flush all data in the table for event logs.
            -y, --modifydb          Modify column in the table for event logs.
            -b, --maxlog N          Set the max number of logs to N.
            -a, --append MSG        Append MSG into the event log.
                    -t, --type [0-2]        Specify the event type.
                    -u, --user USER         Specify the username.
                    -p, --ip IP             Specify the IP.
                    -m, --comp NAME         Specify the computer name.
                    -x, --msgid MSGID               Specify the mesage id.
            -q, --query             Query the data of event logs.
                    -s, --sort [0-17]       Set the sort type.
                    -l, --lower NUM         Set the lower bound.
                                             (NUM >= 0, NUM <= upper)
                    -o, --upper NUM         Set the upper bound.
                                             (NUM >= 0, NUM >= lower)
                    -e, --filter [0-3]      Specify the filter type.
                    -i, --group [0-9]       group by TBL_FIELD.
                    -d, --date1 DATE1               Specify the date1 - date2.
                    -g, --date2 DATE2               Specify the date1 - date2.
                    -u, --user USER         Specify the username.
                    -p, --ip IP             Specify the IP.
                    -m, --comp NAME         Specify the computer name.
                    -k, --keyword KEYWORD           Filter the keyword in log.
    
    Event types:
            0 = Information
            1 = Warning
            2 = Error
    
    Sort types:
            0 = Sort by date in ascending order.
            1 = Sort by date in descending order.
            2 = Sort by time in ascending order.
            3 = Sort by time in descending order.
            4 = Sort by event type in ascending order.
            5 = Sort by event type in descending order.
            6 = Sort by user in ascending order.
            7 = Sort by user in descending order.
            8 = Sort by IP in ascending order.
            9 = Sort by IP in descending order.
            10 = Sort by computer name in ascending order.
            11 = Sort by computer name in descending order.
            12 = Sort by id in ascending order.
            13 = Sort by id in descending order.
            14 = Sort by msgid in ascending order.
            15 = Sort by msgid in descending order.
            16 = Sort by timet in ascending order.
            17 = Sort by timet in descending order.
    
    Report bugs to <nas_rd@qnap.com>
    Finally service is started...
    NOTICE there are some "garbage", it!\e[0m , on the command line as the script is done...
    Code:
    LogitechMediaServer 8.2.0-1626678931 is started in the Background on [5323] !   
    Please wait a few minutes, before you try to access the LogitechMediaServer webgui through http://192.168.6.3:9001 !                                            
    
    [admin@QNAP2 LogitechMediaServer]$ it!\e[0m
    NAS: QNAP TS-459U+ QTS 4.2.6 (4x 2TB, RAID5)
    Services: LMS 8.2.0 by QLMS 2.21.00 QLMS at QNAP club
    Squeezebox: 6x Receiver, 3x Boom, 2x SB3 Classic, 1x Touch
    Controller: Control by Material skin or iPeng, Local music or Spotify by Spotty

  2. #852
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,622
    @digimaster - can the users of your package select which LMS build they want to use? I'm seeing a surprisingly high number of QLMS users among the early adaptors of LMS 8.3. While this doesn't hurt at this point (there's no difference between 8.3.0 and 8.2.0), there could be times of less stability, where 8.3 will have new/experimental features etc. I believe it would be good if QLMS defaulted to the stable branch.
    Michael

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

  3. #853
    Senior Member
    Join Date
    Aug 2008
    Posts
    160
    I had noticed that I'd updated to 8.3, as a result of enabling nightly updates in .QLMS.conf.

    I did think this may cause issues down the line so I used wget to download the latest stable 8.2.0 to the QLMS Backup folder then ran QlogitechMediaServer.sh rollback and selected this version to install. I then disabled nightly updates in .QLMS.conf.

  4. #854
    Senior Member dolodobendan's Avatar
    Join Date
    Dec 2017
    Location
    Braunschweig, Germany
    Posts
    1,446
    Quote Originally Posted by mherger View Post
    @digimaster - can the users of your package select which LMS build they want to use? I'm seeing a surprisingly high number of QLMS users among the early adaptors of LMS 8.3. While this doesn't hurt at this point (there's no difference between 8.3.0 and 8.2.0), there could be times of less stability, where 8.3 will have new/experimental features etc. I believe it would be good if QLMS defaulted to the stable branch.
    There's some options in the .QLMS.conf regarding updates:

    Code:
    # Update settings !
    
    #NOUPDATE=0	# (0)	[ When set only manuel update can be done, or UPDATE=/NIGHTLY= ?.?.? will trigger a update ! ]
    UPDATE=1	# (1)	[ Will check on official update on every startup, 0 will disable it. ]
    NIGHTLY=1	# (1)	[ Check on NIGHTLY update on every startup, 0 will disable it. ]
    NOMAJOR=0	# (0)	[ When set NIGHTLY wont check a major level up. Example when set if RELEASE is 7.9.2, NIGHLY will not check 8.0.0 ]
    It looks like it's only possible to prevent major updates. No options to prevent minor updates or revision updates.

    Edit: I'm getting old.

    UPDATE=0 keeps LMS at the current version and in combination with NIGHTLY=1 it will check for updates for that version. NOMINOR and NOREVISION options would be easier to understand, though. Or not. Who knows.
    Last edited by dolodobendan; 2021-08-22 at 11:21.
    QLMS 8.3@2.21 x64 (digimaster) / QNAP 469L QTS 4.3.4
    LMS 8.3 x64 / Intel NUC8 i3

  5. #855
    Senior Member
    Join Date
    May 2017
    Location
    Netherlands
    Posts
    725
    Quote Originally Posted by mherger View Post
    @digimaster - can the users of your package select which LMS build they want to use? I'm seeing a surprisingly high number of QLMS users among the early adaptors of LMS 8.3. While this doesn't hurt at this point (there's no difference between 8.3.0 and 8.2.0), there could be times of less stability, where 8.3 will have new/experimental features etc. I believe it would be good if QLMS defaulted to the stable branch.
    When in QLMS.conf NIGHTLY=1, it will look for the latest nightly build, and if found will download and install it.
    If one wants to stay on a major release, they have to set NIGHTLY=0 and UPDATE=8.2.0 in the QLMS.conf.

    This will download LMS 8.2.0 and install it, but will not check on nigthly release anymore.

    Another way is ./QLogitechmediaserver.sh rollback and choice the release, then this will be installed. Remember to disable NIGHTLY=0 in QLMS.conf

    Or set NIGHTLY=0 and UPDATE=0 or NOUPDATE=1 in QLMS.conf.
    Then download prefereerd version, and place it in the download share of QNap, and then restart QLMS.
    If one downloaded the right version/release, it will be installed, by that we the user is in controle what version will be used.

    maintainer of QLogitechMediaServer, QOptware-NG and QAutoSub.

    Qnap TS-453a, with LogitechMediaSever 8.0.0 Nightly ( with spotty, youtube, Radio Paradise a.m. )
    Several raspberry with hifiberry amp+ and picoreplayer.
    Love logitechmediaserver for it flexibel way, to play music from different sources.


    Thanks for the DONATIONS

  6. #856
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,622

    QLogitechMediaServer for Qnap withQTS 4.2 or higher and x86_64/I686/X86 support !

    > When in QLMS.conf NIGHTLY=1, it will look for the latest nightly build,
    > and if found will download and install it.


    Which nightly? There's the "stable" nightly 8.2.1, and the dev nightly
    8.3.0. Users should not be on a dev branch unless they decide to do so.
    8.2.1 is ok.


  7. #857
    Senior Member
    Join Date
    Apr 2005
    Location
    USA
    Posts
    622
    Quote Originally Posted by mherger View Post
    > When in QLMS.conf NIGHTLY=1, it will look for the latest nightly build,
    > and if found will download and install it.


    Which nightly? There's the "stable" nightly 8.2.1, and the dev nightly
    8.3.0. Users should not be on a dev branch unless they decide to do so.
    8.2.1 is ok.
    I used the defaults and just stopped and started LMS. It updated from 8.2.0 to 8.3.0.

  8. #858
    @digimaster
    I would suggest implementing the same naming scheme that is now becoming common in other implementations (piCorePlayer https://docs.picoreplayer.org/how-to/upgrade_lms/, LMS Community container https://registry.hub.docker.com/r/lm...hmediaserver/#!), that is:
    - Release version http://downloads.slimdevices.com/releases/latest.xml currently 8.2.0
    - Stable version http://downloads.slimdevices.com/rel...tly/stable.xml currently 8.2.1
    - Development version http://downloads.slimdevices.com/rel...ightly/dev.xml currently 8.3.0
    I'm not a developer, I believe this would imply some reprogramming of your update routines (perhaps taking inspiration from the piCorePlayer lms-update.sh)
    Then one could always download and copy into the public share of the QNAP whatever version they may like, this upgrade/downgrade technique is very useful and should be kept.
    (At least, these are my suggestions, I would be grateful if you could take them in consideration!)
    Last edited by scala; 2021-08-28 at 14:11.

  9. #859
    Senior Member
    Join Date
    May 2017
    Location
    Netherlands
    Posts
    725
    Quote Originally Posted by scala View Post
    @digimaster
    I would suggest implementing the same naming scheme that is now becoming common in other implementations (piCorePlayer https://docs.picoreplayer.org/how-to/upgrade_lms/, LMS Community container https://registry.hub.docker.com/r/lm...hmediaserver/#!), that is:
    - Release version http://downloads.slimdevices.com/releases/latest.xml currently 8.2.0
    - Stable version http://downloads.slimdevices.com/rel...tly/stable.xml currently 8.2.1
    - Development version http://downloads.slimdevices.com/rel...ightly/dev.xml currently 8.3.0
    I'm not a developer, I believe this would imply some reprogramming of your update routines (perhaps taking inspiration from the piCorePlayer lms-update.sh)
    Then one could always download and copy into the public share of the QNAP whatever version they may like, this upgrade/downgrade technique is very useful and should be kept.
    (At least, these are my suggestions, I would be grateful if you could take them in consideration!)
    Hmm i think you're suggestions are very good. Have to look how to make it work in QLMS.

    Thanks for bring it to my attention.


    Hat a good look, and yes inspired by lms-update.sh did give me a new direction on how to handle upgraded. Hope end September to release a newer version, where the way of updating is changed.



    Verstuurd vanaf mijn Nokia 5.3 met Tapatalk
    Last edited by digimaster; 2021-09-02 at 11:15.

    maintainer of QLogitechMediaServer, QOptware-NG and QAutoSub.

    Qnap TS-453a, with LogitechMediaSever 8.0.0 Nightly ( with spotty, youtube, Radio Paradise a.m. )
    Several raspberry with hifiberry amp+ and picoreplayer.
    Love logitechmediaserver for it flexibel way, to play music from different sources.


    Thanks for the DONATIONS

  10. #860
    Junior Member
    Join Date
    Mar 2007
    Location
    Almere, Netherlands
    Posts
    6

    QLMS on QTS 5.0 ?

    Is there already some knowledge about running QLMS on the new QTS 5.0?
    Does it work?

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
  •