
These are just some random thoughts here. Sorry if confusing. Jim Wight wrote:
ago became the test system, so, yes, it has fewer tickets. The main thing we changed was the ticket number format. The Config.pm settings that are different are:
I would change all of these things back, to exactly match production as much as possible. (unless you can make suggested disk image below)
The last one is because the test system has additional queues that I subsequently experimented with.
Try making these extra queues 'invalid'.
I upgrade by: <list of changes I made>
If I were really at wit's end, I would take a copy of my system with all the data, and return everything back to default. Then start implementing the x number of site specific modifications to see which one is breaking the function in question. (suggestion: try returning the .dtl files back to normal first, then customer authentication)
It appeared as soon as I logged in after upgrading the production system to 1.2.3 (from 1.1.1).
Question: So you took your test system manually through each step: 1.1.1 --> 1.2.1 1.2.1 --> 1.2.2 1.2.2 --> 1.2.3 You then rounded up all the changes to your test system and laid them down into your production system thus taking it: 1.1.1 --> 1.2.3 directly, bypassing the in-between steps? (just trying to see if I got that right).
I upgraded the production system by copying the modified 1.2.3 tree from the test machine, modifying the settings in Config.pm listed above and running DBUpdate-to-1.2. NB I have moved TicketCounter.log out of the tree so that I have one fewer thing to change; its location - the same on both systems - is defined in Config.pm ($Self->{CounterLog}).
If it were me, I'd make a complete image of your production machine (symantec ghost works for me), copy it onto a new machine and follow the exact upgrade steps that you did on the production system, trying to reduce the number of new changes (other than those mandated obviously by the upgrade itself).
So far, by adding print diagnostics to Kernel/Modules/AgentQueueView.pm, I see the creation of HTML suddenly stopping mid-ticket in this loop at line 190.
# -- # show ticket's # -- foreach (@ViewableTickets) { print $Self->ShowTicket(TicketID => $_); }
but so far I haven't a clue what set of circumstances is giving rise to it.
Not quite sure what this is. Developers?
I'm not using mod_perl.
What version of mod_perl? ********************************* Jake Covert Infrastructure Analyst Electronic Data Systems PSIC Support Group (586) 986-9698 Work (586) 518-3859 Pager http://www.eds.com *********************************