Some problems met when installing the namazu. #189

Activity

1. maoling commented on Apr 4, 2019

   

   maoling

   on Apr 4, 2019

   Author

   More actions

   @AkihiroSuda PTAL.
2. AkihiroSuda commented on Apr 4, 2019

   

   AkihiroSuda

   on Apr 4, 2019

   Member

   More actions

   container name needs to be specified:

   namazu/nmz/cli/container/run/runflag.go

   Line 81 in 2162f3d

   image := parsedArgs[0]
3. maoling commented on Apr 4, 2019

   

   maoling

   on Apr 4, 2019

   Author

   More actions

   @AkihiroSuda Thanks for your quick reply

   • Look at the usage:

   Docker-compatible options:
   -d, --detach Run container in background and print container ID (nmz itself runs in foreground)
   -i, --interactive Keep STDIN open even if not attached
   -p Publish a container's port(s) to the host
   --name Assign a name to the container
   --rm Automatically remove the container when it exits
   -t, --tty Allocate a pseudo-TTY
   -v, --volume=[] Bind mount a volume
   --volumes-from Mount volumes from the specified container(s)
   --privileged Give extended privileges to this container

   Namazu-specific options:
   -nmz-autopilot Namazu configuration file

   NOTE: Unlike docker, COMMAND is mandatory at the moment.

   is every command mandatory?

   container name needs to be specified:

   I follow an example from this which also failed.
   Could you plz give a complete cmd example, thank in advance.
4. maoling commented on Apr 4, 2019

   

   maoling

   on Apr 4, 2019

   Author

   More actions

   [NMZ-DBG] 03:46:11.07: Registering an exploration policy "replayable" (at explorepolicy.go:36)
   [NMZ-DBG] 03:46:11.07: Namazu Config=Config{map[string]interface {}{
   "restport": int(10080),
   "explorepolicyparam": map[string]interface {}{
   "faultActionProbability": float64(0.5),
   "minInterval": "80ms",
   "maxInterval": "3000ms",
   "shellActionInterval": "5000ms",
   "shellActionCommand": "echo hello $(date)",
   },
   "clean": "",
   "skipinitorchestrator": bool(false),
   "validate": "",
   "notcleanifvalidationfail": bool(false),
   "explorepolicy": "random",
   "init": "",
   "storagetype": "naive",
   "container": map[string]interface {}{
   "enableFSInspector": bool(true),
   "ethernetNFQNumber": int(42),
   "procWatchInterval": time.Duration(1000000000),
   "enableEthernetInspector": bool(false),
   "enableProcInspector": bool(true),
   },
   "run": "run.sh",
   "pbport": int(-1),
   }} (at run.go:50)
   prerequisite error: CAP_SYS_NICE is needed.

   Usage: namazu container run [OPTIONS] IMAGE COMMAND

   Run a command in a new Namazu Container

   **prerequisite error: CAP_SYS_NICE is needed.**
   
   if cfg.GetBool("container.enableProcInspector") {
           if !capInst.Get(cap.EFFECTIVE, cap.CAP_SYS_NICE) {
               return fmt.Errorf("CAP_SYS_NICE is needed.")
           }
       }
   
5. maoling commented on Apr 4, 2019

   

   maoling

   on Apr 4, 2019

   Author

   More actions

   docker run -it --privileged=true --cap-add=sys_nice osrg/namazu /bin/bash
   solve the prerequisite error: CAP_SYS_NICE is needed problem
6. maoling

   changed the title [-]"panic: runtime error: index out of range [recovered]" when running the namazu in the docker mode.[/-] [+]Some problems met when installing the namazu.[/+] on Apr 8, 2019
7. maoling commented on Apr 8, 2019

   

   maoling

   on Apr 8, 2019

   Author

   More actions

   @AkihiroSuda

   • Wuuuuuu,I had installed the namazu successfully.I saw it was running in the daemon:

   ng]interface {}{"comment":"injected by the random explorer"}}, "type":"action", "uuid":"7fc53aec-ac4d-4d97-afb4-33aacf17775c", "entity":"_namazu_shell_action_entity"}} (at orchestrator.go:97)
   [NMZ-DBG] 02:15:01.25: action Signal{map[string]interface {}{"uuid":"7fc53aec-ac4d-4d97-afb4-33aacf17775c", "entity":"_namazu_shell_action_entity", "class":"ShellAction", "option":map[string]interface {}{"command":"echo hello $(date)", "comments":map[string]interface {}{"comment":"injected by the random explorer"}},

   • ./bin/nmz container run --nmz-autopilot /gopath/src/github.com/osrg/namazu/example/template/config.toml -d --name zk3 -p 2183:2183 --privileged -v /foo:/foo jplock/zookeeper
     @AkihiroSuda
     how can I watch the fuzzy effect that namazu takes on my zookeeper-server?