Mediatomb not accessible since last update

[eeeuser1]

Hi,
I've upgraded with the new update.

my web browser pointed to http://192.168.0.100:49152/ now give error message "media tomb cannot be reached" ,user:admin pass:excito, or any choice for that matter.

Also my upnp internet radio cannot find it now.

ps -ef does not show mediatomb
The service is ticked in web-admin

this is the only error in /var/log/mediatomb (twice) :-
There is already an Autoscan set on /var/samba/public/video
There is already an Autoscan set on /var/samba/public/video

although we only have music and /video is empty!

if i type ls -al in /var/log
mediatomb log is owned by nobody:nogroup

What can I do?

[Eek]

Hi

this is a coruption in de mediatomb sqlite database.
you can fix this by removing the database,
see the following link:

http://forum.excito.net//viewtopic.php?t=857

cheers
Eek

[tor]

Hi,

From which version did you upgrade? This is a known bug in Mediatomb that i actually thought we had avoided.

To fix this you have to edit your /etc/mediatomb/config.xml

Locate the three lines that looks something like

Code: Select all

<directory location="/var/samba/public/video/" mode="timed" interval="7200" level="basic" recursive="yes" hidden-files="no"/>
<directory location="/var/samba/public/music/" mode="timed" interval="7200" level="basic" recursive="yes" hidden-files="no"/>
<directory location="/var/samba/public/pictures/" mode="timed" interval="7200" level="basic" recursive="yes" hidden-files="no"/>

and remove the trailing slashes in the paths. Should end up something like

Code: Select all

<directory location="/var/samba/public/video" mode="timed" interval="7200" level="basic" recursive="yes" hidden-files="no"/>
<directory location="/var/samba/public/music" mode="timed" interval="7200" level="basic" recursive="yes" hidden-files="no"/>
<directory location="/var/samba/public/pictures" mode="timed" interval="7200" level="basic" recursive="yes" hidden-files="no"/>

Then restart Mediatomb.

/Tor

[eeeuser1]

Thanks for the prompt reply tor,

However I deleted the db as per the previous reply before I found yours

It's re-building the db now and seems ok.

Would it still benefit me to remove the slashes?

J

[Eek]

During the upgrade from 9 to 10
I got the question if i wanted the new config or keep the old.
I think i choose keep the old.
maybe if I choose for the new config,
the problem would not even occur.

Let's hope the bug is really fixed

cheers
Eek

[tor]

Ok, if you upgraded manually and kept the original config file you would get this error.

/Tor