Hi,
Sorry for waking this thread up, but I've been doing some more testing and
I can confirm "- test" flag makes melted crash. If I run melted with "-
test" I have no problems until I leave it without touching it for 1 entire
day and then try to do a "CLEAR" and then several "APND" to completely
change the playlist, then melted crashes. If I do the same without "-
test", melted handles everything fine. I know Dan said that "- test" only
skips the fork() and changes the log level, but I cant get why this would
make melted crash! Will look at the code when I get time to... Please
Markus or Dan, if you have anything new on this issue let me know.
Regards,
Juan Martin
2014-04-15 18:29 GMT-03:00 Juan Martin Runge <jmru...@gmail.com>:
> Markus,
> Sorry for the late answer, but was away on vacation and I saw your mail
> today. I can confirm -test works as expected on my server. Im using it to
> run melted with monit (http://mmonit.com/monit/) and was working for at
> least a week without problems. I also use it with lots of "APPEND" and it
> never died to me.
>
> Maybe something about the docker container?
>
> Regards,
>
> Juan Martin
>
>
> 2014-04-09 11:19 GMT-03:00 Markus Kienast <elias1...@gmail.com>:
>
>> Hi Dan,
>>
>> I created this Docker image and it works well.
>>
>> There are some glitches though still. For Docker it is beneficial, if a
>> service does not detach form the terminal and run as a daemon. This helps
>> to detect, when the service crashes, so it can be restarted from the host
>> system by restarting the Docker container, either monitored by upstart for
>> example.
>>
>> To achieve this behavior I made use of the "-test" flag. In order to not
>> flood my disk with stdout and stderr output, which Docker catches and
>> stores in a log file, I am discarding these streams via /dev/null.
>>
>> However, it seems that "-test" is making Melted run unstable, at least in
>> the Docker container. For example, when I send a large list of commands
>> (APND) to Melted via telnet, it dies on me.
>>
>> So basically what I am asking is:
>> a) is there another method to make Melted not detach? One, which
>> preferably still does not produce any debug output!
>>
>> b) if not, does Melted fork once or twice, ergo do I need the "expect
>> fork" or "expect daemon" stanza in upstart. As I would run Melted in daemon
>> mode and watch it with upstart from within the docker container if a) is
>> not available.
>>
>> Also I wanted to use the RUN command to execute this list of commands,
>> which made Melted crash. But I was unable to get Melted to accept my xy.txt
>> file as valid input. Both absolute and relative paths to the file did not
>> work.
>>
>> Any tip concerning that?
>>
>> My best Regards,
>> Markus
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Put Bad Developers to Shame
>> Dominate Development with Jenkins Continuous Integration
>> Continuously Automate Build, Test & Deployment
>> Start a new project now. Try Jenkins in the cloud.
>> http://p.sf.net/sfu/13600_Cloudbees
>> _______________________________________________
>> Mlt-devel mailing list
>> Mlt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mlt-devel
>>
>>
>
------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
Mlt-devel mailing list
Mlt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlt-devel
