[SOLVED] Can't load Package Manager after upgrade

[ianatschool]

I just upgraded from 3.1.18 to 3.2.16. Ran the database migration and rebuildconfig files. After a problem with the sessions being invalid and not allowing logon (which was solved by dropping the session table and recreating) I have a problem with the package manager.

After every upgrade I go to package manager and reinstall any packages that say they aren't installed properly.

If I try to access package manager it tries for about 10 minutes then times out with a gateway time-out message. There are lots of errors in the log regarding packages with their deploy check failing with no such file.

Code: Select all

[Mon Jul 28 08:43:01 2014][Error][Kernel::System::Package::DeployCheck][1306] FAQ-2.1.4: No such file: D:/PROGRA~1/OTRS/OTRS/bin/FAQImport.pl!

I assume these errors are because the package needs reinstalling but I can't if I can't load package manager.

PLEASE HELP!!!!

[jojo]

... then times out with a gateway time-out message.

Fix this issue

[ianatschool]

Not sure that helps me a great deal!! The timeout comes after quite a while of trying to load the package manager yet everything else seems fine.

I have monitored our firewall to see if any outgoing traffic is being blocked which it isn't so it is an internal server problem. I would love to fix the issue but am not sure what to do!

[reneeb]

Try to run the Package manager on the commandline (bin/otrs.PackageManager.pl)...

[ianatschool]

I could run it from the command line and tried to reinstall from there. It said they were reinstalled but there were package files missing.

In the end I tried to then upgrade again to 3.3 and had other errors so have reverted back to 3.1.16 for now.

Would be good to find someone else who has upgraded windows version from 3.1 to 3.2!

[ianatschool]

I fixed this issue by running package manager from command line and uninstalling the packages I had installed. It then worked fine in the browser

[crythias]

also, package manager timeouts may be related to MySQL max size limits.