Re: [slim] how do i debug logitechmediaserver-7.9.1 on CentOS 7

2017-11-13 Thread ezekieldas
This worked best for me in finding loops 'find . -follow -printf ""' I was able to isolate some files and moved them out of /opt/mp3 (see below). I then restarted squeezeboxserver and library.db appears to remain at a manageable size: -rw-r--r--. 1 squeezeboxserver squeezeboxserver 112M Nov 13 15

Re: [slim] how do i debug logitechmediaserver-7.9.1 on CentOS 7

2017-11-13 Thread Jeff07971
Have you got SELinux enabled ? Anything in the audit log ? *Players:* SliMP3,Squeezebox3 x3,Receiver,SqueezePlayer,PiCorePlayer x3,Wandboard *Server:* LMS Version: 7.9.1 - 1503129892 on Centos 7 VM on ESXi 6.5.0U1 on Dell T320 *Plugins:* AutoRescan/BBCiPlayer/PowerSave/PowerSwitchIII/Squeezecl

Re: [slim] how do i debug logitechmediaserver-7.9.1 on CentOS 7

2017-11-13 Thread Roland0
ezekieldas wrote: > While I understand sym and hard links I don't entirely understand what > 'find -L' is doing. The manual page isn't making sense to me. > See 'here' (https://serverfault.com/questions/265598/how-do-i-find-circular-symbolic-links) and 'here' (https://unix.stackexchange.com/que

Re: [slim] how do i debug logitechmediaserver-7.9.1 on CentOS 7

2017-11-13 Thread ezekieldas
Hello and thanks. I modified dbhighmem to reflect 2 but this had no positive effect. Same behavior as described above. While I understand sym and hard links I don't entirely understand what 'find -L' is doing. The manual page isn't making sense to me. I'm unsure if these examples are telling me ev

Re: [slim] how do i debug logitechmediaserver-7.9.1 on CentOS 7

2017-11-13 Thread Roland0
ezekieldas wrote: > Why would 450Gb be a problem? It's not - mine is larger, and others much larger. > > There may be a few links in that tree but nothing excessive. Can this > not handle symlinks? > It can - just make sure there's no loop (use find -L /path to check) > > I'd like to do th

Re: [slim] how do i debug logitechmediaserver-7.9.1 on CentOS 7

2017-11-13 Thread Michael Herger
My hardware is just commodity x86 stuff. It would seem to me the source of the issue is the processing and/or representation of the music library. Why would 450Gb be a problem? The size in GB doesn't really matter. What is important is the number of files. There may be a few links in that t

Re: [slim] how do i debug logitechmediaserver-7.9.1 on CentOS 7

2017-11-13 Thread ezekieldas
My hardware is just commodity x86 stuff. It would seem to me the source of the issue is the processing and/or representation of the music library. Why would 450Gb be a problem? There may be a few links in that tree but nothing excessive. Can this not handle symlinks? I'd like to do this: "change

Re: [slim] how do i debug logitechmediaserver-7.9.1 on CentOS 7

2017-11-13 Thread Michael Herger
Thanks Roland0. You just saved me a lot of typing :-). ezekieldas - what hardware are you running your LMS on? Could there be symlinks in your music library? -- Michael ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.c

Re: [slim] how do i debug logitechmediaserver-7.9.1 on CentOS 7

2017-11-13 Thread Roland0
ezekieldas wrote: > > I know very little about sqllite but it looks like it's having a really > difficult time loading a 9Gb table. Does it attempt to load library.db > in entirety, or does it just reference that when necessary? > While your assumtion is correct, your library DB size is extre

Re: [slim] how do i debug logitechmediaserver-7.9.1 on CentOS 7

2017-11-13 Thread ezekieldas
Hi Michael. Thanks for responding. 1) plugins: I have spotty (thank you very very much btw), MusicWalkWithMe, NPR, BandCamp plugins installed. 2) --d_startup: I added this to SQUEEZEBOX_ARGS yet verbosity of log output remains the same. Is order important? I was able to get the proc running aga

Re: [slim] how do i debug logitechmediaserver-7.9.1 on CentOS 7

2017-11-12 Thread Michael Herger
At startup I see these three items in /var/log/squeezeboxserver/server.log. Meanwhile the squeezeboxserver proc is burning through CPU and consumes all swap until the proc crashes. web interface never becomes available. The only fix I have in getting LMS up is to remove the contents of /var/lib/s

[slim] how do i debug logitechmediaserver-7.9.1 on CentOS 7

2017-11-12 Thread ezekieldas
At startup I see these three items in /var/log/squeezeboxserver/server.log. Meanwhile the squeezeboxserver proc is burning through CPU and consumes all swap until the proc crashes. web interface never becomes available. The only fix I have in getting LMS up is to remove the contents of /var/lib/s