On 17/04/15 11:16, Justin Cormack wrote:
On 17 April 2015 at 12:11, Andrew Stuart
<[email protected]> wrote:
limits are quite low and you may need to increase them with sysctl eg maybe
kern.maxfiles.
I’m puzzled as to why the web servers might be opening lots of file to handle
traffic - unless of course a socket is a file which is entirely possible I
guess. Even then I wouldn’t have imaged the web servers would be opening large
numbers of files. Anyway, how do I modify kern.maxfiles for a rump kernel?
sockets are files. It is a bit odd, but it might be keepalive keeping
them open. Or it could be another limit.
I think Martin had problems with TIME_WAIT and available memory.
We need to add an easy way to configure these types of things - I have
been thinking about it as I need to turn on ipv6 autoconfiguration
which is a sysctl too.
There is. You can use rumprun-posix on the guest IP port 12345. It
shouldn't depend on the guest having an IP stack, though, but all in
good time. At least it works. See here for more details:
http://wiki.rumpkernel.org/Repo%3A-rumprun-posix#remote-clients
I'm also in the process of adding sockstat there, but it seems to have
bitrotted a bit since I last used it 4(?) years ago. Should have it
done by tonight.
Can you get at the web server error log file?
I’ve turned it off as I have no read-write file system.
Can you make it log errors to stdout/stderr?
The root file system is a(n unlimited size) memory file system, and you
can use cat from rumprun-posix to cat the logs.
