The free forums are no longer in use. It remains available as read-only archive.
Log In
Home
12:16 am
January 11, 2011
Offline
Some details about the site first as it is a site that is going through development with chunks of working stuff I will put up on the production site as we reach certain points. The production site is running on apache2, php5 etc with a base install of v1.6 downloaded today. My backup was taken from a working base install of 1.6 with demo data. It has akeeba backup, admin tools and community builder installed as extra modules. The site function and works well. From this new and working site I took a backup with no compression to save time. It is just a tar ball. All good.
On another server (local vmware image) I setup a up a mysql db with the same user and password as the prod site. I killed all the firewalls (iptables), and everthing works with a new install. I the delete all the web site files, drop the database tables ready to restore. I now know to keep a copy of XCloner.php and tar.php locally in my local hacking toolbox to help this process. I download the tar ball from my prod site (I have less control over the prod site so I get it working there and then it back to dev system), run up XCloner.php, it finds the tar ball, I use direct copy for the files (I dont use ftp) and it restores the file system (great), it then restore the database (great) lets me jump stratight to the newly restored site all is good.
Then I try to log in as administrator and NOPE NO WAY! I have gone down into the users table and updated user names and passwords. Tried a differen dbase user and password in configuration.php (root access to the dbase) and no change and no entry. The site works great so it is talking to the dbase ok I guess. I just cant access the administration console. So I went and changed user on the prod site. Checked it is all working again. Re-tarballed up with the backup tool. Copied it back to the dev site. Droped the database tables and deleted all the files again. Checked it was all working in prod. Recloned it and the same result. Site works but no access to the adnministration console.
I thought file access and so as its a dev system I can play a little, so I just gave the whole site everything (chmod -R 777 /var/www/html) and no change. The site works well but I just cant control it once it is cloned. Any ideas?
Joomla is pretty new to me and I am not a php wizard or a mysql dba. I
am a middleware java hacker with lots of *nix systems experience, oracle or postgress dbase and big trading of banking systems. Are there any logs or telltail files where you suggest I look.
Thanks for you patience to listen to the ramble but I think I covered most of it. You will probably come back with a 2 line- try this and it fxes it. anyway thanks if know what the problem may be.
regards
Graham
9:48 am
September 26, 2010
Offline
Hi Graham, Joomla 1.6 is pretty new to me also, based on what i know, could you check this:
1. make sure your new site php.ini session.save_path value path exists and is fully writeable, presuming that maybe you are not using the datatabase to store the sessions
2. check the jos_sessions table from the new site, try and empty it, then try to login and see if any records are created?
3. try and install a core Joomla 1.6 on the new server by using the default package, are you able to login to that site?
Regards, Ovidiu
8:09 pm
January 11, 2011
Offline
Hi Ovidiu,
1. The session_save_path in php.ini points to the /var/lib/php/sessions directory and the directory rights are as follows
drwxrwx--- 2 root apache 4096 Jan 11 20:37 session
The webserver operates as user=apache and group=apache so the apache group would give complete access to this directory so that looks good and no problem.
2. I cleared down the session table where there was only 1 row. By the way my database does not use the default database prefix of jos_ which is just something I noted. This lead to no change and still not able to login as administrator.
3. Found the problem when installing from fesh. Somehow the MYSQL database user does not have the LOCK TABLE as WRITE privilege. An install works fine but when you go add a new module it requires a table lock and it fails. Interesting. Now have to investigate why the user does not have table lock.
Thanks for your suggestion.
Graham
10:33 am
September 30, 2010
Offline
The thread is exactly 1 year old, and I was searching a solution for the same problem. I got it. For all other coming allso over this thread:
Check if you have in the configuration.php a Cookie domain set. E.g.: public $cookie_domain = 'here-my-old-domain.xy';
If yes - delete the entry of the domain(name). The line sould look: public $cookie_domain = '';
Try it again.
Good luck.
🙂
All RSS1 Guest(s)
