Hello andyg. Thanks for your response.
No, currently I am not be able to find out which file is responsible for the craah. My collection is too big and the duration for each building up the database/index needs round about one hour. I solved temporarily the problem on a quick and dirty way. I tried to understand the scripts and dependencies, guessed a little bit and changed the scripts /usr/squeezecenter/gdresize.pl and /usr/squeezecenter/gdresized.pl . I changed "use constant RESIZER => 1:" to "use constant RESIZER => 0;" . It seems that I disabled the resizer and it works. I don't know the side effects if I want to play the files with the big image. In the most cases I am hearing internet radio so it's for me not a high priority. Some other problems with the squezzebox are hurting more (for example that the SB won't store the database/index of the music collection. Every reboot the squeezebox and my other connected SB systems are round about one hour out of order because the server is recreating a new index. Nothing changed in the archive! I can't understand the reason that the squeezebox won't use the old index.) Ok, I set the following logger to ERROR. (I guessed only to isolate the problem.) applet.CrashLog applet.LogSettings applet.Squeezebox applet.SqueezeCenter squezzebox.server squezzebox.server.cache I tried to find another logger only for the resizer to get an idea to find the responsible files. May be you can give me a hint to find the files. Please have in mind that I won't to start a one hour scan to find only one file! May be there are more than one file. ;) I am familiar with Linux, it's no problem to connect the hard disk temporarily to a Linux system and scriting. I am not familiar with the file format of mp3, flac etc. so I have no idea how to resize embedded images. At this point I need some help or some hints. The Syslogd is writing the log to my sdcard so I haven't any problem with free space. By the way it seems that here is another bug. The Syslogd started by the /etc/init.d/rcS script but it seems that the sdcard and usb hd not initialized if the script is executed. After booting the syslogd is writing in /var/log/messages although the sdacrd and usdb hd are connected at beginning and the folder "log" already exists in the root. Best regards and thank you for the help Tamex andyg;682618 Wrote: > Can you find out which file the resizer is crashing on? It might simply > be too large to process (and I never got around to enabling the memory > limit feature to prevent this). > > On Jan 6, 2012, at 7:22 PM, Tamex wrote: > > > > > Hi, > > > > it seems that I have the problem too. > > If I start the SBserver on my touch, the touch is scanning and > > discovering the harddisk, but at the step resizing the images the > touch > > terminates media server. > > > > I have the following error in my syslog. > > > > <---schnipp---> > > ... > > an 6 09:39:24 kernel: Out of memory: kill process 6580 > (slimserver.pl) > > score > > 1889 or a child > > Jan 6 09:39:24 kernel: Killed process 6580 (slimserver.pl) > > Jan 6 09:39:24 kernel: gdresized.pl invoked oom-killer: > > gfp_mask=0x1200d2, ord > > er=0, oomkilladj=0 > > ... > > <---schnapp---> > > I am using the firmware 7.7.1 r9558. Is it possible that the giflib > > library is not built correctly in version 7.7.1 too? > > > > Best regards > > Tamex > > > > > > -- > > Tamex > > > ------------------------------------------------------------------------ > > Tamex's Profile: > http://forums.slimdevices.com/member.php?userid=45295 > > View this thread: > http://forums.slimdevices.com/showthread.php?t=85083 > > > > -- Tamex ------------------------------------------------------------------------ Tamex's Profile: http://forums.slimdevices.com/member.php?userid=45295 View this thread: http://forums.slimdevices.com/showthread.php?t=85083 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
