Thanks for your feedback, Greg. I decided to tone down the warning. It
has been around for years, but nobody seems to have experienced any
negative effect. 8.3 should not longer show this message unless you
incrase the log level.
___
Squeezecenter
SamY wrote:
> It was way before my involvement with LMS but 'this thread'
> (https://forums.slimdevices.com/showthread.php?74458-Adding-a-player-parameter)
> from 2010 explains its origin. It seems that the notification's callback
> was originally defined only in the iPeng client app, which is
mherger wrote:
>
> Hard to tell: I can't find any code related to this notification! What
> would the first two parameters be?
It was way before my involvement with LMS but this thread beginning in
2010 explains its origin. It seems that the notification's callback was
originally defined
Slim::Control::Request::notifyFromArray($client,
['getexternalvolumeinfo', 0, 1, string(())]);
Hard to tell: I can't find any code related to this notification! What
would the first two parameters be?
___
Squeezecenter mailing list
mherger wrote:
> What would your plugin be?
Hi, Michael. I was just browsing this thread and saw that Chris never
responded to your question regarding his 'post'
Has anybody ever got in touch with the Squeezelite-X author wrt. this
issue? Maybe he could give some insight into what's going on.
And then I'm probably simply going to tone down the warning, as it has
been around forever, and from what it seems the issue reported has been
of no negative
FWIW, I, too, see this error in my logs when restarting LMS.
Code:
[22-01-14 21:52:54.9520] Slim::Control::Request::renderAsArray (2233) Error:
request should set useIxHashes in Slim::Control::Request->new()
[22-01-14 21:52:54.9524]
Ah great, now I jinxed it. And it's back to the drawing board.
>
> [21-09-05 00:09:59.2925] main::init (390) Starting Logitech Media Server
> (v8.3.0, 1630708871, Sat Sep 4 01:31:25 CEST 2021) perl 5.030001 -
> x86_64-linux-thread-multi
> [21-09-05 11:31:36.1364]
mherger wrote:
> > Whatever you did it seems to have worked!
>
> Hmm... I don't think I've done anything. Are you still logging with
> INFO? I'm wondering whether enabling logging actually would "fix" this
> issue some miraculous way...
No, it's back to log only error level events. There
Whatever you did it seems to have worked!
Hmm... I don't think I've done anything. Are you still logging with
INFO? I'm wondering whether enabling logging actually would "fix" this
issue some miraculous way...
___
Squeezecenter mailing list
mherger wrote:
> > Erm, can you think of any reason why this error would NOT appear when
> > info logging control.command? I alternated between info and error
> > logging when restarting LMS and I could only observe this with the
> > default error level logging. :confused:
>
> Hmm... I quickly
mherger wrote:
> > Erm, can you think of any reason why this error would NOT appear when
> > info logging control.command? I alternated between info and error
> > logging when restarting LMS and I could only observe this with the
> > default error level logging. :confused:
>
> Hmm... I quickly
Erm, can you think of any reason why this error would NOT appear when
info logging control.command? I alternated between info and error
logging when restarting LMS and I could only observe this with the
default error level logging. :confused:
Hmm... I quickly skimmed code, but I didn't see any
I'm glad to hear that. :)
Erm, can you think of any reason why this error would NOT appear when
info logging control.command? I alternated between info and error
logging when restarting LMS and I could only observe this with the
default error level logging. :confused:
QLMS 8.3@2.21 x64
I did set control.command to "info" and made it stick. I then restarted
LMS by stopping QLMS, waiting for it to terminate all processes, and
then restarting QLMS. There's no trace of this error in the server.log,
but I'll try again. The error should be there, right? It doesn't get a
different
mherger wrote:
> > Now it seems to back to five events. Does this help in any way?
>
> Not really...
>
> Ok, this is going to be noisy, but will hopefully get us more
> information about which call is being made: enable logging for
> control.command, make the setting stick, restart LMS.
Now it seems to back to five events. Does this help in any way?
Not really...
Ok, this is going to be noisy, but will hopefully get us more
information about which call is being made: enable logging for
control.command, make the setting stick, restart LMS. Then upload your
server.log.zip
mherger wrote:
> > Still my main startup event:
>
> At some point you mentioned the LineIn plugin as a trigger for one/some
>
> of these. Could you please enable debug logging for this plugin, make
> log settings stick, restart, and check what you get for it?
Did I? I cannot remember using
Still my main startup event:
At some point you mentioned the LineIn plugin as a trigger for one/some
of these. Could you please enable debug logging for this plugin, make
log settings stick, restart, and check what you get for it?
___
Squeezecenter
Aesculus wrote:
> Sorry to be late to this thread. My plugin causes this hash error when
> using iPeng.
>
What would your plugin be?
Michael
"It doesn't work - what shall I do?" - "Please check your server.log
and/or scanner.log file!"
(LMS: Settings/Information)
Still my main startup event:
Code:
[21-08-22 20:30:23.2386] main::init (390) Starting Logitech Media Server
(v8.3.0, 1629376548, Thu Aug 19 15:01:35 CEST 2021) perl 5.030001 -
x86_64-linux-thread-multi
[21-08-22 20:30:44.2684]
Sorry to be late to this thread. My plugin causes this hash error when
using iPeng.
Either of these methods results in the error:
Slim::Control::Request::notifyFromArray($client,
['getexternalvolumeinfo', 0, 1, string(())]);
Slim::Control::Request::notifyFromArray($client,
I've got the same:
https://forums.slimdevices.com/showthread.php?112769-Recurring-error-in-LMS-logs-quot-request-should-set-useIxHashes-quot
gorman's Profile: http://forums.slimdevices.com/member.php?userid=56
View this
Shozzer wrote:
> Just looking further at this it seems to occur when the server is
> restarted and Squeezelite-X is trying to reconnect to the server. If I
> exit Squeezelite-X and restart the server then no problem occurs. Would
> others concur?
Sorry, I missed your post. Does this also
I am having a similar errors and just stumbled on this thread. See
https://forums.slimdevices.com/showthread.php?111897-SB3-randomly-resetting=970632=1#post970632
[20-03-29 18:07:29.0456] Slim::Control::Request::renderAsArray (2233)
Error: request should set useIxHashes in
Just looking further at this it seems to occur when the server is
restarted and Squeezelite-X is trying to reconnect to the server. If I
exit Squeezelite-X and restart the server then no problem occurs. Would
others concur?
Hi
I too am seeing the same error in my log files. Has anyone had any
further thoughts regarding this error?
Steve
Shozzer's Profile: http://forums.slimdevices.com/member.php?userid=58726
View this thread:
Paul Webster wrote:
> Do you have any home automation connected to LMS?
No. I think the closest to home automation would be my Philips Hue
bridge, but it's not connected to LMS.
Here's my LMS installation manual (German / English mix):
The .XMLs for Multi Library and Custom Browse are "just
Do you have any home automation connected to LMS?
Paul Webster
http://dabdig.blogspot.com
Author Radio France (FIP etc) plugin
Paul Webster's Profile: http://forums.slimdevices.com/member.php?userid=105
View this thread:
mherger wrote:
> > Does this help in any way?
> I'm a bit lost, tbh. I believe it is being triggered by some external
> system talking to LMS over the CLI. But all my suspicions have been
> proved wrong so far.
>
> --
> --
>
> Michael
Can't blame you. What would be such an "external
Does this help in any way?
I'm a bit lost, tbh. I believe it is being triggered by some external
system talking to LMS over the CLI. But all my suspicions have been
proved wrong so far.
--
--
Michael
___
Squeezecenter mailing list
- I installed the Line-In plugin, restarted LMS via the popup dialog
and got the error.
- Then I stopped QLMS (which stopped everything LMS related, I
suppose): No error.
- Then I uninstalled that plugin again and restarted using the popup
dialog and got the error again:
Code:
There are too many changing parts right now... (LMS updates, SLX is now
on 64 bit, etc.)
I deactivated all Plugins except Custom Browse, Custom Scan, Multi
Library, and Material. I didn't get the error when I restarted LMS
(using the restart dialog). I reactivated the plugins, two at the time,
I don't:
I wonder whether philippe_44's bridges might suffer from a similar
problem. Philippe, would your plugins be using the getexternalvolumeinfo
notification?
--
Michael
___
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
mherger wrote:
> > Thanks for investigating this. Log attached.
>
> Are you using IRBlaster? If not, what other 3rd party plugins?
>
> Anybody else here using IRBlaster? Or not? :-)
>
> --
>
> Michael
Yes I do have the IRBlaster plugin installed.
Ralphy
*1*-Touch, *5*-Classics,
mherger wrote:
> > Thanks for investigating this. Log attached.
>
> Are you using IRBlaster? If not, what other 3rd party plugins?
>
> Anybody else here using IRBlaster? Or not? :-)
>
> --
>
> Michael
I don't:
29307
+---+
Thanks for investigating this. Log attached.
Are you using IRBlaster? If not, what other 3rd party plugins?
Anybody else here using IRBlaster? Or not? :-)
--
Michael
___
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
mherger wrote:
> Could you please enable logging for network.cometd, make the setting
> stick, then restart LMS? That should give (a lot!) more information
> about who's talking to LMS.
>
> --
>
> Michael
Thanks for investigating this. Log attached.
mherger wrote:
> Could you please enable logging for network.cometd, make the setting
> stick, then restart LMS? That should give (a lot!) more information
> about who's talking to LMS.
>
> --
>
> Michael
Do you want me to do that again with CLI? I reinstalled LMS from scratch
when I
Could you please enable logging for network.cometd, make the setting
stick, then restart LMS? That should give (a lot!) more information
about who's talking to LMS.
--
Michael
___
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
mherger wrote:
> > With material 1.3.1 installed, I'm getting 5 occurances with ipeng
> > classic.
>
> Are you using Squeezelite-X on Windows, too? I still haven't been able
> to reproduce this issue.
>
> --
>
> Michael
No. I'm not using SLX.
Ralphy
*1*-Touch, *5*-Classics, *3*-Booms,
With material 1.3.1 installed, I'm getting 5 occurances with ipeng
classic.
Are you using Squeezelite-X on Windows, too? I still haven't been able
to reproduce this issue.
--
Michael
___
Squeezecenter mailing list
ralphy wrote:
> With material 1.3.1 installed, I'm getting 5 occurances with ipeng
> classic.
> >
Code:
> >
> [20-02-04 12:22:12.9718] main::init (387) Starting Logitech Media Server
(v8.0.0, r20789.d9c3b2280, 1580849057) perl 5.024001 -
dolodobendan wrote:
> With LMS 8.0.0 there's only two occurrences of this error, not the usual
> four:
>
> (LMS needed a restart to update Material to 1.3.1. So, could be that,
> too.)
>
> @ralphy: Do you still get two instances of this error, or is it cut in
> half, too?
With material 1.3.1
With LMS 8.0.0 there's only two occurrences of this error, not the usual
four:
Code:
[20-02-02 20:29:34.7569] main::init (387) Starting Logitech Media Server
(v8.0.0, 1580340675, Thu Jan 30 01:25:30 CET 2020) perl 5.028002 -
x86_64-linux-thread-multi
[20-02-02
The error does occur only if Material is the selected skin in SLX, not
with the default skin.
QLMS 7.9.3@2.04 x64 (digimaster) with perl 5.28 dedicated to me. :D /
QNAP 469L QTS 4.3.4
dolodobendan's Profile:
ralphy wrote:
> I get similiar log messages generated from iPeng classic 2.0.17 except
> it's using cometd instead of cli.
>
> >
Code:
> > [20-01-19 07:54:35.5837] main::init (387) Starting Logitech Media
Server (v7.9.3, r20731.7bc69ec, 1579217098) perl 5.014002 -
I, too, use iPeng (the "normal" version). Maybe it's some combination of
factors? I'll try that later.
QLMS 7.9.3@2.04 x64 (digimaster) with perl 5.28 dedicated to me. :D /
QNAP 469L QTS 4.3.4
dolodobendan's Profile:
I get similiar log messages generated from iPeng classic 2.0.17 except
it's using cometd instead of cli.
Code:
[20-01-19 07:54:35.5837] main::init (387) Starting Logitech Media Server
(v7.9.3, r20731.7bc69ec, 1579217098) perl 5.014002 -
mherger wrote:
> That log file is interesting...
Yes, of course. Nothing worse than boring log files. :p
mherger wrote:
> a few questions:
>
> - is 192.168.178.2 the machine on which you're running Squeezelite-X? Or
>
> LMS?
>
> - if not, what is it?
It's my PC (running SLX).
mherger
That log file is interesting... a few questions:
- is 192.168.178.2 the machine on which you're running Squeezelite-X? Or
LMS?
- if not, what is it?
- would you have some application outside LMS which was talking to LMS?
- are you using alarms? If so, how do you manage them? Do you often
I tried it again (steps 39) with the same result (error).
Active plugins:
- Additional Browse Modes
- AirPlay bridge
- Custom Browse
- Custom Scan
- Date and Time
- Full text search
- Material Skin (selected)
- Multi Library
- Podcasts
- PowerSave
- Presets Editor
- Radio
- Save Playlist
I just realized that SLX already switched players at 3). Alas, there
goes my theory. But at least I managed to (re)produce the error.
QLMS 7.9.3@2.04 x64 (digimaster) with perl 5.28 dedicated to me. :D /
QNAP 469L QTS 4.3.4
mherger wrote:
> I still can't reproduce this... Can you go into more detail, please?
> What screen is active in SLX? How long would you wait in between
> shutting down LMS and restarting it? How long would it take before LMS
> reports that issue?
More detail: I'll try my best.
Active
I now can reproduce this. This happens always when LMS is restarted
while SLX is running with the player enabled AND that player is the
currently controlled player.
I still can't reproduce this... Can you go into more detail, please?
What screen is active in SLX? How long would you wait in
Oh, and Material has to be the selected skin...
QLMS 7.9.3@2.04 x64 (digimaster) with perl 5.28 dedicated to me. :D /
QNAP 469L QTS 4.3.4
dolodobendan's Profile: http://forums.slimdevices.com/member.php?userid=67663
View
There was nothing new in the logs. Five times this
Code:
[20-01-17 15:57:46.3242] Slim::Control::Request::renderAsArray (2233) Error:
request should set useIxHashes in Slim::Control::Request->new()
[20-01-17 15:57:46.3252] Slim::Control::Request::renderAsArray
mherger wrote:
> Please enable debug logging for plugin.cli. This should give us an idea
>
> what kind of command is triggering this.
>
> --
>
> Michael
Check.
Note to myself. This happens when I click on Klassik / Genre / Work /
Recordings on this three-dotted button in SLX with
Please enable debug logging for plugin.cli. This should give us an idea
what kind of command is triggering this.
--
Michael
___
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
mherger wrote:
> >>> Not really, no. Could it be squeezelite-win on my PC? I'm not 100%
> >> sure,
> >>
> >> Is this the "Squeezelite X" application? I could give it a try.
> >
> > Jein, SLX (Squeezelite X) uses, if enabled, squeezelite-win as a
> player.
>
> But you are using SLX? I'd rather
Not really, no. Could it be squeezelite-win on my PC? I'm not 100%
sure,
Is this the "Squeezelite X" application? I could give it a try.
Jein, SLX (Squeezelite X) uses, if enabled, squeezelite-win as a player.
But you are using SLX? I'd rather think it's SLX than the player itself.
--
mherger wrote:
> > Not really, no. Could it be squeezelite-win on my PC? I'm not 100%
> sure,
>
> Is this the "Squeezelite X" application? I could give it a try.
>
> --
>
> Michael
Jein, SLX (Squeezelite X) uses, if enabled, squeezelite-win as a player.
QLMS 7.9.3@2.04 x64 (digimaster)
Not really, no. Could it be squeezelite-win on my PC? I'm not 100% sure,
Is this the "Squeezelite X" application? I could give it a try.
--
Michael
___
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
mherger wrote:
> Would you know what is using the CLI? I've never seen this in
> production. I wonder whether some application using the CLI is sending
> invalid input or something.
> --
>
> Michael
Not really, no. Could it be squeezelite-win on my PC? I'm not 100% sure,
but I think can
kidstypike also had this error see
https://forums.slimdevices.com/showthread.php?110727-BETA-piCorePlayer6-0-0-PI4-support=960673=1#post960673
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this
Would you know what is using the CLI? I've never seen this in
production. I wonder whether some application using the CLI is sending
invalid input or something.
--
Michael
___
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
Still a thing. Happened after restarting the NAS.
Code:
[20-01-15 19:27:56.5093] main::init (387) Starting Logitech Media Server
(v7.9.3, 1578994763, Tue Jan 14 11:12:43 CET 2020) perl 5.028001 -
x86_64-linux-thread-multi
[20-01-15 19:28:20.8097]
67 matches
Mail list logo
