TT error

During the winter of 2013-2014, I've noticed this error occurring occasionally. I click again or refresh and the site is fine.

But this morning, Mar 6, 2014, the error is occurring more often.

q.
Service Temporarily Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Apache/2.2.8 (Ubuntu) DAV/2 SVN/1.5.1 PHP/5.2.4-2ubuntu5.27 with Suhosin-Patch mod_ssl/2.2.8 OpenSSL/0.9.8g Server at toledotalk.com Port 80
q..


Logging into my web hosting provider at 9:20 a.m. on Mar 6, 2014 to check traffic, although I don't think it will mean anything to me.

View Storage And Traffic 

This Month
Please note that the traffic total isn't accurate for the current month because the current traffic logs need to be processed.

Start Date: 20140301
End Date: 20140306

Traffic (total)
   14.077 GB
   317487 hits

Storage (daily average)
    1.062 GB total
    0.450 GB home
    0.235 GB mail
    0.000 GB virtual mail
    0.377 GB mysql
Storage (yesterday)
    1.204 GB total
    0.592 GB home
    0.235 GB mail
    0.000 GB virtual mail
    0.377 GB mysql


Last Month
Start Date: 20140201
End Date: 20140228

Traffic (total)
   76.339 GB
  1889075 hits

Storage (daily average)
    1.223 GB total
    0.612 GB home
    0.235 GB mail
    0.000 GB virtual mail
    0.375 GB mysql



hr.

My Mar 11, 2014 TT comment in a thread, started by someone else.

http://toledotalk.com/cgi-bin/tt.pl/article/173369/11Mar2014/Toledo_Talk_Problems

---

The Toledo Talk web server returns a 503 error.

q.
Service Temporarily Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
q..

I'm guessing that the reasons for the error are unrelated to what's listed in the above message.

The web server produced this error occasionally in February and maybe January. But  in the past seven days, the frequency of this error has increased dramatically.

The Linux server is fine. The database is fine. It's the web server that is having the issue.

I'll contact the web hosting company.

The simple solution for now is to hit refresh. Before this past week, the error lasted only a second or two, but now it may last for 5 to 10 seconds.




 #toledotalk