Cant login to my manager :/ [modx 2.0 beta 3]

Not getting anywhere on this at the moment. I’m guessing I missed some kind of requirement somewhere, so I put a copy of my phpinfo here: http://jacob.larsen.net/phpinfo.html

I’m simply evaluating revolution at the moment, so this is the setup of the development server on my laptop.

mysql 5.1.30really5.0.75-0ubuntu10.2.

Your client API is 5.0.75 and your server is 5.1.30 If so, that is the problem...

Unfortunately it is not so simple. For some reason server 5.0.75 is reported as 5.1.30 in the Ubuntu version scheme. Phpmyadmin reports version 5.0.75-0ubuntu10.2 for server. The other version number is from the Ubuntu package manager.

- Did setup go without any errors?
- Is there anything relevant in core/cache/logs/error.log?
- Are there any browser errors when you log in?
- Did you install from SVN, or use the traditional or advanced package of beta3?

magic_quotes_gpc On

Turn that to off. That might solve it.

No errors reported during setup.
There is some interesting stuff in error.log, I already attached this before. I tried following it a bit and I got to the point in modSessionHandler::write() where I can see that $this->modx->getObject(’modSession’, array (’id’ => $id), $cacheLifetime) fails even if that id has already been written right before. Probably not even close to the real cause, since it looks mostly external, I would need to get a bit more into the code before I can continue this thread though.
I don’t see any browser errors at login, I assume you are talking about script errors?
I have tried the beta3 simple package and SVN from revolution and 2.0 branches, all with the same result. I did notice something strange though, I have run the build script many times now for the SVN install and no run took longer than 10 seconds while the doc says I should expect 150-200 seconds runtime. There were no obvious error messages though.

Actually I started with magic_quotes_gpc Off. I tried changing it just in case, since that is default, and there is no mention of it in requirements. Anyway, it does not change the outcome of this problem. I guess this is a thing I forgot to mention before, sorry...

Is there a way of logging the raw SQL queries and their responses from inside MODx or xPDO? Maybe it can shed some more light on my problem to see the actual DB traffic.

This is my build output if you can use it (from 2.0 branch):
[2009-09-05 04:13:56] (INFO @ /2.0/_build/transport.core.php) Beginning build script processes...
[2009-09-05 04:13:56] (INFO @ /2.0/_build/transport.core.php) Removed pre-existing core/ and core.transport.zip.
[2009-09-05 04:13:56] (INFO @ /2.0/_build/transport.core.php) Core transport package created.
[2009-09-05 04:13:56] (INFO @ /2.0/_build/transport.core.php) Default workspace packaged.
[2009-09-05 04:13:56] (INFO @ /2.0/_build/transport.core.php) Packaged in modxcms.com provisioner reference.
[2009-09-05 04:13:56] (INFO @ /2.0/_build/transport.core.php) Packaged in 50 modActions.
[2009-09-05 04:13:56] (INFO @ /2.0/_build/transport.core.php) Packaged in 8 modMenus.
[2009-09-05 04:13:56] (INFO @ /2.0/_build/transport.core.php) Packaged all default modContentTypes.
[2009-09-05 04:13:56] (INFO @ /2.0/_build/transport.core.php) Packaged in web context.
[2009-09-05 04:13:56] (INFO @ /2.0/_build/transport.core.php) Packaged in mgr context.
[2009-09-05 04:13:56] (INFO @ /2.0/_build/transport.core.php) Packaged in connectors.
[2009-09-05 04:13:56] (INFO @ /2.0/_build/transport.core.php) Packaged in 104 default events.
[2009-09-05 04:13:56] (INFO @ /2.0/_build/transport.core.php) Packaged in 91 default system settings.
[2009-09-05 04:13:56] (INFO @ /2.0/_build/transport.core.php) Packaged in 2 default context settings.
[2009-09-05 04:13:56] (INFO @ /2.0/_build/transport.core.php) Packaged in 1 default user groups.
[2009-09-05 04:13:56] (INFO @ /2.0/_build/transport.core.php) Packaged in 2 default roles Member and SuperUser.
[2009-09-05 04:13:57] (INFO @ /2.0/_build/transport.core.php) Packaged in 2 default access policies.
[2009-09-05 04:13:57] (INFO @ /2.0/_build/transport.core.php) Packaged in 2 default access context permissions.
[2009-09-05 04:13:58] (INFO @ /2.0/_build/transport.core.php) Packaged core lexicon entries (14) and topics (39).
[2009-09-05 04:13:58] (INFO @ /2.0/_build/transport.core.php) Beginning to zip up transport package...
[2009-09-05 04:13:59] (INFO @ /2.0/_build/transport.core.php) Transport zip created. Build script finished.

Execution time: 3.8256 s

Quote from: Jacob at Sep 04, 2009, 07:26 PM

I have tried the beta3 simple package and SVN from revolution and 2.0 branches, all with the same result. I did notice something strange though, I have run the build script many times now for the SVN install and no run took longer than 10 seconds while the doc says I should expect 150-200 seconds runtime. There were no obvious error messages though.

Yeah, we found some fixes to speed it up big time in the latest commits. beta4 will be much faster to setup than beta3.


So, can you explain to me just what happens when you try to login? Does it just go blank, or what?

When I press the login button, I see a progress bar for a moment with "loading", I estimate it gets to about 20 percent of the way, then it disappears and the login page reloads. If I enter a bad password, I get an actual error instead, but about at the same point on the progress bar.

Hm, definitely sounds like a session error. It’s hard to debug since you’ve got a pretty custom LAMP stack there. We’ll try and look into it.

A google search on "ubuntu php mysql pdo errors" shows a ton of results. Seems this is a common problem when setting up PDO configurations on various versions of Ubuntu. I would investigate these and see if this is the problem...