mediatomb help on Alt-F

[nesta...@gmail.com]

And so I gave in and installed mediatomb, despite all the forums online on how hard it is to configure.

First I tried it on ubuntu and was able to look at the config file and edit from: /etc/mediatomb/config.xml

But can't find the same file in /etc in Alt-F. So that's my first need.

Second, whereas, minidlna allows for configuring different folders for different media, I don't see this with mediatomb.

Anyone here with a walk through on configuring mediatomb on Alf-F?

And if they wish to also share their xml file and how they went about it. Including such info, as building it database or scanning, etc.

Thanks in advance.

[Joao Cardoso]

On Sunday, January 27, 2013 7:24:24 AM UTC, nesta...@gmail.com wrote:

And so I gave in and installed mediatomb, despite all the forums online on how hard it is to configure.

First I tried it on ubuntu and was able to look at the config file and edit from: /etc/mediatomb/config.xml

But can't find the same file in /etc in Alt-F. So that's my first need.

 /var/lib/mediatomb/config.xml

Second, whereas, minidlna allows for configuring different folders for different media, I don't see this with mediatomb.

What is wrong with Services->User->mediatomb Configure?

[nesta...@gmail.com]

On Sunday, January 27, 2013 11:21:29 AM UTC-7, Joao Cardoso wrote:

On Sunday, January 27, 2013 7:24:24 AM UTC, nesta...@gmail.com wrote:

And so I gave in and installed mediatomb, despite all the forums online on how hard it is to configure.

First I tried it on ubuntu and was able to look at the config file and edit from: /etc/mediatomb/config.xml

But can't find the same file in /etc in Alt-F. So that's my first need.

 /var/lib/mediatomb/config.xml

Second, whereas, minidlna allows for configuring different folders for different media, I don't see this with mediatomb.

What is wrong with Services->User->mediatomb Configure?

Nothing really. I find nothing wrong with Alt-F per se. All troubles seem to be packages. For now here's what happening. I installed media tomb via, Alt-F packages. Then removed minidlna. I got to Services>User>media tomb configure and click on "Startnow" and the response is "Running." But when I hit "submit" The changes goes to "Stopped." Also when I do then same and go savesettings, the server stops. I really don't know what to do. I haven't done anything with the config file, as I did not, until now, know where it is.  

[nesta...@gmail.com]

And now removed media tomb, reinstalled and started it., after savingsettings and rebooting. The attached is the result.

[Joao Cardoso]

On Monday, January 28, 2013 5:30:46 AM UTC, nesta...@gmail.com wrote:

And now removed media tomb, reinstalled and started it., after savingsettings and rebooting.

In 99% of the cases you don't need to reboot linux for changes to take effect. That is a bad habit inherited from MS-W.

Also, in most of the cases, hitting the Submit button is enough for most well designed apps to just reload and start using the new configuration; not well-written apps are just stopped and restarted when the Submit button is hit. You can verify that in the app logs (see bellow).

 

The attached is the result.

On Sunday, January 27, 2013 9:36:25 PM UTC-7, nesta...@gmail.com wrote:

On Sunday, January 27, 2013 11:21:29 AM UTC-7, Joao Cardoso wrote:

On Sunday, January 27, 2013 7:24:24 AM UTC, nesta...@gmail.com wrote:

And so I gave in and installed mediatomb, despite all the forums online on how hard it is to configure.

First I tried it on ubuntu and was able to look at the config file and edit from: /etc/mediatomb/config.xml

But can't find the same file in /etc in Alt-F. So that's my first need.

 /var/lib/mediatomb/config.xml

Second, whereas, minidlna allows for configuring different folders for different media, I don't see this with mediatomb.

What is wrong with Services->User->mediatomb Configure?

Nothing really. I find nothing wrong with Alt-F per se. All troubles seem to be packages. For now here's what happening. I installed media tomb via, Alt-F packages. Then removed minidlna. I got to Services>User>media tomb configure and click on "Startnow" and the response is "Running." But when I hit "submit" The changes goes to "Stopped." Also when I do then same and go savesettings, the server stops. I really don't know what to do.

Start examining the log files, at /var/log/mediatomb.log. A handy way of doing it is to use System->Utilities, View Logs, mediatomb.

A common cause of failure, that shows itself as "Overlapping Autoscans are not allowed" is to have nested folders defined.

As mediatomb uses a database, it might happens that previously defined (but now deleted) folders conflict with new folders.

E.g., if it happens that you had /mnt/sda2/Public defined and latter on change your mind and remove that and use instead /mnt/sda2/Public/Videos, you might hit the above error -- I found that only removing the database (/var/lib/mediatomb/mediatomb.db) cures the issue, but I only use mediatomb to test it.

[nesta...@gmail.com]

On Monday, January 28, 2013 8:43:55 AM UTC-7, Joao Cardoso wrote:

On Monday, January 28, 2013 5:30:46 AM UTC, nesta...@gmail.com wrote:

And now removed media tomb, reinstalled and started it., after savingsettings and rebooting.

In 99% of the cases you don't need to reboot linux for changes to take effect. That is a bad habit inherited from MS-W.

Also, in most of the cases, hitting the Submit button is enough for most well designed apps to just reload and start using the new configuration; not well-written apps are just stopped and restarted when the Submit button is hit. You can verify that in the app logs (see bellow).

This is rather interesting, there's no mediatomb folders in /var/x/x/x/. Please see attached. But on the web interface, it shows as installed. But it won't start. See attached as well. 

[Joao Cardoso]

On Tuesday, January 29, 2013 4:50:19 AM UTC, nesta...@gmail.com wrote:

On Monday, January 28, 2013 8:43:55 AM UTC-7, Joao Cardoso wrote:

On Monday, January 28, 2013 5:30:46 AM UTC, nesta...@gmail.com wrote:

And now removed media tomb, reinstalled and started it., after savingsettings and rebooting.

In 99% of the cases you don't need to reboot linux for changes to take effect. That is a bad habit inherited from MS-W.

Also, in most of the cases, hitting the Submit button is enough for most well designed apps to just reload and start using the new configuration; not well-written apps are just stopped and restarted when the Submit button is hit. You can verify that in the app logs (see bellow).

This is rather interesting, there's no mediatomb folders in /var/x/x/x/.

A '/' in the beginning of a path means an absolute path, thus when you do 'cd /var' after doing 'cd /lib' you are really under '/var' and not under '/var/lib'

Either use 'cd /var/lib' or 'cd /var' followed by 'cd lib'

There are good linux tutorials out there.

Please see attached. But on the web interface, it shows as installed. But it won't start.

I already said you to see the logs under System Utilities, View Logs:

[nesta...@gmail.com]

I removed mediatomb.
I reinstalled it and configured it, by doing this, using Alt-F web ui:
Services---User, Configure. Here I chose my public RW folder, that was created originally at setup.
But then it won`t start, when I hit start.
I telnet into the box and went to the var folder, where I created the mediatomb folder that the mediatomb.log said it could not create, by doing this:

mkdir /var/lib/mediatomb/
And then gave it write permission:
chmod 777 /var/lib/mediatomb/

Saved and exit.

Start mediatomb and it started.

Now you need to log into the web interface, and the best way is to locate the port, as it creates a different port on each install, I want to think. Anyway, that port, which you can find in its config file, plus the ip of the DNS, using a webbrowser, you can log into mediatom and direct it to the same folder you`d directed it earlier, so it begins to build its database of your files. Now you have to wait, as in waiting for paint to dry, which will give you the chance to see it build its directory live, which is an xml file (look closely to its skull and you will see the blood eyes blink, perhaps indicating that it`s indexing your files). Once done, I suppose you`d have chance to enjoy your files. I have plenty, so I`m still waiting.

I`ve noted this for someone who may have same or similar issues I had. If others here feel the need, they can edit this post.