Page 1 of 1

how to pin down a problem that happens only after a week?

PostPosted: Thu Feb 07, 2013 7:00 am
by n3mmr
I've got this problem where serviio seems to loose interest in checking on the online resources any more after about a week.

If I then change the log settings and restart serviio, my disk might overflow before anything useful is likely to be logged..

So, how do I track this down in a practical way???

Can logs be trimmed off while running w/o disturbing serviio?? or is there some better choice for log settings?

I'm on a Solaris/openindiana host. Using the Linux serviio distro unadulterated.

version 1.1
ffmpeg is 1.1.2 linked with libRTMP 2.4.

Re: how to pin down a problem that happens only after a week

PostPosted: Thu Feb 07, 2013 5:52 pm
by slyguy42o
more of a work around than a solution.. but maybe you could try setting up a cron to recycle the serviio service after a few days?

Re: how to pin down a problem that happens only after a week

PostPosted: Thu Feb 07, 2013 10:18 pm
by n3mmr
slyguy42o wrote:more of a work around than a solution.. but maybe you could try setting up a cron to recycle the serviio service after a few days?


That does away with the problematic result for me... but I was asking about how to try and find some info about the problem to enable me to file a bug report.

Currently I am restarting the serviio service from root's crontab.

Re: how to pin down a problem that happens only after a week

PostPosted: Thu Feb 07, 2013 10:38 pm
by zip
Do you use any plugins? Might be related to a particular plugin / resource. You could try to start with a single plugin and then take it from there.

Logs should rotate ( 5 x 500 kB)