Uploading .mp3 files http error - 2 "exact" files one successful other fails
I have 2 equal .mp3 files - technically different files but both exported from Audacity using the same settings and the same original audio. Exactly the same size, same content (albeit processed separately) - one fails and one succeeds.
Both files play fine but could some character in the file be tripping up the PHP upload?
I see this error - ap_pass_brigade failed - in the log from last week - GoDaddy takes a long time getting the logs saved and today's errors are nowhere. related?
[Tue Apr 26 20:34:35 2016] [9000082] [fcgid:warn] (32)Broken pipe:
[client 173.160.120.186:51688]
mod_fcgid: ap_pass_brigade failed in handle_request_ipc function,
referer http://www.####.com/wp-admin/upload.php
[Thu Apr 28 12:56:54 2016] [9000082] [fcgid:warn] (110)Connection timed out:
[client 104.237.142.57:46250]
mod_fcgid: ap_pass_brigade failed in handle_request_ipc function
[Sun May 01 12:29:20 2016] [9000082] [fcgid:warn]
[client 104.236.68.137:58028]
mod_fcgid: can't apply process slot for /web/cgi-bin/php-fcgi,
referer http://####.com
I have the php memory settings and file uploads to 128mb and the timeout at 120seconds.
This one fails: https://drive.google.com/open?id=0Byiy0gx4A9G-dFR3MjdlTjFZUDg
This one succeeds: https://drive.google.com/open?id=0Byiy0gx4A9G-REhWVnRIMU5jek0
Running PHP 5.4 on GoDaddy
I have tried the 'fixes' for the imagick issue in PHP 4.5 to no avail.
my htaccess:
AddType x-mapp-php5 .php
SetEnv MAGICK_THREAD_LIMIT 1
IfModule mod_security.c
SecFilterEngine Off
SecFilterScanPOST Off
/IfModule
# Exclude the file upload and WP CRON scripts from authentication
FilesMatch "(async-upload\.php|wp-cron\.php|xmlrpc\.php)$"
Satisfy Any
Order allow,deny
Allow from all
Deny from none
/FilesMatch
RewriteEngine On
# BEGIN WordPress
IfModule mod_rewrite.c
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
/IfModule
# END WordPress
GoDaddy's senior tech had no idea what was up - maybe a corrupted Wordpress? I did however do a refresh install and no change.