Skip to main content

Out of memory cpbackup_transp

Comments

18 comments

  • cPanelMichael
    Hello, Do you notice the server is reaching it's memory limit when this happens? EX:
    free -m
    Thank you.
    0
  • jimhermann
    Hello, Do you notice the server is reaching it's memory limit when this happens? EX:
    free -m
    Thank you.

    No. I was not connected at the time. CPanel Monitoring sent me this report: Out of memory: The process "cpbackup_transp" was terminated because the system is low on memory. In order to avoid a system crash due to low memory, the kernel terminated the process named "cpbackup_transp" with the PID "22990". Server host3.uuserver.net Primary IP Address 172.31.13.215 Process Name cpbackup_transp Event Time 2017-09-12 at 11:41:55 UTC PID 22990 Process UID 0 Process Username root Process Total Virtual Memory 2863200kB Process Anonymous Resident Set Size 2576220kB Process File Resident Set Size 64kB Process OOM Score 618 Status Out of Memory ? Memory Information Used 1.2 GB Available 2.66 GB Installed 3.86 GB Load Information 0.32 0.20 0.36 Uptime 3 days, 15 hours, 9 minutes, and 41 seconds IOStat Information avg-cpu: %user %nice %system %iowait %steal %idle 7.78 0.25 2.16 1.38 0.07 88.36 Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn xvda 27.70 1551.02 982.35 486679163 308244096 loop0 4.71 13.39 41.25 4202810 12944796 xvdf 6.38 846.72 472.89 265685327 148384808 Top Processes PID Owner CPU % Memory % Command 3720 mysql 1.96 11.98 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --user=mysql --log-error=host3.uuserver.net.err --open-files-limit=50000 --pid-file=/var/lib/mysql/host3.uuserver.net.pid 3354 cpanelsolr 0.07 6.81 /usr/lib/jvm/jre-1.8.0/bin/java -server -Xms512m -Xmx512m -XX:NewRatio=3 -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=8 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:ConcGCThreads=4 -XX:ParallelGCThreads=4 -XX:+CMSScavengeBeforeRemark -XX:PretenureSizeThreshold=64m -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=50 -XX:CMSMaxAbortablePrecleanTime=6000 -XX:+CMSParallelRemarkEnabled -XX:+ParallelRefProcEnabled -XX:-OmitStackTraceInFastThrow -verbose:gc -XX:+PrintHeapAtGC -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -Xloggc:/home/cpanelsolr/server/logs/solr_gc.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=9 -XX:GCLogFileSize=20M -Dsolr.log.dir=/home/cpanelsolr/server/logs -Djetty.port=8984 -DSTOP.PORT=7984 -DSTOP.KEY=solrrocks -Dhost=127.0.0.1 -Duser.timezone=UTC -Djetty.home=/home/cpanelsolr/server -Dsolr.solr.home=/home/cpanelsolr/server/solr -Dsolr.install.dir=/home/cpanelsolr -Xss256k -Dsolr.autoSoftCommit.maxTime=3000 -Dsolr.log.muteconsole -XX:OnOutOfMemoryError=/home/cpanelsolr/bin/oom_solr.sh 8984 /home/cpanelsolr/server/logs -jar start.jar --module=http 588 root 0.01 0.77 cpsrvd (SSL) - waiting f --llu=1505133779 --listen=10,11,12,3,4,5,6,7,8,9 --accepted=13 4007 mailman 0.01 0.71 /usr/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s 4009 mailman 0.01 0.71 /usr/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s For addtional details, see the attached dmesg log dump. Preview of "oom_dmesg.txt" [310592.457520] [ 624] 99 624 53670 3076 61 3 0 0 httpd [310592.461040] [ 625] 99 625 53670 3076 61 3 0 0 httpd [310592.464518] [ 626] 99 626 53670 3076 61 3 0 0 httpd [310592.468109] [ 627] 99 627 53670 3070 61 3 0 0 httpd [310592.471737] [ 628] 99 628 53670 3071 61 3 0 0 httpd [310592.475485] [ 629] 99 629 53670 3071 61 3 0 0 httpd [310592.479051] [ 630] 99 630 53670 3076 61 3 0 0 httpd [310592.482637] [ 631] 99 631 53670 3070 61 3 0 0 httpd [310592.486206] Out of memory: Kill process 22990 (cpbackup_transp) score 618 or sacrifice child [310592.489653] Killed process 22990 (cpbackup_transp) total-vm:2863200kB, anon-rss:2576220kB, file-rss:64kB, shmem-rss:0kB The system generated this notice on 2017-09-12 at 12:35:04 UTC.
    0
  • cPanelMichael
    Hello, Could you open a support ticket using the link in my signature so we can take a closer look? Thank you.
    0
  • jimhermann
    cPanelMichael, I don't see your signature or a link. Jim
    0
  • jimhermann
    cPanelMichael, I see your signature and link when using IE on my PC. It did not appear when using Safari on my iPhone. What is the Support Fee if I don't need phone support? AWS Technical Support recommended increasing the EC2 Instance from t2.medium (4 GB RAM) to t2.large (8 GB RAM), so I did. Also, I increased the Maximum cPanel Process Memory from 768 MB to 2048 MB. Thanks, Jim
    0
  • jimhermann
    Your Support Request ID is: 8863045
    0
  • jbourque
    I have been having this problem for the past few weeks every time my backups are being transported my server becomes unstable. I have been using Amazon WS for over a year and this has not been an issue, I'm now having to hard power my server in order to gain control. Has anyone found a solution to this? Joe
    0
  • jimhermann
    I had to increase my RAM to 16GB because the cpbackup_transp process uses 14 GB at times. Also, I increased my SWAP size to 8GB. I don't use compression. cPanel blamed the problem on large (20-30 GB) web sites AND on other processes, like MySQL. The transfer still takes 8 hours for 250 GB backup. Jim
    0
  • jimhermann
    Folks, cPanel Support recommended that I stop using AWS S3 storage (not an option) until the developers fix the problem with cPanel case ID CPANEL-160066. They said that there is a memory problem with the cpbackup_transp program. It keeping on using more and more memory as it runs and it takes hours and hours to complete. Today, it's been running for 9 hours for a 300 GB backup and is using 14 GB RAM (RSS). USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 16893 24.1 86.1 20000468 14157680 ? RN 02:47 131:07 cpbackup_transporter - Processing next task 'nuff said, Jim
    0
  • cPanelMichael
    Hello, I'll monitor internal case CPANEL-16066 and update this thread with more information as it becomes available. Thank you.
    0
  • mooseontheloose
    We've been using S3 for a couple years now without issue until recently. Now have all kind of memory issues.
    root 11843 13.5 53.1 15742860 13062672 ? RN 04:34 100:44 cpbackup_transporter - Processing next task
    You can guess when the issue started happening: 49111
    0
  • jimhermann
    Hello, I'll monitor internal case CPANEL-16066 and update this thread with more information as it becomes available. Thank you.

    Would it be possible to use the AWS Python program called aws? It can transfer data at 20-30 MiB/s. It only takes about 4 hours to transfer 330 GB of backup data. Thanks, Jim
    0
  • cPanelMichael
    Hello, There's no update to report on internal case CPANEL-16066 at this time. I'll continue to monitor the case and update this thread with new information as it becomes available.
    Would it be possible to use the AWS Python program called aws?

    Changes to how the Amazon transport works would require a feature request. You can open a feature request using the following URL: Submit A Feature Request Thank you.
    0
  • mooseontheloose
    Any updates on this? We had a server lock up due to the memory leak, forcing us to disable S3 backups.
    0
  • cPanelMichael
    Any updates on this?

    There are no new updates to report at this time. I'll update this thread as soon as an update is available. Thank you.
    0
  • Kelli
    Hi everyone, We're currently investigating this issue, looking for a root cause so that we know how to fix it. CPANEL-16066
    0
  • cPanelMichael
    Hello, To update, the source of the memory leak was identified and the resolution is now undergoing testing before it's released. I'll provide another update once the resolution is published. Thank you.
    0
  • cPanelMichael
    Hello, This is fixed in cPanel version 68.0.21 as part of the following case: Fixed case CPANEL-16066: Update cpanel-perl-524-IO-Socket-SSL to 2.047-3.cp1162. The full cPanel version 68 change log is available at:
    0

Please sign in to leave a comment.