Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Not Answered
  • Replies replies
    5
  • Subscribers subscribers
    25
  • Views views
    192
  • Users 0 members are here
Related
Options

OES 24.3 crash during yast online_update

PascalS

Hi Community,

never had such behavior.

doing a yast online_update on a OES 24.2, crash with an unexpected error. exiting with a "/usr/bin/rm: No such file or directory"

forcing a reboot =>

any advice are welcome

Everyone is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid. [A. Einstein]

Tags:

  • 0  

    Scary. Looks like something has wiped your root partition. Have you tried booting a rescue system to check what's still there?

  • 0 in reply to   

    Yep, this is frightening,

    /usr/bin empty and /sbin, too !

    Fortunately this production server, was not used anymore,

    Still, trying to reanimate the beast, without success ...

    I think I will have to re-install

    Everyone is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid. [A. Einstein]

  • 0 in reply to 

    We restore the VM (I didn't make a snapshot before, as I was to confident in YaST).

    I've been able to reproduce the "crash", this is the latest line before YaST hangs.

    YaSt error is following : "Subprocess failed. Error: RPM failed: Command exited with status 129."

    Why is it removing "glibc" ?

    Everyone is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid. [A. Einstein]

  • 0 in reply to 

    The same thing happened to me. Using a parallel SLES system it shows me that there was no root-directory anymore. There must be a problem with the glibc update process. Normally there is a Delta-rpm at the update of glibc. Updating to OES 24.3 this glibc version doesn't have any Delta-Rpm. This crashes the whole system from within because there is no c-interpreter at the system which is needed for almost every process including kernel activity.

  • 0   in reply to 

    That sounds unusual! We haven’t encountered this issue in our testing and might need more information to troubleshoot it. Could you please create a ticket for us?

    I believe you haven’t added any third-party repositories to the OES server.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.