OTRS ERROR - Getting sometimes

[otrslanka]

Software error:

Attempt to reload /opt/otrs/Kernel/Config/Files/ZZZAAuto.pm aborted.
Compilation failed in require at /opt/otrs//Kernel/Config/Defaults.pm line 2129.

For help, please send mail to the webmaster, giving this error message and the time and date of the error.

Im getting an Error message like this. All functionalities are works fine. Customrs can be dissapointed due to this. How to fix this issue?

[otrslanka]

I didn't had any modifications in the mentioned file. OTRS version is 3.0.11

[banzayats]

Software error:

Attempt to reload /opt/otrs/Kernel/Config/Files/ZZZAAuto.pm aborted.
Compilation failed in require at /opt/otrs//Kernel/Config/Defaults.pm line 2129.

For help, please send mail to the webmaster, giving this error message and the time and date of the error.

Im getting an Error message like this. All functionalities are works fine. Customrs can be dissapointed due to this. How to fix this issue?

Same here viewtopic.php?f=81&t=7394&p=56416&hilit ... 129#p56416

[CSL]

I've had this issue twice on our production server after applying changes that worked fine on our test system. We're running 3.0.11 as well. Both times it was caused by editing the contents of /opt/otrs/Kernel/Config/Files/ACL.pm (manually via text editor), or /opt/otrs/Kernel/Config/Files/ZZZAuto.pm (through the sysconfig interface). I've had two different forms of the error message, one specifying ZZZAuto.pm as the file that failed to reload, and another specifying ZZZAAuto.pm.

It was disruptive to end-users, with roughly 40-50% of mouse clicks on any part of the OTRS interface resulting in a blank 'Software error' page displaying the error message on it.

As far as I can tell, this is caused by one of the perl modules located in /opt/otrs/Kernel/Config/Files/ failing to load correctly. The function at the line given in the error (2129) is attempting to apply 'require' to each of the files in that directory in order to load them, and (i think) is claiming that it has failed to compile one of them. I ran perl -c on all files in that directory both times and all of them checked out as correct apart from ACL.pm, but this is expected as it is an extension of Config.pm and doesn't stand on its own.

I still don't know the root cause of the error. In both instances I rolled back the changes I'd made, which fixed the issue and returned the system to normal. I then re-did the changes, one at a time, in (what I believe) is the exact same way as before, and on both occasions this then worked without any issues. Without being able to provide an explanation, I'd recommend rolling back the changes you think have caused this, making sure the error stops, and then re-doing those changes one at a time (testing thoroughout by clicking through different parts of the interface and watching your web-server error logfile to make sure it hasn't appeared again).

This is something that I'm hoping will disappear after the upgrade to 3.1 - I hope this helps in some way even though it's not a great answer.