Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set CA state to Error when there's insufficient free disk space #438

Closed
smarquard opened this issue Oct 11, 2016 · 3 comments
Closed

Set CA state to Error when there's insufficient free disk space #438

smarquard opened this issue Oct 11, 2016 · 3 comments
Assignees
Milestone

Comments

@smarquard
Copy link

If there's not enough free disk space available for Galicaster, it would be preferable for the CA to change its state to error rather than idle (resulting in an Opencast status of unknown being set for the CA).

I have experimented with a plugin to check the available free space:

https://bitbucket.org/cilt/matterhorn_ansible/raw/cc0d3a4d0721f41c3275406f50ac2c73868bd59c/templates/gc2x/checkspace.py

Configure in conf-dist.ini, with

[plugins]
checkspace = True
...

[checkspace]
minfreespace=100
checkoninit=true

(minfreespace in GB)

but I can't see an easy way for the plugin to change the CA state to error when there's insufficient space (specifically __set_status is a private method).

@dpeite dpeite added feature and removed bug labels Mar 23, 2017
@dpeite dpeite added this to the 2.0.1 milestone Mar 23, 2017
dpeite added a commit that referenced this issue Mar 23, 2017
Checks if it's enough space in disk, if not, error status is set.
dpeite added a commit that referenced this issue Mar 23, 2017
dpeite added a commit that referenced this issue Mar 24, 2017
@Alfro Alfro removed this from the 2.0.1 milestone Apr 3, 2017
@silviabf
Copy link

silviabf commented Jul 5, 2017

The plugin works correctly with unscheduled recordings, but if you scheduled a recording and there is no space: the error is delete when the recording begins, the CA records correctly and after the stop the error is shown again.

@smarquard
Copy link
Author

That sounds like it might be useful: if you have a threshold of say 50G then a scheduled recording could still succeed and it would be better to try than not try at all.

@Alfro Alfro added this to the 2.1.0 milestone Jan 25, 2018
@Alfro
Copy link
Contributor

Alfro commented Jan 25, 2018

I'm closing this. Considering @smarquard answer to @silviabf comment, it's probably better to leave it as-is, as the QA seemed satisfactory.

@Alfro Alfro closed this as completed Jan 25, 2018
Alfro added a commit to teltek/Galicaster-doc that referenced this issue Feb 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants