1. Bash Timeout Script
2. Shell Script Timeout
3. Abrt Cli Status Timed Out 2016

• For more info run: abrt-cli list -since '). I've been looking though dmesg, abrt-cli -list and var/log/messages with no luch of what could be the message whatsoever. Could anyone point to WHAT i should be looking for?
• When change or login to specific user, 'abrt-cli status' timed out is always shown # su - testuser Last login: Mon Jun 12 15:00:40 JST 2017 from localhost on pts/0 'abrt-cli status' timed out Environment. Red Hat Enterprise Linux 7.3; abrt-2.1.11-45.el7.x8664.

Hey guys,

Dismiss Join GitHub today. GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.

after restoring a complete tar system backup (excluding, /mnt,/run,/proc,/sys,/dev,/tmp,/lost+found) i have run into this problem when trying to login via tty:

Complete journal for boot:

Interesting part:

The systems seems usable (after the login delay) and X seems to start fine (according to the log file) But i only get a black screen when i use startx. Could it be that excluding all the paths
( /mnt,/run,/proc,/sys,/dev,/tmp,/lost+found) was too much? I recreated them with the proper permissions after restoring the backup.(bootable usbstick) I thought nothing of these directories should be in the backup as they are virtual file systems, am i right? Briggs and stratton 136200 manual.

This part causes a massive delay of 16 seconds after hitting enter to login:

Then this happens (Failed to create session and root logs in anyways):

Some more failures afterwards:

OLD DIAGNOSTICS START HERE:

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
i restored a complete system backup of my arch installation. I used this to create the backup:

To restore i reformatted my disk and put the tar archive in the root dir. Then used this command:

and manually created the directores i excluded in the backup command.

My system boots but i get weird delays when trrying to login. I dont use graphical login but tty. I put in my User [ENTER] put in my password [ENTER] then i have 10 seconds delay until i get logged in. When i use startx i just get a black screen. Everything else from the console seems to work though..

Thanks in advance!

Last edited by schnip_schnap (2014-03-02 22:43:09)

Where does ABRT store the crashes?¶

• /var/spool/abrt
• Prior to Fedora 18 these were stored in /var/tmp/abrt

Bash Timeout Script

What type of crashes can ABRT handle?¶

See Supported programming languages and software projects.

What to do when ABRT is not able to catch the crash of my application?¶

• Make sure that following services are running:

  • abrtd
  • abrt-ccpp

  $systemctlstatusabrtdabrt-ccpp

• If one of them is not running you can use the following command torestart both of them:

  $sudosystemctlrestartabrtdabrt-ccpp

• If the above doesn’t help, consult journactl or /var/log/messages for error logs.

• By default ABRT won’t handle crashes produced by 3rd party(unpackaged) software, for this to work read How to enable handlingof unpackaged software.

How to enable handling of unpackaged software¶

• Edit /etc/abrt/abrt-action-save-package-data.conf and changeProcessUnpackaged=no to ProcessUnpackaged=yes

  #sed-i's/ProcessUnpackaged=no/ProcessUnpackaged=yes/'/etc/abrt/abrt-action-save-package-data.conf

How to enable handling of non-GPG signed software¶

• Edit /etc/abrt/abrt-action-save-package-data.conf and changeOpenGPGCheck=yes to OpenGPGCheck=no

  #sed-i's/OpenGPGCheck=yes/OpenGPGCheck=no/'/etc/abrt/abrt-action-save-package-data.conf

How do I list crashes handled by ABRT?¶

• Use either GUI application: $gnome-abrt

• or command line tool: $abrt-clilist

  See Usage for more details.

What is μReport?¶

• μReport (microreport) is a JSON object representing a problem: binarycrash, kerneloops, SELinux AVC denial, etc. These reports are designedto be small and completely anonymous which allows us to use them forautomated reporting.

  See μReport page for more details.

What is tainted kernel and why is my kernel tainted?¶

The Linux kernel maintains a taint state which indicates whethersomething happened to the running kernel that might caused a kernelerror.

Common reasons include:

• proprietary kernel module was loaded (P flag)
• previous kernel error (kerneloops) occurred (D flag).
• previous kernel warning (GW flags).
• Both cases D flag and GW flags mean that kernel data structures maybe corrupted. Therefore the current error is not necessary a realerror, it could be a random consequence of the previous error.
• To get rid of the tainted kernel, you need to reboot your machine orstop loading proprietary modules.
• ABRT respects these flags and won’t allow reporting if one or moreare in effect because kernel developers are usually not able to fixissues when the kernel is tainted.

Complete list of taint flags:

Source:http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob;f=kernel/panic.c

How do I create a private bugzilla ticket?¶

ABRT can create reports with restricted access which means theaccess to the report is limited to a group of trusted people. Pleasenote that the restriction differs between various bug trackers and evenif you mark something as restricted it still can leak to public, so ifyou are not sure, then don’t report anything!

To create a private bugzilla ticket, you have to specify the list ofgroups to restrict the access to. The tricky part is that it has to bethe internal id of the group from bugzilla database. To ease the pain,here is the list of the private group ids for supported bugzillas:

How do I enable screencasting?¶

To enable screencasting in abrt you have to install fros package withplugin matching your desktop environment. Currently thereare only 2 plugins available: fros-gnome and fros-recordmydesktop. Gnomeplugin works only with Gnome 3, recordmydesktop should work with the most ofother desktop environments. To install the plugin run one of thefollowing commands (depending on your desktop environment):

Why ABRT Analytics collects tainted kernel oopses?¶

ABRT Analytics collects tainted oopses because each received oops is forwardedto http://oops.kernel.org/ and kernel people want tosee every oops and not only untainted ones.

Why is my backtrace unusable?¶

Shell Script Timeout

Unusable backtrace is usually caused by damaged core dump,missing debug information or usage of unsupported coding technique(i.e. JavaScript in GNOME3).

These cause that the generated backtrace has low information valuefor developers because function names are replaced with '??'string which is place holder for unavailable function name.In order to provide valuable crash reports,ABRT will not let you create a Bugzilla bug for such a backtrace.

You can use ABRT to send the unusable backtrace to maintainersvia Emailreporter, but this is on your own responsibility.

How to enable dumping of setuid binaries¶

By default kernel won’t dump set-user-ID or otherwise protected/tainted binaries.To change this behavior you need to change fs.suid_dumpable kernel variable.

To read the value use:

To change the value use:

Possible values are:

Abrt Cli Status Timed Out 2016

0. (default) — traditional behaviour. Any process which has changedprivilege levels or is execute only will not be dumped.

1. (debug) — all processes dump core when possible. The core dump isowned by the current user and no security is applied. This isintended for system debugging situations only. Ptrace is unchecked.This is insecure as it allows regular users to examine the memorycontents of privileged processes.

2. (suidsafe) — Any binary which normally would not be dumped (see “0”above) is dumped readable by root only. This allows the user to remove thecore dump file but not to read it. For security reasons core dumpsin this mode will not overwrite one another or other files. This modeis appropriate when administrators are attempting to debug problems in anormal environment.

   Additionally, since Linux 3.6, /proc/sys/kernel/core_pattern must either bean absolute pathname or a pipe command, as detailed in core(5). Warningswill be written to the kernel log if core_pattern does not follow theserules, and no core dump will be produced.

Source:http://man7.org/linux/man-pages/man5/proc.5.html