Site is unreachable
Author: s | 2025-04-24
Troubleshooting 'Site is Unreachable' Error Fixing Unreachable Site Learn how to troubleshoot and fix the 'site is unreachable' error. Check your interne
the site is unreachable - Microsoft Community
Sent to 192.168.10.250ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.250ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.250ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.251ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.251ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.251ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.251ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.252ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.252ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.252ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.252192.168.10.250 is unreachable192.168.10.251 is unreachable192.168.10.252 is unreachablehping:hping is another sister command of ping to test the network. In some distributions it is known as hping3 and not installed by default. hping3 is a network tool able to send custom TCP/IP packets and to display target replies like ping program does with ICMP replies.It also uses the same switches like ping for basic functionalities like -h for help and -c for count etc. Here are few basic examples for hping3.hping3 localhost -c 3HPING localhost (lo 127.0.0.1): NO FLAGS are set, 40 headers + 0 data byteslen=40 ip=127.0.0.1 ttl=64 DF id=10586 sport=0 flags=RA seq=0 win=0 rtt=3.5 mslen=40 ip=127.0.0.1 ttl=64 DF id=10657 sport=0 flags=RA seq=1 win=0 rtt=2.3 mslen=40 ip=127.0.0.1 ttl=64 DF id=10668 sport=0 flags=RA seq=2 win=0 rtt=2.4 ms--- localhost hping statistic ---3 packets transmitted, 3 packets received, 0% packet lossround-trip min/avg/max = 2.3/2.7/3.5 msFor sending TCP packet to specific port like
Sorry, the site is unreachable. by Pinterest
These options can fall short when it comes to growing with new users that aren’t already visiting a brand’s website or using its app. (This is typically when brands turn to third-party data that’s generated by cross-site tracking—the very practice users are rebelling against.)There is, however, an opportunity for privacy-respecting advertising that’s still capable of reaching new audiences. Ads that preserve privacy refrain from tracking users or building profiles, but can still be personalized and targeted. Private ads collect data that’s aggregated and anonymous, but still deliver insightful performance analytics to advertisers.In other words, it’s possible to have a thriving, healthy, and private online ad economy—third-party tracking isn’t a necessary part of the equation.Brave Ads, for example, is the first global digital ads platform built for privacy and a cookie-less future. It enables brands to carry out ad campaigns that reach otherwise unreachable audiences in a privacy-preserving way. It’s highly effective advertising without the trackers, cookies, and other creepy stuff that follows users across the Web.Those who make up the Brave Ads audience also happen to be the same people who are unreachable via traditional ad channels. They’re privacy seekers who use the Brave browser to block ads. They’re cord-cutters—80% don’t pay for cable or satellite TV. And they’re disconnectors—only 20% use Snapchat, TikTok, or Pinterest.And while this may sound like the profile of vanguard users, it’s in fact becoming the norm.How Brave Ads workBrave offers familiar ad units, like keyword-based search ads in Brave’s independent search engine, Brave Search. Brave’s search ads are privacy-preserving, text-based ads that appear at the top of a user’s search engine results page (SERP). Brave also offers a variety of other ad units that include full-page images that appear on new browser tabs, native ads in the Brave News feed, and familiar, device-level push notifications.The bundle of available Brave Ads are downloaded to the browser (and refreshed nearly every hour). But the ad matching only happens locally on-device, and ad performance isn’t associated with any given individual. No personal data makes it back to Brave’s servers (or even leaves the user’s device). Users get privacy; advertisers still get actionable insights on ad performance and ROI. And audiences are highly engaged.The aggregated reporting that Brave Ads generate provides useful details about views, clicks, site-visits, and conversions. More insights are available via privacy-respecting surveys that measure brand lift. Brands that advertise with Brave also enjoy boosted perception among unreachable audiences for making the effort to advertise in a privacy-respecting way. It’s a win-win ad model geared for the privacy-first future.Note: Brave Ads don’t replace the on-page, third-party ads that are blocked by Brave Shields. Instead, they’re unobtrusive, native ad units woven seamlessly into the Brave browserThis site can’t be reached is unreachable
Or a network or the unassigned devices in the inventory. AP Refresh Workflow The AP Refresh feature allows you to replace both provisioned and unprovisioned older AP models with newer AP models, using the Access Point Refresh workflow. You can use this procedure to replace old APs with new ones in Catalyst Center for the following use cases: Automation use case: Deployments where wireless controller and APs are provisioned through Catalyst Center network intent configurations. After AP refresh, the new AP is provisioned with the network intent configuration. Assurance use case: Deployments where Catalyst Center is used primarily for Assurance purposes and the wireless controller and APs are not provisioned through Catalyst Center network intent configurations. The new AP isn’t provisioned after AP refresh and only the old configuration is copied to the new AP. For device compatibility information, see the Catalyst Center Compatibility Matrix. Before you begin Ensure that the old AP is in the Unreachable state and assigned to a site. The new AP must not be assigned to any site. For the automation use case, the old AP site must be provisioned as a managed AP location for the wireless controller to which the new AP is associated. For the Assurance use case, the new AP must join the same wireless controller where the old AP was previously associated. For the automation use case, you must connect the new AP to a wireless controller. The new AP must either be available in the Catalyst Center inventory or. Troubleshooting 'Site is Unreachable' Error Fixing Unreachable Site Learn how to troubleshoot and fix the 'site is unreachable' error. Check your interneMy site is 'unreachable' and not responding.
Make sure that once you’ve launched your app, it remains running and keeps performing.What can go wrong?In order to know how and what we should monitor, it helps to have an understanding of what could potentially go wrong. The short answer is probably “well, a lot” — and as such, it’s a really tough question to answer definitively. At the same time, though, there are a range of things that we can anticipate might go wrong.Broadly speaking, we can divide these issues into a number of categories:Hitting “hard” limits; for example a full disk, hitting a physical memory limit or reaching the maximum number of processesNetwork issues; for example a site becoming unreachable, high packet losses, server connections going down or DNS failuresComponent or service failures; perhaps your database server has gone down, for example.Problems with third-party services; your S3 bucket is unreachable, your mail provider is experiencing issues, or your CDN has gone downProblems with your applications; errors and exceptions, inconsistencies in your data or even bugs in your codeKeeping third-party code or operating system components up-to-date; in particular checking for security patches or service packsThere are even silly examples of human error which, alas, do still happen; such as forgetting to renew a SSL certificate.Once you have an idea of what can go wrong, you start to get a feel for what to monitor.Important Things to ConsiderWhilst a lot of monitoring deals in metrics such as server response times, the amount of available memory or the level your CPU is running at, there’s nothing quite as important as the experience your users are having. In all likelihood there will be some correlation between the raw data from your server or application and the wait times your user faces — for example, high network latency probably means slow responseSite to Site VPN - Destination Net Unreachable
(0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 1 2016-01-02 03:01:05Infoservers[3628,3436]ChooseServer: selected server 'Download j0988320 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:01:18Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 2 2016-01-02 03:01:18Infoservers[3628,3436]ChooseServer: selected server 'Download k5769842 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:01:32Infodldwrap[3628,3436]GetFileWithRetry: 'avbugreport_ais-9cc.vpx' successfully downloaded and verified. 2016-01-02 03:01:32Infopkgengine[3628,3436]DownloadPackage(download): 'C:\Users\ADMINI~1\AppData\Local\Temp\_av_iup.tm~a03772\avbugreport_ais-9cc.vpx', ip: 23.32.248.123, size: 592374 bytes 2016-01-02 03:01:32Noticepackageinfo[3628,3436]IsFullOkay: avdump_x64_ais-9cc.vpx - not okay (doesn't exist) 2016-01-02 03:01:32Noticepackageinfo[3628,3436]IsFullOkay: avdump_x64_ais-9cc.vpx - not okay (doesn't exist) 2016-01-02 03:01:32Infopackageinfo[3628,3436]SetFullAsMarked: Package avdump_x64_ais set to 1 2016-01-02 03:01:43Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 1 2016-01-02 03:01:43Infoservers[3628,3436]ChooseServer: selected server 'Download g1301720 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:01:57Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 2 2016-01-02 03:01:57Infoservers[3628,3436]ChooseServer: selected server 'Download z3945188 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:02:09Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 3 2016-01-02 03:02:09Infoservers[3628,3436]ChooseServer: selected server 'Download c6775310 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:02:18Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 4 2016-01-02 03:02:18Infoservers[3628,3436]ChooseServer: selected server 'Download z3945188 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:02:31Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 5 2016-01-02 03:02:31Infoservers[3628,3436]ChooseServer: selected server 'Download c3003438 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:02:43Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 6 2016-01-02 03:02:43Infoservers[3628,3436]ChooseServer: selected server 'Download r7438288 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:02:58Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 7 2016-01-02 03:02:58Infoservers[3628,3436]ChooseServer: selected server 'Download j2554254 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:03:10Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 8 2016-01-02 03:03:10Infoservers[3628,3436]ChooseServer: selected server 'Download y0625269 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:03:23Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 9 2016-01-02 03:03:23Infoservers[3628,3436]ChooseServer: selected server 'Download r7438288 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:03:35Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 10 2016-01-02 03:03:35Infoservers[3628,3436]ChooseServer: selected server 'Download j0988320 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:03:37Errorpkgengine[3628,3436]DownloadPackage(download): 'C:\Users\ADMINI~1\AppData\Local\Temp\_av_iup.tm~a03772\avdump_x64_ais-9cc.vpx', ip: unknown, has failed with code:Imperva FTP download sites are unreachable
Typically we use the IcmpSendEcho function or a component like TIdIcmpClient to make a ping request from Delphi. Today I will show you another way to do this using the WMI (Windows Management Instrumentation). The WMI class which allow you to make a ping request is Win32_PingStatus, to use this class you only need to pass the parameter Address value in your WQL sentence , the form of the Address parameter can be either the computer name (ACCOUNT-PC), IPv4 address (192.168.154.102), or IPv6 address (2010:836B:4179::836B:4179).SELECT * FROM Win32_PingStatus where Address='www.google.com'Some of the advantages of use this class to make a ping is which supports IPv4 addresses and IPv6 addresses (Starting with Windows Vista) , and you can set the ping parameters in a single WQL sentence.For example if you want send a Buffer of 64 bytes (instead of the 32 default size) and resolve the address of the host server you only need to write a sentence like this :SELECT * FROM Win32_PingStatus where Address='192.168.1.221' AND BufferSize=64 AND ResolveAddressNames=TRUENow check this sample console application.program WMIPing;{$APPTYPE CONSOLE}uses SysUtils, ActiveX, ComObj, Variants;function GetStatusCodeStr(statusCode:integer) : string;begin case statusCode of 0 : Result:='Success'; 11001 : Result:='Buffer Too Small'; 11002 : Result:='Destination Net Unreachable'; 11003 : Result:='Destination Host Unreachable'; 11004 : Result:='Destination Protocol Unreachable'; 11005 : Result:='Destination Port Unreachable'; 11006 : Result:='No Resources'; 11007 : Result:='Bad Option'; 11008 : Result:='Hardware Error'; 11009 : Result:='Packet Too Big'; 11010 : Result:='Request Timed Out'; 11011 : Result:='Bad Request'; 11012 : Result:='Bad Route'; 11013 : Result:='TimeToLive Expired Transit'; 11014. Troubleshooting 'Site is Unreachable' Error Fixing Unreachable Site Learn how to troubleshoot and fix the 'site is unreachable' error. Check your interne Static assets to redirect a site to when it is unreachable - caen-web/site-unreachableComments
Sent to 192.168.10.250ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.250ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.250ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.251ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.251ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.251ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.251ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.252ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.252ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.252ICMP Host Unreachable from 192.168.10.249 for ICMP Echo sent to 192.168.10.252192.168.10.250 is unreachable192.168.10.251 is unreachable192.168.10.252 is unreachablehping:hping is another sister command of ping to test the network. In some distributions it is known as hping3 and not installed by default. hping3 is a network tool able to send custom TCP/IP packets and to display target replies like ping program does with ICMP replies.It also uses the same switches like ping for basic functionalities like -h for help and -c for count etc. Here are few basic examples for hping3.hping3 localhost -c 3HPING localhost (lo 127.0.0.1): NO FLAGS are set, 40 headers + 0 data byteslen=40 ip=127.0.0.1 ttl=64 DF id=10586 sport=0 flags=RA seq=0 win=0 rtt=3.5 mslen=40 ip=127.0.0.1 ttl=64 DF id=10657 sport=0 flags=RA seq=1 win=0 rtt=2.3 mslen=40 ip=127.0.0.1 ttl=64 DF id=10668 sport=0 flags=RA seq=2 win=0 rtt=2.4 ms--- localhost hping statistic ---3 packets transmitted, 3 packets received, 0% packet lossround-trip min/avg/max = 2.3/2.7/3.5 msFor sending TCP packet to specific port like
2025-03-28These options can fall short when it comes to growing with new users that aren’t already visiting a brand’s website or using its app. (This is typically when brands turn to third-party data that’s generated by cross-site tracking—the very practice users are rebelling against.)There is, however, an opportunity for privacy-respecting advertising that’s still capable of reaching new audiences. Ads that preserve privacy refrain from tracking users or building profiles, but can still be personalized and targeted. Private ads collect data that’s aggregated and anonymous, but still deliver insightful performance analytics to advertisers.In other words, it’s possible to have a thriving, healthy, and private online ad economy—third-party tracking isn’t a necessary part of the equation.Brave Ads, for example, is the first global digital ads platform built for privacy and a cookie-less future. It enables brands to carry out ad campaigns that reach otherwise unreachable audiences in a privacy-preserving way. It’s highly effective advertising without the trackers, cookies, and other creepy stuff that follows users across the Web.Those who make up the Brave Ads audience also happen to be the same people who are unreachable via traditional ad channels. They’re privacy seekers who use the Brave browser to block ads. They’re cord-cutters—80% don’t pay for cable or satellite TV. And they’re disconnectors—only 20% use Snapchat, TikTok, or Pinterest.And while this may sound like the profile of vanguard users, it’s in fact becoming the norm.How Brave Ads workBrave offers familiar ad units, like keyword-based search ads in Brave’s independent search engine, Brave Search. Brave’s search ads are privacy-preserving, text-based ads that appear at the top of a user’s search engine results page (SERP). Brave also offers a variety of other ad units that include full-page images that appear on new browser tabs, native ads in the Brave News feed, and familiar, device-level push notifications.The bundle of available Brave Ads are downloaded to the browser (and refreshed nearly every hour). But the ad matching only happens locally on-device, and ad performance isn’t associated with any given individual. No personal data makes it back to Brave’s servers (or even leaves the user’s device). Users get privacy; advertisers still get actionable insights on ad performance and ROI. And audiences are highly engaged.The aggregated reporting that Brave Ads generate provides useful details about views, clicks, site-visits, and conversions. More insights are available via privacy-respecting surveys that measure brand lift. Brands that advertise with Brave also enjoy boosted perception among unreachable audiences for making the effort to advertise in a privacy-respecting way. It’s a win-win ad model geared for the privacy-first future.Note: Brave Ads don’t replace the on-page, third-party ads that are blocked by Brave Shields. Instead, they’re unobtrusive, native ad units woven seamlessly into the Brave browser
2025-04-11Make sure that once you’ve launched your app, it remains running and keeps performing.What can go wrong?In order to know how and what we should monitor, it helps to have an understanding of what could potentially go wrong. The short answer is probably “well, a lot” — and as such, it’s a really tough question to answer definitively. At the same time, though, there are a range of things that we can anticipate might go wrong.Broadly speaking, we can divide these issues into a number of categories:Hitting “hard” limits; for example a full disk, hitting a physical memory limit or reaching the maximum number of processesNetwork issues; for example a site becoming unreachable, high packet losses, server connections going down or DNS failuresComponent or service failures; perhaps your database server has gone down, for example.Problems with third-party services; your S3 bucket is unreachable, your mail provider is experiencing issues, or your CDN has gone downProblems with your applications; errors and exceptions, inconsistencies in your data or even bugs in your codeKeeping third-party code or operating system components up-to-date; in particular checking for security patches or service packsThere are even silly examples of human error which, alas, do still happen; such as forgetting to renew a SSL certificate.Once you have an idea of what can go wrong, you start to get a feel for what to monitor.Important Things to ConsiderWhilst a lot of monitoring deals in metrics such as server response times, the amount of available memory or the level your CPU is running at, there’s nothing quite as important as the experience your users are having. In all likelihood there will be some correlation between the raw data from your server or application and the wait times your user faces — for example, high network latency probably means slow response
2025-03-25(0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 1 2016-01-02 03:01:05Infoservers[3628,3436]ChooseServer: selected server 'Download j0988320 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:01:18Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 2 2016-01-02 03:01:18Infoservers[3628,3436]ChooseServer: selected server 'Download k5769842 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:01:32Infodldwrap[3628,3436]GetFileWithRetry: 'avbugreport_ais-9cc.vpx' successfully downloaded and verified. 2016-01-02 03:01:32Infopkgengine[3628,3436]DownloadPackage(download): 'C:\Users\ADMINI~1\AppData\Local\Temp\_av_iup.tm~a03772\avbugreport_ais-9cc.vpx', ip: 23.32.248.123, size: 592374 bytes 2016-01-02 03:01:32Noticepackageinfo[3628,3436]IsFullOkay: avdump_x64_ais-9cc.vpx - not okay (doesn't exist) 2016-01-02 03:01:32Noticepackageinfo[3628,3436]IsFullOkay: avdump_x64_ais-9cc.vpx - not okay (doesn't exist) 2016-01-02 03:01:32Infopackageinfo[3628,3436]SetFullAsMarked: Package avdump_x64_ais set to 1 2016-01-02 03:01:43Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 1 2016-01-02 03:01:43Infoservers[3628,3436]ChooseServer: selected server 'Download g1301720 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:01:57Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 2 2016-01-02 03:01:57Infoservers[3628,3436]ChooseServer: selected server 'Download z3945188 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:02:09Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 3 2016-01-02 03:02:09Infoservers[3628,3436]ChooseServer: selected server 'Download c6775310 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:02:18Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 4 2016-01-02 03:02:18Infoservers[3628,3436]ChooseServer: selected server 'Download z3945188 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:02:31Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 5 2016-01-02 03:02:31Infoservers[3628,3436]ChooseServer: selected server 'Download c3003438 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:02:43Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 6 2016-01-02 03:02:43Infoservers[3628,3436]ChooseServer: selected server 'Download r7438288 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:02:58Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 7 2016-01-02 03:02:58Infoservers[3628,3436]ChooseServer: selected server 'Download j2554254 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:03:10Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 8 2016-01-02 03:03:10Infoservers[3628,3436]ChooseServer: selected server 'Download y0625269 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:03:23Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 9 2016-01-02 03:03:23Infoservers[3628,3436]ChooseServer: selected server 'Download r7438288 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:03:35Errordldwrap[3628,3436]GetFileWithRetry: An error 41222 (0x0000A106) [Host unreachable] has occured when downloading a file from ' Next try: 10 2016-01-02 03:03:35Infoservers[3628,3436]ChooseServer: selected server 'Download j0988320 ABS Server' with current url ' of type 'URL_TYPE_DOWNLOAD_PROGRAM'. 2016-01-02 03:03:37Errorpkgengine[3628,3436]DownloadPackage(download): 'C:\Users\ADMINI~1\AppData\Local\Temp\_av_iup.tm~a03772\avdump_x64_ais-9cc.vpx', ip: unknown, has failed with code:
2025-04-14This is relatively old question, but I wanted to add that instead of netcat you can use hping3 or nping (this tool usually comes with nmap) to check UDP port in similar fashion. These tools have much more verbose output and provide more data.For example checking closed UDP using hping3:$ sudo hping3 --udp -p 26010 router.localHPING router.local (eth0 192.168.1.1): udp mode set, 28 headers + 0 data bytesICMP Port Unreachable from ip=192.168.1.1 name=router.localICMP Port Unreachable from ip=192.168.1.1 name=router.local^C--- router.local hping statistic ---2 packets tramitted, 2 packets received, 0% packet lossround-trip min/avg/max = 0.0/0.0/0.0 msor via nping:$ sudo nping -c 2 --udp -p 26010 router.localStarting Nping 0.7.80 ( ) at 2020-09-19 20:57 EESTSENT (0.0173s) UDP 192.168.1.40:53 > 192.168.1.1:26010 ttl=64 id=16061 iplen=28 RCVD (0.0177s) ICMP [192.168.1.1 > 192.168.1.40 Port unreachable (type=3/code=3) ] IP [ttl=64 id=4711 iplen=56 ]SENT (1.0181s) UDP 192.168.1.40:53 > 192.168.1.1:26010 ttl=64 id=16061 iplen=28 RCVD (1.0185s) ICMP [192.168.1.1 > 192.168.1.40 Port unreachable (type=3/code=3) ] IP [ttl=64 id=4794 iplen=56 ] Max rtt: 0.418ms | Min rtt: 0.343ms | Avg rtt: 0.380msRaw packets sent: 2 (56B) | Rcvd: 2 (112B) | Lost: 0 (0.00%)Nping done: 1 IP address pinged in 1.03 secondsSending data to closed UDP port (if it isn't filtered by firewall) generates ICMP message with icmp_type 3 (destination unreachable), which should be visible in examples above. OS of the client processes this message and returns error to the application that tried to send data onto that port. In the same time OS could report error in other cases too, for example
2025-04-15Akka version: 2.5.11In a 3-node cluster setup, upon killing and restarting the first seed node (as listed in the akka.conf), we sometimes see that the node does not or is not allowed to rejoin the cluster. After the seed node timeout, which we have set to 12s, it joins itself and forms a cluster island. This is automated in a robot test environment.As an example, we have node1 (first seed node - address 10.30.170.94), node2 (10.30.170.26), and node3 (10.30.170.84). Initially all the nodes are started and connected and the cluster is working correctly. Then a kill -9 is issued to node1. Both node2 and node3 lose connection and mark node1 as unreachable as expected. On node2, we see: akka.tcp://opendaylight-cluster-data@10.30.170.94:2550: Unreachable [Unreachable] (1), akka.tcp://opendaylight-cluster-data@10.30.170.84:2550 -> akka.tcp://opendaylight-cluster-data@10.30.170.94:2550: Unreachable [Unreachable] (1)], member status: [akka.tcp://opendaylight-cluster-data@10.30.170.26:2550 Up seen=true, akka.tcp://opendaylight-cluster-data@10.30.170.84:2550 Up seen=true, akka.tcp://opendaylight-cluster-data@10.30.170.94:2550 Up seen=false]">2018-07-16T11:17:14,609 | WARN | opendaylight-cluster-data-akka.actor.default-dispatcher-20 | ReliableDeliverySupervisor | 41 - com.typesafe.akka.slf4j - 2.5.11 | Association with remote system [akka.tcp://opendaylight-cluster-data@10.30.170.94:2550] has failed, address is now gated for [5000] ms. Reason: [Association failed with [akka.tcp://opendaylight-cluster-data@10.30.170.94:2550]] Caused by: [Connection refused: /10.30.170.94:2550]2018-07-16T11:17:18,229 | INFO | opendaylight-cluster-data-akka.actor.default-dispatcher-18 | Cluster(akka://opendaylight-cluster-data) | 41 - com.typesafe.akka.slf4j - 2.5.11 | Cluster Node [akka.tcp://opendaylight-cluster-data@10.30.170.26:2550] - Leader can currently not perform its duties, reachability status: [akka.tcp://opendaylight-cluster-data@10.30.170.26:2550 -> akka.tcp://opendaylight-cluster-data@10.30.170.94:2550: Unreachable [Unreachable] (1), akka.tcp://opendaylight-cluster-data@10.30.170.84:2550 -> akka.tcp://opendaylight-cluster-data@10.30.170.94:2550: Unreachable [Unreachable] (1)], member status: [akka.tcp://opendaylight-cluster-data@10.30.170.26:2550 Up seen=true, akka.tcp://opendaylight-cluster-data@10.30.170.84:2550 Up seen=true, akka.tcp://opendaylight-cluster-data@10.30.170.94:2550 Up seen=false]On node3:2018-07-16T11:18:14,859 | WARN | opendaylight-cluster-data-akka.actor.default-dispatcher-3 | ReliableDeliverySupervisor | 41 - com.typesafe.akka.slf4j - 2.5.11 | Association with remote system [akka.tcp://opendaylight-cluster-data@10.30.170.94:2550] has failed, address is now gated for [5000] ms. Reason: [Association failed with [akka.tcp://opendaylight-cluster-data@10.30.170.94:2550]] Caused by: [Connection refused: /10.30.170.94:2550]After restarting node1, we see that it sends InitJoin messages to node2 and node3 and actually reports an InitJoinAck from node2 but eventually joins itself after 22s:2018-07-16T11:18:20,251 | INFO | opendaylight-cluster-data-akka.actor.default-dispatcher-21 | Cluster(akka://opendaylight-cluster-data) | 41 - com.typesafe.akka.slf4j - 2.5.11 | Cluster Node [akka.tcp://opendaylight-cluster-data@10.30.170.94:2550] - Received InitJoinAck message from [Actor[akka.tcp://opendaylight-cluster-data@10.30.170.26:2550/system/cluster/core/daemon#-1596937295]] to [akka.tcp://opendaylight-cluster-data@10.30.170.94:2550]2018-07-16T11:18:42,585 | INFO | opendaylight-cluster-data-akka.actor.default-dispatcher-19 | Cluster(akka://opendaylight-cluster-data) | 41 - com.typesafe.akka.slf4j - 2.5.11 | Cluster Node [akka.tcp://opendaylight-cluster-data@10.30.170.94:2550] - Node [akka.tcp://opendaylight-cluster-data@10.30.170.94:2550] is JOINING, roles [member-1, dc-default]2018-07-16T11:18:42,614 | INFO | opendaylight-cluster-data-akka.actor.default-dispatcher-19 | Cluster(akka://opendaylight-cluster-data) | 41 - com.typesafe.akka.slf4j - 2.5.11 | Cluster Node [akka.tcp://opendaylight-cluster-data@10.30.170.94:2550] - Leader is moving node [akka.tcp://opendaylight-cluster-data@10.30.170.94:2550] to [Up]On node2, we see InitJoin messages incoming and InitJoinAcks outgoing and that it noticed that node1 was restarted with a new incarnation, marked it as Down, and stated it was removing the previous unreachable incarnation:2018-07-16T11:18:20,105 | INFO | opendaylight-cluster-data-akka.actor.default-dispatcher-2 | Cluster(akka://opendaylight-cluster-data) | 41 - com.typesafe.akka.slf4j - 2.5.11 | Cluster Node [akka.tcp://opendaylight-cluster-data@10.30.170.26:2550] - Received InitJoin message from [Actor[akka.tcp://opendaylight-cluster-data@10.30.170.94:2550/system/cluster/core/daemon/firstSeedNodeProcess-1#-2094984711]] to [akka.tcp://opendaylight-cluster-data@10.30.170.26:2550]2018-07-16T11:18:20,106 | INFO | opendaylight-cluster-data-akka.actor.default-dispatcher-2 | Cluster(akka://opendaylight-cluster-data) | 41 - com.typesafe.akka.slf4j - 2.5.11 | Cluster Node [akka.tcp://opendaylight-cluster-data@10.30.170.26:2550] - Sending InitJoinAck message from node [akka.tcp://opendaylight-cluster-data@10.30.170.26:2550] to [Actor[akka.tcp://opendaylight-cluster-data@10.30.170.94:2550/system/cluster/core/daemon/firstSeedNodeProcess-1#-2094984711]]2018-07-16T11:18:20,291 | INFO | opendaylight-cluster-data-akka.actor.default-dispatcher-18 | Cluster(akka://opendaylight-cluster-data) | 41 - com.typesafe.akka.slf4j - 2.5.11 | Cluster Node [akka.tcp://opendaylight-cluster-data@10.30.170.26:2550] - New incarnation of existing member [Member(address = akka.tcp://opendaylight-cluster-data@10.30.170.94:2550, status = Up)] is trying to join. **Existing will be removed from the cluster and then new member will be allowed to join.**2018-07-16T11:18:20,292 | INFO | opendaylight-cluster-data-akka.actor.default-dispatcher-18 | Cluster(akka://opendaylight-cluster-data) | 41
2025-04-14