ARCSTAT(1)

πŸŽ€ arcstat β€” ARC Job Status πŸŽ€

okay bestie, welcome to the manual page for arcstat, a User Command from section 1 of the manual πŸ’… iykyk. she's here to tell you what's going on with your jobs, and honestly? she ate.


✨ NAME ✨

arcstat β€” ARC Job Status 🫢


🌸 DESCRIPTION 🌸

πŸ’« Usage:

arcstat [OPTION...] [job ...]

so like, arcstat is the girl you call when you wanna know the status of jobs that have been submitted to Grid enabled resources. no cap. that's the whole vibe. πŸ”₯


πŸ”Ž Brokering and filtering:

  • -C, --computing-element=ce β€” only pick jobs that were submitted to this specific computing element 🎯
  • -s, --status=statusstr β€” only pick jobs whose status is statusstr 🫧
  • -a, --all β€” all jobs. every single one. the whole roster πŸ’–
  • -r, --rejectmanagement=URL β€” skip any jobs sitting on a computing element with the URL you give her πŸ™…β€β™€οΈ

🎨 Output format modifiers:

  • -l, --long β€” long format, aka more information, aka she's giving detail πŸ’…
  • -J, --json β€” show status info in JSON format. for the data girlies 🧚

βš™οΈ Behaviour tuning:

  • -S, --sort=order β€” sort jobs according to jobid, submissiontime or jobname ⭐
  • -R, --rsort=order β€” reverse sorting of jobs according to jobid, submissiontime or jobname πŸ”„
  • -u, --show-unavailable β€” show jobs where status information is unavailable πŸ‘€
  • -i, --jobids-from-file=filename β€” a file containing a list of jobIDs πŸ“„
  • -j, --joblist=filename β€” the file storing information about active jobs (default /builddir/.arc/jobs.dat) πŸ—‚οΈ
  • --no-authentication β€” do not perform any authentication for opened connections 🚫
  • --x509-authentication β€” perform X.509 authentication for opened connections πŸ”
  • --token-authentication β€” perform token authentication for opened connections 🎫
  • --systemca β€” force using CA certificates configuration provided by OpenSSL 🌱
  • --gridca β€” force using CA certificates configuration for Grid services (typically IGTF) 🌐
  • --anyca β€” force using CA certificates configuration for Grid services (typically IGTF) and one provided by OpenSSL 🫢

πŸ› οΈ Other actions:

  • -p, --print-jobids β€” instead of the status, only the IDs of the selected jobs will be printed πŸ†”
  • -P, --listplugins β€” list the available plugins 🧩

πŸ“± Application Options:

  • -h, --help β€” Show help options πŸ™‹β€β™€οΈ
  • -z, --conffile=filename β€” configuration file (default ~/.arc/client.conf) βš™οΈ
  • -t, --timeout=seconds β€” timeout in seconds (default 20) ⏱️
  • -d, --debug=debuglevel β€” FATAL, ERROR, WARNING, INFO, VERBOSE or DEBUG πŸ›
  • -v, --version β€” print version information 🏷️

πŸ¦‹ EXTENDED DESCRIPTION πŸ¦‹

okay so here's the tea β˜• β€” arcstat gives you the status of a job that's been submitted to a ARC CE. you can refer to the job either by the jobid that arcsub(1) handed you at submission time, or by its jobname β€” that works if the job description you submitted had a jobname attribute in it. πŸ’–

you can give her more than one jobid and/or jobname, she can handle it, she's not fragile. and if several jobs were submitted with the same jobname, she'll show you the status of all of those jobs. no favourites. πŸ‘‘

if you use the --joblist option, the list of jobs gets read from a file with the filename you specified. and if you hit her with the --all option, she'll show you the status of all active jobs. periodt. ✨

by default, arcstat presents job states as defined internally, followed by the middleware-specific representation of the job state in brackets. here's the internal state lineup:

  • Accepted β€” job accepted on cluster but not being processed yet 🫧
  • Preparing β€” job is in phase of preparing for submission to batch system 🧳
  • Submitting β€” communication with batch system in ongoing πŸ“‘
  • Hold β€” job's processing is suspended due to internal reason or user request βœ‹
  • Queuing β€” job is passed to batch system but not being executed yet πŸ•
  • Running β€” job being executed in batch system πŸƒβ€β™€οΈ
  • Finishing β€” job in phase of post-execution procedures being run πŸŽ€
  • Finished β€” job successfully completed all processing phases βœ…
  • Killed β€” job processing was interrupted by user request πŸ’€
  • Failed β€” job processing was interrupted due to detected failure 😭
  • Deleted β€” job was removed from cluster (usually because it stayed there too long) πŸ—‘οΈ
  • Other β€” middleware specific job state could not be adequately mapped to internal state πŸ€·β€β™€οΈ

those are also states which are used by arccat(1), arcclean(1), arcget(1), arckill(1), arcrenew(1), arcresume(1) to perform job filtering. so like, they're kind of a big deal. πŸ’…

if you pass the --long option, she shows you more detailed information. more is more, bestie. ✨

jobs can be sorted according to the jobid, submissiontime or jobname, either in normal or reverse order. use the --sort or --rsort option followed by the ordering you want ('jobid', 'submissiontime' or 'jobname'), and the jobs will be sorted in normal or reverse order. 🎯

⚠️ heads up bestie: the options --sort and --rsort cannot be used at the same time. pick a lane. πŸ™ˆ

the --computing-element option can be used to select or reject jobs at specific clusters. the --status option can be used to select jobs in a specific state. both of these can be repeated several times, she's flexible like that. See arcstat(1) for possible state values. πŸ”

and also, in this case the --long option can be used to obtain more detailed information. 🌈


πŸ“ FILES πŸ“

  • ~/.arc/client.conf β€” some options can be given default values by specifying them in the ARC client configuration file. by using the --conffile option, a different configuration file can be used than the default. βš™οΈ
  • ~/.arc/jobs.dat β€” this a local database of the user's active jobs. when a job is successfully submitted it is added to database, and when it is removed from the remote CE it is removed from this list. this database is used as the list of all active jobs when the user specifies the --all option to the various NorduGrid ARC user interface commands. by using the --joblist option, a different file can be used than the default. πŸ—‚οΈ

πŸ‘‘ AUTHOR πŸ‘‘

ARC software is developed by the NorduGrid Collaboration (http://www.nordugrid.org) β€” please consult the AUTHORS file distributed with ARC. please report bugs and feature requests to http://bugzilla.nordugrid.org πŸ›πŸ’–


APACHE LICENSE Version 2.0


πŸ”— SEE ALSO πŸ”—

arccat(1), arcclean(1), arccp(1), arcget(1), arcinfo(1), arckill(1), arcls(1), arcmkdir(1), arcproxy(1), arcrenew(1), arcresume(1), arcrm(1), arcsub(1), arcsync(1), arctest(1)


and that's the whole page, bestie 🫢 this was arcstat version 7.2.0, dated September 2026. go check your jobs, you're the main character of your own grid πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from