Not a permission issue i set it to 777 just tob e sure there is no process acting with insufficient credentials. The hdd is 1T and the only thing running on it is openmeetings so that should not be a problem.
The log I posted was what I get in the messagebox that informs me about the errors when I try to open a recording in openmeetins. I just tried another recording about 2 mins that worked. What I did was stop recording, than give the applet some time like 3 minutes before I stopped sharing and then again I gave some time before I left the room. It worked. I will try to reproduce and hopefully I get a positive result. So again thanks for the efforts and the ultra fast and valuable responses from all of you -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Gesendet: Mittwoch, 18. Januar 2012 15:10 An: [email protected] Betreff: Re: AW: Ok, I found the post recorder log messages and it seems that it can't find the raw recording files in the streams directory, which would explain why it has issues processing them, no? :-) => No that could simply mean that one of the conversion jobs fails, so that the next stop does not find the files. I looked into the dir and there are no files of the actual recording. => What directory are you looking at? The folder streams/hibernate only contains the RESULT of the conversion not the actual raw files. Those ones are inside streams/$room_id I still doubt that the given log you posted is really everything from the error-log that is shown when you click on any of the recordings that did not process. I don't think that its a file permission issue, otherwise you would not have any successful recording at all. But of course your hdd should have some space left so that the resulting FLV/AVI can be produced from the raw recorded input files. Sebastian 2012/1/18 Mahmut TEKER <[email protected]>: > Hi, > > Could it be folder writing permission problem? Have you checked the web > user's permission to write into streams folder? > > > Have a nice day, > > _Mahmut > > > On 01/18/2012 03:57 PM, Norbert Haag wrote: >> >> Ok, I found the post recorder log messages and it seems that it can't find >> the raw recording files in the streams directory, which would explain why >> it >> has issues processing them, no? :-) >> >> I looked into the dir and there are no files of the actual recording. So I >> figure the java recording applet might not have send the stream to the >> server while recording? Is that possible? What is the best setting for >> recording (I am on a 16000 bit dsl and I should be able to do a 200 bit >> upstream.? >> >> Thanks for your help >> >> -----Ursprüngliche Nachricht----- >> Von: Norbert Haag [mailto:[email protected]] >> Gesendet: Mittwoch, 18. Januar 2012 13:49 >> An: [email protected] >> Betreff: AW: >> >> Well, actually that is the error message openmeetings comes up with if I >> select the recording. >> I will check the ffmpeg logs first and see if I can get more detailed >> information there. >> >> Thanks a lot for the support Sebastian >> >> >> >> -----Ursprüngliche Nachricht----- >> Von: [email protected] [mailto:[email protected]] >> Gesendet: Mittwoch, 18. Januar 2012 12:16 >> An: [email protected] >> Betreff: Re: >> >> your log seems to be rather incomplete or actually shows no problems. >> >> Sebastian >> >> 2012/1/18 Norbert Haag<[email protected]>: >>> >>> Hello all, >>> >>> >>> >>> I am sorry to nag anyone again with the ffmpeg issue. What happens is >>> that >> >> I >>> >>> can make a record it seems once. Doing a second recording fails with the >>> error log below. I tried all kind of things like making a real small >>> screenresolution (though the resolution of the first recording, the one >> >> that >>> >>> worked, was huge). >>> >>> >>> >>> I am running openmeetings on a dedicated machine with 8GB Ram and direct >>> connection to a pretty big pipe (1.5g) so I guess connectivity and >> >> bandwith >>> >>> is not the issue. >>> >>> >>> >>> Any suggestions? Or maybe someone can point me to a place where I can >>> find >>> more information. >>> >>> >>> >>> I am running openmeetings 1.9.1.r4707 >>> >>> >>> >>> Thanks in advance Norbert >>> >>> >>> >>> Log:18.01.2012 11:42:33 >>> >>> generateFFMPEG >>> >>> process-generateFullFLV >>> >>> error-ffmpeg version 0.9.1, Copyright (c) 2000-2012 the FFmpeg developers >>> built on Jan 18 2012 10:30:56 with gcc 4.4.3 configuration: >>> --prefix=/usr >>> --enable-gpl --enable-version3 --enable-nonfree --enable-libmp3lame >>> libavutil 51. 32. 0 / 51. 32. 0 >>> >>> command-[ffmpeg, -i, >>> >> >> /opt/red5/webapps/openmeetings/streams/7/rec_14_stream_0c422d4daf5fb5ed617d3 >> 41449a2848d_18_01_2012_10_41_27.flv, >>> >>> -i, >>> >> >> /opt/red5/webapps/openmeetings/streams/7/rec_14_stream_15_18_01_2012_10_41_2 >> 7_FULL_WAVE.wav, >>> >>> -ar, 22050, -acodec, libmp3lame, -ab, 32k, -s, 2176x1360, -vcodec, >> >> flashsv, >>> >>> -map, 0:0, -map, 1:0, >>> /opt/red5/webapps/openmeetings/streams/hibernate/flvRecording_14.flv] >>> >>> exitValue-1 >>> >>> >>> >>> >>> >>> Log:18.01.2012 11:42:33 >>> >>> generateFFMPEG >>> >>> process-generateFullFLV >>> >>> error-ffmpeg version 0.9.1, Copyright (c) 2000-2012 the FFmpeg developers >>> built on Jan 18 2012 10:30:56 with gcc 4.4.3 >>> >>> command-[ffmpeg, -i, >>> /opt/red5/webapps/openmeetings/streams/hibernate/flvRecording_14.flv, >>> -vcodec, mjpeg, -vframes, 1, -an, -f, rawvideo, -s, 2176x1360, >>> /opt/red5/webapps/openmeetings/streams/hibernate/flvRecording_14.jpg] >>> >>> exitValue-1 >>> >>> >>> >>> >>> >>> Log:18.01.2012 11:42:33 >>> >>> generateFFMPEG >>> >>> process-alternateDownload >>> >>> error-ffmpeg version 0.9.1, Copyright (c) 2000-2012 the FFmpeg developers >>> built on Jan 18 2012 10:30:56 with gcc 4.4.3 >>> >>> command-[ffmpeg, -i, >>> /opt/red5/webapps/openmeetings/streams/hibernate/flvRecording_14.flv, >>> /opt/red5/webapps/openmeetings/streams/hibernate/flvRecording_14.avi] >>> >>> exitValue-1 >> >> >> > -- Sebastian Wagner http://www.openmeetings.de http://incubator.apache.org/openmeetings/ http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
