Skip to content

Latest commit

History

9 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

Continuous heritrix shell suite (CHSS)

  • Developed and used for basic automation of continuous heritrix jobs from 2020/05, till 2022, with dedicated virtual machines / containers heritrix instances in Webarchive CZ.

1. Deployement and usage of CHSS

1.1.Prerequisities

  • Running on single VM/container and in single instance
    • Dedicated heritrix user
    • Accessible cron for dedicated user
      • Installation of Java
    • Installation of Heritrix vs. 3
  • necessary to set up with all system links / FS shares during deploy of crawling server and installation of heritrix engine are not part of this readme
  • for more complex jobs, should be used DB templates, AMQP protocols and asynchronous event processing

1.2. Structure of dirs

  • Continuous suite is composed of several scripts and specialised functions for passive monitoring and simple running of continuous crawls with high intensisty
  • Consists of:
    • project directory - Specific continuous dir
      • stat-checks - Statistics samples logs dir
      • logs-runtime - Runtime logs dir
    • central directory - General dir for all projects
    • archival directory - structure not included here, dependent on each case and overall archival strategy, also as FS structure

1.3. Basic operation

    1. pull and deploy
cd <Crawler-config-dir>git clone https://github.com/WebarchivCZ/continuous-suite.gitcd continuous-suitemv project-dir <Project-dir>
    1. create new cron record
heritrix@crawler:~$ crontab -e6 4,9,13,17,21 * * * <project_dir>/continuous-suite.sh >> <project_dir>/logs_runtime/<project_name>-cs-`date +\%Y\%m`.log 2>&1
    1. before running, it is necessary to configure paths and variables (see lower, in 2. Customisations)

2. Customisations

2.1. Project directory of continuous crawl

  • main project directory and settings for each continuous project
    • for each instance of continuous crawl create own directory
  • necessary to set up project path: /
  • installation
    • by deploying project-dir for concrete continuous type project
cd <Project-dir> lscontinuous-suite.sh # Main running script, flow of eventssettings-continuous.cfg.sh # Main settings, sourcingseeds.txt # Actual seeds - could be customised, eg. tsv importstat-checks # Directory for aggregated crawl sample statistics in tsv format, eg. Continuous-Cov19-2023-02-01-Cov19.techlog.tsv runtime-logs #Logs of cron runtime

2.1.1. File settings-continuous.cfg.sh

  • main settings for crawler and crawl settings and continuous-suite
    • important - fill up with actual paths and dates
      • specification - typ - Key identifier composed from Type_ProjectName - expecting same as project directory
    • logins and passes set up in local .sh, not here
  • settings categories
    • Crawler variables and paths
    • Crawl Metadata
      • Dates (authomatic)
      • Project
      • important - typ - Key identifier composed from Type_ProjectName - expecting same as project directory
        • Paths
        • Organizational
    • Crawl Quantitative - Dynamic crawler values
    • Seeds source - TSV
    • Stats

2.1.2 File continuous-suite.sh

  • main script with event flow and crawler set up and app logic
  • uses other supporting scripts:
    • project dir
      • settings-continuous.cfg.sh
      • crawler-beans.template
    • central dir
      • start-crawler.sh
      • stat-checker.sh
    • archive dir
      • archive_logs.sh
  • on first deploy:
    • change target for sourcing settings-continuous.cfg.sh after project path: source <Crawler-config-dir>/continuous-suite/<Project-dir>
  • structure:
      1. Initiation of variables
      1. Functions defintions
      • helping functions
      1. Seeds reactualization
      • reactualization of seedsm otpional
    • 4.A Crawl Initiation - Set up deploy
      • deploy crawler-beans.cxml after actual variables
    • 4.B Crawl Initiation - Crawler initiation
      • restart of heritrix crawler
      1. Crawl - Basic Event Flow
      1. Archiving and operationa logs cleaning
  • actual crawl flow accords to basic sequential crawl flow
    • Crawl Initiation
    • Crawl Launch
    • Crawl Unpausing - here depends at crawler setting
    • Crawl Runnning
    • Crawl Termination
    • Crawl Teardown

2.1.3 File crawler-beans.template

  • supporting template file for crawl
  • on deploy:
    • necessary credentials - either include own or comment it
      • for domain facebook.com
        • ,
      • for domain twitter.com
        • ,
      • etc. set up credentialStore
    • customize local beans (ad hoc)
      • rejectLocalCalendars.regexList
      • surtPrefixes
      • rejectLocalCalendars-sheet
      • rejectLocalTraps-sheet
      • SurtPrefixesSheetAssociation
  • structure of main settings and their template (change only ad hoc project / project type / structure)
    • basic settings
      • metadata.jobName=%TYP% %DNES%-%SHORT_N%
      • metadata.operator=%ACTUAL_OPERATOR%
      • metadata.description=%M_COMMENT%
      • warcWriter.prefix=%TYP%-%DNES%-%SHORT_N%_%CRAWLER_HOST%-
      • warcWriter.storePaths=%CORE_STORE%/%TYP_LC%/%TYP%-%DNES%-%SHORT_N%
    • duplication reduction and ops
      • historyBdb.dir=%CRAWLER_JOBS%/history/%YEAR%-history-state-year
      • bdb.dir=%CRAWLER_JOBS%/states/%TYP_LC%/%YEAR%
      • crawlController.scratchDir=%CRAWLER_JOBS%/scratchx%TYP_LC%
    • settings
      • frontier.balanceReplenishAmount=%BALANCE_REPLENISHAM%
      • crawlController.maxToeThreads=%MAX_TOETHREADS%
      • crawlLimiter.maxTimeSeconds=%MAX_TIMESECONDS%
      • #tooManyHopsDecideRule.maxHops=%MAX_HOPS%
      • #transclusionDecideRules.maxTransHops=%MAX_TRANSHOPS%
      • #transclusionDecideRules.maxSpeculativeHops=%MAX_SPECHOPS%
      • #scope.maxHops=%MAX_HOPS%
      • #scope.maxTransHops=%MAX_TRANSHOPS%
      • #scope.maxSpeculativeHops=%MAX_SPECHOPS%
      • warcWriter.poolMaxActive=%POOL_MAXACTIVE%
    • metadata
      • metadata.operatorContactUrl=%OPER_WEB%
      • metadata.operatorFrom=%OPER_MAIL%
      • metadata.organization=%OPER_ORGANIZATIONFULL%
      • metadata.audience=%OPER_AUDIENCE%
      • metadata.userAgentTemplate=%OPER_TEMPLATE%
    • storePaths
      • %CORE_STORE%/%TYP_LC%/%TYP%-%DNES%-%SHORT_N%

2.2 Central opt directory

  • contains scripts central to multipurpose use, not only
/opt/heritrixstart-crawler.sh # Crawler starting scriptstat-checker.sh # Statistics checking

2.2.1. File stat-checker.sh

  • creates statistic logs ".techlog.tsv"
  • usage:
    • automatical from continuous-script.sh
    • manual: <central-dir-path>/crawlchecker.sh <runtime_seconds> Continuous-Cov19-YYYY-MM-DD-Cov19 <ip_adress> <port>
  • set up variables
    • type, ip-adress, file_name, runtime in seconds are taken from Main settings (settings.topics.cfg.sh )
    runtime="${1} seconds"
    TYP=${2} # "Continuous-X"
    ADDRESS=${4}	# "IP adress X.X.X.X"
    PORT=${5} # port
    FName=${3}	# Path+Filename
    
    • login and password need to set up locally
    login="<actual-login>"
    pass="<actual-password>"
    

2.2.2. File start-crawler.sh

  • starts crawler with defined parametres
  • on deploy:
    • change <actual-crawler-login>,<actual-crawler-password>
  • usage:
    • automatical from continuous-script.sh
    • manual
    start-crawler.sh <crawler_ip> <port> <java-XmxInMB> <java-XmsInMB> <HERITRIX_HOME> <JAVA_HOME>

2.3. Archive dir

  • recommended strutcture for logging /mnt/archives/rok/continuous-name vcitane scriptu z toolboxu pre ukladanie logov

2.3.1. File archive_logs.sh

  • external script, created by R. Kreibich and updated by P. Habetinova
  • added for inspiration

3. Indexation and Publication

  • missing from scope of this project
  • it is dependent on indexation processess of project and archive needs

4. Logs structure

4.1. Runtime logs

  • basic process related structure with datetime

4.2. Structure of statisctic logs .tsv

  • samples by set up frequency, should cover main aspects of crawl runtime
| date | elapsedMilliseconds | lastReachedState | novel | dupByHash | warcNovelContentBytes | warcNovelUrls | activeQueues | snoozedQueues | exhaustedQueues | busyThreads | congestionRatio | currentKiBPerSec | currentDocsPerSecond | usedBytes | alertCount |
| ----- | ---------- | ---- | ---------- | ---------- | ---------- | ------ | ---- | ---- | ---- | ---- | --- | --- | ---- | --- | ------- | ---- |
| 09:09:32 | 33102 | PAUSE | 0 | 0 | | | 0 | 0 | 0 | 0 | | 0 | 0 | 1293253128 | 0 | | 09:10:34 | 93431 | RUN | 60365985 | 88987568 | 60366378 | 1392 | 492 | 229 | 120 | 150 | 12.997361 | 2124 | 35 | 1463790776 | 0 | | 09:11:38 | 155843 | RUN | 169967391 | 286983358 | 169967914 | 2711 | 596 | 396 | 194 | 150 | 10.399267 | 5432 | 98 | 1384826816 | 0 | | 09:12:40 | 218913 | RUN | 318117678 | 623741404 | 318118201 | 4458 | 712 | 542 | 295 | 150 | 9.520231 | 7712 | 102 | 3413708416 | 0 |

4.3. Other logs

  • accessible in archived crawl dirs, standardly created by heritrix

5. License

Continuous suite is free software; you can redistribute it and/or modify it under the terms of the GNU GPL 3, with reservation to secrets generally and path and date customisations in continuous-setting.cfg.sh.

About

Continuous heritrix shell suite (CHSS)

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
GitHub - WebarchivCZ/continuous-suite: Continuous heritrix shell suite (CHSS) · GitHub
Skip to content

Latest commit

History

9 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

Continuous heritrix shell suite (CHSS)

  • Developed and used for basic automation of continuous heritrix jobs from 2020/05, till 2022, with dedicated virtual machines / containers heritrix instances in Webarchive CZ.

1. Deployement and usage of CHSS

1.1.Prerequisities

  • Running on single VM/container and in single instance
    • Dedicated heritrix user
    • Accessible cron for dedicated user
      • Installation of Java
    • Installation of Heritrix vs. 3
  • necessary to set up with all system links / FS shares during deploy of crawling server and installation of heritrix engine are not part of this readme
  • for more complex jobs, should be used DB templates, AMQP protocols and asynchronous event processing

1.2. Structure of dirs

  • Continuous suite is composed of several scripts and specialised functions for passive monitoring and simple running of continuous crawls with high intensisty
  • Consists of:
    • project directory - Specific continuous dir
      • stat-checks - Statistics samples logs dir
      • logs-runtime - Runtime logs dir
    • central directory - General dir for all projects
    • archival directory - structure not included here, dependent on each case and overall archival strategy, also as FS structure

1.3. Basic operation

    1. pull and deploy
cd <Crawler-config-dir>git clone https://github.com/WebarchivCZ/continuous-suite.gitcd continuous-suitemv project-dir <Project-dir>
    1. create new cron record
heritrix@crawler:~$ crontab -e6 4,9,13,17,21 * * * <project_dir>/continuous-suite.sh >> <project_dir>/logs_runtime/<project_name>-cs-`date +\%Y\%m`.log 2>&1
    1. before running, it is necessary to configure paths and variables (see lower, in 2. Customisations)

2. Customisations

2.1. Project directory of continuous crawl

  • main project directory and settings for each continuous project
    • for each instance of continuous crawl create own directory
  • necessary to set up project path: /
  • installation
    • by deploying project-dir for concrete continuous type project
cd <Project-dir> lscontinuous-suite.sh # Main running script, flow of eventssettings-continuous.cfg.sh # Main settings, sourcingseeds.txt # Actual seeds - could be customised, eg. tsv importstat-checks # Directory for aggregated crawl sample statistics in tsv format, eg. Continuous-Cov19-2023-02-01-Cov19.techlog.tsv runtime-logs #Logs of cron runtime

2.1.1. File settings-continuous.cfg.sh

  • main settings for crawler and crawl settings and continuous-suite
    • important - fill up with actual paths and dates
      • specification - typ - Key identifier composed from Type_ProjectName - expecting same as project directory
    • logins and passes set up in local .sh, not here
  • settings categories
    • Crawler variables and paths
    • Crawl Metadata
      • Dates (authomatic)
      • Project
      • important - typ - Key identifier composed from Type_ProjectName - expecting same as project directory
        • Paths
        • Organizational
    • Crawl Quantitative - Dynamic crawler values
    • Seeds source - TSV
    • Stats

2.1.2 File continuous-suite.sh

  • main script with event flow and crawler set up and app logic
  • uses other supporting scripts:
    • project dir
      • settings-continuous.cfg.sh
      • crawler-beans.template
    • central dir
      • start-crawler.sh
      • stat-checker.sh
    • archive dir
      • archive_logs.sh
  • on first deploy:
    • change target for sourcing settings-continuous.cfg.sh after project path: source <Crawler-config-dir>/continuous-suite/<Project-dir>
  • structure:
      1. Initiation of variables
      1. Functions defintions
      • helping functions
      1. Seeds reactualization
      • reactualization of seedsm otpional
    • 4.A Crawl Initiation - Set up deploy
      • deploy crawler-beans.cxml after actual variables
    • 4.B Crawl Initiation - Crawler initiation
      • restart of heritrix crawler
      1. Crawl - Basic Event Flow
      1. Archiving and operationa logs cleaning
  • actual crawl flow accords to basic sequential crawl flow
    • Crawl Initiation
    • Crawl Launch
    • Crawl Unpausing - here depends at crawler setting
    • Crawl Runnning
    • Crawl Termination
    • Crawl Teardown

2.1.3 File crawler-beans.template

  • supporting template file for crawl
  • on deploy:
    • necessary credentials - either include own or comment it
      • for domain facebook.com
        • ,
      • for domain twitter.com
        • ,
      • etc. set up credentialStore
    • customize local beans (ad hoc)
      • rejectLocalCalendars.regexList
      • surtPrefixes
      • rejectLocalCalendars-sheet
      • rejectLocalTraps-sheet
      • SurtPrefixesSheetAssociation
  • structure of main settings and their template (change only ad hoc project / project type / structure)
    • basic settings
      • metadata.jobName=%TYP% %DNES%-%SHORT_N%
      • metadata.operator=%ACTUAL_OPERATOR%
      • metadata.description=%M_COMMENT%
      • warcWriter.prefix=%TYP%-%DNES%-%SHORT_N%_%CRAWLER_HOST%-
      • warcWriter.storePaths=%CORE_STORE%/%TYP_LC%/%TYP%-%DNES%-%SHORT_N%
    • duplication reduction and ops
      • historyBdb.dir=%CRAWLER_JOBS%/history/%YEAR%-history-state-year
      • bdb.dir=%CRAWLER_JOBS%/states/%TYP_LC%/%YEAR%
      • crawlController.scratchDir=%CRAWLER_JOBS%/scratchx%TYP_LC%
    • settings
      • frontier.balanceReplenishAmount=%BALANCE_REPLENISHAM%
      • crawlController.maxToeThreads=%MAX_TOETHREADS%
      • crawlLimiter.maxTimeSeconds=%MAX_TIMESECONDS%
      • #tooManyHopsDecideRule.maxHops=%MAX_HOPS%
      • #transclusionDecideRules.maxTransHops=%MAX_TRANSHOPS%
      • #transclusionDecideRules.maxSpeculativeHops=%MAX_SPECHOPS%
      • #scope.maxHops=%MAX_HOPS%
      • #scope.maxTransHops=%MAX_TRANSHOPS%
      • #scope.maxSpeculativeHops=%MAX_SPECHOPS%
      • warcWriter.poolMaxActive=%POOL_MAXACTIVE%
    • metadata
      • metadata.operatorContactUrl=%OPER_WEB%
      • metadata.operatorFrom=%OPER_MAIL%
      • metadata.organization=%OPER_ORGANIZATIONFULL%
      • metadata.audience=%OPER_AUDIENCE%
      • metadata.userAgentTemplate=%OPER_TEMPLATE%
    • storePaths
      • %CORE_STORE%/%TYP_LC%/%TYP%-%DNES%-%SHORT_N%

2.2 Central opt directory

  • contains scripts central to multipurpose use, not only
/opt/heritrixstart-crawler.sh # Crawler starting scriptstat-checker.sh # Statistics checking

2.2.1. File stat-checker.sh

  • creates statistic logs ".techlog.tsv"
  • usage:
    • automatical from continuous-script.sh
    • manual: <central-dir-path>/crawlchecker.sh <runtime_seconds> Continuous-Cov19-YYYY-MM-DD-Cov19 <ip_adress> <port>
  • set up variables
    • type, ip-adress, file_name, runtime in seconds are taken from Main settings (settings.topics.cfg.sh )
    runtime="${1} seconds"
    TYP=${2} # "Continuous-X"
    ADDRESS=${4}	# "IP adress X.X.X.X"
    PORT=${5} # port
    FName=${3}	# Path+Filename
    
    • login and password need to set up locally
    login="<actual-login>"
    pass="<actual-password>"
    

2.2.2. File start-crawler.sh

  • starts crawler with defined parametres
  • on deploy:
    • change <actual-crawler-login>,<actual-crawler-password>
  • usage:
    • automatical from continuous-script.sh
    • manual
    start-crawler.sh <crawler_ip> <port> <java-XmxInMB> <java-XmsInMB> <HERITRIX_HOME> <JAVA_HOME>

2.3. Archive dir

  • recommended strutcture for logging /mnt/archives/rok/continuous-name vcitane scriptu z toolboxu pre ukladanie logov

2.3.1. File archive_logs.sh

  • external script, created by R. Kreibich and updated by P. Habetinova
  • added for inspiration

3. Indexation and Publication

  • missing from scope of this project
  • it is dependent on indexation processess of project and archive needs

4. Logs structure

4.1. Runtime logs

  • basic process related structure with datetime

4.2. Structure of statisctic logs .tsv

  • samples by set up frequency, should cover main aspects of crawl runtime
| date | elapsedMilliseconds | lastReachedState | novel | dupByHash | warcNovelContentBytes | warcNovelUrls | activeQueues | snoozedQueues | exhaustedQueues | busyThreads | congestionRatio | currentKiBPerSec | currentDocsPerSecond | usedBytes | alertCount |
| ----- | ---------- | ---- | ---------- | ---------- | ---------- | ------ | ---- | ---- | ---- | ---- | --- | --- | ---- | --- | ------- | ---- |
| 09:09:32 | 33102 | PAUSE | 0 | 0 | | | 0 | 0 | 0 | 0 | | 0 | 0 | 1293253128 | 0 | | 09:10:34 | 93431 | RUN | 60365985 | 88987568 | 60366378 | 1392 | 492 | 229 | 120 | 150 | 12.997361 | 2124 | 35 | 1463790776 | 0 | | 09:11:38 | 155843 | RUN | 169967391 | 286983358 | 169967914 | 2711 | 596 | 396 | 194 | 150 | 10.399267 | 5432 | 98 | 1384826816 | 0 | | 09:12:40 | 218913 | RUN | 318117678 | 623741404 | 318118201 | 4458 | 712 | 542 | 295 | 150 | 9.520231 | 7712 | 102 | 3413708416 | 0 |

4.3. Other logs

  • accessible in archived crawl dirs, standardly created by heritrix

5. License

Continuous suite is free software; you can redistribute it and/or modify it under the terms of the GNU GPL 3, with reservation to secrets generally and path and date customisations in continuous-setting.cfg.sh.

About

Continuous heritrix shell suite (CHSS)

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - WebarchivCZ/continuous-suite: Continuous heritrix shell suite (CHSS) · GitHub
Skip to content

Latest commit

History

9 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

Continuous heritrix shell suite (CHSS)

  • Developed and used for basic automation of continuous heritrix jobs from 2020/05, till 2022, with dedicated virtual machines / containers heritrix instances in Webarchive CZ.

1. Deployement and usage of CHSS

1.1.Prerequisities

  • Running on single VM/container and in single instance
    • Dedicated heritrix user
    • Accessible cron for dedicated user
      • Installation of Java
    • Installation of Heritrix vs. 3
  • necessary to set up with all system links / FS shares during deploy of crawling server and installation of heritrix engine are not part of this readme
  • for more complex jobs, should be used DB templates, AMQP protocols and asynchronous event processing

1.2. Structure of dirs

  • Continuous suite is composed of several scripts and specialised functions for passive monitoring and simple running of continuous crawls with high intensisty
  • Consists of:
    • project directory - Specific continuous dir
      • stat-checks - Statistics samples logs dir
      • logs-runtime - Runtime logs dir
    • central directory - General dir for all projects
    • archival directory - structure not included here, dependent on each case and overall archival strategy, also as FS structure

1.3. Basic operation

    1. pull and deploy
cd <Crawler-config-dir>git clone https://github.com/WebarchivCZ/continuous-suite.gitcd continuous-suitemv project-dir <Project-dir>
    1. create new cron record
heritrix@crawler:~$ crontab -e6 4,9,13,17,21 * * * <project_dir>/continuous-suite.sh >> <project_dir>/logs_runtime/<project_name>-cs-`date +\%Y\%m`.log 2>&1
    1. before running, it is necessary to configure paths and variables (see lower, in 2. Customisations)

2. Customisations

2.1. Project directory of continuous crawl

  • main project directory and settings for each continuous project
    • for each instance of continuous crawl create own directory
  • necessary to set up project path: /
  • installation
    • by deploying project-dir for concrete continuous type project
cd <Project-dir> lscontinuous-suite.sh # Main running script, flow of eventssettings-continuous.cfg.sh # Main settings, sourcingseeds.txt # Actual seeds - could be customised, eg. tsv importstat-checks # Directory for aggregated crawl sample statistics in tsv format, eg. Continuous-Cov19-2023-02-01-Cov19.techlog.tsv runtime-logs #Logs of cron runtime

2.1.1. File settings-continuous.cfg.sh

  • main settings for crawler and crawl settings and continuous-suite
    • important - fill up with actual paths and dates
      • specification - typ - Key identifier composed from Type_ProjectName - expecting same as project directory
    • logins and passes set up in local .sh, not here
  • settings categories
    • Crawler variables and paths
    • Crawl Metadata
      • Dates (authomatic)
      • Project
      • important - typ - Key identifier composed from Type_ProjectName - expecting same as project directory
        • Paths
        • Organizational
    • Crawl Quantitative - Dynamic crawler values
    • Seeds source - TSV
    • Stats

2.1.2 File continuous-suite.sh

  • main script with event flow and crawler set up and app logic
  • uses other supporting scripts:
    • project dir
      • settings-continuous.cfg.sh
      • crawler-beans.template
    • central dir
      • start-crawler.sh
      • stat-checker.sh
    • archive dir
      • archive_logs.sh
  • on first deploy:
    • change target for sourcing settings-continuous.cfg.sh after project path: source <Crawler-config-dir>/continuous-suite/<Project-dir>
  • structure:
      1. Initiation of variables
      1. Functions defintions
      • helping functions
      1. Seeds reactualization
      • reactualization of seedsm otpional
    • 4.A Crawl Initiation - Set up deploy
      • deploy crawler-beans.cxml after actual variables
    • 4.B Crawl Initiation - Crawler initiation
      • restart of heritrix crawler
      1. Crawl - Basic Event Flow
      1. Archiving and operationa logs cleaning
  • actual crawl flow accords to basic sequential crawl flow
    • Crawl Initiation
    • Crawl Launch
    • Crawl Unpausing - here depends at crawler setting
    • Crawl Runnning
    • Crawl Termination
    • Crawl Teardown

2.1.3 File crawler-beans.template

  • supporting template file for crawl
  • on deploy:
    • necessary credentials - either include own or comment it
      • for domain facebook.com
        • ,
      • for domain twitter.com
        • ,
      • etc. set up credentialStore
    • customize local beans (ad hoc)
      • rejectLocalCalendars.regexList
      • surtPrefixes
      • rejectLocalCalendars-sheet
      • rejectLocalTraps-sheet
      • SurtPrefixesSheetAssociation
  • structure of main settings and their template (change only ad hoc project / project type / structure)
    • basic settings
      • metadata.jobName=%TYP% %DNES%-%SHORT_N%
      • metadata.operator=%ACTUAL_OPERATOR%
      • metadata.description=%M_COMMENT%
      • warcWriter.prefix=%TYP%-%DNES%-%SHORT_N%_%CRAWLER_HOST%-
      • warcWriter.storePaths=%CORE_STORE%/%TYP_LC%/%TYP%-%DNES%-%SHORT_N%
    • duplication reduction and ops
      • historyBdb.dir=%CRAWLER_JOBS%/history/%YEAR%-history-state-year
      • bdb.dir=%CRAWLER_JOBS%/states/%TYP_LC%/%YEAR%
      • crawlController.scratchDir=%CRAWLER_JOBS%/scratchx%TYP_LC%
    • settings
      • frontier.balanceReplenishAmount=%BALANCE_REPLENISHAM%
      • crawlController.maxToeThreads=%MAX_TOETHREADS%
      • crawlLimiter.maxTimeSeconds=%MAX_TIMESECONDS%
      • #tooManyHopsDecideRule.maxHops=%MAX_HOPS%
      • #transclusionDecideRules.maxTransHops=%MAX_TRANSHOPS%
      • #transclusionDecideRules.maxSpeculativeHops=%MAX_SPECHOPS%
      • #scope.maxHops=%MAX_HOPS%
      • #scope.maxTransHops=%MAX_TRANSHOPS%
      • #scope.maxSpeculativeHops=%MAX_SPECHOPS%
      • warcWriter.poolMaxActive=%POOL_MAXACTIVE%
    • metadata
      • metadata.operatorContactUrl=%OPER_WEB%
      • metadata.operatorFrom=%OPER_MAIL%
      • metadata.organization=%OPER_ORGANIZATIONFULL%
      • metadata.audience=%OPER_AUDIENCE%
      • metadata.userAgentTemplate=%OPER_TEMPLATE%
    • storePaths
      • %CORE_STORE%/%TYP_LC%/%TYP%-%DNES%-%SHORT_N%

2.2 Central opt directory

  • contains scripts central to multipurpose use, not only
/opt/heritrixstart-crawler.sh # Crawler starting scriptstat-checker.sh # Statistics checking

2.2.1. File stat-checker.sh

  • creates statistic logs ".techlog.tsv"
  • usage:
    • automatical from continuous-script.sh
    • manual: <central-dir-path>/crawlchecker.sh <runtime_seconds> Continuous-Cov19-YYYY-MM-DD-Cov19 <ip_adress> <port>
  • set up variables
    • type, ip-adress, file_name, runtime in seconds are taken from Main settings (settings.topics.cfg.sh )
    runtime="${1} seconds"
    TYP=${2} # "Continuous-X"
    ADDRESS=${4}	# "IP adress X.X.X.X"
    PORT=${5} # port
    FName=${3}	# Path+Filename
    
    • login and password need to set up locally
    login="<actual-login>"
    pass="<actual-password>"
    

2.2.2. File start-crawler.sh

  • starts crawler with defined parametres
  • on deploy:
    • change <actual-crawler-login>,<actual-crawler-password>
  • usage:
    • automatical from continuous-script.sh
    • manual
    start-crawler.sh <crawler_ip> <port> <java-XmxInMB> <java-XmsInMB> <HERITRIX_HOME> <JAVA_HOME>

2.3. Archive dir

  • recommended strutcture for logging /mnt/archives/rok/continuous-name vcitane scriptu z toolboxu pre ukladanie logov

2.3.1. File archive_logs.sh

  • external script, created by R. Kreibich and updated by P. Habetinova
  • added for inspiration

3. Indexation and Publication

  • missing from scope of this project
  • it is dependent on indexation processess of project and archive needs

4. Logs structure

4.1. Runtime logs

  • basic process related structure with datetime

4.2. Structure of statisctic logs .tsv

  • samples by set up frequency, should cover main aspects of crawl runtime
| date | elapsedMilliseconds | lastReachedState | novel | dupByHash | warcNovelContentBytes | warcNovelUrls | activeQueues | snoozedQueues | exhaustedQueues | busyThreads | congestionRatio | currentKiBPerSec | currentDocsPerSecond | usedBytes | alertCount |
| ----- | ---------- | ---- | ---------- | ---------- | ---------- | ------ | ---- | ---- | ---- | ---- | --- | --- | ---- | --- | ------- | ---- |
| 09:09:32 | 33102 | PAUSE | 0 | 0 | | | 0 | 0 | 0 | 0 | | 0 | 0 | 1293253128 | 0 | | 09:10:34 | 93431 | RUN | 60365985 | 88987568 | 60366378 | 1392 | 492 | 229 | 120 | 150 | 12.997361 | 2124 | 35 | 1463790776 | 0 | | 09:11:38 | 155843 | RUN | 169967391 | 286983358 | 169967914 | 2711 | 596 | 396 | 194 | 150 | 10.399267 | 5432 | 98 | 1384826816 | 0 | | 09:12:40 | 218913 | RUN | 318117678 | 623741404 | 318118201 | 4458 | 712 | 542 | 295 | 150 | 9.520231 | 7712 | 102 | 3413708416 | 0 |

4.3. Other logs

  • accessible in archived crawl dirs, standardly created by heritrix

5. License

Continuous suite is free software; you can redistribute it and/or modify it under the terms of the GNU GPL 3, with reservation to secrets generally and path and date customisations in continuous-setting.cfg.sh.

About

Continuous heritrix shell suite (CHSS)

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - WebarchivCZ/continuous-suite: Continuous heritrix shell suite (CHSS) · GitHub
Skip to content

Latest commit

History

9 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

Continuous heritrix shell suite (CHSS)

  • Developed and used for basic automation of continuous heritrix jobs from 2020/05, till 2022, with dedicated virtual machines / containers heritrix instances in Webarchive CZ.

1. Deployement and usage of CHSS

1.1.Prerequisities

  • Running on single VM/container and in single instance
    • Dedicated heritrix user
    • Accessible cron for dedicated user
      • Installation of Java
    • Installation of Heritrix vs. 3
  • necessary to set up with all system links / FS shares during deploy of crawling server and installation of heritrix engine are not part of this readme
  • for more complex jobs, should be used DB templates, AMQP protocols and asynchronous event processing

1.2. Structure of dirs

  • Continuous suite is composed of several scripts and specialised functions for passive monitoring and simple running of continuous crawls with high intensisty
  • Consists of:
    • project directory - Specific continuous dir
      • stat-checks - Statistics samples logs dir
      • logs-runtime - Runtime logs dir
    • central directory - General dir for all projects
    • archival directory - structure not included here, dependent on each case and overall archival strategy, also as FS structure

1.3. Basic operation

    1. pull and deploy
cd <Crawler-config-dir>git clone https://github.com/WebarchivCZ/continuous-suite.gitcd continuous-suitemv project-dir <Project-dir>
    1. create new cron record
heritrix@crawler:~$ crontab -e6 4,9,13,17,21 * * * <project_dir>/continuous-suite.sh >> <project_dir>/logs_runtime/<project_name>-cs-`date +\%Y\%m`.log 2>&1
    1. before running, it is necessary to configure paths and variables (see lower, in 2. Customisations)

2. Customisations

2.1. Project directory of continuous crawl

  • main project directory and settings for each continuous project
    • for each instance of continuous crawl create own directory
  • necessary to set up project path: /
  • installation
    • by deploying project-dir for concrete continuous type project
cd <Project-dir> lscontinuous-suite.sh # Main running script, flow of eventssettings-continuous.cfg.sh # Main settings, sourcingseeds.txt # Actual seeds - could be customised, eg. tsv importstat-checks # Directory for aggregated crawl sample statistics in tsv format, eg. Continuous-Cov19-2023-02-01-Cov19.techlog.tsv runtime-logs #Logs of cron runtime

2.1.1. File settings-continuous.cfg.sh

  • main settings for crawler and crawl settings and continuous-suite
    • important - fill up with actual paths and dates
      • specification - typ - Key identifier composed from Type_ProjectName - expecting same as project directory
    • logins and passes set up in local .sh, not here
  • settings categories
    • Crawler variables and paths
    • Crawl Metadata
      • Dates (authomatic)
      • Project
      • important - typ - Key identifier composed from Type_ProjectName - expecting same as project directory
        • Paths
        • Organizational
    • Crawl Quantitative - Dynamic crawler values
    • Seeds source - TSV
    • Stats

2.1.2 File continuous-suite.sh

  • main script with event flow and crawler set up and app logic
  • uses other supporting scripts:
    • project dir
      • settings-continuous.cfg.sh
      • crawler-beans.template
    • central dir
      • start-crawler.sh
      • stat-checker.sh
    • archive dir
      • archive_logs.sh
  • on first deploy:
    • change target for sourcing settings-continuous.cfg.sh after project path: source <Crawler-config-dir>/continuous-suite/<Project-dir>
  • structure:
      1. Initiation of variables
      1. Functions defintions
      • helping functions
      1. Seeds reactualization
      • reactualization of seedsm otpional
    • 4.A Crawl Initiation - Set up deploy
      • deploy crawler-beans.cxml after actual variables
    • 4.B Crawl Initiation - Crawler initiation
      • restart of heritrix crawler
      1. Crawl - Basic Event Flow
      1. Archiving and operationa logs cleaning
  • actual crawl flow accords to basic sequential crawl flow
    • Crawl Initiation
    • Crawl Launch
    • Crawl Unpausing - here depends at crawler setting
    • Crawl Runnning
    • Crawl Termination
    • Crawl Teardown

2.1.3 File crawler-beans.template

  • supporting template file for crawl
  • on deploy:
    • necessary credentials - either include own or comment it
      • for domain facebook.com
        • ,
      • for domain twitter.com
        • ,
      • etc. set up credentialStore
    • customize local beans (ad hoc)
      • rejectLocalCalendars.regexList
      • surtPrefixes
      • rejectLocalCalendars-sheet
      • rejectLocalTraps-sheet
      • SurtPrefixesSheetAssociation
  • structure of main settings and their template (change only ad hoc project / project type / structure)
    • basic settings
      • metadata.jobName=%TYP% %DNES%-%SHORT_N%
      • metadata.operator=%ACTUAL_OPERATOR%
      • metadata.description=%M_COMMENT%
      • warcWriter.prefix=%TYP%-%DNES%-%SHORT_N%_%CRAWLER_HOST%-
      • warcWriter.storePaths=%CORE_STORE%/%TYP_LC%/%TYP%-%DNES%-%SHORT_N%
    • duplication reduction and ops
      • historyBdb.dir=%CRAWLER_JOBS%/history/%YEAR%-history-state-year
      • bdb.dir=%CRAWLER_JOBS%/states/%TYP_LC%/%YEAR%
      • crawlController.scratchDir=%CRAWLER_JOBS%/scratchx%TYP_LC%
    • settings
      • frontier.balanceReplenishAmount=%BALANCE_REPLENISHAM%
      • crawlController.maxToeThreads=%MAX_TOETHREADS%
      • crawlLimiter.maxTimeSeconds=%MAX_TIMESECONDS%
      • #tooManyHopsDecideRule.maxHops=%MAX_HOPS%
      • #transclusionDecideRules.maxTransHops=%MAX_TRANSHOPS%
      • #transclusionDecideRules.maxSpeculativeHops=%MAX_SPECHOPS%
      • #scope.maxHops=%MAX_HOPS%
      • #scope.maxTransHops=%MAX_TRANSHOPS%
      • #scope.maxSpeculativeHops=%MAX_SPECHOPS%
      • warcWriter.poolMaxActive=%POOL_MAXACTIVE%
    • metadata
      • metadata.operatorContactUrl=%OPER_WEB%
      • metadata.operatorFrom=%OPER_MAIL%
      • metadata.organization=%OPER_ORGANIZATIONFULL%
      • metadata.audience=%OPER_AUDIENCE%
      • metadata.userAgentTemplate=%OPER_TEMPLATE%
    • storePaths
      • %CORE_STORE%/%TYP_LC%/%TYP%-%DNES%-%SHORT_N%

2.2 Central opt directory

  • contains scripts central to multipurpose use, not only
/opt/heritrixstart-crawler.sh # Crawler starting scriptstat-checker.sh # Statistics checking

2.2.1. File stat-checker.sh

  • creates statistic logs ".techlog.tsv"
  • usage:
    • automatical from continuous-script.sh
    • manual: <central-dir-path>/crawlchecker.sh <runtime_seconds> Continuous-Cov19-YYYY-MM-DD-Cov19 <ip_adress> <port>
  • set up variables
    • type, ip-adress, file_name, runtime in seconds are taken from Main settings (settings.topics.cfg.sh )
    runtime="${1} seconds"
    TYP=${2} # "Continuous-X"
    ADDRESS=${4}	# "IP adress X.X.X.X"
    PORT=${5} # port
    FName=${3}	# Path+Filename
    
    • login and password need to set up locally
    login="<actual-login>"
    pass="<actual-password>"
    

2.2.2. File start-crawler.sh

  • starts crawler with defined parametres
  • on deploy:
    • change <actual-crawler-login>,<actual-crawler-password>
  • usage:
    • automatical from continuous-script.sh
    • manual
    start-crawler.sh <crawler_ip> <port> <java-XmxInMB> <java-XmsInMB> <HERITRIX_HOME> <JAVA_HOME>

2.3. Archive dir

  • recommended strutcture for logging /mnt/archives/rok/continuous-name vcitane scriptu z toolboxu pre ukladanie logov

2.3.1. File archive_logs.sh

  • external script, created by R. Kreibich and updated by P. Habetinova
  • added for inspiration

3. Indexation and Publication

  • missing from scope of this project
  • it is dependent on indexation processess of project and archive needs

4. Logs structure

4.1. Runtime logs

  • basic process related structure with datetime

4.2. Structure of statisctic logs .tsv

  • samples by set up frequency, should cover main aspects of crawl runtime
| date | elapsedMilliseconds | lastReachedState | novel | dupByHash | warcNovelContentBytes | warcNovelUrls | activeQueues | snoozedQueues | exhaustedQueues | busyThreads | congestionRatio | currentKiBPerSec | currentDocsPerSecond | usedBytes | alertCount |
| ----- | ---------- | ---- | ---------- | ---------- | ---------- | ------ | ---- | ---- | ---- | ---- | --- | --- | ---- | --- | ------- | ---- |
| 09:09:32 | 33102 | PAUSE | 0 | 0 | | | 0 | 0 | 0 | 0 | | 0 | 0 | 1293253128 | 0 | | 09:10:34 | 93431 | RUN | 60365985 | 88987568 | 60366378 | 1392 | 492 | 229 | 120 | 150 | 12.997361 | 2124 | 35 | 1463790776 | 0 | | 09:11:38 | 155843 | RUN | 169967391 | 286983358 | 169967914 | 2711 | 596 | 396 | 194 | 150 | 10.399267 | 5432 | 98 | 1384826816 | 0 | | 09:12:40 | 218913 | RUN | 318117678 | 623741404 | 318118201 | 4458 | 712 | 542 | 295 | 150 | 9.520231 | 7712 | 102 | 3413708416 | 0 |

4.3. Other logs

  • accessible in archived crawl dirs, standardly created by heritrix

5. License

Continuous suite is free software; you can redistribute it and/or modify it under the terms of the GNU GPL 3, with reservation to secrets generally and path and date customisations in continuous-setting.cfg.sh.

About

Continuous heritrix shell suite (CHSS)

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' GitHub - WebarchivCZ/continuous-suite: Continuous heritrix shell suite (CHSS) · GitHub
Skip to content

Latest commit

History

9 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

Continuous heritrix shell suite (CHSS)

  • Developed and used for basic automation of continuous heritrix jobs from 2020/05, till 2022, with dedicated virtual machines / containers heritrix instances in Webarchive CZ.

1. Deployement and usage of CHSS

1.1.Prerequisities

  • Running on single VM/container and in single instance
    • Dedicated heritrix user
    • Accessible cron for dedicated user
      • Installation of Java
    • Installation of Heritrix vs. 3
  • necessary to set up with all system links / FS shares during deploy of crawling server and installation of heritrix engine are not part of this readme
  • for more complex jobs, should be used DB templates, AMQP protocols and asynchronous event processing

1.2. Structure of dirs

  • Continuous suite is composed of several scripts and specialised functions for passive monitoring and simple running of continuous crawls with high intensisty
  • Consists of:
    • project directory - Specific continuous dir
      • stat-checks - Statistics samples logs dir
      • logs-runtime - Runtime logs dir
    • central directory - General dir for all projects
    • archival directory - structure not included here, dependent on each case and overall archival strategy, also as FS structure

1.3. Basic operation

    1. pull and deploy
cd <Crawler-config-dir>git clone https://github.com/WebarchivCZ/continuous-suite.gitcd continuous-suitemv project-dir <Project-dir>
    1. create new cron record
heritrix@crawler:~$ crontab -e6 4,9,13,17,21 * * * <project_dir>/continuous-suite.sh >> <project_dir>/logs_runtime/<project_name>-cs-`date +\%Y\%m`.log 2>&1
    1. before running, it is necessary to configure paths and variables (see lower, in 2. Customisations)

2. Customisations

2.1. Project directory of continuous crawl

  • main project directory and settings for each continuous project
    • for each instance of continuous crawl create own directory
  • necessary to set up project path: /
  • installation
    • by deploying project-dir for concrete continuous type project
cd <Project-dir> lscontinuous-suite.sh # Main running script, flow of eventssettings-continuous.cfg.sh # Main settings, sourcingseeds.txt # Actual seeds - could be customised, eg. tsv importstat-checks # Directory for aggregated crawl sample statistics in tsv format, eg. Continuous-Cov19-2023-02-01-Cov19.techlog.tsv runtime-logs #Logs of cron runtime

2.1.1. File settings-continuous.cfg.sh

  • main settings for crawler and crawl settings and continuous-suite
    • important - fill up with actual paths and dates
      • specification - typ - Key identifier composed from Type_ProjectName - expecting same as project directory
    • logins and passes set up in local .sh, not here
  • settings categories
    • Crawler variables and paths
    • Crawl Metadata
      • Dates (authomatic)
      • Project
      • important - typ - Key identifier composed from Type_ProjectName - expecting same as project directory
        • Paths
        • Organizational
    • Crawl Quantitative - Dynamic crawler values
    • Seeds source - TSV
    • Stats

2.1.2 File continuous-suite.sh

  • main script with event flow and crawler set up and app logic
  • uses other supporting scripts:
    • project dir
      • settings-continuous.cfg.sh
      • crawler-beans.template
    • central dir
      • start-crawler.sh
      • stat-checker.sh
    • archive dir
      • archive_logs.sh
  • on first deploy:
    • change target for sourcing settings-continuous.cfg.sh after project path: source <Crawler-config-dir>/continuous-suite/<Project-dir>
  • structure:
      1. Initiation of variables
      1. Functions defintions
      • helping functions
      1. Seeds reactualization
      • reactualization of seedsm otpional
    • 4.A Crawl Initiation - Set up deploy
      • deploy crawler-beans.cxml after actual variables
    • 4.B Crawl Initiation - Crawler initiation
      • restart of heritrix crawler
      1. Crawl - Basic Event Flow
      1. Archiving and operationa logs cleaning
  • actual crawl flow accords to basic sequential crawl flow
    • Crawl Initiation
    • Crawl Launch
    • Crawl Unpausing - here depends at crawler setting
    • Crawl Runnning
    • Crawl Termination
    • Crawl Teardown

2.1.3 File crawler-beans.template

  • supporting template file for crawl
  • on deploy:
    • necessary credentials - either include own or comment it
      • for domain facebook.com
        • ,
      • for domain twitter.com
        • ,
      • etc. set up credentialStore
    • customize local beans (ad hoc)
      • rejectLocalCalendars.regexList
      • surtPrefixes
      • rejectLocalCalendars-sheet
      • rejectLocalTraps-sheet
      • SurtPrefixesSheetAssociation
  • structure of main settings and their template (change only ad hoc project / project type / structure)
    • basic settings
      • metadata.jobName=%TYP% %DNES%-%SHORT_N%
      • metadata.operator=%ACTUAL_OPERATOR%
      • metadata.description=%M_COMMENT%
      • warcWriter.prefix=%TYP%-%DNES%-%SHORT_N%_%CRAWLER_HOST%-
      • warcWriter.storePaths=%CORE_STORE%/%TYP_LC%/%TYP%-%DNES%-%SHORT_N%
    • duplication reduction and ops
      • historyBdb.dir=%CRAWLER_JOBS%/history/%YEAR%-history-state-year
      • bdb.dir=%CRAWLER_JOBS%/states/%TYP_LC%/%YEAR%
      • crawlController.scratchDir=%CRAWLER_JOBS%/scratchx%TYP_LC%
    • settings
      • frontier.balanceReplenishAmount=%BALANCE_REPLENISHAM%
      • crawlController.maxToeThreads=%MAX_TOETHREADS%
      • crawlLimiter.maxTimeSeconds=%MAX_TIMESECONDS%
      • #tooManyHopsDecideRule.maxHops=%MAX_HOPS%
      • #transclusionDecideRules.maxTransHops=%MAX_TRANSHOPS%
      • #transclusionDecideRules.maxSpeculativeHops=%MAX_SPECHOPS%
      • #scope.maxHops=%MAX_HOPS%
      • #scope.maxTransHops=%MAX_TRANSHOPS%
      • #scope.maxSpeculativeHops=%MAX_SPECHOPS%
      • warcWriter.poolMaxActive=%POOL_MAXACTIVE%
    • metadata
      • metadata.operatorContactUrl=%OPER_WEB%
      • metadata.operatorFrom=%OPER_MAIL%
      • metadata.organization=%OPER_ORGANIZATIONFULL%
      • metadata.audience=%OPER_AUDIENCE%
      • metadata.userAgentTemplate=%OPER_TEMPLATE%
    • storePaths
      • %CORE_STORE%/%TYP_LC%/%TYP%-%DNES%-%SHORT_N%

2.2 Central opt directory

  • contains scripts central to multipurpose use, not only
/opt/heritrixstart-crawler.sh # Crawler starting scriptstat-checker.sh # Statistics checking

2.2.1. File stat-checker.sh

  • creates statistic logs ".techlog.tsv"
  • usage:
    • automatical from continuous-script.sh
    • manual: <central-dir-path>/crawlchecker.sh <runtime_seconds> Continuous-Cov19-YYYY-MM-DD-Cov19 <ip_adress> <port>
  • set up variables
    • type, ip-adress, file_name, runtime in seconds are taken from Main settings (settings.topics.cfg.sh )
    runtime="${1} seconds"
    TYP=${2} # "Continuous-X"
    ADDRESS=${4}	# "IP adress X.X.X.X"
    PORT=${5} # port
    FName=${3}	# Path+Filename
    
    • login and password need to set up locally
    login="<actual-login>"
    pass="<actual-password>"
    

2.2.2. File start-crawler.sh

  • starts crawler with defined parametres
  • on deploy:
    • change <actual-crawler-login>,<actual-crawler-password>
  • usage:
    • automatical from continuous-script.sh
    • manual
    start-crawler.sh <crawler_ip> <port> <java-XmxInMB> <java-XmsInMB> <HERITRIX_HOME> <JAVA_HOME>

2.3. Archive dir

  • recommended strutcture for logging /mnt/archives/rok/continuous-name vcitane scriptu z toolboxu pre ukladanie logov

2.3.1. File archive_logs.sh

  • external script, created by R. Kreibich and updated by P. Habetinova
  • added for inspiration

3. Indexation and Publication

  • missing from scope of this project
  • it is dependent on indexation processess of project and archive needs

4. Logs structure

4.1. Runtime logs

  • basic process related structure with datetime

4.2. Structure of statisctic logs .tsv

  • samples by set up frequency, should cover main aspects of crawl runtime
| date | elapsedMilliseconds | lastReachedState | novel | dupByHash | warcNovelContentBytes | warcNovelUrls | activeQueues | snoozedQueues | exhaustedQueues | busyThreads | congestionRatio | currentKiBPerSec | currentDocsPerSecond | usedBytes | alertCount |
| ----- | ---------- | ---- | ---------- | ---------- | ---------- | ------ | ---- | ---- | ---- | ---- | --- | --- | ---- | --- | ------- | ---- |
| 09:09:32 | 33102 | PAUSE | 0 | 0 | | | 0 | 0 | 0 | 0 | | 0 | 0 | 1293253128 | 0 | | 09:10:34 | 93431 | RUN | 60365985 | 88987568 | 60366378 | 1392 | 492 | 229 | 120 | 150 | 12.997361 | 2124 | 35 | 1463790776 | 0 | | 09:11:38 | 155843 | RUN | 169967391 | 286983358 | 169967914 | 2711 | 596 | 396 | 194 | 150 | 10.399267 | 5432 | 98 | 1384826816 | 0 | | 09:12:40 | 218913 | RUN | 318117678 | 623741404 | 318118201 | 4458 | 712 | 542 | 295 | 150 | 9.520231 | 7712 | 102 | 3413708416 | 0 |

4.3. Other logs

  • accessible in archived crawl dirs, standardly created by heritrix

5. License

Continuous suite is free software; you can redistribute it and/or modify it under the terms of the GNU GPL 3, with reservation to secrets generally and path and date customisations in continuous-setting.cfg.sh.

About

Continuous heritrix shell suite (CHSS)

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - WebarchivCZ/continuous-suite: Continuous heritrix shell suite (CHSS) · GitHub
Skip to content

Latest commit

History

9 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

Continuous heritrix shell suite (CHSS)

  • Developed and used for basic automation of continuous heritrix jobs from 2020/05, till 2022, with dedicated virtual machines / containers heritrix instances in Webarchive CZ.

1. Deployement and usage of CHSS

1.1.Prerequisities

  • Running on single VM/container and in single instance
    • Dedicated heritrix user
    • Accessible cron for dedicated user
      • Installation of Java
    • Installation of Heritrix vs. 3
  • necessary to set up with all system links / FS shares during deploy of crawling server and installation of heritrix engine are not part of this readme
  • for more complex jobs, should be used DB templates, AMQP protocols and asynchronous event processing

1.2. Structure of dirs

  • Continuous suite is composed of several scripts and specialised functions for passive monitoring and simple running of continuous crawls with high intensisty
  • Consists of:
    • project directory - Specific continuous dir
      • stat-checks - Statistics samples logs dir
      • logs-runtime - Runtime logs dir
    • central directory - General dir for all projects
    • archival directory - structure not included here, dependent on each case and overall archival strategy, also as FS structure

1.3. Basic operation

    1. pull and deploy
cd <Crawler-config-dir>git clone https://github.com/WebarchivCZ/continuous-suite.gitcd continuous-suitemv project-dir <Project-dir>
    1. create new cron record
heritrix@crawler:~$ crontab -e6 4,9,13,17,21 * * * <project_dir>/continuous-suite.sh >> <project_dir>/logs_runtime/<project_name>-cs-`date +\%Y\%m`.log 2>&1
    1. before running, it is necessary to configure paths and variables (see lower, in 2. Customisations)

2. Customisations

2.1. Project directory of continuous crawl

  • main project directory and settings for each continuous project
    • for each instance of continuous crawl create own directory
  • necessary to set up project path: /
  • installation
    • by deploying project-dir for concrete continuous type project
cd <Project-dir> lscontinuous-suite.sh # Main running script, flow of eventssettings-continuous.cfg.sh # Main settings, sourcingseeds.txt # Actual seeds - could be customised, eg. tsv importstat-checks # Directory for aggregated crawl sample statistics in tsv format, eg. Continuous-Cov19-2023-02-01-Cov19.techlog.tsv runtime-logs #Logs of cron runtime

2.1.1. File settings-continuous.cfg.sh

  • main settings for crawler and crawl settings and continuous-suite
    • important - fill up with actual paths and dates
      • specification - typ - Key identifier composed from Type_ProjectName - expecting same as project directory
    • logins and passes set up in local .sh, not here
  • settings categories
    • Crawler variables and paths
    • Crawl Metadata
      • Dates (authomatic)
      • Project
      • important - typ - Key identifier composed from Type_ProjectName - expecting same as project directory
        • Paths
        • Organizational
    • Crawl Quantitative - Dynamic crawler values
    • Seeds source - TSV
    • Stats

2.1.2 File continuous-suite.sh

  • main script with event flow and crawler set up and app logic
  • uses other supporting scripts:
    • project dir
      • settings-continuous.cfg.sh
      • crawler-beans.template
    • central dir
      • start-crawler.sh
      • stat-checker.sh
    • archive dir
      • archive_logs.sh
  • on first deploy:
    • change target for sourcing settings-continuous.cfg.sh after project path: source <Crawler-config-dir>/continuous-suite/<Project-dir>
  • structure:
      1. Initiation of variables
      1. Functions defintions
      • helping functions
      1. Seeds reactualization
      • reactualization of seedsm otpional
    • 4.A Crawl Initiation - Set up deploy
      • deploy crawler-beans.cxml after actual variables
    • 4.B Crawl Initiation - Crawler initiation
      • restart of heritrix crawler
      1. Crawl - Basic Event Flow
      1. Archiving and operationa logs cleaning
  • actual crawl flow accords to basic sequential crawl flow
    • Crawl Initiation
    • Crawl Launch
    • Crawl Unpausing - here depends at crawler setting
    • Crawl Runnning
    • Crawl Termination
    • Crawl Teardown

2.1.3 File crawler-beans.template

  • supporting template file for crawl
  • on deploy:
    • necessary credentials - either include own or comment it
      • for domain facebook.com
        • ,
      • for domain twitter.com
        • ,
      • etc. set up credentialStore
    • customize local beans (ad hoc)
      • rejectLocalCalendars.regexList
      • surtPrefixes
      • rejectLocalCalendars-sheet
      • rejectLocalTraps-sheet
      • SurtPrefixesSheetAssociation
  • structure of main settings and their template (change only ad hoc project / project type / structure)
    • basic settings
      • metadata.jobName=%TYP% %DNES%-%SHORT_N%
      • metadata.operator=%ACTUAL_OPERATOR%
      • metadata.description=%M_COMMENT%
      • warcWriter.prefix=%TYP%-%DNES%-%SHORT_N%_%CRAWLER_HOST%-
      • warcWriter.storePaths=%CORE_STORE%/%TYP_LC%/%TYP%-%DNES%-%SHORT_N%
    • duplication reduction and ops
      • historyBdb.dir=%CRAWLER_JOBS%/history/%YEAR%-history-state-year
      • bdb.dir=%CRAWLER_JOBS%/states/%TYP_LC%/%YEAR%
      • crawlController.scratchDir=%CRAWLER_JOBS%/scratchx%TYP_LC%
    • settings
      • frontier.balanceReplenishAmount=%BALANCE_REPLENISHAM%
      • crawlController.maxToeThreads=%MAX_TOETHREADS%
      • crawlLimiter.maxTimeSeconds=%MAX_TIMESECONDS%
      • #tooManyHopsDecideRule.maxHops=%MAX_HOPS%
      • #transclusionDecideRules.maxTransHops=%MAX_TRANSHOPS%
      • #transclusionDecideRules.maxSpeculativeHops=%MAX_SPECHOPS%
      • #scope.maxHops=%MAX_HOPS%
      • #scope.maxTransHops=%MAX_TRANSHOPS%
      • #scope.maxSpeculativeHops=%MAX_SPECHOPS%
      • warcWriter.poolMaxActive=%POOL_MAXACTIVE%
    • metadata
      • metadata.operatorContactUrl=%OPER_WEB%
      • metadata.operatorFrom=%OPER_MAIL%
      • metadata.organization=%OPER_ORGANIZATIONFULL%
      • metadata.audience=%OPER_AUDIENCE%
      • metadata.userAgentTemplate=%OPER_TEMPLATE%
    • storePaths
      • %CORE_STORE%/%TYP_LC%/%TYP%-%DNES%-%SHORT_N%

2.2 Central opt directory

  • contains scripts central to multipurpose use, not only
/opt/heritrixstart-crawler.sh # Crawler starting scriptstat-checker.sh # Statistics checking

2.2.1. File stat-checker.sh

  • creates statistic logs ".techlog.tsv"
  • usage:
    • automatical from continuous-script.sh
    • manual: <central-dir-path>/crawlchecker.sh <runtime_seconds> Continuous-Cov19-YYYY-MM-DD-Cov19 <ip_adress> <port>
  • set up variables
    • type, ip-adress, file_name, runtime in seconds are taken from Main settings (settings.topics.cfg.sh )
    runtime="${1} seconds"
    TYP=${2} # "Continuous-X"
    ADDRESS=${4}	# "IP adress X.X.X.X"
    PORT=${5} # port
    FName=${3}	# Path+Filename
    
    • login and password need to set up locally
    login="<actual-login>"
    pass="<actual-password>"
    

2.2.2. File start-crawler.sh

  • starts crawler with defined parametres
  • on deploy:
    • change <actual-crawler-login>,<actual-crawler-password>
  • usage:
    • automatical from continuous-script.sh
    • manual
    start-crawler.sh <crawler_ip> <port> <java-XmxInMB> <java-XmsInMB> <HERITRIX_HOME> <JAVA_HOME>

2.3. Archive dir

  • recommended strutcture for logging /mnt/archives/rok/continuous-name vcitane scriptu z toolboxu pre ukladanie logov

2.3.1. File archive_logs.sh

  • external script, created by R. Kreibich and updated by P. Habetinova
  • added for inspiration

3. Indexation and Publication

  • missing from scope of this project
  • it is dependent on indexation processess of project and archive needs

4. Logs structure

4.1. Runtime logs

  • basic process related structure with datetime

4.2. Structure of statisctic logs .tsv

  • samples by set up frequency, should cover main aspects of crawl runtime
| date | elapsedMilliseconds | lastReachedState | novel | dupByHash | warcNovelContentBytes | warcNovelUrls | activeQueues | snoozedQueues | exhaustedQueues | busyThreads | congestionRatio | currentKiBPerSec | currentDocsPerSecond | usedBytes | alertCount |
| ----- | ---------- | ---- | ---------- | ---------- | ---------- | ------ | ---- | ---- | ---- | ---- | --- | --- | ---- | --- | ------- | ---- |
| 09:09:32 | 33102 | PAUSE | 0 | 0 | | | 0 | 0 | 0 | 0 | | 0 | 0 | 1293253128 | 0 | | 09:10:34 | 93431 | RUN | 60365985 | 88987568 | 60366378 | 1392 | 492 | 229 | 120 | 150 | 12.997361 | 2124 | 35 | 1463790776 | 0 | | 09:11:38 | 155843 | RUN | 169967391 | 286983358 | 169967914 | 2711 | 596 | 396 | 194 | 150 | 10.399267 | 5432 | 98 | 1384826816 | 0 | | 09:12:40 | 218913 | RUN | 318117678 | 623741404 | 318118201 | 4458 | 712 | 542 | 295 | 150 | 9.520231 | 7712 | 102 | 3413708416 | 0 |

4.3. Other logs

  • accessible in archived crawl dirs, standardly created by heritrix

5. License

Continuous suite is free software; you can redistribute it and/or modify it under the terms of the GNU GPL 3, with reservation to secrets generally and path and date customisations in continuous-setting.cfg.sh.

About

Continuous heritrix shell suite (CHSS)

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - WebarchivCZ/continuous-suite: Continuous heritrix shell suite (CHSS) · GitHub
Skip to content

Latest commit

History

9 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

Continuous heritrix shell suite (CHSS)

  • Developed and used for basic automation of continuous heritrix jobs from 2020/05, till 2022, with dedicated virtual machines / containers heritrix instances in Webarchive CZ.

1. Deployement and usage of CHSS

1.1.Prerequisities

  • Running on single VM/container and in single instance
    • Dedicated heritrix user
    • Accessible cron for dedicated user
      • Installation of Java
    • Installation of Heritrix vs. 3
  • necessary to set up with all system links / FS shares during deploy of crawling server and installation of heritrix engine are not part of this readme
  • for more complex jobs, should be used DB templates, AMQP protocols and asynchronous event processing

1.2. Structure of dirs

  • Continuous suite is composed of several scripts and specialised functions for passive monitoring and simple running of continuous crawls with high intensisty
  • Consists of:
    • project directory - Specific continuous dir
      • stat-checks - Statistics samples logs dir
      • logs-runtime - Runtime logs dir
    • central directory - General dir for all projects
    • archival directory - structure not included here, dependent on each case and overall archival strategy, also as FS structure

1.3. Basic operation

    1. pull and deploy
cd <Crawler-config-dir>git clone https://github.com/WebarchivCZ/continuous-suite.gitcd continuous-suitemv project-dir <Project-dir>
    1. create new cron record
heritrix@crawler:~$ crontab -e6 4,9,13,17,21 * * * <project_dir>/continuous-suite.sh >> <project_dir>/logs_runtime/<project_name>-cs-`date +\%Y\%m`.log 2>&1
    1. before running, it is necessary to configure paths and variables (see lower, in 2. Customisations)

2. Customisations

2.1. Project directory of continuous crawl

  • main project directory and settings for each continuous project
    • for each instance of continuous crawl create own directory
  • necessary to set up project path: /
  • installation
    • by deploying project-dir for concrete continuous type project
cd <Project-dir> lscontinuous-suite.sh # Main running script, flow of eventssettings-continuous.cfg.sh # Main settings, sourcingseeds.txt # Actual seeds - could be customised, eg. tsv importstat-checks # Directory for aggregated crawl sample statistics in tsv format, eg. Continuous-Cov19-2023-02-01-Cov19.techlog.tsv runtime-logs #Logs of cron runtime

2.1.1. File settings-continuous.cfg.sh

  • main settings for crawler and crawl settings and continuous-suite
    • important - fill up with actual paths and dates
      • specification - typ - Key identifier composed from Type_ProjectName - expecting same as project directory
    • logins and passes set up in local .sh, not here
  • settings categories
    • Crawler variables and paths
    • Crawl Metadata
      • Dates (authomatic)
      • Project
      • important - typ - Key identifier composed from Type_ProjectName - expecting same as project directory
        • Paths
        • Organizational
    • Crawl Quantitative - Dynamic crawler values
    • Seeds source - TSV
    • Stats

2.1.2 File continuous-suite.sh

  • main script with event flow and crawler set up and app logic
  • uses other supporting scripts:
    • project dir
      • settings-continuous.cfg.sh
      • crawler-beans.template
    • central dir
      • start-crawler.sh
      • stat-checker.sh
    • archive dir
      • archive_logs.sh
  • on first deploy:
    • change target for sourcing settings-continuous.cfg.sh after project path: source <Crawler-config-dir>/continuous-suite/<Project-dir>
  • structure:
      1. Initiation of variables
      1. Functions defintions
      • helping functions
      1. Seeds reactualization
      • reactualization of seedsm otpional
    • 4.A Crawl Initiation - Set up deploy
      • deploy crawler-beans.cxml after actual variables
    • 4.B Crawl Initiation - Crawler initiation
      • restart of heritrix crawler
      1. Crawl - Basic Event Flow
      1. Archiving and operationa logs cleaning
  • actual crawl flow accords to basic sequential crawl flow
    • Crawl Initiation
    • Crawl Launch
    • Crawl Unpausing - here depends at crawler setting
    • Crawl Runnning
    • Crawl Termination
    • Crawl Teardown

2.1.3 File crawler-beans.template

  • supporting template file for crawl
  • on deploy:
    • necessary credentials - either include own or comment it
      • for domain facebook.com
        • ,
      • for domain twitter.com
        • ,
      • etc. set up credentialStore
    • customize local beans (ad hoc)
      • rejectLocalCalendars.regexList
      • surtPrefixes
      • rejectLocalCalendars-sheet
      • rejectLocalTraps-sheet
      • SurtPrefixesSheetAssociation
  • structure of main settings and their template (change only ad hoc project / project type / structure)
    • basic settings
      • metadata.jobName=%TYP% %DNES%-%SHORT_N%
      • metadata.operator=%ACTUAL_OPERATOR%
      • metadata.description=%M_COMMENT%
      • warcWriter.prefix=%TYP%-%DNES%-%SHORT_N%_%CRAWLER_HOST%-
      • warcWriter.storePaths=%CORE_STORE%/%TYP_LC%/%TYP%-%DNES%-%SHORT_N%
    • duplication reduction and ops
      • historyBdb.dir=%CRAWLER_JOBS%/history/%YEAR%-history-state-year
      • bdb.dir=%CRAWLER_JOBS%/states/%TYP_LC%/%YEAR%
      • crawlController.scratchDir=%CRAWLER_JOBS%/scratchx%TYP_LC%
    • settings
      • frontier.balanceReplenishAmount=%BALANCE_REPLENISHAM%
      • crawlController.maxToeThreads=%MAX_TOETHREADS%
      • crawlLimiter.maxTimeSeconds=%MAX_TIMESECONDS%
      • #tooManyHopsDecideRule.maxHops=%MAX_HOPS%
      • #transclusionDecideRules.maxTransHops=%MAX_TRANSHOPS%
      • #transclusionDecideRules.maxSpeculativeHops=%MAX_SPECHOPS%
      • #scope.maxHops=%MAX_HOPS%
      • #scope.maxTransHops=%MAX_TRANSHOPS%
      • #scope.maxSpeculativeHops=%MAX_SPECHOPS%
      • warcWriter.poolMaxActive=%POOL_MAXACTIVE%
    • metadata
      • metadata.operatorContactUrl=%OPER_WEB%
      • metadata.operatorFrom=%OPER_MAIL%
      • metadata.organization=%OPER_ORGANIZATIONFULL%
      • metadata.audience=%OPER_AUDIENCE%
      • metadata.userAgentTemplate=%OPER_TEMPLATE%
    • storePaths
      • %CORE_STORE%/%TYP_LC%/%TYP%-%DNES%-%SHORT_N%

2.2 Central opt directory

  • contains scripts central to multipurpose use, not only
/opt/heritrixstart-crawler.sh # Crawler starting scriptstat-checker.sh # Statistics checking

2.2.1. File stat-checker.sh

  • creates statistic logs ".techlog.tsv"
  • usage:
    • automatical from continuous-script.sh
    • manual: <central-dir-path>/crawlchecker.sh <runtime_seconds> Continuous-Cov19-YYYY-MM-DD-Cov19 <ip_adress> <port>
  • set up variables
    • type, ip-adress, file_name, runtime in seconds are taken from Main settings (settings.topics.cfg.sh )
    runtime="${1} seconds"
    TYP=${2} # "Continuous-X"
    ADDRESS=${4}	# "IP adress X.X.X.X"
    PORT=${5} # port
    FName=${3}	# Path+Filename
    
    • login and password need to set up locally
    login="<actual-login>"
    pass="<actual-password>"
    

2.2.2. File start-crawler.sh

  • starts crawler with defined parametres
  • on deploy:
    • change <actual-crawler-login>,<actual-crawler-password>
  • usage:
    • automatical from continuous-script.sh
    • manual
    start-crawler.sh <crawler_ip> <port> <java-XmxInMB> <java-XmsInMB> <HERITRIX_HOME> <JAVA_HOME>

2.3. Archive dir

  • recommended strutcture for logging /mnt/archives/rok/continuous-name vcitane scriptu z toolboxu pre ukladanie logov

2.3.1. File archive_logs.sh

  • external script, created by R. Kreibich and updated by P. Habetinova
  • added for inspiration

3. Indexation and Publication

  • missing from scope of this project
  • it is dependent on indexation processess of project and archive needs

4. Logs structure

4.1. Runtime logs

  • basic process related structure with datetime

4.2. Structure of statisctic logs .tsv

  • samples by set up frequency, should cover main aspects of crawl runtime
| date | elapsedMilliseconds | lastReachedState | novel | dupByHash | warcNovelContentBytes | warcNovelUrls | activeQueues | snoozedQueues | exhaustedQueues | busyThreads | congestionRatio | currentKiBPerSec | currentDocsPerSecond | usedBytes | alertCount |
| ----- | ---------- | ---- | ---------- | ---------- | ---------- | ------ | ---- | ---- | ---- | ---- | --- | --- | ---- | --- | ------- | ---- |
| 09:09:32 | 33102 | PAUSE | 0 | 0 | | | 0 | 0 | 0 | 0 | | 0 | 0 | 1293253128 | 0 | | 09:10:34 | 93431 | RUN | 60365985 | 88987568 | 60366378 | 1392 | 492 | 229 | 120 | 150 | 12.997361 | 2124 | 35 | 1463790776 | 0 | | 09:11:38 | 155843 | RUN | 169967391 | 286983358 | 169967914 | 2711 | 596 | 396 | 194 | 150 | 10.399267 | 5432 | 98 | 1384826816 | 0 | | 09:12:40 | 218913 | RUN | 318117678 | 623741404 | 318118201 | 4458 | 712 | 542 | 295 | 150 | 9.520231 | 7712 | 102 | 3413708416 | 0 |

4.3. Other logs

  • accessible in archived crawl dirs, standardly created by heritrix

5. License

Continuous suite is free software; you can redistribute it and/or modify it under the terms of the GNU GPL 3, with reservation to secrets generally and path and date customisations in continuous-setting.cfg.sh.

About

Continuous heritrix shell suite (CHSS)

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); GitHub - WebarchivCZ/continuous-suite: Continuous heritrix shell suite (CHSS) · GitHub
Skip to content

Latest commit

History

9 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

Continuous heritrix shell suite (CHSS)

  • Developed and used for basic automation of continuous heritrix jobs from 2020/05, till 2022, with dedicated virtual machines / containers heritrix instances in Webarchive CZ.

1. Deployement and usage of CHSS

1.1.Prerequisities

  • Running on single VM/container and in single instance
    • Dedicated heritrix user
    • Accessible cron for dedicated user
      • Installation of Java
    • Installation of Heritrix vs. 3
  • necessary to set up with all system links / FS shares during deploy of crawling server and installation of heritrix engine are not part of this readme
  • for more complex jobs, should be used DB templates, AMQP protocols and asynchronous event processing

1.2. Structure of dirs

  • Continuous suite is composed of several scripts and specialised functions for passive monitoring and simple running of continuous crawls with high intensisty
  • Consists of:
    • project directory - Specific continuous dir
      • stat-checks - Statistics samples logs dir
      • logs-runtime - Runtime logs dir
    • central directory - General dir for all projects
    • archival directory - structure not included here, dependent on each case and overall archival strategy, also as FS structure

1.3. Basic operation

    1. pull and deploy
cd <Crawler-config-dir>git clone https://github.com/WebarchivCZ/continuous-suite.gitcd continuous-suitemv project-dir <Project-dir>
    1. create new cron record
heritrix@crawler:~$ crontab -e6 4,9,13,17,21 * * * <project_dir>/continuous-suite.sh >> <project_dir>/logs_runtime/<project_name>-cs-`date +\%Y\%m`.log 2>&1
    1. before running, it is necessary to configure paths and variables (see lower, in 2. Customisations)

2. Customisations

2.1. Project directory of continuous crawl

  • main project directory and settings for each continuous project
    • for each instance of continuous crawl create own directory
  • necessary to set up project path: /
  • installation
    • by deploying project-dir for concrete continuous type project
cd <Project-dir> lscontinuous-suite.sh # Main running script, flow of eventssettings-continuous.cfg.sh # Main settings, sourcingseeds.txt # Actual seeds - could be customised, eg. tsv importstat-checks # Directory for aggregated crawl sample statistics in tsv format, eg. Continuous-Cov19-2023-02-01-Cov19.techlog.tsv runtime-logs #Logs of cron runtime

2.1.1. File settings-continuous.cfg.sh

  • main settings for crawler and crawl settings and continuous-suite
    • important - fill up with actual paths and dates
      • specification - typ - Key identifier composed from Type_ProjectName - expecting same as project directory
    • logins and passes set up in local .sh, not here
  • settings categories
    • Crawler variables and paths
    • Crawl Metadata
      • Dates (authomatic)
      • Project
      • important - typ - Key identifier composed from Type_ProjectName - expecting same as project directory
        • Paths
        • Organizational
    • Crawl Quantitative - Dynamic crawler values
    • Seeds source - TSV
    • Stats

2.1.2 File continuous-suite.sh

  • main script with event flow and crawler set up and app logic
  • uses other supporting scripts:
    • project dir
      • settings-continuous.cfg.sh
      • crawler-beans.template
    • central dir
      • start-crawler.sh
      • stat-checker.sh
    • archive dir
      • archive_logs.sh
  • on first deploy:
    • change target for sourcing settings-continuous.cfg.sh after project path: source <Crawler-config-dir>/continuous-suite/<Project-dir>
  • structure:
      1. Initiation of variables
      1. Functions defintions
      • helping functions
      1. Seeds reactualization
      • reactualization of seedsm otpional
    • 4.A Crawl Initiation - Set up deploy
      • deploy crawler-beans.cxml after actual variables
    • 4.B Crawl Initiation - Crawler initiation
      • restart of heritrix crawler
      1. Crawl - Basic Event Flow
      1. Archiving and operationa logs cleaning
  • actual crawl flow accords to basic sequential crawl flow
    • Crawl Initiation
    • Crawl Launch
    • Crawl Unpausing - here depends at crawler setting
    • Crawl Runnning
    • Crawl Termination
    • Crawl Teardown

2.1.3 File crawler-beans.template

  • supporting template file for crawl
  • on deploy:
    • necessary credentials - either include own or comment it
      • for domain facebook.com
        • ,
      • for domain twitter.com
        • ,
      • etc. set up credentialStore
    • customize local beans (ad hoc)
      • rejectLocalCalendars.regexList
      • surtPrefixes
      • rejectLocalCalendars-sheet
      • rejectLocalTraps-sheet
      • SurtPrefixesSheetAssociation
  • structure of main settings and their template (change only ad hoc project / project type / structure)
    • basic settings
      • metadata.jobName=%TYP% %DNES%-%SHORT_N%
      • metadata.operator=%ACTUAL_OPERATOR%
      • metadata.description=%M_COMMENT%
      • warcWriter.prefix=%TYP%-%DNES%-%SHORT_N%_%CRAWLER_HOST%-
      • warcWriter.storePaths=%CORE_STORE%/%TYP_LC%/%TYP%-%DNES%-%SHORT_N%
    • duplication reduction and ops
      • historyBdb.dir=%CRAWLER_JOBS%/history/%YEAR%-history-state-year
      • bdb.dir=%CRAWLER_JOBS%/states/%TYP_LC%/%YEAR%
      • crawlController.scratchDir=%CRAWLER_JOBS%/scratchx%TYP_LC%
    • settings
      • frontier.balanceReplenishAmount=%BALANCE_REPLENISHAM%
      • crawlController.maxToeThreads=%MAX_TOETHREADS%
      • crawlLimiter.maxTimeSeconds=%MAX_TIMESECONDS%
      • #tooManyHopsDecideRule.maxHops=%MAX_HOPS%
      • #transclusionDecideRules.maxTransHops=%MAX_TRANSHOPS%
      • #transclusionDecideRules.maxSpeculativeHops=%MAX_SPECHOPS%
      • #scope.maxHops=%MAX_HOPS%
      • #scope.maxTransHops=%MAX_TRANSHOPS%
      • #scope.maxSpeculativeHops=%MAX_SPECHOPS%
      • warcWriter.poolMaxActive=%POOL_MAXACTIVE%
    • metadata
      • metadata.operatorContactUrl=%OPER_WEB%
      • metadata.operatorFrom=%OPER_MAIL%
      • metadata.organization=%OPER_ORGANIZATIONFULL%
      • metadata.audience=%OPER_AUDIENCE%
      • metadata.userAgentTemplate=%OPER_TEMPLATE%
    • storePaths
      • %CORE_STORE%/%TYP_LC%/%TYP%-%DNES%-%SHORT_N%

2.2 Central opt directory

  • contains scripts central to multipurpose use, not only
/opt/heritrixstart-crawler.sh # Crawler starting scriptstat-checker.sh # Statistics checking

2.2.1. File stat-checker.sh

  • creates statistic logs ".techlog.tsv"
  • usage:
    • automatical from continuous-script.sh
    • manual: <central-dir-path>/crawlchecker.sh <runtime_seconds> Continuous-Cov19-YYYY-MM-DD-Cov19 <ip_adress> <port>
  • set up variables
    • type, ip-adress, file_name, runtime in seconds are taken from Main settings (settings.topics.cfg.sh )
    runtime="${1} seconds"
    TYP=${2} # "Continuous-X"
    ADDRESS=${4}	# "IP adress X.X.X.X"
    PORT=${5} # port
    FName=${3}	# Path+Filename
    
    • login and password need to set up locally
    login="<actual-login>"
    pass="<actual-password>"
    

2.2.2. File start-crawler.sh

  • starts crawler with defined parametres
  • on deploy:
    • change <actual-crawler-login>,<actual-crawler-password>
  • usage:
    • automatical from continuous-script.sh
    • manual
    start-crawler.sh <crawler_ip> <port> <java-XmxInMB> <java-XmsInMB> <HERITRIX_HOME> <JAVA_HOME>

2.3. Archive dir

  • recommended strutcture for logging /mnt/archives/rok/continuous-name vcitane scriptu z toolboxu pre ukladanie logov

2.3.1. File archive_logs.sh

  • external script, created by R. Kreibich and updated by P. Habetinova
  • added for inspiration

3. Indexation and Publication

  • missing from scope of this project
  • it is dependent on indexation processess of project and archive needs

4. Logs structure

4.1. Runtime logs

  • basic process related structure with datetime

4.2. Structure of statisctic logs .tsv

  • samples by set up frequency, should cover main aspects of crawl runtime
| date | elapsedMilliseconds | lastReachedState | novel | dupByHash | warcNovelContentBytes | warcNovelUrls | activeQueues | snoozedQueues | exhaustedQueues | busyThreads | congestionRatio | currentKiBPerSec | currentDocsPerSecond | usedBytes | alertCount |
| ----- | ---------- | ---- | ---------- | ---------- | ---------- | ------ | ---- | ---- | ---- | ---- | --- | --- | ---- | --- | ------- | ---- |
| 09:09:32 | 33102 | PAUSE | 0 | 0 | | | 0 | 0 | 0 | 0 | | 0 | 0 | 1293253128 | 0 | | 09:10:34 | 93431 | RUN | 60365985 | 88987568 | 60366378 | 1392 | 492 | 229 | 120 | 150 | 12.997361 | 2124 | 35 | 1463790776 | 0 | | 09:11:38 | 155843 | RUN | 169967391 | 286983358 | 169967914 | 2711 | 596 | 396 | 194 | 150 | 10.399267 | 5432 | 98 | 1384826816 | 0 | | 09:12:40 | 218913 | RUN | 318117678 | 623741404 | 318118201 | 4458 | 712 | 542 | 295 | 150 | 9.520231 | 7712 | 102 | 3413708416 | 0 |

4.3. Other logs

  • accessible in archived crawl dirs, standardly created by heritrix

5. License

Continuous suite is free software; you can redistribute it and/or modify it under the terms of the GNU GPL 3, with reservation to secrets generally and path and date customisations in continuous-setting.cfg.sh.

About

Continuous heritrix shell suite (CHSS)

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages