I was wondering if anyone has a how-to or a list of steps to follow when
migrating OTRS from Windows to Linux.  I've tried once unsuccessfully.  I've
currently got a working OTRS 2.2.6 system running on windows.  It was
installed with the win32 installer available on www.otrs.org.  My target
system is Ubuntu 8.04.   I'm no linux expert but I can figure out enough to
get myself in trouble.

On my first attempt, I installed mysql-server, mysql-client, and
otrs2_2.0.4p01-18_all.deb.  Then I copied all the var/articles over, copied
the entire contents of the mysql/data folders (yes this is probably a bad
idea, but since the machine is dedicated to otrs I didn't see any need to
preserve anything), and the kernel/config.pm and kernel/config folder.  Then
I manually edited config.pm to change the "c:\" paths to /usr/share/otrs.
After restarting mysql, I was able to access the otrs database with the otrs
account and password without a problem, but I started getting file-system
permission errors trying to access /var/lib/otrs/article when i fired up
otrs... this is where I started getting confused, because the application
runs in apache2 as www-data but the files and directories are all owned by
otrs:www-data.. it seemed to me that it ought to be running with suexec as
otrs, but that was beyond the scope of my understanding.  Instead I tried
granting www-data write permission to the var/articles directories.  That
got around the permission problem, and I'm able to reach the otrs logon page
but it wont accept my credentials.

I think I just totally borked this entire setup so I think I need to start
fresh with some step by step documentation.  If anyone can provide some
assistance or some step by step instructions I would greatly appreciate it!

Thanks
_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support or consulting for your OTRS system?
=> http://www.otrs.com/

Reply via email to