search for: 0mib

...ages. > > Second, I see messages like this periodically: > > May 10 03:57:46 localhost.localdomain python[40222]: detected > unhandled Python exception in > '/usr/local/motor/motor/core/data/importer.py' > May 10 03:57:46 localhost.localdomain abrt-server[40277]: Only 0MiB is > available on /var/spool/abrt > May 10 03:57:46 localhost.localdomain python[40222]: error sending > data to ABRT daemon: > > This happens at various times of the day, and I do not think is > related to the daemon crashing. > > But I did see one occurrence of this: &gt...

...this periodically: > >> > >> May 10 03:57:46 localhost.localdomain python[40222]: detected > >> unhandled Python exception in > >> '/usr/local/motor/motor/core/data/importer.py' > >> May 10 03:57:46 localhost.localdomain abrt-server[40277]: Only 0MiB is > >> available on /var/spool/abrt > >> May 10 03:57:46 localhost.localdomain python[40222]: error sending > >> data to ABRT daemon: > >> > >> This happens at various times of the day, and I do not think is > >> related to the daemon crashing....

On Wed, May 10, 2017 at 3:07 PM, Jonathan Billings <billings at negate.org> wrote: > On Wed, May 10, 2017 at 02:40:04PM -0400, Larry Martell wrote: >> I have a CentOS 7 system that I run a home grown python daemon on. I >> run this same daemon on many other systems without any incident. On >> this one system the daemon seems to die or be killed every day around >>

...cond, I see messages like this periodically: >> >> May 10 03:57:46 localhost.localdomain python[40222]: detected >> unhandled Python exception in >> '/usr/local/motor/motor/core/data/importer.py' >> May 10 03:57:46 localhost.localdomain abrt-server[40277]: Only 0MiB is >> available on /var/spool/abrt >> May 10 03:57:46 localhost.localdomain python[40222]: error sending >> data to ABRT daemon: >> >> This happens at various times of the day, and I do not think is >> related to the daemon crashing. >> >> But I did s...

...>> >> >> >> May 10 03:57:46 localhost.localdomain python[40222]: detected >> >> unhandled Python exception in >> >> '/usr/local/motor/motor/core/data/importer.py' >> >> May 10 03:57:46 localhost.localdomain abrt-server[40277]: Only 0MiB is >> >> available on /var/spool/abrt >> >> May 10 03:57:46 localhost.localdomain python[40222]: error sending >> >> data to ABRT daemon: >> >> >> >> This happens at various times of the day, and I do not think is >> >> related...

...when logging stops in /var/log/messages. Second, I see messages like this periodically: May 10 03:57:46 localhost.localdomain python[40222]: detected unhandled Python exception in '/usr/local/motor/motor/core/data/importer.py' May 10 03:57:46 localhost.localdomain abrt-server[40277]: Only 0MiB is available on /var/spool/abrt May 10 03:57:46 localhost.localdomain python[40222]: error sending data to ABRT daemon: This happens at various times of the day, and I do not think is related to the daemon crashing. But I did see one occurrence of this: May 09 03:49:35 localhost.localdomain pyth...

...uveau 0000:f0:10.0: Adaptor not initialised, running VBIOS init tables. [drm] nouveau 0000:f0:10.0: PTIMER: unknown input clock freq [TTM] Zone kernel: Available graphics memory: 501592 kiB [TTM] Initializing pool allocator [TTM] Initializing DMA pool allocator [drm] nouveau 0000:f0:10.0: Detected 0MiB VRAM (SDRAM) [drm] nouveau 0000:f0:10.0: 128 MiB GART (aperture) [drm:drm_mm_takedown] *ERROR* Memory manager not clean. Delaying takedown [drm:drm_mm_takedown] *ERROR* Memory manager not clean. Delaying takedown [TTM] Finalizing pool allocator [TTM] Finalizing DMA pool allocator [TTM] Zone kernel...