🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 125 (from laksa196)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa125.int.ahrefs:8124/' \
  -H 'Content-Type: text/plain' \
  -H 'X-ClickHouse-Database: crawler3' \
  -H 'Authorization: Basic YXBpOg==' \
  -d 'SELECT getAhrefsURLFromUnparsed(src_unparsed) AS found_url, ifNull(toUnixTimestamp(download_stamp), 0) AS crawl_time, ifNull(toUnixTimestamp(props_url_first_seen), 0) AS first_indexed_time, download_http_code AS http_code, src_unparsed AS src_unparsed, src_root_hash AS src_root_hash, history_drop_reason AS history_drop_reason, meta_title AS meta_title, meta_descriptions AS meta_descriptions, attrs_boilerpipe_text AS attrs_boilerpipe_text, attrs_markdown AS attrs_markdown, attrs_readable_markdown AS attrs_readable_markdown, meta_canonical AS meta_canonical FROM crawler3.page_info_local FINAL PREWHERE (src_root_hash, src_unparsed) IN ((getAhrefsRootHashFromUnparsed(getAhrefsUnparsedNoserviceFromURL(\'https://in.nau.edu/arc/using-the-screen-command/\')), getAhrefsUnparsedNoserviceFromURL(\'https://in.nau.edu/arc/using-the-screen-command/\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/in.nau.edu\/arc\/using-the-screen-command\/","crawl_time":1775839375,"first_indexed_time":1663151210,"http_code":200,"src_unparsed":"edu,nau!in,\/arc\/using-the-screen-command\/ s443","src_root_hash":"5337352048246158725","history_drop_reason":null,"meta_title":"Working With an Unstable Internet Connection | Advanced Research Computing","meta_descriptions":["If you are working with an unstable internet connection via ssh and you don’t want to lose your progress every time you disconnect, the screen command allows…"],"attrs_boilerpipe_text":"If you are working with an unstable internet connection via ssh and you don’t want to lose your progress every time you disconnect, the\nscreen\ncommand allows you to run a background session that you can reconnect to later.\nStarting a screen session\nScreen enables your login process and connected processes to remain running if\/while your ssh connection is interrupted. Its pretty easy:\nStart a command-line shell on one of Monsoon’s login nodes\nStart a screen session by running the\nscreen\ncommand\nInitiate any programs\/processes\nIf desired, you now may disconnect from Monsoon while allowing your programs to continue without being actively connected. Here’s how:\nSimply close your SSH client\/window\nOR:\nExit your active\nscreen\ngracefully with this key-sequence:\nctrl\n+\na\n;\nthen release both keys\n;\nthen hit\nd\n(The\nctrl\n+\na\n,\nd\nsequence detaches from the session. The\nctrl\n+\na\nkeystroke itself tells\nscreen\nto listen for subsequent key-commands.)\nNow that you are disconnected from screen, your processes will continue to run to completion.\nReconnecting to a ‘screen’ session\nTo reconnect to screen to monitor or end your programs do the following.\nEnsure you are logged in to the same system\n(e.g.: wind, rain, dtn1, ondemand)\nRun\nscreen -r\nThe\nscreen -r\ncommand will resume an existing screen session. If there are multiple sessions you will have to be specific:\nRun\nscreen -ls\nto list the\nscreen\nsessions.\n[abc123@wind ~ ]$ screen -ls\r\nThere are screens on:\r\n1144795.pts-0.wind (Detached)\r\n1944762.pts-0.wind (Detached)\r\n2463388.pts-7.wind (Detached)\r\n3 Sockets in \/run\/screen\/S-abc123.\nThen run\nscreen -r <\nnumber\n>\nto resume.\n[abc123@wind ~ ]$ screen -r 1144795","attrs_markdown":"Expand navigation\n\n[Advanced Research Computing](https:\/\/in.nau.edu\/arc)\n\n[Virtual Visit](https:\/\/nau.edu\/flagstaff-campus\/virtual-tour\/) [Request info](https:\/\/nau.edu\/admissions\/request-information\/) [Apply](https:\/\/nau.edu\/how-to-apply\/)\n\nMENUMENU\n\n- [About](https:\/\/in.nau.edu\/arc\/using-the-screen-command\/)\n  - [Overview](https:\/\/in.nau.edu\/arc\/overview\/)\n  - [Details](https:\/\/in.nau.edu\/arc\/details\/)\n  - [Terms of Service](https:\/\/in.nau.edu\/arc\/overview\/terms-of-service\/)\n  - [FAQs](https:\/\/in.nau.edu\/arc\/faqs\/)\n  - [Our Team](https:\/\/in.nau.edu\/arc\/our-team\/)\n  - [Testimonials](https:\/\/rcdata.nau.edu\/hpcpub\/share\/arc_testimonials.mp4)\n- [Services](https:\/\/in.nau.edu\/arc\/using-the-screen-command\/)\n  - [ARC Support Bot](https:\/\/in.nau.edu\/arc\/arc-support-bot\/)\n  - [Coffee\/Office Hours](https:\/\/in.nau.edu\/arc\/hours)\n  - [Data Portal »](https:\/\/in.nau.edu\/arc\/data-portal\/)\n  - [Pricing](https:\/\/in.nau.edu\/arc\/pricing\/)\n  - [Secure Computing](https:\/\/in.nau.edu\/arc\/secure-computing\/)\n  - [Service Requests](https:\/\/in.nau.edu\/arc\/using-the-screen-command\/)\n    - [Request an Account](https:\/\/in.nau.edu\/hpc\/obtaining-an-account\/)\n    - [Request Classroom Access](https:\/\/in.nau.edu\/arc\/request-classroom-access\/)\n    - [Request Data Science Development\/Consulting](https:\/\/in.nau.edu\/arc\/sci-dev\/)\n    - [Request Software](https:\/\/in.nau.edu\/arc\/request-software\/)\n    - [Request Storage](https:\/\/in.nau.edu\/arc\/request-storage\/)\n- [Resources](https:\/\/in.nau.edu\/arc\/using-the-screen-command\/)\n  - [Documentation »](https:\/\/in.nau.edu\/arc\/documentation-page\/)\n  - [Workshops](https:\/\/in.nau.edu\/arc\/workshops)\n  - [Web Apps](https:\/\/in.nau.edu\/arc\/using-the-screen-command\/)\n    - [Doppler (NAU only)](https:\/\/metrics.hpc.nau.edu\/doppler)\n    - [Metrics (NAU only)](https:\/\/metrics.hpc.nau.edu\/)\n    - [OnDemand](http:\/\/ondemand.hpc.nau.edu\/)\n    - [XDMod](https:\/\/xdmod.hpc.nau.edu\/)\n    - [XDMoD Reports](https:\/\/siris.hpc.nau.edu\/xdmod_reports\/)\n- [Research](https:\/\/in.nau.edu\/arc\/using-the-screen-command\/)\n  - [Current Projects](https:\/\/in.nau.edu\/arc\/current-projects\/)\n  - [Publications](https:\/\/in.nau.edu\/arc\/published-papers\/)\n- [Collaboration](https:\/\/in.nau.edu\/arc\/using-the-screen-command\/)\n  - [Arizona Research Computing](https:\/\/suncorridor.org\/research-support\/arizona-research-computing\/)\n  - [CRN](https:\/\/in.nau.edu\/its\/crn\/)\n  - [External](https:\/\/in.nau.edu\/arc\/collaboration\/)\n\n- [IN](https:\/\/in.nau.edu\/)\n- [ARC](https:\/\/in.nau.edu\/arc)\n- Working With an Unstable Internet Connection\n\n# Working With an Unstable Internet Connection\nIf you are working with an unstable internet connection via ssh and you don’t want to lose your progress every time you disconnect, the screen command allows you to run a background session that you can reconnect to later.\n\n### Starting a screen session\nScreen enables your login process and connected processes to remain running if\/while your ssh connection is interrupted. Its pretty easy:\n\n1. Start a command-line shell on one of Monsoon’s login nodes\n2. Start a screen session by running the screen command\n3. Initiate any programs\/processes\n\nIf desired, you now may disconnect from Monsoon while allowing your programs to continue without being actively connected. Here’s how:\n\n1. Simply close your SSH client\/window  \n    OR:\n2. Exit your active screen gracefully with this key-sequence:  \n    `ctrl`\\+`a`; *then release both keys*; *then hit* `d` (The `ctrl`\\+`a`, `d` sequence detaches from the session. The `ctrl`\\+`a` keystroke itself tells screen to listen for subsequent key-commands.)\n\nNow that you are disconnected from screen, your processes will continue to run to completion.\n\n### Reconnecting to a ‘screen’ session\nTo reconnect to screen to monitor or end your programs do the following.\n\n1. Ensure you are logged in to the same system  \n    (e.g.: wind, rain, dtn1, ondemand)\n2. Run screen -r\n\nThe screen -r command will resume an existing screen session. If there are multiple sessions you will have to be specific:\n\n1. Run screen -ls to list the screen sessions.\n   ```\n   [abc123@wind ~ ]$ screen -ls\r\nThere are screens on:\r\n1144795.pts-0.wind (Detached)\r\n1944762.pts-0.wind (Detached)\r\n2463388.pts-7.wind (Detached)\r\n3 Sockets in \/run\/screen\/S-abc123.\n   ```\n2. Then run screen -r \\<*number*\\> to resume.\n   ```\n   [abc123@wind ~ ]$ screen -r 1144795\n   ```","attrs_readable_markdown":"If you are working with an unstable internet connection via ssh and you don’t want to lose your progress every time you disconnect, the screen command allows you to run a background session that you can reconnect to later.\n\n### Starting a screen session\nScreen enables your login process and connected processes to remain running if\/while your ssh connection is interrupted. Its pretty easy:\n\n1. Start a command-line shell on one of Monsoon’s login nodes\n2. Start a screen session by running the screen command\n3. Initiate any programs\/processes\n\nIf desired, you now may disconnect from Monsoon while allowing your programs to continue without being actively connected. Here’s how:\n\n1. Simply close your SSH client\/window  \n    OR:\n2. Exit your active screen gracefully with this key-sequence:  \n    `ctrl`\\+`a`; *then release both keys*; *then hit* `d` (The `ctrl`\\+`a`, `d` sequence detaches from the session. The `ctrl`\\+`a` keystroke itself tells screen to listen for subsequent key-commands.)\n\nNow that you are disconnected from screen, your processes will continue to run to completion.\n\n### Reconnecting to a ‘screen’ session\nTo reconnect to screen to monitor or end your programs do the following.\n\n1. Ensure you are logged in to the same system  \n    (e.g.: wind, rain, dtn1, ondemand)\n2. Run screen -r\n\nThe screen -r command will resume an existing screen session. If there are multiple sessions you will have to be specific:\n\n1. Run screen -ls to list the screen sessions.\n   ```\n   [abc123@wind ~ ]$ screen -ls\r\nThere are screens on:\r\n1144795.pts-0.wind (Detached)\r\n1944762.pts-0.wind (Detached)\r\n2463388.pts-7.wind (Detached)\r\n3 Sockets in \/run\/screen\/S-abc123.\n   ```\n2. Then run screen -r \\<*number*\\> to resume.\n   ```\n   [abc123@wind ~ ]$ screen -r 1144795\n   ```","meta_canonical":null}

3. Robots.txt Check

Query:

Response:

4. Spam/Ban Check

Query:

Response:

5. Seen Status Check

ℹ️ Skipped - page is already crawled

📄

INDEXABLE

✅

CRAWLED

3 days ago

🤖

ROBOTS ALLOWED

Page Info Filters

Filter	Status	Condition	Details
HTTP status	PASS	`download_http_code = 200`	HTTP 200
Age cutoff	PASS	`download_stamp > now() - 6 MONTH`	0.1 months ago
History drop	PASS	`isNull(history_drop_reason)`	No drop reason
Spam/ban	PASS	`fh_dont_index != 1 AND ml_spam_score = 0`	ml_spam_score=0
Canonical	PASS	`meta_canonical IS NULL OR = '' OR = src_unparsed`	Not set

Page Details

Property	Value
URL	https://in.nau.edu/arc/using-the-screen-command/
Last Crawled	2026-04-10 16:42:55 (3 days ago)
First Indexed	2022-09-14 10:26:50 (3 years ago)
HTTP Status Code	200
Meta Title	Working With an Unstable Internet Connection \| Advanced Research Computing
Meta Description	If you are working with an unstable internet connection via ssh and you don’t want to lose your progress every time you disconnect, the screen command allows…
Meta Canonical	null
Boilerpipe Text	If you are working with an unstable internet connection via ssh and you don’t want to lose your progress every time you disconnect, the screen command allows you to run a background session that you can reconnect to later. Starting a screen session Screen enables your login process and connected processes to remain running if/while your ssh connection is interrupted. Its pretty easy: Start a command-line shell on one of Monsoon’s login nodes Start a screen session by running the screen command Initiate any programs/processes If desired, you now may disconnect from Monsoon while allowing your programs to continue without being actively connected. Here’s how: Simply close your SSH client/window OR: Exit your active screen gracefully with this key-sequence: ctrl + a ; then release both keys ; then hit d (The ctrl + a , d sequence detaches from the session. The ctrl + a keystroke itself tells screen to listen for subsequent key-commands.) Now that you are disconnected from screen, your processes will continue to run to completion. Reconnecting to a ‘screen’ session To reconnect to screen to monitor or end your programs do the following. Ensure you are logged in to the same system (e.g.: wind, rain, dtn1, ondemand) Run screen -r The screen -r command will resume an existing screen session. If there are multiple sessions you will have to be specific: Run screen -ls to list the screen sessions. [abc123@wind ~ ]$ screen -ls There are screens on: 1144795.pts-0.wind (Detached) 1944762.pts-0.wind (Detached) 2463388.pts-7.wind (Detached) 3 Sockets in /run/screen/S-abc123. Then run screen -r < number > to resume. [abc123@wind ~ ]$ screen -r 1144795
Markdown	Expand navigation [Advanced Research Computing](https://in.nau.edu/arc) [Virtual Visit](https://nau.edu/flagstaff-campus/virtual-tour/) [Request info](https://nau.edu/admissions/request-information/) [Apply](https://nau.edu/how-to-apply/) MENUMENU - [About](https://in.nau.edu/arc/using-the-screen-command/) - [Overview](https://in.nau.edu/arc/overview/) - [Details](https://in.nau.edu/arc/details/) - [Terms of Service](https://in.nau.edu/arc/overview/terms-of-service/) - [FAQs](https://in.nau.edu/arc/faqs/) - [Our Team](https://in.nau.edu/arc/our-team/) - [Testimonials](https://rcdata.nau.edu/hpcpub/share/arc_testimonials.mp4) - [Services](https://in.nau.edu/arc/using-the-screen-command/) - [ARC Support Bot](https://in.nau.edu/arc/arc-support-bot/) - [Coffee/Office Hours](https://in.nau.edu/arc/hours) - [Data Portal »](https://in.nau.edu/arc/data-portal/) - [Pricing](https://in.nau.edu/arc/pricing/) - [Secure Computing](https://in.nau.edu/arc/secure-computing/) - [Service Requests](https://in.nau.edu/arc/using-the-screen-command/) - [Request an Account](https://in.nau.edu/hpc/obtaining-an-account/) - [Request Classroom Access](https://in.nau.edu/arc/request-classroom-access/) - [Request Data Science Development/Consulting](https://in.nau.edu/arc/sci-dev/) - [Request Software](https://in.nau.edu/arc/request-software/) - [Request Storage](https://in.nau.edu/arc/request-storage/) - [Resources](https://in.nau.edu/arc/using-the-screen-command/) - [Documentation »](https://in.nau.edu/arc/documentation-page/) - [Workshops](https://in.nau.edu/arc/workshops) - [Web Apps](https://in.nau.edu/arc/using-the-screen-command/) - [Doppler (NAU only)](https://metrics.hpc.nau.edu/doppler) - [Metrics (NAU only)](https://metrics.hpc.nau.edu/) - [OnDemand](http://ondemand.hpc.nau.edu/) - [XDMod](https://xdmod.hpc.nau.edu/) - [XDMoD Reports](https://siris.hpc.nau.edu/xdmod_reports/) - [Research](https://in.nau.edu/arc/using-the-screen-command/) - [Current Projects](https://in.nau.edu/arc/current-projects/) - [Publications](https://in.nau.edu/arc/published-papers/) - [Collaboration](https://in.nau.edu/arc/using-the-screen-command/) - [Arizona Research Computing](https://suncorridor.org/research-support/arizona-research-computing/) - [CRN](https://in.nau.edu/its/crn/) - [External](https://in.nau.edu/arc/collaboration/) - [IN](https://in.nau.edu/) - [ARC](https://in.nau.edu/arc) - Working With an Unstable Internet Connection # Working With an Unstable Internet Connection If you are working with an unstable internet connection via ssh and you don’t want to lose your progress every time you disconnect, the screen command allows you to run a background session that you can reconnect to later. ### Starting a screen session Screen enables your login process and connected processes to remain running if/while your ssh connection is interrupted. Its pretty easy: 1. Start a command-line shell on one of Monsoon’s login nodes 2. Start a screen session by running the screen command 3. Initiate any programs/processes If desired, you now may disconnect from Monsoon while allowing your programs to continue without being actively connected. Here’s how: 1. Simply close your SSH client/window OR: 2. Exit your active screen gracefully with this key-sequence: `ctrl`\+`a`; then release both keys; then hit `d` (The `ctrl`\+`a`, `d` sequence detaches from the session. The `ctrl`\+`a` keystroke itself tells screen to listen for subsequent key-commands.) Now that you are disconnected from screen, your processes will continue to run to completion. ### Reconnecting to a ‘screen’ session To reconnect to screen to monitor or end your programs do the following. 1. Ensure you are logged in to the same system (e.g.: wind, rain, dtn1, ondemand) 2. Run screen -r The screen -r command will resume an existing screen session. If there are multiple sessions you will have to be specific: 1. Run screen -ls to list the screen sessions. ``` [abc123@wind ~ ]$ screen -ls There are screens on: 1144795.pts-0.wind (Detached) 1944762.pts-0.wind (Detached) 2463388.pts-7.wind (Detached) 3 Sockets in /run/screen/S-abc123. ``` 2. Then run screen -r \<number\> to resume. ``` [abc123@wind ~ ]$ screen -r 1144795 ```
Readable Markdown	If you are working with an unstable internet connection via ssh and you don’t want to lose your progress every time you disconnect, the screen command allows you to run a background session that you can reconnect to later. ### Starting a screen session Screen enables your login process and connected processes to remain running if/while your ssh connection is interrupted. Its pretty easy: 1. Start a command-line shell on one of Monsoon’s login nodes 2. Start a screen session by running the screen command 3. Initiate any programs/processes If desired, you now may disconnect from Monsoon while allowing your programs to continue without being actively connected. Here’s how: 1. Simply close your SSH client/window OR: 2. Exit your active screen gracefully with this key-sequence: `ctrl`\+`a`; then release both keys; then hit `d` (The `ctrl`\+`a`, `d` sequence detaches from the session. The `ctrl`\+`a` keystroke itself tells screen to listen for subsequent key-commands.) Now that you are disconnected from screen, your processes will continue to run to completion. ### Reconnecting to a ‘screen’ session To reconnect to screen to monitor or end your programs do the following. 1. Ensure you are logged in to the same system (e.g.: wind, rain, dtn1, ondemand) 2. Run screen -r The screen -r command will resume an existing screen session. If there are multiple sessions you will have to be specific: 1. Run screen -ls to list the screen sessions. ``` [abc123@wind ~ ]$ screen -ls There are screens on: 1144795.pts-0.wind (Detached) 1944762.pts-0.wind (Detached) 2463388.pts-7.wind (Detached) 3 Sockets in /run/screen/S-abc123. ``` 2. Then run screen -r \<number\> to resume. ``` [abc123@wind ~ ]$ screen -r 1144795 ```
Shard	125 (laksa)
Root Hash	5337352048246158725
Unparsed URL	edu,nau!in,/arc/using-the-screen-command/ s443