Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Respawning until exit on Ubuntu Server 12.04

Help
globus68
2012-11-08
2013-05-30
  • globus68
    globus68
    2012-11-08

    Hello gurus!
    I have just installed Ubuntu Server 12.04 headless. I have installed Mediatomb on this server, but it will not start. dmesg says it terminates with status 1 and respawning, and at last "mediatomb respawning too fast, stopped".

    It works sometimes when transcoding is off in config.xml. However when enabling transcoding it will not start. I would really like to transcode my MOV videos (delivered by my small pocket camera) to a format understood by my Philips TV.

    Any ideas, please?

    Best regards
    globus68

     
  • Brady
    Brady
    2013-04-02

    Yes - I've had same problem on different vers Ubuntu servers for awhile.
    This may help:

    $ sudo nano /etc/init/mediatomb.conf
    

    Change your start stops:
    "

    start on started apache2
    stop on stopped apache2
    respawn
    

    "
    (If apache is your web server - if not replace with something appropriate)
    This should give the system more time to 'come up' before starting mediatomb as service.
    I am not sure who puts the Ubuntu packages together for Mediatomb but the symptom is in syslog :

    $ grep mediatomb /var/log/syslog
    

    (these appear when upstart is trying to start it during boot)

    Apr  1 11:00:10 myhostname kernel: [  350.308705] init: mediatomb main process (1102) terminated with status 1
    Apr  1 11:00:10 myhostname kernel: [  350.308730] init: mediatomb main process ended, respawning
    Apr  1 11:00:11 myhostname kernel: [  351.482870] init: mediatomb main process (1413) terminated with status 1
    Apr  1 11:00:11 myhostname kernel: [  351.482896] init: mediatomb main process ended, respawning
    Apr  1 11:00:11 myhostname kernel: [  351.548674] init: mediatomb main process (1492) terminated with status 1
    Apr  1 11:00:11 myhostname kernel: [  351.548700] init: mediatomb main process ended, respawning
    Apr  1 11:00:11 myhostname kernel: [  351.612825] init: mediatomb main process (1500) terminated with status 1
    Apr  1 11:00:11 myhostname kernel: [  351.612847] init: mediatomb main process ended, respawning
    Apr  1 11:00:11 myhostname kernel: [  351.724582] init: mediatomb main process (1505) terminated with status 1
    Apr  1 11:00:11 myhostname kernel: [  351.724607] init: mediatomb main process ended, respawning
    Apr  1 11:00:11 myhostname kernel: [  351.796617] init: mediatomb main process (1509) terminated with status 1
    Apr  1 11:00:11 myhostname kernel: [  351.796641] init: mediatomb main process ended, respawning
    Apr  1 11:00:11 myhostname kernel: [  351.860651] init: mediatomb main process (1519) terminated with status 1
    Apr  1 11:00:11 myhostname kernel: [  351.860675] init: mediatomb main process ended, respawning
    Apr  1 11:00:11 myhostname kernel: [  351.924530] init: mediatomb main process (1522) terminated with status 1
    Apr  1 11:00:11 myhostname kernel: [  351.924555] init: mediatomb main process ended, respawning
    Apr  1 11:00:11 myhostname kernel: [  351.976834] init: mediatomb main process (1527) terminated with status 1
    Apr  1 11:00:11 myhostname kernel: [  351.976861] init: mediatomb main process ended, respawning
    Apr  1 11:00:11 myhostname kernel: [  352.044640] init: mediatomb main process (1530) terminated with status 1
    Apr  1 11:00:11 myhostname kernel: [  352.044665] init: mediatomb main process ended, respawning
    Apr  1 11:00:11 myhostname kernel: [  352.102468] init: mediatomb main process (1534) terminated with status 1
    Apr  1 11:00:11 myhostname kernel: [  352.102492] init: mediatomb respawning too fast, stopped
    
     
  • Brady
    Brady
    2013-04-02

    I wanted to add: the service runs fine otherwise (from command line only) :
    $ sudo service mediatomb {start | stop | restart}

    So my response above may not answer the first post (I just re-read it), but I have noticed this behavior when upstart tries to start it during boot - so wanted to mention it.