Bug 1479 - Mediatomb service does nt start on boot
Summary: Mediatomb service does nt start on boot
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-30 07:16 CEST by Dimitrios Glentadakis
Modified: 2011-10-30 09:02 CET (History)
2 users (show)

See Also:
Source RPM: mediatomb
CVE:
Status comment:

Attachments
output of the /var/log/mediatomb (4.53 KB, text/plain)
2011-06-05 11:52 CEST, Dimitrios Glentadakis 		Details
Output of /sbin/prcsys --test S /etc/rc3.d/ (3.46 KB, text/plain)
2011-06-18 13:12 CEST, Dimitrios Glentadakis 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Dimitrios Glentadakis 2011-05-30 07:16:41 CEST 
I have checked in the control panel, mediatomb to startup on boot but this does nt happen

[root@localhost dglent]# service mediatomb status
mediatomb είναι νεκÏÏ Î±Î»Î»Î¬ Ïο αÏÏείο pid ÏÏάÏÏει

mediatomb is dead but the pid file exists
Comment 1 Christiaan Welvaart 2011-06-04 17:48:43 CEST 
Did you fill in a value for MT_INTERFACE in /etc/mediatomb.conf ? IIRC mediatomb has some security issues by design so it's not a very good idea to start it by default.

Keywords: (none) => NEEDINFO
CC: (none) => cjw

Comment 2 Dimitrios Glentadakis 2011-06-04 17:57:37 CEST 
Yes,
if i add manually an entry in the rc.local it starts on boot or if i run service mediatomb restart it works. I dont know about security issues, i hope they are not very important (for me).
Comment 3 Christiaan Welvaart 2011-06-05 10:59:06 CEST 
After reinstalling mediatomb (the files were still there from an older package) and rebooting it's running so I cannot reproduce the problem you see. This VM uses systemd, and has a similar problem: the NFS share mediatomb is supposed to use is not mounted on boot up.

Mediatomb not starting may be caused by some init script dependency problem. Is there any error message at the end of /var/log/mediatomb when this happens?

The security issue is that the web interface allows (read-only) access to the file system for anyone who can connect to it.

Keywords: NEEDINFO => (none)

Comment 4 Dimitrios Glentadakis 2011-06-05 11:52:15 CEST 
Created attachment 517 [details]
output of the /var/log/mediatomb
Comment 5 Dimitrios Glentadakis 2011-06-05 11:54:27 CEST 
It seems that it cant file the eth0 :

2011-06-05 11:45:18   ERROR: Could not determine interface address: *Unable to assign the requested address (*translated from Greek)
2011-06-05 11:45:18   ERROR: Could not find interface: eth0
Comment 6 Christiaan Welvaart 2011-06-18 12:47:24 CEST 
Could you provide the output of
  /sbin/prcsys --test S /etc/rc3.d/
? You can also check the syslog for a mediatomb startup message and then look for network-related messages before or after that line. The mediatomb initscript looks OK to me.
Comment 7 Dimitrios Glentadakis 2011-06-18 13:12:31 CEST 
Created attachment 583 [details]
Output of /sbin/prcsys --test S /etc/rc3.d/
Comment 8 Dimitrios Glentadakis 2011-06-18 13:13:09 CEST 
In the syslog there is nothing about mediatomb
Manuel Hiebel 2011-07-27 19:05:38 CEST

CC: (none) => manuel
Source RPM: (none) => mediatomb

Comment 9 Manuel Hiebel 2011-10-30 02:04:35 CET 
Is this bug still valid in mageia 1/ cauldron ?
Comment 10 Dimitrios Glentadakis 2011-10-30 09:02:57 CET 
No, in Mageia 1, i tested and it worked fine now

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME
Note You need to log in before you can comment on or make changes to this bug.