Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: [Fri Nov 09 12:24:58.173550 2018] [perl:error] [pid 16308:tid 140327243474688] [client 2001:1a68:a::35:16272] Error while loading /usr/sbin/rt-server: Errno architecture (x86_64-linux-thread-multi-4.18.10-200.fc28.x86_64) does not match executable architecture (x86_64-linux-thread-multi-4.17.3-200.fc28.x86_64) at /usr/lib64/perl5/Errno.pm line 12.\nCompilation failed in require at /usr/share/perl5/vendor_perl/File/Temp.pm line 526.\nBEGIN failed--compilation aborted at /usr/share/perl5/vendor_perl/File/Temp.pm line 526.\nCompilation failed in require at /usr/share/perl5/vendor_perl/MIME/Tools.pm line 14.\nBEGIN failed--compilation aborted at /usr/share/perl5/vendor_perl/MIME/Tools.pm line 14.\nCompilation failed in require at /usr/share/perl5/vendor_perl/MIME/Entity.pm line 243.\nBEGIN failed--compilation aborted at /usr/share/perl5/vendor_perl/MIME/Entity.pm line 243.\nCompilation failed in require at /usr/share/perl5/vendor_perl/RT/I18N.pm line 66.\nBEGIN failed--compilation aborted at /usr/share/perl5/vendor_perl/RT/I18N.pm line 66.\nCompilation failed in require at /usr/share/perl5/vendor_perl/RT.pm line 166.\n Expected results: Additional info: After upgrade to rt-4.4.3-1 from fedora fc29, rt works correctly without any error.
This has nothing to do with rt. This is cause by Errno Perl module that checks it has been built against the same kernel version as perl interpreter because they use the same errno constants. It looks like you updated only perl-libs without updating perl-Errno. Could you check it? What are your exact perl-libs and perl-Errno releases? However, RPM dependencies between these two package should prevent from happening that (since Fedora 25). See bug #1393421. Didn't you force installing packages not to obey the dependencies?
Hello It seems that i have all updates perls modules [root@mask ~]# rpm -q perl perl-5.26.2-414.fc28.x86_64 [root@mask ~]# rpm -q perl-Errno perl-Errno-1.28-414.fc28.x86_64
Does Errno itself work for you? Use "perl -e 'use Errno'" to test it. If it exits without any error message, it works. Otherwise it should report similar error as rt in your bug report. Do you still get the error message from rt, or does rt works for you now?
[root@mask ~]# perl -e 'use Errno' [root@mask ~]# I had problem only with RT from FC28. I have recompiled RT SRPM from FC29 and its works - that's why I reported bug about RT.
I cannot see how the bug could be caused by rt, but since it seems perl is fine, I moving it back to rt for further investigation.
(In reply to Łukasz Trąbiński from comment #4) Do you have a reproducer? I can't reproduce this issue with rt-4.4.2 on F28 nor does its testsuite trigger it.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.