> I was advised that the client is being phased out in favor of -manager, so I 
> built this, and tried it.  Issuing the --rebuild option, I see the following 
> message in the log:
>
> lib  serv:  DEBUG:2010-07-11 06h00.12 utc:18122:    Connected to server on 
> socket 3.
>
> That's the last log message I get.  Attaching strace to the process yields 
> this:
>
> select(4, [3], [], [3], {0, 860725})    = 0 (Timeout)
> select(4, [3], [], [3], {1, 0})         = 0 (Timeout)
> select(4, [3], [], [3], {1, 0})         = 0 (Timeout)
> select(4, [3], [], [3], {1, 0}
>
> The second line repeats about once a second, ad nauseum.
>
> I also attached strace to the daemon process (the spawned which I assume the 
> manager is communicating with), and it produced a lot of output.  After about 
> half an hour, it finally errored out.  The manager never did anything 
> interesting, and neither did the strace output, as far as I saw.  It did not 
> exit when the daemon process died.

Aaron, could you make sure that the --rebuild Manager is the only Manager
running when you issue the --rebuild.  So kill all Manager processes, then
try the --rebuild.  I've seen it hang when the Manager is already running.

If it still fails, it would be interesting to know what the Scanner is
doing while the Manager is just sitting there.
_______________________________________________
Openvas-devel mailing list
Openvas-devel@wald.intevation.org
http://lists.wald.intevation.org/mailman/listinfo/openvas-devel

Reply via email to