What does these Bug reports mean?

I get a lot of these Bug reports that are similar to this one. Sometimes they are much longer. My site seams to be working fine. Are these reports important? Should I just delete them?

I do go to the files that are listed but do not know what to do with the line items in question.

[23-May-2017 14:11:33 America/New_York] Request URI: /index.php?main_page=product_info&products_id=35, IP address: 66.249.64.76
#1 mysqli_connect() called at [xxxxxxxx/xxxxxxxx/xxxxxxxx/xxxxxxxx/xxxxxxxx/zencart155e/includes/classes/db/mysql/query_factory.php:64]
#2 queryFactory->connect() called at [xxxxxxxx/xxxxxxxx/xxxxxxxx/xxxxxxxx/xxxxxxxx/zencart155e/includes/init_includes/init_database.php:23]
#3 require(xxxxxxxx/xxxxxxxx/xxxxxxxx/xxxxxxxx/xxxxxxxx/zencart155e/includes/init_includes/init_database.php) called at [xxxxxxxx/xxxxxxxx/xxxxxxxx/xxxxxxxx/xxxxxxxx/zencart155e/includes/autoload_func.php:48]
#4 require(xxxxxxxx/xxxxxxxx/xxxxxxxx/xxxxxxxx/xxxxxxxx/zencart155e/includes/autoload_func.php) called at [xxxxxxxx/xxxxxxxx/xxxxxxxx/xxxxxxxx/xxxxxxxx/zencart155e/includes/application_top.php:170]
#5 require(xxxxxxxx/xxxxxxxx/xxxxxxxx/xxxxxxxx/xxxxxxxx/zencart155e/includes/application_top.php) called at [xxxxxxxx/xxxxxxxx/xxxxxxxx/xxxxxxxx/xxxxxxxx/zencart155e/index.php:26]

[23-May-2017 14:11:33 America/New_York] PHP Warning: mysqli_connect(): (HY000/2002): No route to host in xxxxxxxx/xxxxxxxx/xxxxxxxx/xxxxxxxx/xxxxxxxx/zencart155e/includes/classes/db/mysql/query_factory.php on line 64

From searching the internet and reading a few similar posts regarding: "No route to host in" it appears that this is a server/network setup issue. Would suggest speaking with your host about the problem(s). Likely they have changed something (not likely to say that they have) and it has/is causing this issue.

mc12345678:

From searching the internet and reading a few similar posts regarding: "No route to host in" it appears that this is a server/network setup issue. Would suggest speaking with your host about the problem(s). Likely they have changed something (not likely to say that they have) and it has/is causing this issue.

Thanks for your advice.

Sounds like your host's database engine/server is being restarted during those times.

DrByte:

Sounds like your host's database engine/server is being restarted during those times.

I do not know what you mean DrByte. Is this something I should be concerned about or should I just ignore them and delete them?

The reports say that your database (and therefore your shop) have gone offline. If this happens frequently it can be a sign of an unstable server and your site going offline too many times. The Database server can go offline if it's too busy, maybe the server you are located on hasn't enough resources.

You can contact your host & ask them why MySQL went offline. They should be aware & able to help.

terraGirl:

The reports say that your database (and therefore your shop) have gone offline. If this happens frequently it can be a sign of an unstable server and your site going offline too many times. The Database server can go offline if it's too busy, maybe the server you are located on hasn't enough resources.

You can contact your host & ask them why MySQL went offline. They should be aware & able to help.

Thanks, I will give them a call to see what they have to say.
Appreciate the help.

You should delete the error logs related to the MySQL server as you know what the problem is. Except for the 3 default files (index.php, index.html, .htaccess) that remain at all times, you want to keep the "logs" dir. pretty much empty so you can easily see when new problems occur. Also, a service like UptimeRobot (free) can help you track uptime for your website; an important part of website Maintenance.

Of course understand that if a conversation is yet to be had about the dates/times and messages received, if the logs have been removed (without some form of backup) then such data is lost on your side and could delay addressing the issue(s) with the host. Afterall, what proof or information would you have if it has been deleted?

Once that is resolved to your liking, then yes the logs should be removed and when a new one appears it should be understood why and as necessary addressed or removed.

After seeing hundreds more errors in the logs file I finely got around to calling my hosting company. They spent some time with me looking at many of the files and found that the IP addresses are coming from a company called "Digital Ocean". Anyone know anything about this company?
My hosting company said they are pinging my database and that is why I am getting all of these. Wondering if I should block there IP address?
Your input would be very much appreciated.

Any IP causing problems with your site that you cannot control or correct should be blocked.

Maynards:

After seeing hundreds more errors in the logs file I finely got around to calling my hosting company. They spent some time with me looking at many of the files and found that the IP addresses are coming from a company called "Digital Ocean". Anyone know anything about this company?
My hosting company said they are pinging my database and that is why I am getting all of these. Wondering if I should block there IP address?
Your input would be very much appreciated.

Digital Ocean are a hosting company, but with a difference. They are primarily used by developers that don't require a permanent online presence. It is a cloud based service that bill based on usage (rather than monthly, yearly, etc). Basically, pay for resources used rather than time.
I've used them myself on occasion to test for software compatibility with different operating systems (its pretty cool to be able to deploy a server of almost any configuration, use it for an hour or so testing, then destroy it again - for the cost of just a few cents)

Digital Ocean are a reputable company that take complaints of people using their servers for nefarious purposes very seriously, and it sounds like you probably have a legitimate complaint.

I would suggest that you report the issue to Digital Ocean before considering blocking the IP.
The reasons being

1. If a rogue customer is targeting you and you block the IP they will simply deploy another 'droplet' (server) with a different IP to continue their probe. If you report them to DigitalO they will cancel the abusers account (so as to help protect their reputation) thus making blocking unnecessary.
2. More often than not, when people block an IP address they never seem to unblock it again, and since a dynamic IP address can be passed from customer to customer, you will not only be blocking the one rogue customer, but you will also be blocking future customers - some of which may end up wanting to buy from you. (Although a Digital Ocean customer is unlikely to be a 'real' customer (to your store) due to the nature of their service, I feel that this is always worth keeping in mind whenever considering blocking IP addresses. Often times all you end up doing is blocking some legitimate (but unfortunate) person that has had their computer hacked and being used as a 'relay' for the bad guy. Basically, you end up blocking a victim rather then the perpetrator. :(

Now having said that - I can't think of any scenario where a Digital Ocean customer would ever have a legitimate reason to access any aspect of your store/site (unless requested as part of vulnerability testing) so you will never get a real store customer from anyone using a Digital Ocean IP address, so from that POV, IP blocking isn't going to harm the innocent. It is simply better to just report them so the abuser(s) get their account cancelled.

Blocking the IP without reporting is killing the messenger, but not solving the problem.

Cheers
RodG.

Thanks RodG for your explanation on how this works with a server. I still consider myself as a newbie on a lot of this stuff.

RodG:

Digital Ocean are a hosting company, but with a difference. They are primarily used by developers that don't require a permanent online presence. It is a cloud based service that bill based on usage (rather than monthly, yearly, etc). Basically, pay for resources used rather than time.
I've used them myself on occasion to test for software compatibility with different operating systems (its pretty cool to be able to deploy a server of almost any configuration, use it for an hour or so testing, then destroy it again - for the cost of just a few cents)

Digital Ocean are a reputable company that take complaints of people using their servers for nefarious purposes very seriously, and it sounds like you probably have a legitimate complaint.

I would suggest that you report the issue to Digital Ocean before considering blocking the IP.
The reasons being

1. If a rogue customer is targeting you and you block the IP they will simply deploy another 'droplet' (server) with a different IP to continue their probe. If you report them to DigitalO they will cancel the abusers account (so as to help protect their reputation) thus making blocking unnecessary.
2. More often than not, when people block an IP address they never seem to unblock it again, and since a dynamic IP address can be passed from customer to customer, you will not only be blocking the one rogue customer, but you will also be blocking future customers - some of which may end up wanting to buy from you. (Although a Digital Ocean customer is unlikely to be a 'real' customer (to your store) due to the nature of their service, I feel that this is always worth keeping in mind whenever considering blocking IP addresses. Often times all you end up doing is blocking some legitimate (but unfortunate) person that has had their computer hacked and being used as a 'relay' for the bad guy. Basically, you end up blocking a victim rather then the perpetrator. :(

Now having said that - I can't think of any scenario where a Digital Ocean customer would ever have a legitimate reason to access any aspect of your store/site (unless requested as part of vulnerability testing) so you will never get a real store customer from anyone using a Digital Ocean IP address, so from that POV, IP blocking isn't going to harm the innocent. It is simply better to just report them so the abuser(s) get their account cancelled.

Blocking the IP without reporting is killing the messenger, but not solving the problem.

Cheers
RodG.
I agree. Good advice, RodG.

Since my last post I did contact Digital Ocean the owners of the IP addresses that have been triggering hundreds of files in my debug file. It looks like they have no interest in correcting the problem. Today I see hundreds more in the logs file.

Any other suggestion of what I should do would be appreciated.

Maynards:

Since my last post I did contact Digital Ocean the owners of the IP addresses that have been triggering hundreds of files in my debug file. It looks like they have no interest in correcting the problem. Today I see hundreds more in the logs file.

Any other suggestion of what I should do would be appreciated.

Same thing happened quite a while back with us. After following a similar route to that suggested by RodG and receiving response similar to yours, I blocked the entire DigitalOcean IP range.

Be careful blocking the entire DO range, or you'll run into troubles with Zen Cart upgrade alert notifications, since those services are hosted on one of our DO droplets.

i'm not sure where your host came up with digital ocean. in the OP, the IP address is:

66.249.64.76

when i do a lookup on that address, it brings me to mountain view and google.

in my experience, when i see these errors, it is due to an insufficient amount of resources mostly due to some aggressive spidering/indexing of your website. i think terraGirl, in post 6, covers it quite adequately.

blocking those IP addresses could do you a disservice as your site will not be indexed.

it is difficult in a shared hosting environment to find an adequately tuned server that can handle all requests coming from spiders and bots.

i would do some reading on throttling spiders and bots, ie:

http://beamusup.com/configuring-search-engine-robot-crawl-rate/

if you and your host can not address these issues, i would look for another host.

good luck!

carlwhat:

i'm not sure where your host came up with digital ocean. in the OP, the IP address is:

66.249.64.76

when i do a lookup on that address, it brings me to mountain view and google.

Shoot. I just took the OP at their word that this was a Digital Ocean address. I really should have known better and verified it for myself.

Hardly a surprise that DO showed no apparent interest. Not their problem, and nothing they could do.

I definitely agree that blocking this IP address would be a bad move, especially since many stores could never survive without Google (something that always worries me).

Limiting the crawl rate would be the way to go.

Cheers
RodG

carlwhat:

i'm not sure where your host came up with digital ocean. in the OP, the IP address is:

66.249.64.76

when i do a lookup on that address, it brings me to mountain view and google.

in my experience, when i see these errors, it is due to an insufficient amount of resources mostly due to some aggressive spidering/indexing of your website. i think terraGirl, in post 6, covers it quite adequately.

blocking those IP addresses could do you a disservice as your site will not be indexed.

it is difficult in a shared hosting environment to find an adequately tuned server that can handle all requests coming from spiders and bots.

i would do some reading on throttling spiders and bots, ie:

http://beamusup.com/configuring-search-engine-robot-crawl-rate/

if you and your host can not address these issues, i would look for another host.

good luck!

Good Catch carlwhat
I posted the only one I can find with that IP address. I should have posted any other. My mistake.

All the others that I looked at where coming from Digital Ocean.