Page 2 of 2 FirstFirst 12
Results 11 to 18 of 18

Thread: Is there some stability problem with Leap x.x?

  1. #11
    Join Date
    Nov 2020
    Location
    Bremerton WA
    Posts
    7

    Default Re: Is there some stability problem with Leap x.x?

    Quote Originally Posted by dcurtisfra View Post
    If you mean that, it's a MSI Wind Netbook, they were announced at the 2008 CeBit – 12 years ago – 1 GB or 2 GB of RAM and 80 GB to 250 GB disks …
    I could have sworn it was much older than that but I looked & the oldest files I can find are from 2008 so you must be correct. I've never done an exhaustive check but I regard MSI as a top brand. That machine has been running continuously since I got it. I put a 1T drive in it when I got it.
    (snip)
    That message means that, the system has entered the systemd Rescue mode – you'll need to enter the root user's password and check the systemd Journal for the reason the system didn't boot correctly …
    How do I do that......"check the systemd Journal"? Is it a regular log file? Where & what name. I can find it if I know where and what to look for. I know I should have done this long ago. But usually I can tell what the problem is by what the machine does....so I've never gotten deeply into log files.
    Given the amount of RAM available – Leap 15.2 needs at least 1 GB of RAM – better 2 GB of RAM – you'll have to be careful about the system you install on the box.
    • My suggestion is, because it's a file server, an installation role of “Server” – no GUI …

    Disk space – plus encryption – may I suggest that, the default Leap Btrfs file system should be avoided – stick to ext4 for the system and user partitions – I suspect that, XFS for the user partition will stretch the system's resources.

    Pay careful attention to the amount of disk being used for the /tmp/ and /var/ directories – if they run out of space, the system will become unstable …
    All my machines are 4-16 gig memory. I have few drives smaller than 1T. Usually my root partitions are 100 Gig or larger. And, yes, as soon as I started having these crashes I stopped testing Btrfs & XFS. Everything I have is ext4. And I generally don't let my disks get more than 75% full. I usually keep 20-30+ gig empty.
    From the openSUSE installation medium, run the Firmware and Memory tests …
    Yes. I do if I suspect any problem.

  2. #12
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    3,671

    Default Re: Is there some stability problem with Leap x.x?

    Quote Originally Posted by tgdf3141tgdf View Post
    How do I do that......"check the systemd Journal"? Is it a regular log file? Where & what name.
    The systemd Journal is inspected by “journalctl” – “journalctl --this-boot” for the system Journal of the current boot – “journalctl --list-boots” to list the system boots in the current Journal …
    • systemd maintains it's Journals in a sub-directory of ‘/var/log/journal/’ – they're binary files and can only usefully be inspected by means of “journalctl” …
    • If a user invokes “journalctl” they can only inspect the Journal entries related to that user's sessions …
    • The Journal entries related to the system can only be inspected by the user “root” or, a member of one of the “systemd-journal”, “adm” and “wheel” user groups …

  3. #13
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    3,671

    Talking Re: Is there some stability problem with Leap x.x?

    @tgdf3141tgdf:

    Given that, you've not been penny-pinching with disk space, consider setting up with separate partitions for /tmp/ and /var/ …
    • I'm currently running with about 4 GiB for /tmp/ and, 20 GiB for /var/ …
    • But, 1st check the systemd Journal for the reason why the system boot landed in the Rescue mode …

  4. #14
    Join Date
    Nov 2020
    Location
    Bremerton WA
    Posts
    7

    Default Re: Is there some stability problem with Leap x.x?

    Quote Originally Posted by dcurtisfra View Post
    The systemd Journal is inspected by “journalctl”
    Thanks. I checked that. It took about 2.5 sec to see, "Please fix the "kio_sftp" KIO slave" which was meaningless to me. It took another 2.5 sec to find

    "This is a known issue with Dolphin and ECDSA keys. OpenSSH in recent versions have moved to use ECDSA by default over RSA, and this works fine with most implementations that rely on OpenSSH's "known hosts" file."

    WHAT????!!!!!!!!!!!!

    In my original posts, I'm writing that SuSE 11.x works fine out of the box but I have LAN troubles with Leap 15.2, nobody thinks to mention that in 15.2 ssh doesn't work properly & a moderator tells me that my question is chit chat, not technical & specific enough?????!!!!!

    Personally I'd say that the current implementations of SuSE (I guess technically it's only KDE) are buggy as heck. THERE'S A KNOWN ISSUE WITH DOLPHIN.....THE OS FILE BROWSER!!!!!!!!!!!!! And this is just the tip of the iceberg I easily found in my first search!!!!!!!!!!

    But in the spirit of 'Count your blessings' I did get 2 good suggestions: journalctl & the tip about booting from an SSD.

    Let me return a tip: It can be better to cry than to laugh. What that means is, it's better to say, "There are bugs in the OS, here they are, & this is what to do about it." than to say, "Nothing's wrong." and have people have nothing but problems, get disgusted, & dump your product.

    I've suspected for quite some time now that there's been something wrong with ssh in Leap x.x but I had no confirmation & it seemed too big a task to begin researching.

    I see now I have no choice but to begin the task,no matter how onerous. But what this REALLY, REALLY, REALLY, REALLY confirms for me, is that when Microsoft bought into SuSE, it wasn't because they were hoping to better the OS, or give people a better option than Windows. They did it to make more money, enslave more people to their paid OS, & throw as many monkey wrenches as they could into the emerging Linux community.

    We may be getting new leadership in the US. But rest assured: Greed is still alive & well in the business community.
    CP/M since 1980
    OS/360 since 1962

  5. #15
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,116
    Blog Entries
    2

    Default Re: Is there some stability problem with Leap x.x?

    From the description of your problems, I'd have suspected your primary suspect is your disk drive although you say it isn't...
    Still, if you've been using your machine daily, I'd recommend it's still suspect if it's over 5 years old (and keep in mind that most consumer grade drives aren't sold with factory warranties over 3 years).
    If drives aren't your problem, then the next thing to check is your memory. Particularly if your memory is the original installed in your system and depending on your environment, pull your RAM and clean the electrical contacts with a pencil eraser and re-install. As long as you have your machine open, you may want to clean the electrical contacts for your disk drive as well (if it's easy access).
    If you end up buying a new drive, of course consider an SSD, even if your Winbook fails you can transfer the drive to another machine either internally or as an external drive.

    Next thing I'd suggest is to consider if you really need to encrypt your drives.
    Some people misunderstand what kind of threats drive encryption protects you from... It won't protect you from malware, viruses and other threats when your machine is running, it only protects you when the machine is powered off and your machine is stolen.
    If you need that kind of protection, so be it but don't encrypt if you don't need that kind of protection.
    Encrypting is just another layer where the Peter Principle can bite you... Extra exposure to potential problems.

    Now,
    As for your problems specifically with newer OS nowadays...
    You should know that unlike the older OS you remember ran well, today's OS is a lot less likely to cause problems than yesteryear.
    Whereas in the old days there was a lot of reading and writing to disk, nowadays there is reading and not much writing... most of that writing to disk is now written to RAM.
    And, that is perhaps a good reason to not run KDE Plasma if you have only 4GB of RAM, which might be enough but if you're a relatively heavy User probably isn't anymore and you may be writing to swap.

    If you like KDE Plasma, consider installing LXQt as an alternate Desktop.
    LXQt uses the same Qt framework most KDE Plasma apps use, so from within LXQt you'll be able to keep using the same KDE apps.
    The difference is that all those automated tasks running in the background in KDE won't in LXQt, and you'll also find fewer graphical effects by default, the net effect is that you'll be able to do the same work you did before without many changes but as though you have a couple extra gigabytes of RAM in your machine.

    Your Winbook has given you good service for many years, but it may be getting a bit tired...
    Modify what is running on it, and you'll help it give you several more years to come.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  6. #16
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    3,671

    Question Re: Is there some stability problem with Leap x.x?

    Quote Originally Posted by tgdf3141tgdf View Post
    Thanks. I checked that. It took about 2.5 sec to see, "Please fix the "kio_sftp" KIO slave" which was meaningless to me. It took another 2.5 sec to find

    "This is a known issue with Dolphin and ECDSA keys. OpenSSH in recent versions have moved to use ECDSA by default over RSA, and this works fine with most implementations that rely on OpenSSH's "known hosts" file."
    Yes, but – please take note of the timestamps on the Ubuntu forum and, the timestamps on the KDE Bug Report …
    • Timestamps related to the year 2015 and the year 2011 means that, the information is more than a little bit dated …

    A further but, there's a couple of CLI command executions mentioned in the Ubuntu forum entry:
    Code:
    ssh-keygen -f "$HOME/.ssh/known_hosts" -R server
    ssh -o HostKeyAlgorithms=ssh-rsa user@server
    In other words, for the affected users, the SSH keys have to be regenerated …

    What happens for the case of a fresh, newly created, new user?
    • For a new, fresh, user, does Dolphin behave correctly for the case of a newly setup connection via SSH to the wanted target?

  7. #17
    Join Date
    Dec 2020
    Location
    Germany
    Posts
    26

    Default Re: Is there some stability problem with Leap x.x?

    i alwas have some sort of bletooth problem with any of the openSUSE versions but no issue in stability

  8. #18
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    27,689

    Default Re: Is there some stability problem with Leap x.x?

    Quote Originally Posted by lag145 View Post
    i alwas have some sort of bletooth problem with any of the openSUSE versions but no issue in stability
    When you have a bluetooth problem, then please start a thread about it with technical relevant information. Just putting such a vague complaint here at the end of another discussion (that more or less finished already more then a month ago) will not really work.
    Henk van Velden

Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •