Re: [Burp-users] summary_script not working after update

[Graham K. <gr...@gr...>]

On Tue, Mar 21, 2017 at 01:20:05PM +0100, Henrik Schmidt wrote:
> Graham Keeling schrieb am 21.03.2017 um 12:37:
> > On Tue, March 21, 2017 7:17 pm, Henrik Schmidt wrote:
> >> Hi,
> >>
> >> I did update my server from 1.4.40 to 2.0.59 and the summary script is
> >> not working any longer.
> >>
> >> The logfile says :
> >>
> >> Mar 21 10:11:10 copter burp[18222]: Could not get lockfile.
> >> Mar 21 10:11:10 copter burp[18222]: Another process is probably running,
> >>
> >> Of course another process is running, the burp server process.
> >> This was no problem for burp 1.4.40.
> >>
> >> How to fix this ?
> >>
> >> Thanks for this great backup programm.
> > Hello,
> >
> > The summary script uses the status monitor, which has changed a bit in 2.0.x.
> >
> > It is now a client and connects over ssl.
> >
> > What is the command that you are running for the summary script?
> > You should no longer be giving it '-c /etc/burp/burp-server.conf'.
> > Instead, either give it '-c /etc/burp/burp.conf', or don't give it a -c
> > parameter at all.
> >
> > More info on the status monitor changes here:
> > http://burp.grke.org/docs/monitor.html
> >
> >
> > ------------------------------------------------------------------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > _______________________________________________
> > Burp-users mailing list
> > Bur...@li...
> > https://lists.sourceforge.net/lists/listinfo/burp-users
> 
> 
> Thanks.
> 
> I'm now using my burpui 'restore user' client configuration as he can
> see all clients and it does work.
> 
> I had to reduce the burpui gunicorn worker count to be less than the
> max_status_children value.
> 
> Otherwise burpui was occupying all available status connections.
> 
> burp together with burpui is a great backup solution.
> 
> The protocol version 2 isn't stable yet ?
> 
> Best,
> 
> Henrik Schmidt

Hello,

That is right, protocol 2 isn't stable yet.