Forum Activity for @dannya

Future queue operations

Jamroom Developers

Is it possible to set a future date for a queue operation? Specifically, I am creating a song/blog/whatever and I have sharing enable. The creation/release date is in the future. But the sharing operation is going to the queue right away. I want the queue operation to happen on the release date.
updated by @dannya: 06/26/15 08:36:40PM

ffmpeg error

Jamroom Developers

I am facing issue when creating mp4 files. It happens on some media and all others working fine.


FFMPEG Error:

ffmpeg version N-50408-gdc666d3 Copyright (c) 2000-2013 the FFmpeg developers built on Feb 28 2013 23:01:11 with gcc 4.3.2 (Debian 4.3.2-1.1) configuration: --enable-shared --enable-gpl --enable-version3 --enable-nonfree --enable-hardcoded-tables --cc=cc --host-cflags= --host-ldflags= --enable-libx264 --enable-libfaac --enable-libmp3lame libavutil 52. 17.103 / 52. 17.103 libavcodec 54. 92.100 / 54. 92.100 libavformat 54. 63.102 / 54. 63.102 libavdevice 54. 3.103 / 54. 3.103 libavfilter 3. 41.100 / 3. 41.100 libswscale 2. 2.100 / 2. 2.100 libswresample 0. 17.102 / 0. 17.102 libpostproc 52. 2.100 / 52. 2.100 [mp3 @ 0x1075ffe0] max_analyze_duration 5000000 reached at 5015510 microseconds [mp3 @ 0x1075ffe0] Estimating duration from bitrate, this may be inaccurate Input #0, mp3, from '/home/cleartracks/public_html/data/cache/xtMix/xtDistribLicense_335_distriblicense_sample_file.mp3': Duration: 00:15:43.05, start: 0.000000, bitrate: 128 kb/s Stream #0:0: Audio: mp3, 44100 Hz, stereo, s16p, 128 kb/s [mjpeg @ 0x10762360] invalid id 217 [image2 @ 0x107619e0] decoding for stream 0 failed [image2 @ 0x107619e0] Could not find codec parameters for stream 0 (Video: mjpeg): unspecified size Consider increasing the value for the 'analyzeduration' and 'probesize' options /home/cleartracks/public_html/data/cache/xtMix/temp_image.jpg: could not find codec parameters |
updated by @dannya: 06/26/15 12:34:56PM

Monitoring cloud conversions

Jamroom Developers

Awesome!

Is there any way to get this data via shell/perl/awk/sed script? Trying to send the data to Munin dashboard.

Custom uploader

Jamroom Developers

Is it possible to swap out the uploader without breaking all the modules. I want to do 3 things:

1. Change the progress bar on direct uploads
2. After linking a user to their dropbox account (and saving their key after authentication), I want to give the user the option to select a file that will be ingested by background process via queued function after the form is submitted.


updated by @dannya: 06/19/15 10:55:45PM

Monitoring cloud conversions

Jamroom Developers

I'm looking a various monitoring tools. Is there any way to create an alert that fires whenever a queue exceeds X seconds?

I'm also trying to think how we can see conversion performance over time accross all the conversion servers in a cluster.

The goal here is to get some advance notice when you performance is slow and need to add another server.
updated by @dannya: 06/26/15 08:36:35PM

Troubleshooting workers

Using Jamroom

As I said, sysadmins say they checked connectivity and there is no issues connecting on port 80 or 443.

They asked if there is a specific command to test.

It would be great if you could provide specific instructions for testing it. The JR system check also does not indicate any issues, but I don't know if it checks any cloud requirements.

Troubleshooting workers

Using Jamroom

Also, the activity log error on tx1 is not timing out, but its getting an "unable to load url" error

Troubleshooting workers

Using Jamroom

As I said, connection from cache1 to tx1 was confirmed.
Url responds.
but tx 1 is not getting response

Troubleshooting workers

Using Jamroom

Ok. all these are done. Created a new upload an new stuck queues.
Checked cron server and saw ping was not being responded to

But if I go to url, it responds

https://cache1.cleartracks.com/cloudcore/ping

Something is still wrong

Troubleshooting workers

Using Jamroom

Ok. This is dragging out.

1. How do I clear out the current queues.
2. All changes have been made to https servers
3. Which modules need to be enable on:
---main server
---queue server
---cloud client server