Saving random seed failed.

Devyn · 01-31-2016, 09:42 PM

Hey Guy's,

I'm receiving this 'Saving random seed failed.' from running mkdumprd.

PHP Code:



[root@mbpc-pc cores]#
[root@mbpc-pc cores]# df -m /var/crash
Filesystem           1M-blocks  Used Available Use Mounted on
/dev/mapper/mbpcvg-rootlv
                         31370 16722     13049  57% /
[root@mbpc-pc cores]# service kdump start
No kdump initial ramdisk found.                            [WARNING]
Rebuilding /boot/initrd-2.6.32-573.12.1.el6.x86_64kdump.img
DEVYN: /sbin/mkdumprd -d -f  /boot/initrd-2.6.32-573.12.1.el6.x86_64kdump.img 2.6.32-573.12.1.el6.x86_64 ...
Saving random seed failed.
Failed to run mkdumprd
[root@mbpc-pc cores]#
[root@mbpc-pc cores]#
[root@mbpc-pc cores]#
[root@mbpc-pc cores]# /sbin/mkdumprd -d -f  /boot/initrd-2.6.32-573.12.1.el6.x86_64kdump.img 2.6.32-573.12.1.el6.x86_64
Saving random seed failed.
[root@mbpc-pc cores]#

Based on the sources, it looks like it's running this command:

PHP Code:



[ ! -d $MNTIMAGE/var/lib ] && mkdir -p $MNTIMAGE/var/lib
inst /var/lib/random-seed $MNTIMAGE/var/lib/random-seed 2>/dev/null || {
    error "Saving random seed failed."
    cleanup_and_exit 1
}

but I haven't another Linux system to compare this too so I'm not sure which RPM package provides the above /var/lib/random-seed (it's missing on my system) or if something else is broken if it's not a missing RPM.

Any help would be appreciated. This is RHEL / CentOS compatible linux 6.6 (Scientific Linux).

Cheers,
DH

hoes · 02-01-2016, 01:33 PM

rpm -q --whatprovides random-seed ?

Devyn · 02-08-2016, 10:17 PM

Well on mine it's none because the file /var/lib/random-seed doesn't exist. So I can't really check:

# rpm -q --whatprovides random-seed
no package provides random-seed
#

How is this file created?

Cheers,
DH

hoes · 02-09-2016, 03:49 PM

Google /var/lib/random-seed and you find that it is a file to which the random seeds are stored.
You might want to check if you have the file and otherwise just touch it and see it that works.

Devyn · 02-12-2016, 07:50 AM

Quote:

Originally Posted by hoes

Google /var/lib/random-seed and you find that it is a file to which the random seeds are stored.
You might want to check if you have the file and otherwise just touch it and see it that works.

Tried with 0 byte and 512 then 1024. App now freezes instead of printing that message. I'll try this again later. I'll try a copy from another system as well.

Cheers,
DH

hoes · 02-13-2016, 03:05 AM

What about this link: https://bugzilla.redhat.com/show_bug.cgi?id=1045891
It seems that /var/lib/random-seed is found in /var/lib/systemd/random-seed
This is also the case for me.

Devyn · 02-14-2016, 11:25 AM

Thanks hoes! That one wasn't found either on this 6.7 Scientific Linux. I think I'll leave figuring this out as I've other items I need to resolve first of higher priority and this file might reappear with one of the updates.

Cheers,
DH

Devyn · 02-14-2016, 11:38 AM

Ok I just wanted it more then not. So I recreate it in this manner:

Quote:

[root@mbpc-pc qla2464-firmware]#
[root@mbpc-pc qla2464-firmware]# ls -altri /var/lib/systemd/random-seed
ls: cannot access /var/lib/systemd/random-seed: No such file or directory
[root@mbpc-pc qla2464-firmware]# ls -altri /var/lib/random-seed
ls: cannot access /var/lib/random-seed: No such file or directory
[root@mbpc-pc qla2464-firmware]# dd if=/dev/urandom of=/var/lib/random-seed bs=1024 count=1
1+0 records in
1+0 records out
1024 bytes (1.0 kB) copied, 0.000944831 s, 1.1 MB/s
[root@mbpc-pc qla2464-firmware]# ls -altri /var/lib/random-seed
135115 -rw-r--r--. 1 root root 1024 Feb 14 12:28 /var/lib/random-seed
[root@mbpc-pc qla2464-firmware]# dd if=/dev/urandom of=/var/lib/systemd/random-seed bs=1024 count=1
dd: opening `/var/lib/systemd/random-seed': No such file or directory
[root@mbpc-pc qla2464-firmware]#

However when I try to start kdump this is what I get and it doesn't even begin to create the file it says it's creating:

Quote:

[root@mbpc-pc qla2464-firmware]# service kdump start
No kdump initial ramdisk found. [WARNING]
Rebuilding /boot/initrd-2.6.32-573.12.1.el6.scst.x86_64kdump.img
DEVYN: /sbin/mkdumprd -d -f /boot/initrd-2.6.32-573.12.1.el6.scst.x86_64kdump.img 2.6.32-573.12.1.el6.scst.x86_64 ...

Strace of /etc/init.d/kdump start

Quote:

rt_sigaction(SIGINT, {SIG_DFL, [], SA_RESTORER, 0x33796326a0}, {0x43d360, [], SA_RESTORER, 0x33796326a0}, 8) = 0
write(1, "Rebuilding /boot/initrd-2.6.32-5"..., 65Rebuilding /boot/initrd-2.6.32-573.12.1.el6.scst.x86_64kdump.img
) = 65
write(1, "DEVYN: /sbin/mkdumprd -d -f /boot"..., 117DEVYN: /sbin/mkdumprd -d -f /boot/initrd-2.6.32-573.12.1.el6.scst.x86_64kdump.img 2.6.32-573.12.1.el6.scst.x86_64 ...
) = 117
rt_sigprocmask(SIG_BLOCK, [INT CHLD], [], 8) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7f7dc18159d0) = 27818
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigaction(SIGINT, {0x43d360, [], SA_RESTORER, 0x33796326a0}, {SIG_DFL, [], SA_RESTORER, 0x33796326a0}, 8) = 0
wait4(-1, ^CProcess 27782 detached
<detached ...>

Cheers,
DH

Devyn · 02-14-2016, 11:42 AM

Ok never mind. Seems to be ok now, just took a few minutes:

[root@mbpc-pc qla2464-firmware]# service kdump start
No kdump initial ramdisk found. [WARNING]
Rebuilding /boot/initrd-2.6.32-573.12.1.el6.scst.x86_64kdump.img
DEVYN: /sbin/mkdumprd -d -f /boot/initrd-2.6.32-573.12.1.el6.scst.x86_64kdump.img 2.6.32-573.12.1.el6.scst.x86_64 ...
Warning: There might not be enough space to save a vmcore.
The size of UUID=af6c5c11-6f1c-4735-8a7b-9869613de495 should be greater than 3526912 kilo bytes.
Starting kdump: [ OK ]
[root@mbpc-pc qla2464-firmware]#

Thank you guy's for helping out on this thread. Much appreciated!

Cheers,
DH