Can't use string ("DashboardMyLastChangedTickets") as a HASH ref while "strict refs"

[lg037808]

Hi,

in otrs 6.0.24, 6.0.25 and 6.0.26 I get the error messages:

[Sun Mar 22 12:18:04.531357 2020] [:error] [pid 21538:tid 139876983072512] Can't use string ("DashboardMyLastChangedTickets") as a HASH ref while "strict refs" in use at /opt/otrs/Kernel/Modules/AdminPackageManager.pm line 1678.\n
[Sun Mar 22 12:43:21.973206 2020] [:error] [pid 21539:tid 139876999857920] Can't use string ("DashboardMyLastChangedTickets") as a HASH ref while "strict refs" in use at /opt/otrs/Kernel/System/SupportDataCollector/Plugin/OTRS/PackageDeployment.pm line 41.\n
[Sun Mar 22 12:43:41.774435 2020] [:error] [pid 21539:tid 139876999857920] Can't use string ("DashboardMyLastChangedTickets") as a HASH ref while "strict refs" in use at /opt/otrs/Kernel/System/SysConfig.pm line 4490.\n
[Sun Mar 22 12:44:19.182111 2020] [:error] [pid 21539:tid 139876999857920] Can't use string ("DashboardMyLastChangedTickets") as a HASH ref while "strict refs" in use at /opt/otrs/Kernel/System/SysConfig.pm line 4490.\n
[Sun Mar 22 12:44:21.984917 2020] [:error] [pid 21539:tid 139876999857920] Can't use string ("DashboardMyLastChangedTickets") as a HASH ref while "strict refs" in use at /opt/otrs/Kernel/System/SysConfig.pm line 4490.\n
[Sun Mar 22 12:44:28.648791 2020] [:error] [pid 21539:tid 139876999857920] Can't use string ("DashboardMyLastChangedTickets") as a HASH ref while "strict refs" in use at /opt/otrs/Kernel/Modules/AdminPackageManager.pm line 1678.\n

The result of these error messages is that I cannot access most of the admin-tools in web-UI.

Thanks for help!

[wurzel]

Hi,

what did you do before these errors appeared?
Seems you have a "DashboardMyLastChangedTickets" configured wrongly?

Flo

[lg037808]

I just migrated the OTRS to a new server. Doing this I migrated from PostgreSQL to mysql using the otrsCloneDB.

How can I overcome this problem?

[wurzel]

Hi,

Check restoring of DashboardMyLastChangedTickets.xml

show your steps you did

Flo

[lg037808]

Hi,

thanks for your answer.

Here is what I did:

1. installed otrsCloneDB on the old server (otrs 6.0.24)
2. stopped otrs.Daemon
3. Clone DB
4. downloaded and installed new otrs 6.0.26 on the new server
5. copied Kernel/Config.pm from the old server
6. configured the new DB in Kernel/Config.pm on the new server
7. started otrs.Daemon on the new server

Btw. I also tried 6.0.24 (instead of 6.0.26) on the new server: same result

[root]

Hi,

Did you ever run scripts/DBUpdate-to-6.pl ion the new server?

- Roy

[lg037808]

Hi,

yes, I run the script but it terminates with the same error reported in this ticket.

But the question is: If I use the same arts-version on the old and the new server and just migrate from postgresql to mysql, is it really required to run the DB-update?

[root]

Hi,

The script deploy's a ACLs, processes, etc. Did you reinstalled all packages?

- Roy

[wurzel]

Hi,

did you restore all your custom files? I assume that there is more than the Config.pm to restore.
You must follow all steps in https://doc.otrs.com/doc/manual/admin/6 ... ating.html

Flo

[lg037808]

Hi Flo,

yes, I followed the instructions of the manual you posted. But the first error of the type mentioned in the heading occurred when I run the DBupdate script.

As I do not have root-access on the server it is not possible to run otrs.SetPermissions.pl. I just commented out the check for the root-user. This allows me to execute the otrs.SetPermissions.pl without errors.

Gerald

[lg037808]

Hi,

it seems to be a problem with the DB. I installed a clean otrs-system on another server. I worked without any problems. Then I exported the DB from the corrupt system and imported it into the new system, did the bin/otrs.Console.pl Admin::Package::UpgradeAll and started the fresh installed system. Then I got the same errors on the system which was working before.

• Is it possible that the problems come from the migration from Postgres to mysql (I used otrs.CloneDB to do the migration)?

• I get lots of error messages from Znuny4OTRS. Maybe the errors have something to do with Znuny4OTRS? (Howto deinstall Znuny4OTRS without UI?)

Thanks for your help

[root]

it seems to be a problem with the DB. I installed a clean otrs-system on another server. I worked without any problems. Then I exported the DB from the corrupt system and imported it into the new system, did the bin/otrs.Console.pl Admin::Package::UpgradeAll and started the fresh installed system. Then I got the same errors on the system which was working before.

• Is it possible that the problems come from the migration from Postgres to mysql (I used otrs.CloneDB to do the migration)?

• I get lots of error messages from Znuny4OTRS. Maybe the errors have something to do with Znuny4OTRS? (Howto deinstall Znuny4OTRS without UI?)

Hi,

Never had this after running CloneDB. The error from Znuny4OTRS-Repo (I guess it's the repo) typically came when running UpgradeAll. When the package is not installed - what is not is after moving the database from server a to b - the files are missing in the file system. Did you run Admin::Packacke::ReinstallAll? Please post the exact error you get.

- Roy

[lg037808]

Hi,

at least I found that the problem was caused by plugin DashboardMyLastChangedTickets. It changed the default dashboard and therefor OTRS was not able to start correctly. It was not possible to reinstall this plugin with Admin::Packacke::ReinstallAll.

I had to install and then uninstall all plugins installed in previous version of otrs from the opm on the command line. Then I was able to access the UI. After that I could uninstall the DashboardMyLastChangedTickets plugin. Now OTRS is up and running again.

Thanks to everybody for the support!

[wurzel]

Hi,

at least I found that the problem was caused by plugin DashboardMyLastChangedTickets.

ah really?

that was my first idea in the beginning.

Flo