Hm ok, I think that threading error is just a red-herring. If you feel
comfortable enough, I could try and import your setup into a spare gear on
my account and triage it that way. You can take an exact export with the
rhc snapshot command and I can import it and see if I can pin down what's
up with the auth.
If you're not comfortable with that, a few other things you can check are:
1. Make sure there's not a symlink overriding your parameters_443.py
pointing to a non-existant file. Basically I just stick the password in
parameters_8080.py and symlink that to parameters_80.py and
parameters_443.py
2. Make sure the parameters file you're using doesn't have some weird
permissions set (also ssh in and make sure they look good there in
$OPENSHIFT_REPO_DIR since it's possible something could get munged on the
push up).
3. Try and copy that same parameters file you're using in a vanilla web2py
setup and make sure that instance can read it and you can log in.
4. Lastly, if you're familiar with linux, you could manually run web2py in
the Openshift gear preceded by strace to see where it's looking for your
parameters file (maybe python profiling would do something similar? I
haven't used it, just a guess). Maybe syspath got messed up in the setup or
something like that.
Let me know how it goes.
On Saturday, December 29, 2012 11:30:58 PM UTC-6, Gustavo Souza wrote:
>
> Hello, Andrew!
>
> I'm using https, and my error logs I am giving this message:
>
> [Sun Dec 30 00:13:12 2012] [notice] SELinux policy enabled; httpd running
> as context unconfined_u:system_r:openshift_t:s0:c5,c110
> [Sun Dec 30 00:13:12 2012] [notice] mod_bw : Memory Allocated 32 bytes
> (each conf takes 32 bytes)
> [Sun Dec 30 00:13:12 2012] [notice] mod_bw : Version 0.8 - Initialized [1
> Confs]
> [Sun Dec 30 00:13:12 2012] [notice] Digest: generating secret for digest
> authentication ...
> [Sun Dec 30 00:13:12 2012] [notice] Digest: done
> [Sun Dec 30 00:13:12 2012] [notice] Apache/2.2.15 (Unix) mod_wsgi/3.2
> Python/2.6.6 configured -- resuming normal operations
> [Sun Dec 30 00:13:30 2012] [error] Exception KeyError:
> KeyError(140598980249568,) in <module 'threading' from
> '/usr/lib64/python2.6/threading.pyc'> ignored
> [Sun Dec 30 00:25:31 2012] [notice] mod_bw : Memory Allocated 32 bytes
> (each conf takes 32 bytes)
> [Sun Dec 30 00:25:31 2012] [notice] mod_bw : Version 0.8 - Initialized [1
> Confs]
> [Sun Dec 30 00:25:31 2012] [notice] Digest: generating secret for digest
> authentication ...
> [Sun Dec 30 00:25:31 2012] [notice] Digest: done
> [Sun Dec 30 00:25:31 2012] [notice] Apache/2.2.15 (Unix) mod_wsgi/3.2
> Python/2.6.6 configured -- resuming normal operations
>
>
>
> 2012/12/28 Andrew <andrew....@gmail.com <javascript:>>
>
>> Gustavo,
>>
>> Make sure that you're accessing it via https, I've noticed that if I
>> click on the admin button from the main page accessed via http, it uses
>> whatever transport protocol that was specified to get there.
>>
>> If you're already doing this I'd take a look at the web2py logs in
>> $OPENSHIFT_PYTHON_LOG_DIR. A while back I had submitted a bug for how their
>> proxy didn't set wsgi params when it passed the request to the gear. That's
>> been the only time I've run into an issue like that.
>>
>> Also make sure your options_std.py is linked to options.py
>>
>> If you come across any more info, I'd be happy to take a look.
>>
>> Andrew
>>
>>
>> On Wednesday, December 26, 2012 8:38:21 AM UTC-6, Gustavo Souza wrote:
>>>
>>> Hi Adrew, I followed these steps and was able to deploy the web2py, and
>>> it works! ... I did with version 2.3.2
>>> My only problem is that the web2py admin panel is disabled.
>>> I created the file "parameters_443.py" and put the password hash, but
>>> still the message appears "admin disabled because unable to access password
>>> file "
>>>
>>> I have to change something?
>>>
>>> Em domingo, 19 de agosto de 2012 20h39min52s UTC-3, Andrew escreveu:
>>>>
>>>> A little different in order.
>>>>
>>>> Do all the openshift stuff first, then download web2py and copy it into
>>>> the wsgi folder.
>>>>
>>>> I would suggest using the application file I provide on the github repo
>>>> and modify:
>>>>
>>>> This:
>>>> sys.path.append(os.path.join(**os.environ['OPENSHIFT_REPO_**DIR'],
>>>> 'libs', 'gluon'))
>>>> to This:
>>>> sys.path.append(os.path.join(**os.environ['OPENSHIFT_REPO_**DIR'],
>>>> 'wsgi', 'web2by', 'gluon')) #honestly I don't know if sys.path.append
>>>> handles stuff recursively so maybe this isn't necessary and you just
>>>> comment out the gluon line.
>>>>
>>>> There are other nuances like addressing db host / port / user / pass
>>>> variables that should all be setup in wsgi/application file. For example
>>>> if
>>>> you're using SQL lite, I have an example variable setup in the
>>>> wsgi/application handler and then in your model you'd just use something
>>>> like:
>>>>
>>>> db = DAL('sqlite://storage.sqlite',**folder=SQLITE_DIR)
>>>>
>>>> If you want to use the admin, you'll need to create a parameters_443.py
>>>> with your hashed password in it but there are caveats to using the IDE in
>>>> the cloud since app changes are applied via rhc / git. This is why I
>>>> created the openshift deployer.
>>>>
>>>> Andrew
>>>>
>>> --
>>
>>
>>
>>
>
>
>
> --
> **
> *
> *
> *Gustavo de Souza Lima*
> gus...@agenciax4.com.br <javascript:>
> DESENVOLVEDOR
>
> *(21) 2423-4351* (escritório)
> *(21) 8163-0309* (celular)
>
> Twitter: @dodilei <https://twitter.com/dodilei>
> Google+: gplus.to/dodilei
>
> tech4noobs.agenciax4.com.br/
>
--
