autopsy

autopsy copied to clipboard

Unable to start (Error: cannot start smartos)

2

I already had VirtualBox in my system. When I run `autopsy start` command, it's giving following error - ``` Error: cannot start smartos at /usr/local/lib/node_modules/autopsy/node_modules/vboxmanage/lib/instance.coffee:44:25 at Object.callback (/usr/local/lib/node_modules/autopsy/node_modules/vboxmanage/lib/command.coffee:64:16) at next...

enVolt

There are new [versions](https://github.com/joyent/mdb_v8/releases) of `mdb_v8` and It'd be nice to have the new version (at this time of writing 1.3.0) included within autopsy. I had to analyse the dump...

r3dsm0k3

autopsy core hangs at `waiting for token to indicate ready state`

8

mdb.js is expecting to see `C++ symbol demangling enabled` as the last line of output from `::load v8 `, but this doesn't appear to be output anymore on recent versions...

dnwe

"Error: Encrypted private key detected, but no passphrase given" on "autopsy setup"

1

pararuk

error while "sudo npm install -g autopsy"

3

npm ERR! Error: No compatible version found: vboxmanage@'github:davidmarkclements/node-vboxmanage' npm ERR! Valid install targets: npm ERR! ["0.0.2","0.0.4","0.0.5","0.0.6","0.0.7","0.0.8","0.0.9","0.0.11","0.0.12","0.0.13","0.0.14","0.0.15"] npm ERR! at installTargetsError (/usr/lib/node_modules/npm/lib/cache.js:719:10) npm ERR! at /usr/lib/node_modules/npm/lib/cache.js:638:10 npm ERR! at saved (/usr/lib/node_modules/npm-registry-client/lib/get.js:142:7)...

ashishsinghshah

Hi there, I think this will fix #5 cheers /dom

tootedom

node-vboxmanage dependency cannot be resolved by npm install

1

Currently the package.json seems to specify the nove-vboxmanage dependency with a `github:` prefix [package.json:36](https://github.com/nearform/autopsy/blob/b268422e13ea4b02018a762ecd31290102977fda/package.json#L36) This doesn't seem to conform to any of the currently supported ways of specifying a GH...

dnwe

document that you can generate a core dump with gdb

2

You can generate a coredump like: ``` # get your pid pgrep -lf node # attach gdb -p your_pid ``` Then in gdb: ``` # gdb: generate core dump gcore...

ghost

if mdb is not passed a proper object and/or core file it will exit with an error code, we need to handle this case instead of just hanging

davidmarkclements

nt

davidmarkclements