Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: haveged

  1. #1
    Join Date
    May 2015
    Location
    Michigan/Florida
    Posts
    65

    Default haveged

    Just did the zypper dup for tumbleweed 20181110 and made a check with zypper ps -s after a reboot and came up with this.

    How can you restart a deleted processes? Should haveged be reinstalled?



    Code:
    zypper ps -s
    The following running processes use deleted files:
    
    PID | PPID | UID | User | Command           | Service
    ----+------+-----+------+-------------------+--------
    387 | 1    | 0   | root | haveged (deleted) | haveged
    
    You may wish to restart these processes.

  2. #2
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    17,079

    Default Re: haveged

    On Mon, 12 Nov 2018 19:46:03 +0000, GDixon wrote:

    > Just did the zypper dup for tumbleweed 20181110 and made a check with
    > zypper ps -s after a reboot and came up with this.
    >
    > How can you restart a deleted processes? Should haveged be reinstalled?
    >
    >
    >
    >
    > Code:
    > --------------------
    > zypper ps -s
    > The following running processes use deleted files:
    >
    > PID | PPID | UID | User | Command | Service
    > ----+------+-----+------+-------------------+--------
    > 387 | 1 | 0 | root | haveged (deleted) | haveged
    >
    > You may wish to restart these processes.
    > --------------------


    For this service, you can just run:

    sudo systemctl restart haveged

    No need to reinstall the service - Linux keeps the existing process
    running (and doesn't free up the file inodes) until the service restarts.

    There are a few services that may continue to hold files open after a
    restart that zypper ps -s will incorrectly report. I see that on one of
    my Leap systems on occasion - nothing really to worry about.

    Jim




    --
    Jim Henderson
    openSUSE Forums Administrator
    Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

  3. #3
    Join Date
    May 2015
    Location
    Michigan/Florida
    Posts
    65

    Default Re: haveged

    Thank you,

    That did solve the situation.

    Edit:
    I spoke too soon. It does start the service but on either a reboot or shutdown the service isn't started and needs to be started again.
    Where can I make this change to start haveged permanent?

    Greg

  4. #4
    Join Date
    May 2015
    Location
    Michigan/Florida
    Posts
    65

    Default Re: haveged

    I did check services manager and haveged is checked to start on boot.

  5. #5
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,499
    Blog Entries
    2

    Default Re: haveged

    When your service is stopped,
    Run the following and post the results
    Code:
    systemctl status havegod
    Your result should include among possible other things
    - Current status of your service
    - Whether it ever started
    - If it started, that it definitely exited
    - A system log snippet that might relate to the start and stop.

    HTH,
    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. #6
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    1,131

    Default Re: haveged

    Quote Originally Posted by tsu2 View Post
    When your service is stopped,
    Run the following and post the results
    Code:
    systemctl status havegod
    Your result should include among possible other things
    - Current status of your service
    - Whether it ever started
    - If it started, that it definitely exited
    - A system log snippet that might relate to the start and stop.

    HTH,
    TSU
    Some puzzling restarts occur:
    Code:
    erlangen:~ # journalctl -b -u haveged.service 
    -- Logs begin at Sun 2018-08-26 08:48:18 CEST, end at Tue 2018-11-13 06:50:10 CET. --
    Nov 12 19:19:32 erlangen haveged[214]: haveged: listening socket at 3
    Nov 12 19:19:33 erlangen haveged[214]: haveged: restart in new root: /sysroot
    Nov 12 19:19:33 erlangen haveged[214]: haveged: listening socket at 3
    Nov 12 19:19:33 erlangen haveged[214]: haveged: Fail:set_watermark()!
    Nov 12 19:19:33 erlangen haveged[214]: haveged starting up
    Nov 12 19:19:33 erlangen systemd[1]: haveged.service: Main process exited, code=exited, status=1/FAILURE
    Nov 12 19:19:33 erlangen systemd[1]: haveged.service: Failed with result 'exit-code'.
    Nov 12 19:19:33 erlangen systemd[1]: haveged.service: Service RestartSec=100ms expired, scheduling restart.
    Nov 12 19:19:33 erlangen systemd[1]: haveged.service: Scheduled restart job, restart counter is at 1.
    Nov 12 19:19:33 erlangen systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm.
    Nov 12 19:19:33 erlangen systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm.
    Nov 12 19:19:33 erlangen haveged[410]: haveged: listening socket at 3
    Nov 12 19:19:34 erlangen systemd[1]: haveged.service: Service RestartSec=100ms expired, scheduling restart.
    Nov 12 19:19:34 erlangen systemd[1]: haveged.service: Scheduled restart job, restart counter is at 2.
    Nov 12 19:19:34 erlangen systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm.
    Nov 12 19:19:34 erlangen systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm.
    Nov 12 19:19:34 erlangen haveged[567]: haveged: listening socket at 3
    erlangen:~ #
    Any idea?
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  7. #7
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,499
    Blog Entries
    2

    Default Re: haveged

    Quote Originally Posted by karlmistelberger View Post
    Some puzzling restarts occur:
    Code:
    erlangen:~ # journalctl -b -u haveged.service 
    -- Logs begin at Sun 2018-08-26 08:48:18 CEST, end at Tue 2018-11-13 06:50:10 CET. --
    Nov 12 19:19:32 erlangen haveged[214]: haveged: listening socket at 3
    Nov 12 19:19:33 erlangen haveged[214]: haveged: restart in new root: /sysroot
    Nov 12 19:19:33 erlangen haveged[214]: haveged: listening socket at 3
    Nov 12 19:19:33 erlangen haveged[214]: haveged: Fail:set_watermark()!
    Nov 12 19:19:33 erlangen haveged[214]: haveged starting up
    Nov 12 19:19:33 erlangen systemd[1]: haveged.service: Main process exited, code=exited, status=1/FAILURE
    Nov 12 19:19:33 erlangen systemd[1]: haveged.service: Failed with result 'exit-code'.
    Nov 12 19:19:33 erlangen systemd[1]: haveged.service: Service RestartSec=100ms expired, scheduling restart.
    Nov 12 19:19:33 erlangen systemd[1]: haveged.service: Scheduled restart job, restart counter is at 1.
    Nov 12 19:19:33 erlangen systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm.
    Nov 12 19:19:33 erlangen systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm.
    Nov 12 19:19:33 erlangen haveged[410]: haveged: listening socket at 3
    Nov 12 19:19:34 erlangen systemd[1]: haveged.service: Service RestartSec=100ms expired, scheduling restart.
    Nov 12 19:19:34 erlangen systemd[1]: haveged.service: Scheduled restart job, restart counter is at 2.
    Nov 12 19:19:34 erlangen systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm.
    Nov 12 19:19:34 erlangen systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm.
    Nov 12 19:19:34 erlangen haveged[567]: haveged: listening socket at 3
    erlangen:~ #
    Any idea?
    According to what you just posted, your haveged service is running fine although after a few restarts in the beginning.
    As I described in my post previous to this one, you need to run the following to return current status of the service
    Code:
    systemctl status haveged
    To further verify that your system has no related issues, you can check the result of the following command which reads the size of your entropy cache, which should be larger than 1024
    Code:
    cat /proc/sys/kernel/random/entropy_avail
    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!

  8. #8
    Join Date
    May 2015
    Location
    Michigan/Florida
    Posts
    65

    Default Re: haveged

    Entropy cache is fine so it appears waiting for the next DUP would be wise and see where things lie.

    Sometimes waiting is the best answer.

  9. #9
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    1,131

    Default Re: haveged

    Quote Originally Posted by GDixon View Post
    Entropy cache is fine so it appears waiting for the next DUP would be wise and see where things lie.

    Sometimes waiting is the best answer.
    You may try systemctl restart haveged:

    Code:
    erlangen:~ # journalctl --since today -u haveged.service 
    -- Logs begin at Sun 2018-08-26 08:48:18 CEST, end at Tue 2018-11-13 22:15:18 CET. --
    Nov 13 22:14:27 erlangen haveged[567]: haveged: Stopping due to signal 15
    Nov 13 22:14:27 erlangen systemd[1]: Stopping Entropy Daemon based on the HAVEGE algorithm...
    Nov 13 22:14:27 erlangen haveged[567]: haveged starting up
    Nov 13 22:14:27 erlangen systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm.
    Nov 13 22:14:27 erlangen systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm.
    Nov 13 22:14:27 erlangen haveged[29491]: haveged: listening socket at 3
    erlangen:~ # cat /proc/sys/kernel/random/entropy_avail
    3755
    erlangen:~ #
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  10. #10
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,499
    Blog Entries
    2

    Default Re: haveged

    Looking at a couple of my machines,
    It looks like it's not unusual for haveged to have to undergo at least one restart although none of mine had to restart more than once after the initial start.

    I don't think that restarts are anything to be concerned about,
    The only real test of consequence is the entropy cache test I posted...
    If that's good, then your system is healthy.

    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!

Page 1 of 2 12 LastLast

Posting Permissions

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