Only if it is the case und you have pip for python2 installed too. If
true then you have to use the command "pip3" for installation.I tested
it on a fresh install of linux mint and it works instantly with pip3.
Am Montag, den 09.10.2017, 12:46 +0200 schrieb tatooin:
> Indeed; but I actually have installed python3-pip, removed gvm-cli
> and reinstalled it, but same results. It still complains about module
> gmp :-(
> On Mon, 2017-10-09 at 12:38 +0200, Raphael Grewe wrote:
> > Hi,maybe you used pip for python2. You have to use pip for
> > python3.Linux Mint package: python3-pip 
> > RegardsRaphael Grewe
> > Am Montag, den 09.10.2017, 09:52 +0200 schrieb tatooin:
> > > I followed the official documentation on https://bitbucket.org/gr
> > > eenbone/gvm-tools
> > > That is:
> > > apt-get install python3-paramiko python3-lxml python3-dialogpip
> > > install setuptoolspip install configparser
> > > I then downloaded the gvm-tools archive on the official
> > > repository and did "pip install ."
> > > Everything went fine at all stage, but still gvm refuse to run
> > > with the "ImportError: No module named gmp"  error.
> > > I'm running linux mint 18.2 
> > > Thank you
> > > On Fri, 2017-10-06 at 20:49 +0200, Raphael Grewe wrote:
> > > > Which command did you use to install the tools?
> > > > 
> > > > 
> > > > Gesendet mit BlueMail 
> > > > 
> > > > Am 6. Okt. 2017, um 18:50, tatooin <[email protected]> schrieb:
> > > > >  Thanks Trent for your quick reply. I tried GVM, but I've
> > > > > some problems to make it runs smoothly. After installing
> > > > > dependencies it requested, I always end up with the following
> > > > > error message:
> > > > > 
> > > > > 
> > > > >  
> > > > > 
> > > > > 
> > > > > 
> > > > >  ForensicLab ~ # gvm-cli 
> > > > > 
> > > > > 
> > > > >  Traceback (most recent call last):
> > > > > 
> > > > > 
> > > > >    File "/usr/local/bin/gvm-cli", line 11, in <module>
> > > > > 
> > > > > 
> > > > >      load_entry_point('gvm-tools==1.2.0', 'console_scripts',
> > > > > 'gvm-cli')()
> > > > > 
> > > > > 
> > > > >    File "/usr/local/lib/python2.7/dist-
> > > > > packages/pkg_resources/__init__.py", line 570, in
> > > > > load_entry_point
> > > > > 
> > > > > 
> > > > >      return get_distribution(dist).load_entry_point(group,
> > > > > name)
> > > > > 
> > > > > 
> > > > >    File "/usr/local/lib/python2.7/dist-
> > > > > packages/pkg_resources/__init__.py", line 2751, in
> > > > > load_entry_point
> > > > > 
> > > > > 
> > > > >      return ep.load()
> > > > > 
> > > > > 
> > > > >    File "/usr/local/lib/python2.7/dist-
> > > > > packages/pkg_resources/__init__.py", line 2405, in load
> > > > > 
> > > > > 
> > > > >      return self.resolve()
> > > > > 
> > > > > 
> > > > >    File "/usr/local/lib/python2.7/dist-
> > > > > packages/pkg_resources/__init__.py", line 2411, in resolve
> > > > > 
> > > > > 
> > > > >      module = __import__(self.module_name,
> > > > > fromlist=['__name__'], level=0)
> > > > > 
> > > > > 
> > > > >    File "/usr/local/lib/python2.7/dist-
> > > > > packages/gmp/clients/gvm_cli.py", line 33, in <module>
> > > > > 
> > > > > 
> > > > >      from gmp.gvm_connection import (SSHConnection,
> > > > > 
> > > > > 
> > > > >    File "/usr/local/lib/python2.7/dist-
> > > > > packages/gmp/gvm_connection.py", line 33, in <module>
> > > > > 
> > > > > 
> > > > >      from gmp.gmp import _gmp
> > > > > 
> > > > > 
> > > > >  ImportError: No module named gmp
> > > > > 
> > > > > 
> > > > >  
> > > > > 
> > > > > 
> > > > > 
> > > > >  Seems like a dependency problem with gmp; which is weird
> > > > > because gmp is in the source tree of gvm !
> > > > > 
> > > > > 
> > > > >  
> > > > > 
> > > > > 
> > > > > 
> > > > >  Any clue ?
> > > > > 
> > > > > 
> > > > >  
> > > > > 
> > > > > 
> > > > > 
> > > > >  Thanks
> > > > > 
> > > > > 
> > > > >  
> > > > > 
> > > > > 
> > > > > 
> > > > >  On Fri, 2017-10-06 at 10:55 +0000, Trent Townsend wrote:
> > > > > 
> > > > > >   Vincent, 
> > > > > >  
> > > > > >     I had the exact same issue about a month ago.  I never
> > > > > > figured out why OMP stopped working.  
> > > > > >   Long story short, the problem described below is limited
> > > > > > to OMP.  The exact same XML commands I was using, when
> > > > > > migrated to GVM Tools, produced repetitive, dependable, and
> > > > > > expected results in the form of proper reports being
> > > > > > generated.  I don't know why OMP refused to produce the
> > > > > > reports (<get_reports report_id=x/>) but GVM Tools works
> > > > > > like a charm. Also, I believe GVM Tools is going to replace
> > > > > > OMP so migrating to GVM isn’t bad anyway. 
> > > > > >   
> > > > > >  
> > > > > >   
> > > > > >  
> > > > > >   
> > > > > >    -- 
> > > > > >    
> > > > > >     Trent Townsend
> > > > > >     
> > > > > >    
> > > > > >     CISSP, CCNA
> > > > > >     
> > > > > >    
> > > > > >     Next Step Innovation 
> > > > > >     
> > > > > >    
> > > > > >     601.708.4500 x1201
> > > > > >     
> > > > > >    
> > > > > >   
> > > > > >    
> > > > > >  On Oct 6, 2017, at 5:08 AM, tatooin <
> > > > > >    [email protected]> wrote:
> > > > > >    
> > > > > >  
> > > > > >    
> > > > > >  
> > > > > >    
> > > > > >   
> > > > > > >  
> > > > > > >     
> > > > > > >     
> > > > > > >      Hello,
> > > > > > >      
> > > > > > >     
> > > > > > >      
> > > > > > >  
> > > > > > >      
> > > > > > >     
> > > > > > >      I'm trying  to generate reports with omp under
> > > > > > > openvas9. With openvas8, the command below was working
> > > > > > > fine to generate a scan report in csv format:
> > > > > > >      
> > > > > > >     
> > > > > > >      
> > > > > > >  
> > > > > > >      
> > > > > > >     
> > > > > > >      omp -h 127.0.0.1 -u admin -w pass -iX '<get_reports
> > > > > > > report_id="'$reportId'" levels="hml"
> > > > > > > format_id="'$formatId'" apply_overrides="1"/>' |
> > > > > > > xmlstarlet sel -t -v get_reports_response/report/text\(\)
> > > > > > > | base64 -i -d > $reportName
> > > > > > >      
> > > > > > >     
> > > > > > >      
> > > > > > >  
> > > > > > >      
> > > > > > >     
> > > > > > >      Under openvas9, this no longer works. The output of
> > > > > > > xmlstarlet is now empty. I don't have knowledge in XML,
> > > > > > > and I don't succeed to generate reports with omp directly
> > > > > > > in base64 alhough I understood from the documentation it
> > > > > > > seems possible. 
> > > > > > >      
> > > > > > >     
> > > > > > >      
> > > > > > >  
> > > > > > >      
> > > > > > >     
> > > > > > >      What's wrong with my command upon, or is there a
> > > > > > > better way to generate reports with omp ?
> > > > > > >      
> > > > > > >     
> > > > > > >      
> > > > > > >  
> > > > > > >      
> > > > > > >     
> > > > > > >      Thank you !
> > > > > > >      
> > > > > > >     
> > > > > > >      Vincent
> > > > > > >      
> > > > > > >     
> > > > > > >   
> > > > > >  
> > > > > >   
> > > > > > >  
> > > > > > >    
> > > > > > >     _______________________________________________
> > > > > > >     
> > > > > > >  
> > > > > > >     Openvas-discuss mailing list
> > > > > > >     
> > > > > > >  
> > > > > > >     [email protected]
> > > > > > >     
> > > > > > >  
> > > > > > >     https://lists.wald.intevation.org/cgi-bin/mailman/lis
> > > > > > > tinfo/openvas-discuss
> > > > > > >     
> > > > > > >   
> > > > > >  
> > > > > >   
> > > > > >  
> > > > > >   
> > > > > > 
> > > > > >   
> > > > > >  
> > > > > > 
> > > > > >     This email is confidential and intended solely for the
> > > > > > use of the individual to whom it is addressed. Any views or
> > > > > > opinions presented are solely those of the author, and do
> > > > > > not necessarily represent those of Next Step Innovation. If
> > > > > > you are not the intended recipient, be advised that you
> > > > > > have received this email in error, and that any use,
> > > > > > dissemination, forwarding, printing or copying of this
> > > > > > email is strictly prohibited. If you have received this
> > > > > > email in error, please contact the sender. 
> > > > > > 
> > > > > >     
> > > > > 
> > > > >  
> > > > > Openvas-discuss mailing list
> > > > > [email protected]
> > > > > https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/op
> > > > > envas-discuss

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Reply via email to