SID-00268: Moving twiki to another server

Status:	Answered	TWiki version:	4.2.0	Perl version:	perl 5.10.0
Category:	CategoryInstallation	Server OS:	Ubuntu 2.6.27-11.31 server	Last update:	14 years ago

I was wondering if there are any issues with just tarballing the twiki directory on one server, copying over the Apache config files (virtual host, twiki.conf, etc), modifying the files appropriate for the new server and just transferring everything over to another server? I was trying to avoid having to do a fresh twiki install but wanted to consult with your organization first.

-- PatriciaNolan - 2009-04-15

Discussion and Answer

That should work fine. Make sure you install the dependencies (CPAN, gnu tools) as outlined in TWikiSystemRequirements.

-- PeterThoeny - 2009-04-15

Thank you for your reply. However, unfortunately even though I have gone through all the steps to ensure the configurations are the same. I have all the CPAN and gnu modules/tools according to my checks. When I type in the URL of the website I have setup as per the virtual host settings I continually get "Address Not Found". The permission/security settings are exactly like the original server that hosted our twiki. It is as if Apache is not even recognizing the files are there. I have restarted both Apache and the server many times along with playing with settings, removing all the files--double-checking them--and putting them back in Apache directories. I have gone through the twiki directory and the key files I understand to review for a proper installation. Is there anything I am missing? It seems like it must be a simple oversight given the error message. I have even gone so far as stopping Apache on the original server since that twiki website is still live until this new one is correctly working. Any insight you may have will be greatly appreciated.

Thank you in advance.

-- PatriciaNolan - 2009-04-16

Check the Apache error_log and access_log to pin-point the issue.

-- PeterThoeny - 2009-04-16

Thanks for the quick reply. That's the hard part.....the access and error logs for the virtual host file are empty and the generic Apache access and error logs make no reference to access attempts or anything close to the twiki. I just got through adding another site to the virtual host directory and setting up its configuration with no problem. There are no typos....at least not that I can see.....as I have scoured the files 9twiki.conf and the virtual host file for the new twiki website and the basic Apache2.conf file) countless times for any discrepancies. It's as if those files weren't even there....it's very strange.

-- PatriciaNolan - 2009-04-16

Sorry....correction twiki.conf, not 9twiki.conf.

-- PatriciaNolan - 2009-04-16

Wild guess: Check access permissions of twiki/bin files. Some hosting env are very picky where 775 does not work but 755 does.

-- PeterThoeny - 2009-04-16

"Address not found" and nothing in the logs almost sounds like the new Apache isn't running. Can you try an HTTP trace at the browser to see what's going on? Or try "netstat -an" on the server to see if there's only one service listening on the port you selected?

I don't know about ubuntu, but some unices reserve ports less than 1024 for processes that require administrative access. An OS-specific workaround is required to bind to port 80 without that.

-- SeanCMorgan - 2009-04-16

Thanks for your time. The Apache service is running as three other websites are running off virtual host settings on the same Ubuntu server. I'm using the standard port 80 for the sites. One thing I did notice is the the LocalSite.cfg file still showed all the old path statements to the twiki directory. I corrected this and rebooted the server but still no luck. I did compare the permission settings between the two twiki/bin directories and they are the same and reflect the preferred 755. It's quite the mystery.

-- PatriciaNolan - 2009-04-16

To provide a little more info about the web structure of the new server that will hopefully host or twiki site.....the destination server currently is running four other web sites/services of ours and is in another directory under /var other than the typical /var/www. Would this possibly be an issue with just transferring over the tarball? Are there possibly some binary files or other files that cannot be modified that reference /var/www and won't allow any other paths to be used? It's a shot in the dark but I am at a loss at this point and am about to just reinstall twiki on the new server if there is no other recourse. I am trying to avoid this, however, and appreciate any other insight you might provide.

Thank you again, PN

-- PatriciaNolan - 2009-04-20

As a followup to my previous message, if the fact is that there are twiki files looking for /var/www still..... I could just move the twiki directory to /var/www and have the Apache files include that directory as well and see if that works. I thought I would wait until I hear from you regarding anything else that might be overlooked before doing so. Thank you again, PN

-- PatriciaNolan - 2009-04-20

A couple of random thoughts:

• Check the 'shebangs' in /bin (i.e.., the path to Perl in line #1)
• Can you run /bin/configure in the browser? That is usually step one, and it will show you any subsequent path errors.

-- SeanCMorgan - 2009-04-20

Closing this question after more than 30 days of inactivity. Feel free to reopen if needed. Consider engaging one of the TWiki consultants if you need timely help. We invite you to get involved with the community, it is more likely you get community support if you support the open source project!

-- PeterThoeny - 2009-06-02

One possible issue could be SELinux. Disable it for a TWiki server.

-- PeterThoeny - 2011-12-08

If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.