Issues in ec2 about lime HOT 4 CLOSED

Can you verify that you're using the latest version of LiME? If so can you
try adjusting the timeout with the timeout=1000 parameter?

On Fri, Aug 19, 2016, 20:31 Alex Arwine [email protected] wrote:

I've compiled LiME in debug mode and verified that functionality in a
ubuntu 16.04 vagrant instance. However, on 16.04 in ec2, with apparmor
disabled seems to hang.

I ran LiME with the following:

insmod ./lime-4.4.0-34-generic.ko "path=/tmp/ram.lime format=lime"

This is the output of dmesg:

[ 194.329700] lime: module verification failed: signature and/or required key missing - tainting kernel
[ 194.329897] [LiME] Parameters
[ 194.329899] [LiME] PATH: /tmp/ram.lime
[ 194.329900] [LiME] DIO: 0
[ 194.329901] [LiME] FORMAT: lime
[ 194.329901] [LiME] LOCALHOSTONLY: 0
[ 194.329902] [LiME] Initializing Dump...
[ 194.329903] [LiME] Direct IO Disabled
[ 194.329940] [LiME] Writing range 1000 - 9dfff.
[ 194.330501] [LiME] Writing range 100000 - efffffff.
[ 247.104859] [LiME] Writing range 100000000 - 10fffffff.
[ 251.316417] [LiME] Writing range 110000000 - 117ffffff.

insmod is still taking up cpu, but as far as I can tell no additional
writes are getting written to the lime file. FWIW, the lime file at this
point is about 4G, roughly the size of the ec2 test box's ram.

Let me know how I can provide more information

Thanks!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#21, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAkQ9e_Cr6lqzmFeIexPsM2DXDddplWfks5qhljygaJpZM4Jo90-
.

from lime.

Ok, I was on the latest version, and timeout seemed to allow the dump to complete

I'm curious though; it looks like the default timeout is 5000, wouldn't that just mean that I wait 4 additional seconds before it times out and completes?

Thanks for the quick turnaround

from lime.

Yes but the timeout is per page, so it's a balancing act between not being
too low as to skip the range if it's good and being too high as to take too
long per page. I'll make the default 1 second instead of 5. It was
originally 500ms, but that was getting false positives on at least one
system.

On Sat, Aug 20, 2016, 09:59 Alex Arwine [email protected] wrote:

Ok, I was on the latest version, and timeout seemed to allow the dump to
complete

I'm curious though; it looks like the default timeout is 5000, wouldn't
that just mean that I wait 4 additional seconds before it times out and
completes?

Thanks for the quick turnaround

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
#21 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAkQ9RhprVE18aC_KG5mFIKEtsVySYs9ks5qhxZQgaJpZM4Jo90-
.

from lime.

Thanks again!

from lime.