9:50 a.m.
Hello,
I have attempted a few times to upload a log-collector which has a
confirmed DB in it but I continually get the following error:
An internal error occurred:
('analyzer failed, rc=%s, err=%r', 255, 'Unable to detect the database dump
from sosreport, aborting..\n')
See logs for full stacktrace.
Thank you,
Jason
4:55 a.m.
On Mon, Feb 12, 2018 at 5:50 PM, Jason Bryant <jbryant(a)redhat.com> wrote:
Hello,
I have attempted a few times to upload a log-collector which has a confirmed
DB in it but I continually get the following error:
An internal error occurred:
('analyzer failed, rc=%s, err=%r', 255, 'Unable to detect the database dump
from sosreport, aborting..\n')
See logs for full stacktrace.
Have you forgotten to attach them?
Which version is the analyzer? Which version was used to collect the
logs? We had a pug due to postgres95 using different filename for
pgdump, it might be what you're seeing.
7:39 a.m.
Hi Dan,
I was using the Web UI and I uploaded the entire logcollector un-edited
so nothing was forgotten. As for the version of the analyzer whatever is
public facing. As for postgres95 I am not sure that is correct as other
logcollectors uploaded before and after worked no problem from the same
browser/session.
Thank you,
Jason
On 03/01/2018 05:55 AM, Dan Kenigsberg wrote:
On Mon, Feb 12, 2018 at 5:50 PM, Jason Bryant
<jbryant(a)redhat.com> wrote:
> Hello,
>
> I have attempted a few times to upload a log-collector which has a confirmed
> DB in it but I continually get the following error:
>
>
> An internal error occurred:
>
> ('analyzer failed, rc=%s, err=%r', 255, 'Unable to detect the database
dump
> from sosreport, aborting..\n')
>
> See logs for full stacktrace.
Have you forgotten to attach them?
Which version is the analyzer? Which version was used to collect the
logs? We had a pug due to postgres95 using different filename for
pgdump, it might be what you're seeing.
2487
days inactive
2504
days old
2 comments
2 participants
participants (2)
-
Dan Kenigsberg -
Jason Bryant