search for: image_mover

...ely add nobarrier, and see what happens. Finally got to add nobarrier (I'll skip why it took so long), and it looks like this just caused the problem to morph a bit. On the C7 NFS server, besides having 50 external machines ftp-ing files to it, we run 2 jobs: 1 that moves files around (called image_mover) and one that changes perms on some files (called chmod_job). And on the C6 NFS client, besides the job that was hanging (called the importer), we also run a another job (called ftp_job) that ftps files to the C6 machine. The ftp_job had never hung before, but now the importer that used to hang ha...

...> And that is the daemon. But I only see that on this one day, and it > crashes every day. > > And I see this type of message frequently throughout the day, every day: > > May 09 03:40:01 localhost.localdomain CROND[21447]: (motor) CMD > (python /usr/local/motor/motor/scripts/image_mover.py -v1 -d > /usr/local/motor/data > ~/last_image_move_log.txt) > May 09 03:40:01 localhost.localdomain abrt-server[21453]: Only 0MiB is > available on /var/spool/abrt > May 09 03:40:01 localhost.localdomain python[21402]: error sending > data to ABRT daemon: > May 09 03:40:01 l...

On Fri, Oct 21, 2016 at 11:42 AM, <m.roth at 5-cent.us> wrote: > Larry Martell wrote: >> On Fri, Oct 21, 2016 at 11:21 AM, <m.roth at 5-cent.us> wrote: >>> Larry Martell wrote: >>>> We have 1 system ruining Centos7 that is the NFS server. There are 50 >>>> external machines that FTP files to this server fairly continuously. >>>>

...this one day, and it > >> crashes every day. > >> > >> And I see this type of message frequently throughout the day, every day: > >> > >> May 09 03:40:01 localhost.localdomain CROND[21447]: (motor) CMD > >> (python /usr/local/motor/motor/scripts/image_mover.py -v1 -d > >> /usr/local/motor/data > ~/last_image_move_log.txt) > >> May 09 03:40:01 localhost.localdomain abrt-server[21453]: Only 0MiB is > >> available on /var/spool/abrt > >> May 09 03:40:01 localhost.localdomain python[21402]: error sending > >&gt...

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 >>

...rror sending data to ABRT daemon: And that is the daemon. But I only see that on this one day, and it crashes every day. And I see this type of message frequently throughout the day, every day: May 09 03:40:01 localhost.localdomain CROND[21447]: (motor) CMD (python /usr/local/motor/motor/scripts/image_mover.py -v1 -d /usr/local/motor/data > ~/last_image_move_log.txt) May 09 03:40:01 localhost.localdomain abrt-server[21453]: Only 0MiB is available on /var/spool/abrt May 09 03:40:01 localhost.localdomain python[21402]: error sending data to ABRT daemon: May 09 03:40:01 localhost.localdomain postfix/p...

...aemon. But I only see that on this one day, and it >> crashes every day. >> >> And I see this type of message frequently throughout the day, every day: >> >> May 09 03:40:01 localhost.localdomain CROND[21447]: (motor) CMD >> (python /usr/local/motor/motor/scripts/image_mover.py -v1 -d >> /usr/local/motor/data > ~/last_image_move_log.txt) >> May 09 03:40:01 localhost.localdomain abrt-server[21453]: Only 0MiB is >> available on /var/spool/abrt >> May 09 03:40:01 localhost.localdomain python[21402]: error sending >> data to ABRT daemon: &g...

...;> >> crashes every day. >> >> >> >> And I see this type of message frequently throughout the day, every day: >> >> >> >> May 09 03:40:01 localhost.localdomain CROND[21447]: (motor) CMD >> >> (python /usr/local/motor/motor/scripts/image_mover.py -v1 -d >> >> /usr/local/motor/data > ~/last_image_move_log.txt) >> >> May 09 03:40:01 localhost.localdomain abrt-server[21453]: Only 0MiB is >> >> available on /var/spool/abrt >> >> May 09 03:40:01 localhost.localdomain python[21402]: error send...