Opened 4 years ago

Closed 4 years ago

#1890 closed help (fixed)

fcm commit error: No space left on device

Reported by: csteadman Owned by: um_support
Component: UM Model Keywords:
Cc: Platform:
UM Version: <select version>

Description

Hello,

I'm trying to commit changes to a branch and got the following error:

csteadman@puma:/home/csteadman/FCM/vn8.4_classic_sulphr_nitrate_debug/src> fcm commit
[FAIL] /tmp/iBJZ5vTGnr: No space left on device

Thanks for your help.

Claudia

Change History (5)

comment:1 Changed 4 years ago by csteadman

I'm also getting an error when using the UMUI:

Error in startup script: error writing "file4": no space left on device

while executing

"puts -nonewline $fp $basis"

(procedure "get_basis_file" line 32)
invoked from within

"get_basis_file $exp_id $job_id $job_file $read_write"

invoked from within

"set writable [get_basis_file $exp_id $job_id $job_file $read_write]"

(file "/home/umui/umui/ghui2.0/vn1.4/tcl/edit_job.tcl" line 48)

comment:2 Changed 4 years ago by andy

  • Resolution set to fixed
  • Status changed from new to closed

Hi Claudia,

This should be okay now. The /tmp space on puma occasionally gets full and causes this problem. An hourly cron job removes old files from /tmp and clears the problem.

Regards
Andy

comment:3 Changed 4 years ago by csteadman

Hi Andy,

Thanks for your reply. I was able to commit jobs yesterday and today, but I've since run into the same error saying the disk is full again. I understand that there's a cron job that removes the files hourly, but I've been trying to run a job since 9:55 (it's 10:21 now). It seems like maybe there's an underlying issue, like there isn't enough of a safety margin in the system?

Cheers,
Claudia

comment:4 Changed 4 years ago by csteadman

  • Resolution fixed deleted
  • Status changed from closed to reopened

comment:5 Changed 4 years ago by andy

  • Resolution set to fixed
  • Status changed from reopened to closed

Hi Claudia,

The web server on Puma was taking all the space up in / for some reason and a restart seems to have fixed this. We are going to get a new Puma soon and will increase the space available in / to a more reasonable amount.

I'll mark this as fixed again but please reopen the ticket if you find it happens again.

Regards
Andy

Note: See TracTickets for help on using tickets.