Weird behaviour after upgrade to 0.50.1-1

[6feet5]

Hi all,

I'm having some serious problems with my bubba and it all started after upgrading to 0.50.1-1.

When trying to access the web interface I get to the greeting screen without any problem. But when I select "Bubba administration" I sometimes get in but mostly not. And if I do get in, selecting another screen, like download, will freeze everything. The mail pages are ok though, so it's something with the web administration.

I can SSH to it. Having read about ftd acting strangely, I ran "ps ax" and this is part of what I get:

Code: Select all

 1285 ?        Ss     0:08 /usr/sbin/apache2 -k start -DSSL
 1297 ?        Ss     0:03 /usr/bin/fetchmail -f /etc/fetchmailrc --syslog -i /var/mail/.fetchmail-UIDL-cache
 1305 ttyS0    Ss+    0:00 /sbin/getty -L ttyS0 115200 vt100
 1306 ?        S      0:11 /usr/sbin/apache2 -k start -DSSL
 1307 ?        S      0:06 /usr/sbin/apache2 -k start -DSSL
 1309 ?        S      0:13 /usr/sbin/apache2 -k start -DSSL
 1310 ?        S      0:00 /usr/sbin/apache2 -k start -DSSL
 1338 ?        S      0:00 /usr/sbin/apache2 -k start -DSSL
 1575 ?        Ss     0:00 /usr/bin/mediatomb -c /etc/mediatomb/config.xml -d -u nobody -g nogroup -P /var/run/mediatomb.pid -l /var/log/mediatomb
 1576 ?        S      0:00 /usr/bin/mediatomb -c /etc/mediatomb/config.xml -d -u nobody -g nogroup -P /var/run/mediatomb.pid -l /var/log/mediatomb
 1577 ?        S    107:49 /usr/bin/mediatomb -c /etc/mediatomb/config.xml -d -u nobody -g nogroup -P /var/run/mediatomb.pid -l /var/log/mediatomb
 1582 ?        S      0:00 /usr/bin/mediatomb -c /etc/mediatomb/config.xml -d -u nobody -g nogroup -P /var/run/mediatomb.pid -l /var/log/mediatomb
 1584 ?        S      0:00 /usr/bin/mediatomb -c /etc/mediatomb/config.xml -d -u nobody -g nogroup -P /var/run/mediatomb.pid -l /var/log/mediatomb
 1586 ?        S      0:00 /usr/bin/mediatomb -c /etc/mediatomb/config.xml -d -u nobody -g nogroup -P /var/run/mediatomb.pid -l /var/log/mediatomb
 1589 ?        S      0:22 /usr/bin/mediatomb -c /etc/mediatomb/config.xml -d -u nobody -g nogroup -P /var/run/mediatomb.pid -l /var/log/mediatomb
 1608 ?        R     18:12 /usr/bin/mediatomb -c /etc/mediatomb/config.xml -d -u nobody -g nogroup -P /var/run/mediatomb.pid -l /var/log/mediatomb
 1629 ?        Ss     0:00 /usr/bin/dbus-daemon --system
 1652 ?        Ss     0:00 avahi-daemon: running [bubba.local]
 1676 ?        S      1:25 /usr/sbin/mt-daapd
 1679 ?        S      0:00 /usr/sbin/mt-daapd
 1682 ?        S      0:00 /usr/sbin/mt-daapd
 1725 ?        S      0:15 /usr/sbin/apache2 -k start -DSSL
 1776 ?        S      0:05 /usr/sbin/smbd -D
 1777 ?        S      0:00 imap-login
 1779 ?        S      0:04 imap
 1793 ?        S      0:15 /usr/sbin/apache2 -k start -DSSL
 1794 ?        S      0:14 /usr/sbin/apache2 -k start -DSSL
 1795 ?        S      0:14 /usr/sbin/apache2 -k start -DSSL
 1796 ?        S      0:00 /usr/sbin/apache2 -k start -DSSL
 1981 ?        S      0:00 pickup -l -t fifo -u -c
 2268 ?        Ss     0:00 sshd: johan [priv]
 2270 ?        S      0:00 sshd: johan [priv]
 2274 ?        S      0:00 sshd: johan@pts/0
 2275 pts/0    Ss     0:00 -bash
 2320 ?        S      0:00 /usr/bin/mediatomb -c /etc/mediatomb/config.xml -d -u nobody -g nogroup -P /var/run/mediatomb.pid -l /var/log/mediatomb
 2321 ?        S      0:00 /usr/sbin/apache2 -k start -DSSL
 2341 ?        S      0:00 /usr/bin/mediatomb -c /etc/mediatomb/config.xml -d -u nobody -g nogroup -P /var/run/mediatomb.pid -l /var/log/mediatomb
 2342 ?        S      0:00 /usr/bin/mediatomb -c /etc/mediatomb/config.xml -d -u nobody -g nogroup -P /var/run/mediatomb.pid -l /var/log/mediatomb
 2343 ?        S      0:00 /usr/bin/mediatomb -c /etc/mediatomb/config.xml -d -u nobody -g nogroup -P /var/run/mediatomb.pid -l /var/log/mediatomb
 2344 ?        S      0:00 /usr/bin/mediatomb -c /etc/mediatomb/config.xml -d -u nobody -g nogroup -P /var/run/mediatomb.pid -l /var/log/mediatomb
 2345 pts/0    R+     0:00 ps ax

Why are there so many apache and mediatomb processes? Is this the way its supposed to be? As you can see, one of the mediatomb processes is eating up alot of execution time and top will reveal it takes about 80% of the CPU. Since this is a fresh install I'm guessing it's indexing my MP3 collection, but still that's a lot of processes.
As I wasn't able to find ftd in the output, I ran "ps ax|grep ftd" and then I get one process. Running it again will display it with a different PID. As a matter of fact, everytime I run ps I get a new PID on ftd as if ftd keeps restarting. Is this the way it's supposed to be?

Needless to say maybe, but my downloads aren't working

Best regards,
Johan

[tor]

Hi,

The many mediatomb processes are ok. This is due to the application being highly threaded.

But it seems like something has gone wrong with the download manager. Could you log in in a shell on bubba and become root. Then stop ftd

Code: Select all

/etc/init.d/ftd stop

Manually starting it on the commandline

Code: Select all

ftd -f

and see if we can get any useful information that way.

/Tor

[6feet5]

It seems like my problem is gone.

I found two torrents in the torrent folder that wasn't visible from download page. Removing them, then restarting ftd solved the problem.


/Johan