Changes

From Amahi Wiki
Jump to: navigation, search
162 bytes removed ,  01:41, 8 October 2015
==== DLNA Configuration File ====
The configuration file (a.k.a ".conf") has some options that can be configured. Changes can be made to the file as the "root" user via a "Terminal Session" windowusing the [http://www.cs.rit.edu/~cslab/vi.html vi] or [http://www.nano-editor.org/ nano] editors.
* The ".conf" file is found at:
<blockquote><u>Fedora 19:</u></blockquote>
/etc/minidlna.conf
<blockquote><u>Ubuntu:</u></blockquote>
/etc/minidlna.conf
 
<u>Fedora 14:</u>
/var/hda/apps/dlna/amahi.conf
* One section of the ".conf" file allows for changing where the directory locations where media files are stored.
* If you edit the minidlna.conf, the minidlna service must be restarted:
 <blockquote><u>Fedora 19:</u></blockquote>
systemctl restart minidlna.service
Check the '''log file''' for the app at: <br><br>
<blockquote><u>Fedora 19:</u></blockquote>
/var/log/minidlna.log
<blockquote><u>Ubuntu:</u></blockquote>
/var/log/minidlna.log
 
<u>Fedora 14:</u>
/tmp/minidlna/minidlna.log
==== New Media Files ====
* If you have problems where DLNA cannot see some files, it may be due to some ownership/permissions issues. You can do this (change the path and USERNAME accordingly):
<blockquote>{{Code| cd /var/hda/files/movies && chown -R USERNAME:users *}}</blockquote>
'''NOTE:'''<br> Some Amahi applications that share the same media files require specific ownership/permissions to media directories and files.
In the case of Fedora the following could apply:
<blockquote>{{Code| cd /var/hda/files/ chown -vR apache:users movies chmod -vR 775 * cd movies chmod -vR 775 *}}</blockquote>
==== DLNA Not Running After Boot-Up ====
* As a "root" user start a "Terminal Session", at the command-line enter:
<blockquote>{{Code|<u>Fedora 19:</u></blockquote> systemctl status minidlna.service}}</blockquote>
<blockquote>Response:
{{Text|Text=<pre>minidlna.service - MiniDLNA is a DLNA/UPnP-AV server software
Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled)
Active: failed (Result: exit-code) since Sat 2013-08-10 08:46:45 MDT; 16min ago
Process: 527 ExecStart=/usr/sbin/minidlna -f /etc/minidlna.conf -P /var/run/minidlna/minidlna.pid (code=exited,
status=255)}}</blockquotepre
* Also somewhere in the "messages" log reveals:
<blockquote>{{Text|Text= Aug 10 09:20:28 localhost minidlna[526]: [2013/08/10 09:20:28] minidlna.c:753: fatal: No IP address automatically detected!}}</blockquote>
* What does all this mean? When DLNA starts it automatically expects to retrieve the Amahi servers' IP address. DLNA could not get the address as the network services on the server had not yet completed start-up and configuration.
* To enable NetworkManager Wait Online at startup with the following command:
<blockquote>{{Code|<u>Fedora 19:</u></blockquote> systemctl enable NetworkManager-wait-online}}</blockquote>
* Enter the following to ensure that DLNA is enabled to start at each system boot:
<blockquote>{{Code|<u>Fedora 19:</u></blockquote> systemctl enable minidlna.service}}</blockquote>
* If this was the problem encountered, on the next system boot DLNA should be running.
* Q: Does it transcode on the fly while streaming?: Nope
* Q: I added additional share locations into the config file but they do not appear!: try removing files.db under /tmp/minidlna/ and restarting the amahi-dlna service
 
=== Playlists ===
 
TBD
 
=== Update to latest minidlna ===
Coming soon...
 
=== App's screenshot and logo ===
 
[[Image:dlna-sshot.jpg]]
 
[[Image:dlna-logo.jpg]]
 
[[Category:Apps]]
12,424

edits