Znuny Open Source Ticketsystem

The process completes on the DB server. The application server seems to get tired of waiting for a response though, so not sure what exactly is going on.

**UPDATE** I was able to get our test machine upgraded by commenting out steps 1 through 5 in the DBUpgrade-to-3.1.pl script after it times out. Then I had to comment out lines 6 through 8 after the script timed out again (after step 8 ). Then the script would finish. I don't think anything was corr...

I have tracked down what I believe is the issue – the Stats module works fine, it just takes too long to collect the info from the database server so the connection is lost. We have a large number of Customer IDs, and once I set the Framework::Frontend::Agent::Stats::CustomerIDAsMultiSelect to “No”,...

Since the error referred in part to ITSM, it was suggested I uninstall and then reinstall the ITSM module. I did this and now the NEW and ADD links will spin for about 8 – 11 minutes before I get a connection reset error. Before uninstalling and reinstalling the ITSM Module I could at least get into...

***UPDATE*** I have updated our box to v3.2.2 – no luck fixing the issue. I did find the following in the logs for web when I attempted to open the NEW statistics screen: [Tue Feb 26 16:30:26 2013] -e: Use of uninitialized value in sprintf at /opt/otrs//Kernel/System/Stats/Dynamic/ITSMChangeManageme...

I am upgrading our test box to v3.2.1 - I have everything upgraded, but found an issue when trying to add a new report. This happens with either the ADD button on the overview page or when selecting NEW on the drop down. The page either takes a long time (as in 2 minutes or so) to load, times out an...

Solved my own problem. I just needed to add the Dynamic Field Key in the dtl:block statement.

<!-- dtl:block:DynamicField_FieldKey -->
other info
<!-- dtl:block:DynamicField_FieldKey -->

Should have known it would be that easy.

Scott

Just to clarify - this is not for "groups" as OTRS sees them. We currently have agents that are in three different departments that each have a dropdown box that only they need to see when creating a new ticket. In the view screens (zoom, overview medium, and preview) they are the only one...

Currently we have OTRS 2.4.7 in production. There are three groups of agents that have unique Free Text Fields (dropdown lists) that are only visible to agents in the group associated with the dropdown. This is done by adding the information into a Theme set up for each of the three groups. This way...

I disable the three dynamic fields that were converted from free text fields during our upgrade. The error is gone, so it looks like bad data was the culprit.

Thanks to everyone for the help. I really appreciate it.

Scott

I found 2 Generic Agent jobs set to run automatically. I changed them fro valid to invalid. Nothing is showing in the logs as far as Generic Agents now, but I still get a YAML error. Here is the new error: Feb 7 14:06:11 test-ticket OTRS-CGI-90[1007]: [Error][Kernel::System::YAML::Load][Line:130]: L...

I'm not really sure what is causing the error. I am posting a more specific error message received in e-mail - hopefully this will help: ERROR: OTRS-otrs.GenericAgent.pl-90 Perl: 5.8.8 OS: linux Time: Thu Feb 7 07:40:03 2013 Message: Loading the YAML string failed: YAML::XS::Load Error: The problem:...

I am getting the following error in our system log about once per hour: OTRS-otrs.GenericAgent.pl-90[25744]: [Error][Kernel::System::YAML::Load][Line:130]: Loading the YAML string failed: YAML::XS::Load Error: The problem: block sequence entries are not allowed in this context was found at document:...

I am attempting to run the DBUpgrade-to-3.1.pl script and get as far as step 5. After it finishes going through our rather large database (100000+) everything after step 5 fails. I saw another post where someone had the same error as me, and they mentioned increasing their mysql timeout. Anyone know...