sfraser

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 15 total)
  • Posted in:
  • 17. Mai 2022 at 18:37 #52225

    Not sure I understand, would this be added to the M2P client mount, or the TrueNAS server files system ACL?

    Thanks,

    5. Oktober 2021 at 0:21 #51702

    I have done something similar with a couple of pi’s. I have several old slimdevices SB’s, Radio’s of various vintages and types still in circulation as well as several max2play pi’s running squeezelite. The SB radios are in the bathrooms and home gym, the rest of the squeezebox’s are co-located with the family room stereo and basement home theatre. However in my rear porch and kitchen I have wall mount and ceiling mount speakers and no pratical spot for a stereo system. For those two installations I ran the speaker wire back down to the basement to a 19″ rack. I built two pi’s and installed them in two hifiBerry metal cases with the XLR DAC pro variant HAT’s. They plug directly into separate 2 chan. amps. Of course Max2play is running on all the pi’s , and I use the volume control on the squeezelite S/W via the material skin URL on my phone to control all the players and the volume per player. I often have the porch, family room and kitchen sync’d together but not always. The Crown amps are very powerful , several hundred watts per channel, so I set the gain on the amps to 50%, to help avoid accidents. Everything works very well. I don’t see any issue co-locating all the Pi’s with a 8 channel amp as you mentioned. I did have a pi4 running as the LMS server for a while and it worked great with a 90k track library and 8-10 players. I have since moved the LMS to a jail in a FreeNAS server which also hosts my music library.

    20. August 2020 at 21:47 #49568

    Sorry for hijacking this thread. Does MAX2play SAMBAshares support SMBv1 ?

    • This reply was modified 1 year, 11 months ago by  sfraser.
    • This reply was modified 1 year, 11 months ago by  sfraser.
    • This reply was modified 1 year, 11 months ago by  sfraser.
    22. August 2019 at 16:15 #46827

    Been running M2P on a new Pi4 w/4G RAM installed in a FLirc case for 2 days now. Music is accessed via cifs on a freenas host. Initial scan of 90K libarary was around 80 minutes VS 4 hours on the Pi3. Flirc case is keeping temps down via passive cooling, nothing else to report other than two thumsb up! Thanks guys!

    7. August 2019 at 18:02 #46706

    Ok disabling Full tech search seemed to work. The scan did not fail and I can reliably access the LMS after a start and stop of the LMS process .

    Thanks !

    Scott

    6. August 2019 at 17:55 #46662

    After reviewing the debug again, it looks like perl revision issue?

    #### SQUEEZESERVER LOG ####
    2019-08-06 11:42:14 squeezeboxserver_safe started.

    #### PERL VERSION ####
    v5.24.1

    #### SQUEEZEBOXSERVER PERL VERSION FOUND ####
    5.24

    2. August 2019 at 17:17 #46647

    Please see log output below. BTW I have been disscusing another issue with Michael Herger over on the LMS forum inregards to scans terminating unexpectedly. He mentioned a „nonindexed parameter“ being added recently, and asked if i had downgraded without wiping the database. Could these issues be related?

    Thanks,

    Scott

    2019-08-01 18:08:51 squeezeboxserver_safe stopped.
    2019-08-02 10:58:52 squeezeboxserver_safe started.
    [19-08-02 10:58:55.3236] main::init (387) Starting Logitech Media Server (v7.9.1, 1522157629, Fri Mar 30 12:27:11 CEST 2018) perl 5.024001 – arm-linux-gnueabihf-thread-multi-64int
    [19-08-02 10:58:56.6737] Slim::Plugin::FullTextSearch::Plugin::_initPopularTerms (501) Fulltext index missing or outdated – re-building
    [19-08-02 10:58:56.6744] Slim::Plugin::FullTextSearch::Plugin::_rebuildIndex (396) Starting fulltext index build
    [19-08-02 10:58:56.6748] Slim::Plugin::FullTextSearch::Plugin::_rebuildIndex (400) Initialize fulltext table
    [19-08-02 10:58:56.6756] Slim::Schema::Storage::throw_exception (122) Error: DBI Exception: DBD::SQLite::db do failed: unrecognized parameter: notindexed=id [for Statement „DROP TABLE IF EXISTS fulltext;“]
    [19-08-02 10:58:56.6762] Slim::Schema::Storage::throw_exception (122) Backtrace:

    frame 0: Slim::Utils::Log::logBacktrace (/usr/share/perl5/Slim/Schema/Storage.pm line 122)
    frame 1: Slim::Schema::Storage::throw_exception (/usr/share/squeezeboxserver/CPAN/DBIx/Class/Storage/DBI.pm line 1007)
    frame 2: DBIx::Class::Storage::DBI::__ANON__ (/usr/share/perl5/Slim/Plugin/FullTextSearch/Plugin.pm line 402)
    frame 3: Slim::Plugin::FullTextSearch::Plugin::_rebuildIndex (/usr/share/perl5/Slim/Plugin/FullTextSearch/Plugin.pm line 504)
    frame 4: Slim::Plugin::FullTextSearch::Plugin::_initPopularTerms (/usr/share/perl5/Slim/Plugin/FullTextSearch/Plugin.pm line 120)
    frame 5: Slim::Plugin::FullTextSearch::Plugin::initPlugin (/usr/share/perl5/Slim/Utils/PluginManager.pm line 391)
    frame 6: (eval) (/usr/share/perl5/Slim/Utils/PluginManager.pm line 391)
    frame 7: Slim::Utils::PluginManager::load (/usr/sbin/squeezeboxserver line 597)
    frame 8: main::init (/usr/sbin/squeezeboxserver line 675)
    frame 9: main::main (/usr/sbin/squeezeboxserver line 1213)

    [19-08-02 10:58:56.6768] Slim::Utils::PluginManager::load (393) Warning: Couldn’t call Slim::Plugin::FullTextSearch::Plugin->initPlugin: Carp::Clan::__ANON__(): DBI Exception: DBD::SQLite::db do failed: unrecognized parameter: notindexed=id [for Statement „DROP TABLE IF EXISTS fulltext;“] at /usr/share/perl5/Slim/Schema/Storage.pm line 126
    2019-08-02 10:59:13 squeezeboxserver_safe stopped.
    2019-08-02 11:00:20 squeezeboxserver_safe started.
    2019-08-02 11:00:26 Logitech Media Server died. Restarting.
    2019-08-02 11:00:33 Logitech Media Server died. Restarting.
    2019-08-02 11:00:38 squeezeboxserver_safe stopped.
    2019-08-02 11:00:38 squeezeboxserver_safe started.
    2019-08-02 11:00:43 Logitech Media Server died. Restarting.
    2019-08-02 11:00:48 Logitech Media Server died. Restarting.
    2019-08-02 11:00:53 Logitech Media Server died. Restarting.
    2019-08-02 11:00:58 Logitech Media Server died. Restarting.
    2019-08-02 11:01:03 Logitech Media Server died. Restarting.
    2019-08-02 11:01:08 Logitech Media Server died. Restarting.
    2019-08-02 11:01:13 Logitech Media Server died. Restarting.
    2019-08-02 11:01:18 Logitech Media Server died. Restarting.
    2019-08-02 11:01:23 Logitech Media Server died. Restarting.
    2019-08-02 11:01:28 Logitech Media Server died. Restarting.
    2019-08-02 11:01:33 Logitech Media Server died. Restarting.
    2019-08-02 11:01:38 Logitech Media Server died. Restarting.
    2019-08-02 11:01:43 Logitech Media Server died. Restarting.
    2019-08-02 11:01:48 Logitech Media Server died. Restarting.
    2019-08-02 11:01:53 Logitech Media Server died. Restarting.
    2019-08-02 11:01:58 Logitech Media Server died. Restarting.
    2019-08-02 11:02:03 Logitech Media Server died. Restarting.
    2019-08-02 11:02:08 Logitech Media Server died. Restarting.
    2019-08-02 11:02:14 Logitech Media Server died. Restarting.
    2019-08-02 11:02:19 Logitech Media Server died. Restarting.
    2019-08-02 11:02:24 Logitech Media Server died. Restarting.
    2019-08-02 11:02:29 Logitech Media Server died. Restarting.
    2019-08-02 11:02:34 Logitech Media Server died. Restarting.
    2019-08-02 11:02:39 Logitech Media Server died. Restarting.
    2019-08-02 11:02:44 Logitech Media Server died. Restarting.
    2019-08-02 11:02:49 Logitech Media Server died. Restarting.
    2019-08-02 11:02:54 Logitech Media Server died. Restarting.
    2019-08-02 11:02:59 Logitech Media Server died. Restarting.
    2019-08-02 11:03:04 Logitech Media Server died. Restarting.
    2019-08-02 11:03:09 Logitech Media Server died. Restarting.
    2019-08-02 11:03:14 Logitech Media Server died. Restarting.
    2019-08-02 11:03:19 Logitech Media Server died. Restarting.
    2019-08-02 11:03:24 Logitech Media Server died. Restarting.
    2019-08-02 11:03:29 Logitech Media Server died. Restarting.
    2019-08-02 11:03:34 Logitech Media Server died. Restarting.
    2019-08-02 11:03:39 Logitech Media Server died. Restarting.
    2019-08-02 11:03:44 Logitech Media Server died. Restarting.
    2019-08-02 11:03:49 Logitech Media Server died. Restarting.
    2019-08-02 11:03:54 Logitech Media Server died. Restarting.
    2019-08-02 11:03:59 Logitech Media Server died. Restarting.
    2019-08-02 11:04:04 Logitech Media Server died. Restarting.
    2019-08-02 11:04:09 Logitech Media Server died. Restarting.
    2019-08-02 11:04:14 Logitech Media Server died. Restarting.
    2019-08-02 11:04:19 Logitech Media Server died. Restarting.
    2019-08-02 11:04:24 Logitech Media Server died. Restarting.
    2019-08-02 11:04:29 Logitech Media Server died. Restarting.
    2019-08-02 11:04:34 Logitech Media Server died. Restarting.
    2019-08-02 11:04:39 Logitech Media Server died. Restarting.
    2019-08-02 11:04:44 Logitech Media Server died. Restarting.
    2019-08-02 11:04:49 Logitech Media Server died. Restarting.
    2019-08-02 11:04:54 Logitech Media Server died. Restarting.
    2019-08-02 11:04:59 Logitech Media Server died. Restarting.
    2019-08-02 11:05:04 Logitech Media Server died. Restarting.
    2019-08-02 11:05:09 Logitech Media Server died. Restarting.
    2019-08-02 11:05:14 Logitech Media Server died. Restarting.
    2019-08-02 11:05:19 Logitech Media Server died. Restarting.
    2019-08-02 11:05:24 Logitech Media Server died. Restarting.
    2019-08-02 11:05:29 Logitech Media Server died. Restarting.
    2019-08-02 11:05:34 Logitech Media Server died. Restarting.
    2019-08-02 11:05:39 Logitech Media Server died. Restarting.
    2019-08-02 11:05:44 Logitech Media Server died. Restarting.
    2019-08-02 11:05:49 Logitech Media Server died. Restarting.
    2019-08-02 11:05:54 Logitech Media Server died. Restarting.
    2019-08-02 11:05:59 Logitech Media Server died. Restarting.
    2019-08-02 11:06:04 Logitech Media Server died. Restarting.
    2019-08-02 11:06:09 Logitech Media Server died. Restarting.
    2019-08-02 11:06:14 Logitech Media Server died. Restarting.
    2019-08-02 11:06:19 Logitech Media Server died. Restarting.
    2019-08-02 11:06:24 Logitech Media Server died. Restarting.
    2019-08-02 11:06:29 Logitech Media Server died. Restarting.
    2019-08-02 11:06:34 Logitech Media Server died. Restarting.
    2019-08-02 11:06:39 Logitech Media Server died. Restarting.
    2019-08-02 11:06:44 Logitech Media Server died. Restarting.
    2019-08-02 11:06:49 Logitech Media Server died. Restarting.
    2019-08-02 11:06:54 Logitech Media Server died. Restarting.
    2019-08-02 11:06:59 Logitech Media Server died. Restarting.
    2019-08-02 11:07:04 Logitech Media Server died. Restarting.
    2019-08-02 11:07:09 Logitech Media Server died. Restarting.
    2019-08-02 11:07:14 Logitech Media Server died. Restarting.
    2019-08-02 11:07:19 Logitech Media Server died. Restarting.
    2019-08-02 11:07:24 Logitech Media Server died. Restarting.
    2019-08-02 11:07:29 Logitech Media Server died. Restarting.
    2019-08-02 11:07:34 Logitech Media Server died. Restarting.
    2019-08-02 11:07:39 Logitech Media Server died. Restarting.
    2019-08-02 11:07:44 Logitech Media Server died. Restarting.
    2019-08-02 11:07:49 Logitech Media Server died. Restarting.
    2019-08-02 11:07:54 Logitech Media Server died. Restarting.
    2019-08-02 11:07:59 Logitech Media Server died. Restarting.
    2019-08-02 11:08:04 Logitech Media Server died. Restarting.
    2019-08-02 11:08:10 Logitech Media Server died. Restarting.
    2019-08-02 11:08:15 Logitech Media Server died. Restarting.
    2019-08-02 11:08:20 Logitech Media Server died. Restarting.
    2019-08-02 11:08:25 Logitech Media Server died. Restarting.
    2019-08-02 11:08:30 Logitech Media Server died. Restarting.
    2019-08-02 11:08:35 Logitech Media Server died. Restarting.
    2019-08-02 11:08:40 Logitech Media Server died. Restarting.
    2019-08-02 11:08:45 Logitech Media Server died. Restarting.
    2019-08-02 11:08:50 Logitech Media Server died. Restarting.
    2019-08-02 11:08:55 Logitech Media Server died. Restarting.
    2019-08-02 11:09:00 Logitech Media Server died. Restarting.
    2019-08-02 11:09:05 Logitech Media Server died. Restarting.
    2019-08-02 11:09:10 Logitech Media Server died. Restarting.
    2019-08-02 11:09:15 Logitech Media Server died. Restarting.
    2019-08-02 11:09:20 Logitech Media Server died. Restarting.
    2019-08-02 11:09:25 Logitech Media Server died. Restarting.
    2019-08-02 11:09:30 Logitech Media Server died. Restarting.
    2019-08-02 11:09:35 Logitech Media Server died. Restarting.
    2019-08-02 11:09:40 Logitech Media Server died. Restarting.
    2019-08-02 11:09:45 Logitech Media Server died. Restarting.
    2019-08-02 11:09:50 Logitech Media Server died. Restarting.

    #### PERL VERSION ####
    v5.24.1

    #### SQUEEZEBOXSERVER PERL VERSION FOUND ####
    5.24

    1. August 2019 at 21:31 #46633

    I would like to comply, but I can’t get to the LMS log files, at least not directly via LMS, when the server won’t respond to the 9000 port call.

    30. Juli 2019 at 18:09 #46571

    Now that we have the option for more RAM along with the faster CPU with the Pi4’s has anyone investigated at what size LMS libary we should start looking at the 2G or 4G model? Will the OS allow the LMS database to utilize the additional RAM effectively?

    I am approaching 90k tracks stored on a remote FREENAS file system, so I am also interested in the faster network speed during file scan’s etc.

    Thanks

    Scott

    PS Great work BTW!

    2. Mai 2019 at 18:22 #45220

    Thankyou, Yes that is exactly what I did last night.

    Cheers,

    Scott

    25. Juni 2018 at 20:43 #36360

    Understood, In general, under normal operating circumstances only one LMS is up and operational, the 2nd M2P is up, but the LMS is stopped. With no sarcasm or complaining implied, I have found the M2P/LMS to be less than reliable over the past year or so, therefore I have a second unit on backup. If the primary unit fails, I start the the 2nd LMS migrate the players, and rebuild the primary when I have the time.

    • This reply was modified 4 years, 1 month ago by  sfraser.
    • This reply was modified 4 years, 1 month ago by  sfraser.
    • This reply was modified 4 years, 1 month ago by  sfraser.
    23. Juni 2018 at 4:11 #36319

    Here are some of the failed scan results. Again, a second identical unit has no issues completing a scan onthe same files. I will run a a scan on the „working“ unit tomorrow and post the results for comparison.

    [18-06-22 18:20:35.3437] Slim::Utils::Scanner::Local::new (853) Handling new audio track file:///mnt/media/LMS/MP3/Dave/Compilations/Ace%20Ventura_%20Pet%20Detective/11%20Ace%20Is%20In%20The%20House.mp3
    [18-06-22 18:20:35.3447] Slim::Schema::_newTrack (1489)
    New Track: [file:///mnt/media/LMS/MP3/Dave/Compilations/Ace%20Ventura_%20Pet%20Detective/11%20Ace%20Is%20In%20The%20House.mp3]
    [18-06-22 18:20:35.3452] Slim::Schema::_newTrack (1499) readTags is 1
    [18-06-22 18:20:35.3562] Audio::Scan::scan (75) Warning: Error: Unable to read at least 631 bytes from file.
    [18-06-22 18:20:35.3679] Slim::Schema::forceCommit (2156) Syncing to the database.
    [18-06-22 18:20:35.4275] Slim::Utils::SQLiteHelper::updateProgress (439) Notify to server: [„exit“]
    [18-06-22 18:20:40.4392] Slim::Utils::SQLiteHelper::updateProgress (468) Notify to server failed: 500 read timeout

    22. Juni 2018 at 15:28 #36316

    Hi I am back, had some family issues to take care of the past few weeks. I rebuilt the problematic Pi again yesterday and I am still seeing terminated media scans. I am running another scan now, will post the log’s in a couple of hours.

    Both Pi’s are now running M2P 2.46 with LMS 7.9.2 – 1529332109 . both Pi’s mount the same NAS file system with same userid/password. One scan’s perfectly, the other has the media scan termination notice. I have notice it is now failing after approx 65k tracks (out of 77k) instead of at 55K reportly earlier. I may try a new micro SIM card over the weekend as well, as they can sometimes be at the root of all evil.

    Thanks

    Scott

    27. Oktober 2017 at 15:37 #32160

    Hi, i always use the IP address of the node to access the node. Is there any reason why it should not work with ip address vs the host name?

    Thanks for your help,

    Scott

    27. Oktober 2017 at 3:57 #32140

    Looks like there might be a bigger issue, as I am experiencing the same symptoms. I can access LMS via port 9000 but not max2play directly. I did try restarting apache with no success. see below

    [email protected]:~$ sudo /etc/init.d/apache2 start
    Starting apache2 (via systemctl): apache2.serviceWarning: Unit file of apache2.service changed on disk, ’systemctl daemon-reload‘ recommended.
    Job for apache2.service failed. See ’systemctl status apache2.service‘ and ‚journalctl -xn‘ for details.
    failed!
    [email protected]:~$ sudo systemctl daemon-reload
    [email protected]:~$ sudo /etc/init.d/apache2 start
    Starting apache2 (via systemctl): apache2.serviceJob for apache2.service failed. See ’systemctl status apache2.service‘ and ‚journalctl -xn‘ for details.
    failed!
    [email protected]:~$

Viewing 15 posts - 1 through 15 (of 15 total)