Skip to main content

Security Advisor Notification

Comments

69 comments

  • RevivalTech

    Getting the error too.

    Running manually gives me this though:

    # /usr/bin/needs-restarting
    This system is receiving updates from CloudLinux Network server.
    Failed to read PID 2036106's smaps.
    Failed to read PID 2037216's smaps.

    0
  • RevivalTech

    Getting issue too just to note.

    1
  • Gerald Watkins

    Ridiculous

    0
  • cPRex Jurassic Moderator

    Just to confirm, the last case I mentioned, RE-922, has been resolved in all versions of 126.  If you're still seeing an issue we'll likely need to see a new ticket as there are no active cases related to this area.

    0
  • V3NTUS

    I often get the same error reported in this thread, and it's been months already.

    "Maintenance ended; however, it did not exit cleanly (256). The following events were logged: “scripts/find_outdated_services”. Review the update logs to determine why the update failed."

    Upon running # /usr/bin/needs-restarting -s

    I get lines like:

    Failed to read PID 112231's smaps.
    Failed to read PID 112724's smaps.
    Failed to read PID 112726's smaps.
    Failed to read PID 112727's smaps.
    Failed to read PID 112760's smaps.
    Failed to read PID 112768's smaps.
    Failed to read PID 112777's smaps.
    Failed to read PID 112778's smaps.
    Failed to read PID 112810's smaps.

    Are you sure this case has been resolved??

    0
  • cPRex Jurassic Moderator

    V3NTUS - the original issue was resolved, but it doesn't mean it couldn't have returned in a different way, or that something else is happening.  Could you submit a ticket so this could be examined directly on your system?

    0
  • frenziedfox

    I have started getting it via 'New Security Advisor' email this morning as well on AlmaLinux v9.6.0:


    "Failed to check whether running executables are up-to-date: The system received unexpected output from “/usr/bin/needs-restarting”: Waiting for process with pid 1079551 to finish."

    1079551 (or whatever the PID is) never stays long enough to find out what it is!

    ---
    [root@srv02 ~]# /usr/bin/needs-restarting -s
    Failed to read PID 106782's smaps.
    Failed to read PID 106783's smaps.
    Failed to read PID 106784's smaps.
    ---

    0
  • cPRex Jurassic Moderator

    frenziedfox - can you submit a ticket so we can determine if this is the same issue as RE-922, or if something else is happening here?

    0
  • frenziedfox

    Hi cPRex,

    I have the domain hosts now dealing with this server.

    Let me know if there are problems.

    Alex

    0

Please sign in to leave a comment.