Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

improvements suggestions regarding sending the report #596

Open
captainjs opened this issue Feb 4, 2020 · 2 comments
Open

improvements suggestions regarding sending the report #596

captainjs opened this issue Feb 4, 2020 · 2 comments

Comments

@captainjs
Copy link

captainjs commented Feb 4, 2020

Hi,
I am contacting you because I tried using "abrt-cli report " from a customer system using RHEL7.7.
abrt-cli is version 2.1.11-55.el7.

I selected option 2, for example (create a new support case, I would like to be contacted by Red Hat Support).
It's only after answering quite a few settings that it fails, obviously, because these servers are not directly connected to the internet.

So I was thinking of 3 options to improve:

  1. The tool could either inform it requires an active connection at the earliest opportunity (which is obvious, I know)

  2. The tool could send its report to the Satellite server (if existing). Usually from there it's connected to internet and it would be easier to submit it from there.

  3. The tool can complete, and since it's offline, the result could be downloaded, copied on another server with a connection, and send. Or one could send the result file, which would do the required actions.

Many thanks!

@ernestask
Copy link
Collaborator

Since you mention RHEL 7, you could look into https://abrt.readthedocs.io/en/latest/admin.html#configuring-centralized-crash-collection. Does that sound like something that might do it?

@ernestask
Copy link
Collaborator

On RHEL 8 systems that gets more complicated, given that a bunch of ABRT packages were cut out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants