Just wanted to mention a small issue I ran into migrating off of
ReadyNAS. Changing from ancient perl version changes the way URI::Encode
works, so restoring my trackstat backup was not fully accurate. See the
'Erlands plugins thread'
(https://forums.slimdevices.com/showthread.php?49483-Announce-
Ligérien wrote:
> So... I upgraded the NAS to OS6, ..
>
> Now that the NAS is stable, I may try the lastest 8.0.1 nightly to see
> if Michael's recent tweaks may work. I did no do it before as it was so
> slow
>
> Patrick
I installed 8.0.1 and it works great, already posted here:
'Med
mherger wrote:
> >
>
> [...]
>
> If you can update the NAS to some new OS, then you can handle pCP
> easily!
>
> --
>
> Michael
So... I upgraded the NAS to OS6, it went smoothly, for those who are
afraid, don't be, just Back-up before, and know that if you have
redundant disks, it takes 5
I am just not familiar enough with those little animals Raspberries and
all PiCo to know what to buy
Pi4/2GB
and install...
https://picoreplayer.org
:-)
If you can update the NAS to some new OS, then you can handle pCP easily!
--
Michael
___
Sq
mps wrote:
> Yeah, IÂve reluctantly reached the conclusion that itÂs time for me to
> retire my LMS on ReadyNAS (see my earlier post today in this thread).
> While the // is fixable, the SSL problem seems more fundamental. I hate
> seeing you have to spend time supporting such archaic systems..
Another way to check ... an automated source code checker.
I think it has not been updated for all things changed in Perl since
5.12 ... but it might help identify the size of the problem and
therefore whether or not it is now too big to tackle.
perlver - http://p3rl.org/perlver
Perl::MinimumVers
bpa wrote:
> Not a C comment but a the Perl defined OR operator "//" . The "//"
> operator is only supported in Perl 5.10 onwards and not in Perl 5.8
Would a statement in the source like "use v5.8.8;" protect against this
sort of inadvertent version dependent mishap ?
--
mherger wrote:
> > Perl 5.8.0 was released in 2002, 5.10 was 2007 -
>
> When I started to use LMS (SliMP3.pl at the time :-)) it was on Perl
> 5.8. And I had issues, crashes, which lead me to compile 5.10 for the
> sole purpose of running LMS...
IIRC - Perl got "stuck" on 5.8 for a long time
Perl 5.8.0 was released in 2002, 5.10 was 2007 -
When I started to use LMS (SliMP3.pl at the time :-)) it was on Perl
5.8. And I had issues, crashes, which lead me to compile 5.10 for the
sole purpose of running LMS...
--
Michael
___
Squeezecenter
bpa wrote:
> Triode had used one instance of "//" in BBCiPlayer plugin - it took me
> ages to find it as it caused weird problems for a NAS user.
I have to confess that IÂve used it more than once in my plugins...
(including YT) I assumed that the oldest reasonable Perl was the 5.14
used on Win
mherger wrote:
> > Not a C comment but a the Perl defined OR operator "//" . The "//"
> > operator is only supported in Perl 5.10 onwards and not in Perl 5.8
>
> Yep, we introduced an incompatible statement at some place.
>
> Considering the fact that a.) this has gone really long without
>
mherger wrote:
> > Not a C comment but a the Perl defined OR operator "//" . The "//"
> > operator is only supported in Perl 5.10 onwards and not in Perl 5.8
>
> Yep, we introduced an incompatible statement at some place.
>
> Considering the fact that a.) this has gone really long without
>
bpa wrote:
> Not a C comment but a the Perl defined OR operator "//" . The "//"
> operator is only supported in Perl 5.10 onwards and not in Perl 5.8
Ah, looks like I have C++ bias in my thinking. Thanks for setting me
straight :)
-
Not a C comment but a the Perl defined OR operator "//" . The "//"
operator is only supported in Perl 5.10 onwards and not in Perl 5.8
Yep, we introduced an incompatible statement at some place.
Considering the fact that a.) this has gone really long without
noticing, and b.) SSL on these in
mps wrote:
> Here's the problem: A C-style comment and maybe a missing semicolon. If
> I replace
> >
Code:
> > # Load the handler when requested..
> my $handler = $class->loadURLHandler($url)
> // $class->loadHandler($protocol);
>
Hi Michael,
File sent by email.
Re-downloaded and reinstalled, clean, rebooted NAS in between deletion
of previous version and reinstall.
==> Same errors, same output of the command line function .
I'll go back to 7.9.3 in the meantime. 7.9.4 is called v7.9.4_unreleased
so I won't try :)
Any cl
Here's the problem: A C-style comment and maybe a missing semicolon. If
I replace
Code:
# Load the handler when requested..
my $handler = $class->loadURLHandler($url)
// $class->loadHandler($protocol);
with
Code:
It doesn't look like the attachment went through on the last comment.
Trying it again.
32301
+---+
|Filename: ProtocolHandlers.pm |
|Download: http://forums.slimdevices.com/attachment.php?attach
mherger wrote:
> Great. The good news is: it doesn't crash in the same place any more.
> The bad news is: it's crashing on a line which has not changed in 12
> years...
>
> >DynaLoader.pm => /usr/lib/perl/5.8/DynaLoader.pm
> >
> >dirsFor: Didn't find a match request: [scprefs]
> >
mherger wrote:
> EDIT: forget the following. Just download LMS 8.0.1 instead:
> http://downloads.slimdevices.com/nightly/?ver=8.0
>
>
No. That again gives me a server log of
Code:
2020-11-23 11:37:00 Logitech Media Server died. Restarting.
2020-11-23 11:37:15 Logit
Great. The good news is: it doesn't crash in the same place any more.
The bad news is: it's crashing on a line which has not changed in 12
years...
DynaLoader.pm => /usr/lib/perl/5.8/DynaLoader.pm
dirsFor: Didn't find a match request: [scprefs]
Bareword found where operator expec
Code:
Got @INC containing:
/c/.squeezeboxserver
/usr/share/squeezeboxserver/CPAN
/usr/share/squeezeboxserver
/usr/sbin
/etc/perl
/usr/local/lib/perl/5.8.8
/usr/local/share/perl/5.8.8
/usr/lib/perl5
/usr/share/perl5
/usr/lib/perl/5.8
/usr/share/perl/5.
Is there a file
/usr/share/squeezeboxserver/CPAN/arch/5.8/i386-linux-thread-multi/Audio/Scan.pm?
Yes, there is:
-rw-r--r-- 1 backup 1000 24497 2020-11-23 08:52 Scan.pm
Odd.
And could you please post the output of
Code:
> > /usr/sbin/squeezeboxserver --prefsdir /c
mherger wrote:
> > Sorry, version 8.0.1 does not work, same issue as before:
>
> Argh... what revision is this?
The latest from this morning 8:55:
logitechmediaserver-8.0.1-1606118512-i386-readynas.bin. I double
checked...
>
> Is there a file
> /usr/share/squeezeboxserver/CPAN/arch/5.8/i386-
Sorry, version 8.0.1 does not work, same issue as before:
Argh... what revision is this?
Is there a file
/usr/share/squeezeboxserver/CPAN/arch/5.8/i386-linux-thread-multi/Audio/Scan.pm?
--
Michael
___
Squeezecenter mailing list
Squeezecenter@lists.
mherger wrote:
> >> I need to edit my posting. Please download 8.0.1 instead
> >> (http://downloads.slimdevices.com/nightly/?ver=8.0).
> >
> > Downloading. I assume I don't need to replace/add Scan.pm for this
> > version?
>
> Correct.
>
> > Yeah, i run into those issues also for other things,
I need to edit my posting. Please download 8.0.1 instead
(http://downloads.slimdevices.com/nightly/?ver=8.0).
Downloading. I assume I don't need to replace/add Scan.pm for this
version?
Correct.
Yeah, i run into those issues also for other things, like domoticZ...
Do you know if the upgrade
>I need to edit my posting. Please download 8.0.1 instead
>(http://downloads.slimdevices.com/nightly/?ver=8.0).
Downloading. I assume I don't need to replace/add Scan.pm for this
version?
>Lack of up-to-date SSL support will be a problem. As more and more
sites
>move to using https, you'll run
Ok, could you please try the following: download
I need to edit my posting. Please download 8.0.1 instead
(http://downloads.slimdevices.com/nightly/?ver=8.0).
It started all right, here is the server.log with quite a few errors.
Excellent!
[20-11-23 12:10:08.1309] Slim::Networking::Re
mherger wrote:
> Ok, could you please try the following: download
>
> https://raw.githubusercontent.com/andygrundman/Audio-Scan/7b9cec5ec2308bdf248824636f6347f9176e6397/lib/Audio/Scan.pm
>
> and save it in
>
> /usr/share/squeezeboxserver/CPAN/arch/5.8/i386-linux-thread-multi/Audio/
>
> You'll
Ok, could you please try the following: download
https://raw.githubusercontent.com/andygrundman/Audio-Scan/7b9cec5ec2308bdf248824636f6347f9176e6397/lib/Audio/Scan.pm
and save it in
/usr/share/squeezeboxserver/CPAN/arch/5.8/i386-linux-thread-multi/Audio/
You'll have to create the Audio folder,
OK. This fixes it, but seems insane.
It's not! You've actually found an issue I had "fixed" a first time more
than six years ago. See the commit message here:
https://github.com/Logitech/slimserver/commit/8bcd23b10407b9106e2e341238e3607382f3d892
I'll see what I can do. Will probably just do
Hi Michael,
OK. This fixes it, but seems insane.
In /usr/share/squeezeboxserver/lib/Audio/Scan.pm
Code:
BEGIN {
# foreach ('0.99', '0.93', '0.95', '0.94') {# Get rid of this line
foreach ('0.95') { # And replace it with this
on
OK. It crashes in /usr/share/squeezeboxserver/lib/Audio/Scan.pm in the
line
Code:
eval { XSLoader::load('Audio::Scan', $_); };
This is in a loop where it segfaults on the third time through, with $_
= '0.95'
-
Thanks for the response, Michael. I'm a little confused where to put the
prints. I put one at the bottom of bootstrap.pm, and it prints fine. I
put a print statement at the top of squeezeboxServer, and it doesn't
print. Finally, I put CHECK blocks in both files, and neither one prints
anything. C
Hmm, it successfully gets to the end of the BEGIN block that calls
loadModule, do you have any ideas where to print next?
That's good to know! This means most likely it's not a binary causing
the problem (which I would not have understood anyway, as we didn't
touch them).
Next up would be th
Hmm, it successfully gets to the end of the BEGIN block that calls
loadModule, do you have any ideas where to print next?
In case it's useful, here's a gdb stacktrace of the segv, but there is
no symbol table info, so I can't do anything like "info locals"
Code:
Progra
Oops! That wasn't the line that was crashing! Since I was printing to
stdout, the output was buffered and not necessarily printed before the
crash. Changing my print statement to print STDERR shows that I get all
the way to the end of loadModules. I will push forward to find the
actual segfaultin
Thanks, Michael. It segfaults in
https://github.com/Logitech/slimserver/blob/776e969ec5f8101f20f7687f525d42674ea52900/Slim/bootstrap.pm#L257
Code:
$SIG{'PIPE'} = 'IGNORE';
The following modules are loaded after the second attempt:
.
Segmentation fault
Ok, you seem to feel comfortable on the command line. What we see here
is that you get pretty far in the bootstrap process. The above line
comes from:
https://github.com/Logitech/slimserver/blob/publ
Thanks, Michael. Now we're getting somewhere
Code:
prairie:/etc/frontview/addons/bin/SQUEEZEBOX# /usr/sbin/squeezeboxserver
--prefsdir /c/.squeezeboxserver/prefs --logdir /c/.squeezeboxserver/log
--cachedir /c/.squeezeboxserver/cache --d_startup
Got @INC containing:
Exactly. Please add d_startup on the command line, too.
Michael
"It doesn't work - what shall I do?" - "Please check your server.log
and/or scanner.log file!"
(LMS: Settings/Information)
mherger's Profile: http://forums.
mherger wrote:
> >>> Thanks for responding, Michael. Unfortunately, the log is also
> the[color=blue][color=green]
>
>
> Sure, but still no additional output?!? Can you paste the full command
> as you entered it, with all its output?
>
> Michael
Code:
prairie:/etc/
Thanks for responding, Michael. Unfortunately, the log is also the
same
Hmm... what if you run the server directly as you tried before? With the
additional --d_startup parameter?
Still segfaults...
Sure, but still no additional output?!? Can you paste the full command
as you entered it, wi
mherger wrote:
> > Thanks for responding, Michael. Unfortunately, the log is also the
> same
>
> Hmm... what if you run the server directly as you tried before? With the
>
> additional --d_startup parameter?
>
Still segfaults...
--
Thanks for responding, Michael. Unfortunately, the log is also the same
Hmm... what if you run the server directly as you tried before? With the
additional --d_startup parameter?
Did any binary modules change between 7.9.1 and 7.9.4?
No! That's exactly why I'm utterly confused, why I'd lik
Thanks for responding, Michael. Unfortunately, the log is also the same
Code:
prairie:/etc/frontview/addons/bin/SQUEEZEBOX# cat
/c/.squeezeboxserver/log/server.log
2020-11-21 00:30:05 squeezeboxserver_safe started.
2020-11-21 00:30:20 Logitech Media Server died. Res
A small update. Following the advice in
https://forums.slimdevices.com/showthread.php?113243-Media-Server-7-9-2-not-working-on-ReadyNAS-Ultra/page2,
I set SLIMOPTIONS to --d_startup with absolutely no change in behavior
That option wouldn't change any of the behaviour, except for the
logging. C
A small update. Following the advice in
https://forums.slimdevices.com/showthread.php?113243-Media-Server-7-9-2-not-working-on-ReadyNAS-Ultra/page2,
I set SLIMOPTIONS to --d_startup with absolutely no change in behavior
:(
I just upgraded my ReadyNas Pro Logitech Media Server from 7.9.1 =>
7.9.4, and it no longer starts :(
slimserver.log just keeps repeating " Logitech Media Server died.
Restarting."
I tried manually running /usr/sbin/squeezeboxserver and immediately get
a segmentation fault.
I am using perl 5.8
50 matches
Mail list logo
