Sponsored Content
Full Discussion: Rngd: failed fips test
Top Forums UNIX for Advanced & Expert Users Rngd: failed fips test Post 302971488 by radha254 on Wednesday 20th of April 2016 07:52:43 PM
Old 04-20-2016
Linux Rngd: failed fips test

I have recently enabled the process rngd, but after couple of days i see it got stopped automatically . Below is what i could find from messages file .

can someone shed light on what could be the reason and how can this can be taken care?

Code:
Apr 1 08:12:05 sap01 rngd: failed fips test
Apr 1 08:12:05 sap01 rngd: too many FIPS failures, disabling entropy source
Apr 1 08:12:05 sap01 ranged: No entropy sources working, exiting rngd"

Moderator's Comments:
Mod Comment Please use CODE tags for all sample input, output, and code segments.

Last edited by Don Cragun; 04-20-2016 at 09:10 PM.. Reason: Add CODE and ICODE tags.
 

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Bad day !! test condition failed --need a one liner to do --help

Hi all this is simple but bad day for me nothing work out .. Problem is that I wan to check the argument passed to my script and accordignly exit or setup ENV variable I have a script name src_cpcp_preproc.sh i want to pass 2 argumet from command line argumet and check it in the script... (13 Replies)
Discussion started by: jambesh
13 Replies

2. Red Hat

validate test failed

hi everybody, I am new in Linux. I have successfully installed knoppix in my laptop, however, when I want to install ns2.26, some errors occurs in validation test.. It returned "Some Test failed" and it give some comands to re-run the test. I have already set the path before the validation test.... (1 Reply)
Discussion started by: newbie06
1 Replies

3. Shell Programming and Scripting

Test on string containing spacewhile test 1 -eq 1 do read a $a if test $a = quitC then break fi d

This is the code: while test 1 -eq 1 do read a $a if test $a = stop then break fi done I read a command on every loop an execute it. I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test. For example echo hello. Now the... (1 Reply)
Discussion started by: Max89
1 Replies

4. Shell Programming and Scripting

How to check weather a string is like test* or test* ot *test* in if condition

How to check weather a string is like test* or test* ot *test* in if condition (5 Replies)
Discussion started by: johnjerome
5 Replies

5. Shell Programming and Scripting

Prefixing test case methods with letter 'test'

Hi, I have a Python unit test cases source code file which contains more than a hundred test case methods. In that, some of the test case methods already have prefix 'test' where as some of them do not have. Now, I need to add the string 'test' (case-sensitive) as a prefix to those of the... (5 Replies)
Discussion started by: royalibrahim
5 Replies

6. Linux

Issue with FIPS

Hello, I'm facing an issue after upgrading CFT (File transfer tool) from 2.5 to 2.7, on one of our test Linux boxes. With CFT profile loaded, we can not initiate remote connections (ssh user @ server). We have the following message: OpenSSL version mismatch. Built against 90801f, You... (3 Replies)
Discussion started by: Joyb25
3 Replies
stopped(7)						 Miscellaneous Information Manual						stopped(7)

NAME
stopped - event signalling that a job has stopped SYNOPSIS
stopped JOB=JOB INSTANCE=INSTANCE RESULT=RESULT [PROCESS=PROCESS] [EXIT_STATUS=STATUS] [EXIT_SIGNAL=SIGNAL] [ENV]... DESCRIPTION
The stopped event is generated by the Upstart init(8) daemon when an instance of a job has stopped. The JOB environment variable contains the job name, and the INSTANCE environment variable contains the instance name which will be empty for single-instance jobs. If the job was stopped normally, the RESULT environment variable will be ok, otherwise if the job was stopped because it has failed it will be failed. When the job has failed, the process that failed will be given in the PROCESS environment variable. This may be pre-start, post-start, main, pre-stop or post-stop; it may also be the special value respawn to indicate that the job was stopped because it hit the respawn limit. Finally in the case of a failed job, one of either EXIT_STATUS or EXIT_SIGNAL may be given to indicate the cause of the stop. Either EXIT_STATUS will contain the exit status code of the process, or EXIT_SIGNAL will contain the name of the signal that the process received. The normal exit job configuration stanza can be used to prevent particular exit status values or signals resulting in a failed job, see init(5) for more information. If neither EXIT_STATUS or EXIT_SIGNAL is given for a failed process, it is because the process failed to spawn (for example, file not found). See the system logs for the error. init(8) emits this event as an informational signal, services and tasks started or stopped by this event will do so in parallel with other activity. It is typically combined with the starting(7) event by services when inserting themselves as a dependency. Job configuration files may use the export stanza to export environment variables from their own environment into the stopped event. See init(5) for more details. EXAMPLE
A service that wishes to be running whenever another service would be running, started before and stopped after it, might use: start on starting apache stop on stopped apache A task that must be run after another task or service has been stopped might use: start on stopped postgresql SEE ALSO
starting(7) started(7) stopping(7) init(5) Upstart 2009-07-09 stopped(7)
All times are GMT -4. The time now is 01:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy