It took me a while to get back to this (it’s not a mission-critical server, but I have hit a point where I really do need to get it working again). `apachectl restart` hung for many, many minutes without any input, and I eventually quit it. I ran it again with `strace -Ff apachectl restart`. Towards the end it had read all of the vhost config files and opened up the request and error logs configured in them, and it read the media types config file: [pid 22537] read(35, "# This file maps Internet media "..., 4096) = 4096 But after that is where things got weird: [pid 22537] mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f73aff27000 [pid 22537] open("/dev/random", O_RDONLY|O_CLOEXEC) = 35 [pid 22537] read(35, " p$\242\33\241", 1024) = 6 [pid 22537] read(35, "\205\31\345\274A\336", 1018) = 6 [pid 22537] read(35, "\335\16\7\370\343\311", 1012) = 6 [pid 22537] read(35, "\265\362\20}F\234", 1006) = 6 [pid 22537] read(35, "\223}\\\0+\242", 1000) = 6 [pid 22537] read(35, Each `read` line there took about a full minute. It’s spending FOREVER reading from /dev/random. That led me to try to read from /dev/random, and it is only generating a byte every few seconds. I don’t know why, but /dev/random appears to be borked on this machine. I changed ssl-global.conf to use /dev/urandom instead of /dev/random, and it started right up in a matter of seconds. I know this is now off-topic, but does anyone know why /dev/random would suddenly be gathering almost no entropy? I have never had this problem on this system before. Thanks, Nick
|