WSGI appending 'admin' to file name

MediaCore Community » General Discussion & Feedback

WSGI appending 'admin' to file name

11 posts Started 1 year ago by tinycg Latest reply from Nathan Wright

tinycg
Member
Posted 1 year ago

I'm still working through some issues as mediacore_restart is stating the 'kill: (xxxx) - No such process' but in working through issues I also noticed that in my error logs I'm getting "Target WSGI script not found or unable to stat: /xxxx/deployment-scripts/mod_wsgi/mediacore.wsgiadmin"

And can't figure out where I might have a typo or something thats causing 'admin' to be appended to the correct file location.

Thats currently the only error in the error log, though as stated above I do seem to have other issues.

I removed the virtualenv and started from scratch today installing a fresh copy of python 2.5 vs 2.6, updated pylons to 0.9.7 as I'd seen in another post, and checked my WSGI install which seems to be all setup.

When I go to the URL it appears I'm put into a redirect loop, but given that its looking for a filename it will never find, I'd like to at least see if I can correct that first :)

When I do a reload with the paste server, it's spitting back a lot of 'File' stuff, and I'm not familiar with it enough to know whether this is normal, of an issue.

I have Apache 2.2, Python 2.5, root access, etc..

Thanks for any help in advance.
Anthony Theocharis
Key Master
Posted 1 year ago

Hey tinycg,

If you're running a post 0.7.2 release of mediacore, you won't need to update pylons. That could be causing some trouble by itself.

Are you sure you didn't accidentally type "admin" after the WSGIScriptAlias line? Like...
WSGIScriptAlias /my_media/ /path/to/mediacore_install/deployment-scripts/mod_wsgi/mediacore.wsgiadmin instead of WSGIScriptAlias /my_media/ /path/to/mediacore_install/deployment-scripts/mod_wsgi/mediacore.wsgi

If you haven't, I suggest pulling down the latest version MediaCore 0.8rc2 that I just released, and following the updated docs.

I just went through the steps and it worked for me. If that helps (or if it doesn't) post back here and we'll see if we can narrow it down further.
tinycg
Member
Posted 1 year ago

I quadruple checked the scriptAlias line, didnt see it there. I was running 0.8rc1, and could run yet another fresh install of python 2.5 if you think updating pylons was a bad idea.

I'll pull down the new RC today and give it a run through and report back, thanks for the help.
Nathan Wright
Maintainer
Posted 1 year ago
I've found the problem, but I'm not sure why WSGIScriptAlias behaves the way it does...

If you're serving from the root of your domain then the line in httpd.conf should look like this:
```
WSGIScriptAlias / /path/to/mediacore_install/deployment-scripts/mod_wsgi/mediacore.wsgi
```
but if you're serving from a subdirectory such as my_media (like the example given in the docs):
```
WSGIScriptAlias /my_media /path/to/mediacore_install/deployment-scripts/mod_wsgi/mediacore.wsgi
```
Notice there's no trailing slash when it's a subdirectory.
Anthony Theocharis
Key Master
Posted 1 year ago

Good catch, Nate. I've updated the docs to remove the trailing slash.
tinycg
Member
Posted 1 year ago

That cleared my issue right up and it seems to be running, I'll install rc2 tonight, but I did notice in the admin now it seems to be removing the sub-directory from the links, so that its building instead of
{domain}/my_media/admin/{podcasts|comments|etc}

its

{domain}/admin/{podcasts|comments|etc}

if I correct it by hand, it loads the pages fine. This could be an issue that was corrected in the latest rc? but didn't know if there was an issue with the AliasMatch maybe as well?
Anthony Theocharis
Key Master
Posted 1 year ago

This should be fixed in the latest release/docs, through the use of the proxy_prefix config setting.
tinycg
Member
Posted 1 year ago

Thanks guys, most things seem to be running fine, and I've worked out all the configuration issues, so mediacore seems very happy. Except for 2 things I've noticed..

I'm able to upload and play a video on the explore/featured section, but going to the media itself produces a mediacore friendly 404. (edit # 2) The mod_rewrite being done seems correct as I'm getting sub-dir/media/name-of-media but, it doesnt seem to know what to do with it.

I'm able to save files, but upon the upload being successful, I can't change the media type, it seems to allow me to change it after save just fine.

I get an error on trying to remove the file saying it was unable to complete the action.

On a sidenote - I have h264 streaming setup and flowplayer seems happy, and will play natively encoded mp4 h.264 files if its set to 'audio' as the type, but the minute I set it to 'video' I get mediacore telling me to encode it, which from reading it seems to be expecting an flv, which is fine, but really not needed, is there a way I can get mediacore to 'trust me' :)

Thanks again, this is an awesome app, seriously impressed.

p.s. - running 0.8rc2 now.
Nathan Wright
Maintainer
Posted 1 year ago

I've committed a patch to fix that mp4 video issue you described, but I'm not sure what's going on with the other file-related issues. Could you try reproducing the problem again and grabbing the error messages/tracebacks from apache's error_log? Alternatively, if you have a local mailserver running, you can edit your development.ini or deployment.ini file to have the errors emailed to you.

Glad to hear you're enjoying MediaCore!

Cheers, Nathan
tinycg
Member
Posted 1 year ago

Thanks for the help Nathan, here's what was coming out of the error_log, I'll turn on email errors tonight.

[error] [client x.x.x.x] File does not exist: /pathtoinstall/mediacore/public/admin/styles/videos.css, referer: http://domain/media/admin/media
[error] [client x.x.x.x] Error - <type 'exceptions.UnboundLocalError'>: local variable 'file' referenced before assignment
[error] [client x.x.x.x] Error - <type 'exceptions.UnboundLocalError'>: local variable 'file' referenced before assignment
[error] [client x.x.x.x] Error - <type 'exceptions.UnboundLocalError'>: local variable 'file' referenced before assignment
[error] /pathtoenv/mediacore_env/lib/python2.5/site-packages/SQLAlchemy-0.5.8-py2.5.egg/sqlalchemy/engine/default.py:123: Warning: Column 'duration' cannot be null
[error] cursor.execute(statement, parameters)
[error] [client x.x.x.x] File does not exist: /pathtovhost/httpdocs/images, referer: http://domain/media/styles/base.css
[error] [client x.x.x.x] File does not exist: /pathtoinstall/mediacore/public/admin/styles/videos.css, referer: http://domain/media/admin/media
[error] /pathtoenv/lib/python2.5/site-packages/SQLAlchemy-0.5.8-py2.5.egg/sqlalchemy/engine/default.py:123: Warning: Column 'duration' cannot be null
[error] cursor.execute(statement, parameters)
[error] [client x.x.x.x] mod_wsgi (pid=17625): Exception occurred processing WSGI script '/pathtoinstall/deployment-scripts/mod_wsgi/mediacore.wsgi'.
[error] [client x.x.x.x] IOError: failed to write data
[error] [client x.x.x.x] File does not exist: /pathtoinstall/mediacore/public/admin/styles/videos.css, referer: http://domain/media/admin/media
[error] [client x.x.x.x] Error - <type 'exceptions.OSError'>: [Errno 2] No such file or directory: '/pathtoinstall/data/deleted/media'
[error] [client x.x.x.x] Error - <type 'exceptions.UnboundLocalError'>: local variable 'file' referenced before assignment
[error] [client x.x.x.x] Error - <type 'exceptions.UnboundLocalError'>: local variable 'file' referenced before assignment

Of note, I changed 'my_media' to just 'media' and cleaned out specific install info just to protect the install
Nathan Wright
Maintainer
Posted 1 year ago

This sounds like it might be a permissions problem. First, there should be a folder called 'deleted' in your data dir: if it doesn't exist, create it. Then make sure you the data dir and all its subdirs are writable (by Apache if you're deploying with mod_wsgi or mod_fastcgi).

RSS feed for this topic

Reply

You must log in to post.

Community Forums

WSGI appending 'admin' to file name

Reply