Znuny Open Source Ticketsystem

Using the same Config.pm I installed OTRS 4, and it doesn't seem to have this problem. I would be happy to submit my Config.pm (sans sensitive data) if that would help make OTRS 5 more stable.

I reinstalled from scratch with a new database, so I'm not sure what's going on. The only thing that stayed the same is the Config.pm file. It was a pain to get that configured, so I really didn't want to start that over.

The previous post was a red herring. I had a couple groups synching that didn't exist in this new database. I think I'm just going to abandon 5 and go back to 4. OTRS 5 just seems to flakey. At least 4 seemed to work fine.

I installed a new instance and the same thing is happening. I did find an error in my apache logs. [Mon Dec 7 12:09:25 2015] -e: DBD::mysql::db do failed: Cannot add or update a child row: a for eign key constraint fails (`otrs2`.`group_user`, CONSTRAINT `FK_group_user_group_id_id` FOREIGN KEY (`gro...

I renamed the old otrs directory and copied a fresh install with the old Config.pm, and I'm still having this issue. The stats window is sometimes blank too. Maybe my Config.pm is causing a problem, because that is the only thing left from the original aside from the database?

OTRS is installed on a CentOS7 server running Apache and MariaDB. I just did a yum install from the ftp site. I have been experimenting with Package Manager in the Admin page a bit. I've uninstalled almost all of the packages I've tried so far. I'm starting to lean towards just reinstalling OTRS. I'...

I'm having a problem with an installation of OTRS 5.0.4 that I'm hoping someone can help me with. My organization is evaluating ticketing systems, so I'm hoping to get this resolved, because OTRS seems like the best candidate. There is weird random behavior that I'm having problems troubleshooting. ...