Skip to main content

Upgrade EA3 to EA4 Errors

Comments

7 comments

  • cPanelMichael
    • Blocker: A fatal error was encountered while getting information from the server's configured repositories: Error: File contains no section headers. file: file:///etc/yum.repos.d/xrdp.repo, line: 1 ' [xrdp]\n' : Executed /usr/bin/yum -v repolist
    • Blocker: A fatal error was encountered when trying to call "/usr/bin/yum -q list bash" : Illegal seek ( )

    Hello Caleb, It looks like your system's package manager (YUM) is unable to update. YUM is required to be in working order to allow the EasyApache 4 conversion to succeed. The error message suggests one of your YUM repo files is corrupted or missing required information. Do you have any custom YUM repo files configured in the /etc/yum.repos.d/ directory? Do you notice any error messages when running the "yum clean all" and "yum repolist" commands? Thank you.
    0
  • Caleb Anderson
    root@s45-40-132-177 [~]# yum clean all Loaded plugins: fastestmirror Error: File contains no section headers. file: file:///etc/yum.repos.d/xrdp.repo, line: 1 ' [xrdp]\n' root@s45-40-132-177 [~]# root@s45-40-132-177 [~]# yum clean all Loaded plugins: fastestmirror Error: File contains no section headers. file: file:///etc/yum.repos.d/xrdp.repo, line: 1 ' [xrdp]\n' root@s45-40-132-177 [~]#
    0
  • cPanelMichael
    Hello Caleb, It looks like you are using custom YUM repo files that do not include the required information. This is generally something your hosting provider or system administrator should address if you are not comfortable managing YUM on your own. That said, feel free to open a
    0
  • Caleb Anderson
    I am the system administrator as this is a dedicated server with godaddy and not a shared server. i dont know much about how to fix the issue. is there anything or any steps that you could walk me through to fix this issue.
    0
  • cPanelMichael
    Hello Caleb, Can you open a
    0
  • Caleb Anderson
    9978507
    0
  • cPanelMichael
    Hello, To update, this was solved by repairing a typo in the /etc/yum.repos.d/xrdp.repo file associated with the third-party YUM repo. Thank you.
    0

Please sign in to leave a comment.