Bubba|Two Software update 1.2.0

[tor]

Hi MagnusJonsson,

Could this be that the Squeezecenter is doing a reindexing of your media? This could, depending on media library size, take a lot of CPU and time.

/Tor

[MagnusJonsson]

Hi Tor,

Possibly, but does it make sense that more than 24 hrs later, it is still using a lot of CPU load ?
I have taken a number of snap shots for the last hour, and the CPU load seems consistently high.

Code: Select all

112      27113 87.6  3.9  19004 10116 ?        R    12:34   0:04  \_ /usr/bin/perl -w /usr/sbin/squeezecenter-server --pref...

112      27167 94.1 11.9  40948 30668 ?        R    12:38   0:16  \_ /usr/bin/perl -w /usr/sbin/squeezecenter-server --pref...

112      27214 70.0  1.1   5392  2920 ?        R    12:41   0:00  \_ /usr/bin/perl -w /usr/sbin/squeezecenter-server --pref...

112      27403 92.5  3.5  17996  9216 ?        R    12:59   0:03  \_ /usr/bin/perl -w /usr/sbin/squeezecenter-server --pref...

112      27852  170  2.0   8188  5132 ?        R    13:39   0:01  \_ /usr/bin/perl -w /usr/sbin/squeezecenter-server --pref...

112      28046 98.6  3.1  16844  8076 ?        R    13:49   0:02  \_ /usr/bin/perl -w /usr/sbin/squeezecenter-server --pref...

112      28118 81.0 15.9  51324 40948 ?        R    13:55   0:24  \_ /usr/bin/perl -w /usr/sbin/squeezecenter-server --pref...


[carl]

Can you see if there is some intelligent logs in /var/log/squeezecenter/server.log or /var/log/squeezecenter/scanner.log?

[MagnusJonsson]

The file server.log (being approximately 6 MB in size) has it latest entry from 6 days ago and that looks from my point of view fairly harmless.

The file scanner.log (being approximately 600 KB) has it latest entry (an exception) from the 26th of July.
(See below)

Code: Select all

[09-07-26 15:28:03.1448] Slim::Schema::throw_exception (235) Error: Carp::Clan::__ANON__(): Error executing 'SELECT me.id, me.titlesort, me.contributor, me.com
pilation, me.year, me.artwork, me.disc, me.discc, me.musicmagic_mixable, me.titlesearch, me.replay_gain, me.replay_peak, me.musicbrainz_id, me.title, tracks.id
, tracks.url, tracks.content_type, tracks.title, tracks.titlesort, tracks.titlesearch, tracks.album, tracks.tracknum, tracks.timestamp, tracks.filesize, tracks
.disc, tracks.remote, tracks.audio, tracks.audio_size, tracks.audio_offset, tracks.year, tracks.secs, tracks.cover, tracks.vbr_scale, tracks.bitrate, tracks.sa
mplerate, tracks.samplesize, tracks.channels, tracks.block_alignment, tracks.endian, tracks.bpm, tracks.tagversion, tracks.drm, tracks.musicmagic_mixable, trac
ks.musicbrainz_id, tracks.lossless, tracks.lyrics, tracks.replay_gain, tracks.replay_peak FROM albums me LEFT JOIN tracks tracks ON ( tracks.album = me.id ) OR
DER BY tracks.album': DBD::mysql::st execute failed: Incorrect key file for table '/tmp/#sql_814_0.MYI'; try to repair it at /usr/share/perl5/DBIx/Class/Storag
e/DBI.pm line 773.
[09-07-26 15:28:03.1533] Slim::Schema::throw_exception (235) Backtrace:

   frame 0: Slim::Utils::Log::logBacktrace (/usr/share/perl5/Slim/Schema.pm line 235)
   frame 1: Slim::Schema::throw_exception (/usr/share/perl5/DBIx/Class/Schema.pm line 639)
   frame 2: DBIx::Class::Schema::txn_do (/usr/sbin/squeezecenter-scanner line 225)
   frame 3: (eval) (/usr/sbin/squeezecenter-scanner line 225)
   frame 4: main::main (/usr/sbin/squeezecenter-scanner line 353)


I have tried to start (restart) the process

Code: Select all

 /etc/init.d/squeezecenter restart


but as soon as it wakes up, the CPU load goes to 90+ %. No additions to the logs you mention is being done.

[Fourwinds]

Have you used the following ps command syntax to see the full commandline of what is running ?

Code: Select all

/bin/ps auxwww

[MagnusJonsson]

Thanks Fourwinds for your suggestion. I gave it a try right away:

Code: Select all

112       8530  0.1  0.6   4668  1684 ?        Ss   22:13   0:00 /bin/bash /usr/sbin/squeezecenter_safe /usr/sbin/squeezecenter-server --prefsdir /var/lib/squeezecenter/prefs --logdir /var/log/squeezecenter/ --cachedir /var/lib/squeezecenter/cache
112       8538  105  3.8  19928  9988 ?        R    22:14   0:04 /usr/bin/perl -w /usr/sbin/squeezecenter-server --prefsdir /var/lib/squeezecenter/prefs --logdir /var/log/squeezecenter/ --cachedir /var/lib/squeezecenter/cache


Unfortunately it does not make more sense to me than the previous output.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

The reason why I even tried to update to 1.2.0 (even though the obvious reason of wanting to have the latest and greatest) is the fact that I have a Popcorn Hour A-110 connected through a network to my B2 using a SMB share. I've streamed movies with fairly good results in this setup.

One day my wife was unable to use the Popcorn. It seemed to have difficulties even listing the files on the B2 samba share. Oh boy, I thought, now the Popcorn broke down.
However, it turned out that it worked just fine when looking at a share on my regular PC.
I must admit that I have previously been forced to restart my B2 on a bi-weekly basis due to the fact that file transfers (streaming from the samba share) has been slow or inadequate and this restarting has always helped with good throughput as result (for another 14 days)

Anyway, this time nothing helped. Upgrading to 1.2.0 surely did not help either, it made things worse.

If it was not for the fact that I have a Squeezebox connected to my system, I actually think that I would have chosen a less fancy destiny for my B2 such as a book stand on a shelf, and just purchased a regular NAS.
In my point of view the B2 seems to under perform as a firewall as well. When using B2 as a firewall I seem to loose about 30% of my bandwidth compared to a dirt cheep D-Link router.

Maybe the best is just to discard all data on the disc and hope that a re-format and re-installation makes things go back to normal again. Okay, that normal includes a bi-weekly reboot.
Or just put the B2 to rest, run the Squeezecenter from the PC and live a happy life with a lot cheaper NAS.

Which way to go ?

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

[MagnusJonsson]

I have tried to start some minor investigation on what could be the problem.

The fist issue that was causing problems is the fact that the apache logs were extremely big and thus causing the system to malfunction since there was no disc space left.

Code: Select all

Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             9.2G  9.2G     0 100% /
tmpfs                 126M     0  126M   0% /lib/init/rw
udev                   10M   20K   10M   1% /dev
tmpfs                 126M  4.0K  126M   1% /dev/shm
/dev/mapper/bubba-storage
                      907G  433G  428G  51% /home


However, the script /etc/logrotate.d/apache2 looks just fine so I purged the files to see if it was as simple as the apache server running out of space. Unfortunately this did not help, so I will not pursue (with the help of a Linux knowledge friend) why the squeezebox process goes havoc all the time.

[carl]

I have tried to start some minor investigation on what could be the problem.

The fist issue that was causing problems is the fact that the apache logs were extremely big and thus causing the system to malfunction since there was no disc space left.

Code: Select all

Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             9.2G  9.2G     0 100% /
tmpfs                 126M     0  126M   0% /lib/init/rw
udev                   10M   20K   10M   1% /dev
tmpfs                 126M  4.0K  126M   1% /dev/shm
/dev/mapper/bubba-storage
                      907G  433G  428G  51% /home


However, the script /etc/logrotate.d/apache2 looks just fine so I purged the files to see if it was as simple as the apache server running out of space. Unfortunately this did not help, so I will not pursue (with the help of a Linux knowledge friend) why the squeezebox process goes havoc all the time.

As I've been unable to reproduce above error, I would like to access your bubba to see what might be the problem. If this is ok with you, could you contact support@excito.com with suitable login data.

/Carl

[MagnusJonsson]

Thank you very much Carl. I appreciate your support.

You should have received a mail by now !

King regards,
Magnus

[MagnusJonsson]

Thanks very much Carl for your excellent support !

My wife is happy, and obviously so am I !!!

King regards,
Magnus

[pcrene]

Thats why i bought...BUBBA...

Rene

[tor]

Hi Philippe,

Nice work. This was actually on our internal todo-list (So expect these features to show up in an upcoming upgrade)

/Tor