Mediatomb: upnp error -117

Hello all;

Anybody use mediatomb? when i started it i have this error:

Blockquote
MediaTomb UPnP Server version 0.12.1 - http://mediatomb.cc/

===============================================================================
Copyright 2005-2010 Gena Batsyan, Sergey Bostandzhyan, Leonhard Wimmer.
MediaTomb is free software, covered by the GNU General Public License version 2

2020-02-11 01:02:11 INFO: Loading configuration from: /boot/home/.mediatomb/config.xml
2020-02-11 01:02:11 INFO: Checking configuration…
2020-02-11 01:02:11 INFO: Setting filesystem import charset to UTF-8
2020-02-11 01:02:11 INFO: Setting metadata import charset to UTF-8
2020-02-11 01:02:11 INFO: Setting playlist charset to UTF-8
2020-02-11 01:02:11 WARNING: You enabled the YouTube feature, which allows you
to watch YouTube videos on your UPnP device!
Please check Servicevoorwaarden
By using this feature you may be violating YouTube
service terms and conditions!

2020-02-11 01:02:11 INFO: Configuration check succeeded.
2020-02-11 01:02:11 ERROR: main: upnp error -117
2020-02-11 01:02:11 ERROR: upnp_cleanup: UpnpUnRegisterRootDevice failed

Blockquote

any help is apreciated.

If it is from HaikuDepot, then the standard yada-yada : you should report it here:

You need to enable multicast:
ifconfig /dev/net/rtl8139/0 allmulti

replace “rtl8139” with your driver.

thanks for the reply Diver! but still not working…

screenshot1

1 Like

I get a “connection refused” on your link. Are you sure that site is up? Also, I heard that YouTube was removing some protocols which could interfere with what you are trying to do.

You can check with the new gerbera devs at:

1 Like

Seems to be working ok here?

Blockquote~> mediatomb

MediaTomb UPnP Server version 0.12.1 - http://mediatomb.cc/

===============================================================================
Copyright 2005-2010 Gena Batsyan, Sergey Bostandzhyan, Leonhard Wimmer.
MediaTomb is free software, covered by the GNU General Public License version 2

2020-02-12 20:21:47 INFO: MediaTomb configuration was created in: /boot/home/.mediatomb/config.xml
2020-02-12 20:21:47 INFO: Loading configuration from: /boot/home/.mediatomb/config.xml
2020-02-12 20:21:47 INFO: UUID generated: a9f2696c-e21b-406b-bcea-a0fb9370828d
2020-02-12 20:21:47 INFO: Checking configuration…
2020-02-12 20:21:47 INFO: Setting filesystem import charset to UTF-8
2020-02-12 20:21:47 INFO: Setting metadata import charset to UTF-8
2020-02-12 20:21:47 INFO: Setting playlist charset to UTF-8
2020-02-12 20:21:47 WARNING: You enabled the YouTube feature, which allows you
to watch YouTube videos on your UPnP device!
Please check Servicevoorwaarden
By using this feature you may be violating YouTube
service terms and conditions!

2020-02-12 20:21:47 INFO: Configuration check succeeded.
2020-02-12 20:21:47 WARNING: Sqlite3 database seems to be corrupt or doesn’t exist yet.
2020-02-12 20:21:47 INFO: no sqlite3 backup is available or backup is corrupt. automatically creating database…
2020-02-12 20:21:47 INFO: database created successfully.
2020-02-12 20:21:47 INFO: Initialized port: 49152
2020-02-12 20:21:47 INFO: Server bound to: 10.0.2.15
2020-02-12 20:21:48 INFO: MediaTomb Web UI can be reached by following this link:
2020-02-12 20:21:48 INFO: http://10.0.2.15:49152/

Played a bit with it (changed network settings in VBox for this):
Haiku streaming with mediatomb
Ubuntu connecting to it and playing an mp3 from the network

2 Likes

Yes, it seems that mediatomb is not finding my network interface or something else. I try to set it by the configuration xml, but it returns an error that does not find it…

Can you share with me your config.xml to compare it? you only install the package and everything works at first?

I’ll see to grab it later today

https://pastebin.com/rFwyxZ5Z

Thanks!! i used your config, but the same error. I see that you are using the 32bits package. … its correct if i assume that the port in 64bts its not working?

Haven’t checked on 64bit yet, will try to see if I get around to it later today

Checked just now, indeed seems to be a problem on 64bit …

1 Like

Thanks begasus. Then, i will create the bug-ticket in haiku ports.

1 Like

Created a recipe for gerbera (follow up on mediatomb), issues are the same on 32bit and 64bit as it is for mediatomb on 64bit, reported also on the issue at haikuports

1 Like

Hi all, I just tried to get the new version of Gerbera 1.8.2 (Haiku Depot Server) working on Haiku 64bit nightly.

For reference I looked at: Generating Configuration — Gerbera 2.0.0 documentation
The config.xml I used: boot/home/config/settings/gerbera/config.xml
Starting gerbera in Terminal will crash!

This link is dead now! Begasus, do still have the config.xml file?

My questions:

  • There where somewhat of a tutorial here in the forum!? But where?
  • Is the config.xml file wrong generated?
  • Why is the Browser GUI not working anymore?
    MediaTomb Web UI should be reached by following this link: http://10.0.2.15:49152/ (192.168.0.44:49152)

Would be nice if someone could try to get a working config.xml file for Haiku with the correct location for it in boot/home/config/settings/gerbera/
Thanks for trying…

1 Like

You installed gerbera, not mediatomb. They are different.

2 Likes

Last time I used the config.xml file from Mediatomb and it worked!

1 Like

I tried again.

And again crashed!
How to post the bug report here?

1 Like

Report it at haikuports and / or at gerbera, but as Haiku is not a supported platform for Gerbera, probably they won’t be able to help too much.

The gerbera port provides a pre-baked config file. Maybe it just have to be updated, maybe it something else.

1 Like

I installed Gerbera and typed in Terminal: “gerbera --create-config”
as this will generate the config.xml settings file.

Gerbera provides a command line flag --create-config to generate a default config.xml file. You will need to generate the configuration file when running Gerbera for the first time. Gerbera reports the missing configuration upon startup similar to the message below

As I told earlier this should not needed at all.