Nope.. that does not work. I am familiar with Apache, modules.. in general and to some level inner working. If you tell me a bit more about how it works.. I can try to dig some more.
* the wsgi script needs to be owned by apache user right ? * The conf file that goes under the conf.d also needs to be owned by apache user. * What about tg2env directory ? * What about application directory ? * Any other assumptions.. about path..etc. * Any clue why the sys.path printed shows paste.. but the app fails.. any other way to debug this ? ----------- I have a setup that works as a non-root user. The tg2env and the application both are under this user. and everything works fine. Now, a. What I tried was to copy this and change ownership to apache. I did modify the .pth file and fixed the path specific to the app. This is getting in to the problems that I have put details in the pastebin. There are two other options b. Setup so that global apache .. points to the working environment. (There were more chances of user permission problem... hence I chose to go with a. c. Setup up private apache (as non-root) user and then try to wire this up. Has anyone tried these.. or any of the option look better? Thanks in advance /Jd On Feb 15, 3:16 pm, Graham Dumpleton <[email protected]> wrote: > Try changing options to WSGIDaemonProcess from: > > user=apache group=apache > > to user/group for your own account from which you were doing command > line validation that everything was okay. > > If this works, it shows it is potentially a permissions problem for > the Apache user. > > If it doesn't work, then it is the paths setup in WSGI script file or > when doing stuff from own account it perhaps works because of > inheriting PYTHONPATH or some other Python environment variable from > user environment. > > Graham > > On Feb 15, 9:36 am, Jd <[email protected]> wrote: > > > Un-commenting the reordering section did not help. > > > Any other pointers. > > Note : The sys.path printed seems correct... contains the Paste stuff. > > > /Jd > > > On Feb 11, 9:28 pm, Graham Dumpleton <[email protected]> > > wrote: > > > > On Feb 12, 2:07 pm, Lukasz Szybalski <[email protected]> wrote: > > > > > On Thu, Feb 11, 2010 at 8:02 PM, Graham Dumpleton > > > > > <[email protected]> wrote: > > > > > > On Feb 12, 11:18 am, Lukasz Szybalski <[email protected]> wrote: > > > > >> On Thu, Feb 11, 2010 at 6:10 PM, Jd <[email protected]> wrote: > > > > >> > After spending lot of hours and making progress through number of > > > > >> > errors... I am stuck.. and need some help. > > > > > >> > The error I am getting is. > > > > > >> >http://pastebin.com/f74f5c15e > > > > > >> > Here is my apache conf file. > > > > > >> >http://pastebin.com/m56ca2a55 > > > > > >> > Here is wsgi script. > > > > > >> >http://pastebin.com/m27cdd87e > > > > > >> > Any help is appreciated. > > > > >> > Thanks > > > > > >> Try uncommenting the above code that is in your config code. > > > > >> Lucas > > > > > >> # > > > > >> #Move just added item to the front of the python system path. > > > > >> # > > > > >> #Not needed if modwsgi>=3.0. Uncomment next 6 lines. > > > > >> # > > > > >> ###new_sys_path = [] > > > > >> # > > > > >> ###for item in list(sys.path): > > > > >> # > > > > >> ### if item not in prev_sys_path: > > > > >> # > > > > >> ### new_sys_path.append(item) > > > > >> # > > > > >> ### sys.path.remove(item) > > > > >> # > > > > >> ###sys.path[:0] = new_sys_path > > > > > > That code is indeed still needed if using mod_wsgi 3.0. > > > > > > The reordering of sys.path from mod_wsgi 2.4 onwards only relates to > > > > > when WSGIPythonPath directive or 'python-path' option for > > > > > WSGIDaemonProcess are used and not where sys.path is being explicitly > > > > > updated in WSGI script file using site.addsitedir(). > > > > > > If the above is from some template somewhere in generated script file > > > > > or documentation, it should be changed as the comment is plain wrong. > > > > > Which comment is wrong? Is it the "Not needed if modwsgi>=3.0" or? > > > > Correct, just the comment: > > > > "Not needed if modwsgi>=3.0" > > > > is wrong. > > > > That reordering code is always needed regardless of mod_wsgi version > > > when using site.addsitedir() to update sys.path, so that section of > > > code should never be commented out. > > > > Graham -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
