topic Re: doctor-log on R82.10 in Firewall & Security Management

doctor-log on R82.10

morris — Fri, 25 Sep 2026 11:11:27 GMT

Hi guys,

when running doctor-log.sh on R82.10 management following error occurs:

[Expert@cp-mgmt:0]# ./doctor-log.sh
uudecode fatal error:
standard input: Invalid or missing 'begin' line

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Failed installing sme-diag package

In comparison to R82 doctor-log the content on the R82.10 machine is only 45 lines and after PAYLOAD: is no content.

What is missing?

Re: doctor-log on R82.10

Chris_Atkinson — Fri, 25 Sep 2026 12:43:25 GMT

Which JHF is this machine running, have you reported the issue to TAC?

Re: doctor-log on R82.10

morris — Mon, 28 Sep 2026 08:22:04 GMT

Its R82.10 Take 45.

Also on the management (Take 45) in my lab there is no doctor-log.sh

Re: doctor-log on R82.10

simonemantovani — Mon, 28 Sep 2026 13:06:55 GMT

Hello

It's the same behaviour on R82.20, content of the file is different, also compared with the same file in R81.20; in R82.10 and R82.20, as you wrote, the script is composed only only of 45 lines, and it's missing all the content after the PAYLOAD line that is causing the error.

I checked internally but I'm waiting for a reply, at the moment I can suggest to involve the TAC.

Re: doctor-log on R82.10

Lesley — Tue, 29 Sep 2026 16:41:12 GMT

Official: you should only run doctor log script when asked by TAC and they share the latest version. What is the reason why you want to run this script? Maybe you just have an outdated one on the system. These scripts get updated more frequently then you might think.