jobs log not found about cronicle HOT 6 CLOSED

That log file is temporary, and only exists while the job is running, and only on the target server that is running the job. When the job completes, the log is "uploaded" into the storage system on the master server, and stored in S3, etc. and then deleted from local disk.

Even if you use the Filesystem Storage Plugin, the log file is still moved to its new home in the data directory, with a hashed file path.

If you want to get access to your completed job log files, navigate to the "Job Details" page in the UI, and click on the "View Full Log" link. Example URL:

http://mini.local:3012/api/app/get_job_log?id=jlpu8a5ar2z

from cronicle.

Thanks.
Where is path of this log file on the master server?
I want download this log with api and with json format
.

from cronicle.

You didn't say which Storage Plugin you are using. I'm assuming you are using the Filesystem Plugin?

If so, it's not that easy. As I said above, the files are stored in a hash file format tree, with hexadecimal directories. You should use the API, as I said above:

You can curl it like this:

curl -o LOG_FILE.txt "http://SERVER:PORT/api/app/get_job_log?id=JOB_ID"

Replace SERVER with your master server hostname, PORT with your port number (3012, etc.), and JOB_ID with the job ID. This will download the log file and store it wherever you want.

It is "very difficult" to get access to the raw files on the filesystem, when you are using the Filesystem Storage Plugin. They are stored in a cryptic, distributed, hashed file directory tree format like this:

/opt/cronicle/data/jobs/ff/ae/5a/ffae5a2df778d3780edf058aba5d0988.gz 

It is MUCH better to use the API as shown above.

from cronicle.

You didn't say which Storage Plugin you are using. I'm assuming you are using the Filesystem Plugin?

If so, it's not that easy. As I said above, the files are stored in a hash file format tree, with hexadecimal directories. You should use the API, as I said above:

You can curl it like this:

curl -o LOG_FILE.txt "http://SERVER:PORT/api/app/get_job_log?id=JOB_ID"

Replace SERVER with your master server hostname, PORT with your port number (3012, etc.), and JOB_ID with the job ID. This will download the log file and store it wherever you want.

It is "very difficult" to get access to the raw files on the filesystem, when you are using the Filesystem Storage Plugin. They are stored in a cryptic, distributed, hashed file directory tree format like this:

/opt/cronicle/data/jobs/ff/ae/5a/ffae5a2df778d3780edf058aba5d0988.gz 

It is MUCH better to use the API as shown above.

Thanks for you replay.
Curl can resolve my problem.

By the way.
In addition to Filesystem Storage, it also supports other Storage Plugin? Like MongoDB, MySQL, PostSQL and so on.

from cronicle.

In addition to Filesystem Storage, it also supports other Storage Plugin? Like MongoDB, MySQL, PostSQL and so on.

Currently S3 and Couchbase: https://github.com/jhuckaby/Cronicle/blob/master/docs/Configuration.md#storage-configuration

from cronicle.

In addition to Filesystem Storage, it also supports other Storage Plugin? Like MongoDB, MySQL, PostSQL and so on.

Currently S3 and Couchbase: https://github.com/jhuckaby/Cronicle/blob/master/docs/Configuration.md#storage-configuration

OK, Thanks.

from cronicle.