- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- rng failure
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2004 08:18 AM
05-12-2004 08:18 AM
This is the output from kmadmin -Q rng:
Module Name rng
Module ID 2
Module Path /stand/dlkm/mod.d/rng
Status LOADED
Size 57344
Base Address 0x178e000
BSS Size 0
BSS Base Address 0x0
Hold Count 1
Dependent Count 0
Unload Delay 0 seconds
Description rng - random number generator for the /dev/[u]random interface
Type WSIO
Block Major -1
Character Major 95
Flags b5
Any suggestions?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2004 09:12 AM
05-12-2004 09:12 AM
Re: rng failure
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2004 09:16 AM
05-12-2004 09:16 AM
Re: rng failure
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2004 09:53 AM
05-12-2004 09:53 AM
Re: rng failure
jlong@bp-prod: /home/jlong # cat /dev/random > random.txt
cat: read error: No such file or directory
However, the directory is there:
jlong@bp-prod: /home/jlong # ll /dev/random
cr--r--r-- 1 bin bin 79 0x000000 Aug 27 2003 /dev/random
But I believe your suggestion of checking the swagent.log provided the answer. The depot I installed at the time of the reboot recreated the rng module. I have another maintenance window coming up, and I'll remove and reinstall the KRMG11i depot and see if that corrects the problem. Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2004 10:12 AM
05-12-2004 10:12 AM
Solutionrm /dev/random
rm /dev/urandom
mknod /dev/random c 95 0x00
mknod /dev/random c 95 0x01
You can also simply cd to /sbin/init.d and
./krng stop
./krng start
By the way, these devices do not produce random strings but rather random binary data so you might want to do something like this:
dd if=/dev/random bs=4 count=1 | od -c
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2004 10:22 AM
05-12-2004 10:22 AM
Re: rng failure
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2004 01:11 PM
05-12-2004 01:11 PM
Re: rng failure
I just noticed that
mknod /dev/random c 95 0x01
should be:
mknod /dev/urandom c 95 0x01
but you probably spotted that. The other mknod was correct.