Copied epesi/ www directory to different server

lirit

Evening guys,

I've tar'ed up all the work we did on epesi along with a database dump and copied it to a different server.
I completed setting up all the general stuff like apache, creating a database and importing the sql dump as well as changing that info in data/config.php

Now when I access it via it's new domain I am seeing the 'Starting epesi' logo and it displays a "Session expired, restarting epesi' and loops back forever.

I attempted the following with no success on that issue:
1. deleted data/cache/common.php
2. truncate session (db table)
3. truncate session_client (db table)

thinking that maybe it has something to do with the cache or old entries of the directory it used to be or the way it was accessed before (as I obviously changed the domain now).

I'm guessing this is a known issue? How do I clean things up to get it running?

Regards,
Liran.

lirit

An update - reading the wiki again regarding Re-installation I noticed it mentioned deleting the data/ directory completely which is what I did. Now continuing with the setup procedure is working, though this is completely a re-start for me. While I can easily just enable the modules again and language file as well as the new theme, I I thought it would be a smoother process.

So now since I deleted the data/ directory there's no language file and no theme (my own I mean) so I need to copy them again. Is there another process to ease this that I'm probably not aware of?

Regards,
Liran.

jasiek

Liran,
We copy frequently epesi instances between the production and development servers and perform exactly operations you describe:
- copy entire epesi installation directory to another server (including data directory)
- dump database from old server
- restore database on new server
- update configuration file - database name, user, password - if you keep them the same on both servers you don't need to update anything

The data directory needs to be empty during clean reinstall only. Data directory contains data - like attachments, e-mails - and needs to be copied as well during the migration process.

If you are getting session errors you are right - they are kept in the database - just empty session tables. However you may want to also empty local browser's cache or at least restart it. Please let us know if this helps.

Note: epesi is designed to work from any directory, virtual directory, host, port. It is beign tested on Windows XP, Vista, 2003 Server, Linux variants, OS X, IIS (Internet Information Server), Apache, several stacks like XAMP or WAMP and few hosting plans - to make sure that it is compatible with all environments. Occasionally we find some unusual setup but those bugs are being resolved as they are reported.

lirit

Well then it's odd because as I said, I did attempt to clean the session tables (there are only 2 of them, right?)
but it still gave me that "session expired" error and looped again and again trying to load the website.

After reading the Re-install FAQ I deleted the data directory, and then proceeded with the /setup.php process but that also overwrote all of my tables (I thought it would detect that they exist and wouldn't do it).
It's ok for now as I haven't had any special data except for all of the tweaks and configurations which I can repeat now though next time this happens I'll re-open this thread and we'll try to debug the problem.

Regards,
Liran.

ethnar

There's third session table 'history'.

Clean those three and it should indeed be fine. If it's not - please check next time if it's database data related - install fresh epesi, then overwrite database data with your dump, truncate session, session_client and history. If that will mess up this installation, check the user, variables and modules tables first - check if nothing was lost during the data migration.

Other than that - I'd have to get my hands on that particular installation I'm afraid.

lirit

Thanks I have overlooked that history table.

shacky

Hi,
one more thing to check, my dev-friends forgot about EPESI_DIR variable in config.php. This variable says where epesi should place cookies. On some systems there is no such variable in config.php - it's autodetected during every epesi boot. But on some systems this have to be set during installation process.
As you probably know, session id is placed in a cookie, so if cookies are managed with different dir then current one, there will be such error as occured in you copy - writes session cookie in EPESI_DIR, trying to read cookie from current dir - there is no session id, so session is expired. Just change this variable to current one and everything will be ok.

Paul

lirit

Yep, I did found that config directive and changed it.
I guess it was that 3rd table session_history which I missed.

Thanks,
Liran.

Epesi ENS | Epesi Academy | epesi.cloud PaaS | GitHub

Help Me! | Download from SourceForge