Install error on CentOS5
Hi, I did an install of otrs from RPM on a CentOS 5 box and it worked fine. I've just come to do another one and... it doesn't work fine! The install script completes, but when I login (with root@localhost/root) I get this output: Software error: junk ' Possible SubGroups - Core - Core::LinkObject - Core::Log - Core::PostMaster - Core::MIME-Viewer - Core::Package - Core::PDF - Core::Sendmail - Core::Session - Core::SpellChecker - Core::Time - Core::Web - Core::PostMaster - Core::Stats - Core::Stats::Graph - Crypt::PGP - Crypt::SMIME - Frontend::Agent - Frontend::Admin::ModuleRegistration - Frontend::Agent::ModuleRegistration - Frontend::Agent::ModuleNotify - Frontend::Agent::NavBarModule - Frontend::Agent::Preferences - Frontend::Agent::Stats - Frontend::Customer - Frontend::Customer::Auth - Frontend::Customer::ModuleNotify - Frontend::Customer::ModuleRegistration - Frontend::Customer::Preferences - Frontend::Public - Frontend::Public::ModuleRegistration String ' before XML element For help, please send mail to the webmaster (root@localhost), giving this error message and the time and date of the error. Any idea what's causing this? Thanks, R.
Robin Bowes wrote:
Hi,
I did an install of otrs from RPM on a CentOS 5 box and it worked fine.
I've just come to do another one and... it doesn't work fine!
The install script completes, but when I login (with root@localhost/root) I get this output:
Software error:
junk ' Possible SubGroups - Core
[snip]
String ' before XML element
For help, please send mail to the webmaster (root@localhost), giving this error message and the time and date of the error.
OK, I think I found the problem. On my original install, I used the default charset. On the second install, I used utf-8. It works with the default charset, but not with utf-8. Anyone know if later builds have fixed this? R.
Robin Bowes wrote:
On my original install, I used the default charset. On the second install, I used utf-8. It works with the default charset, but not with utf-8.
Anyone know if later builds have fixed this?
Once again, replying to my own posts... I rebuilt the otrs RPM (using the epel spec file) for 2.3.0beta4 and resolved the dependency issues (had to use cpan2rpm for Net::POP3::SSLWrapper and rpmforge for some other deps) and it seems that utf-8 works OK in 2.3.0beta4. R.
participants (1)
-
Robin Bowes