Regarding GLIBC_PRIVATE errors in your python application

Posted in Problems by

A recent system update to the core glibc package seems to have caused a small number of python apps hosted on our servers to stop working, showing the following in their error logs:

ImportError: /lib64/libresolv.so.2: symbol __h_errno, version
GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

The Apache stack needs to fully stop for this to be fixed. You can do that by starting an ssh session, traversing to the directory hosting your app, and using the `stop` and `start` scripts:

cd ~/webapps/your_app
./apache2/bin/stop
./apache2/bin/start

If you are having any trouble or need further assistance with this, please raise aticket and our support team will gladly help you with.

-
-

[Done] Scheduled maintenance on our ticketing system on Sunday, April the 22nd

Posted in Uncategorized by

On Sunday, 22nd of April, between 11:00 and 12:00 UTC, we will be migrating our ticketing system to new hardware.

During this time our ticketing system will be unavailable. You will not be able to raise new tickets, nor reply or review old ones.

We expect total downtime to be less than 30 minutes.

2018-04-22 12:10 UTC: We are starting the maintenance.

2018-04-22 12:42 UTC: The maintenance has been successfully completed.

-
-

[Fixed] Widespread network issues

Posted in Downtime by

We are currently seeing widespread connectivity issues across our hosting platform, and this is affecting both webserver-to-webserver communication as well as external website accessibility for hosted sites. We’re working on restoring normal network functionality as quickly as possible.

Update Thu Apr 19 07:20 UTC 2018: At this point we believe that we’ve fixed all network issues and that full service has been restored. If you’re still seeing network problems at this time, please let our Support team know.

Update Thu Apr 19 10:11 UTC 2018: We haven’t received any more reports of issues and everything looks good, so we’re marking this Fixed.

-
-

[Done] Emergency Europe network maintenance on March 27-28, 2018

Posted in Uncategorized by

On March 27-28, 2018 between 22:30 UTC and 1:00 UTC we will be performing
emergency network maintenance on our Europe based servers.

Connectivity to the servers will be interrupted for up to 30 minutes during the
maintenance window.

2018-03-28 03:12 UTC: The maintenance has been successfully completed.

-
-

[Fixed] Webmail problems

Posted in Problems by

There is currently an issue with the Webmail interface at https://webmail.webfaction.com which is resulting in sporadic 500 Internal Server Errors for some email users. We are looking into the problem and hope to have normal service restored soon. We will update this entry as soon as we have more information.

2018-03-27 11:25 UTC: The problem has been solved. If you see any other errors, please feel free to contact our support team by opening a ticket.

-
-

[Done] SOCKS proxy for outgoing connections disabled

Posted in Service change by

Starting 30th of March 2018, all outgoing SOCKS proxies from servers will be disabled.

You will still be able to connect to the server your account is on via SSH and create a tunnel to our MySQL and PostgreSQL databases or your long running application like the Apache or Nginx instance your Django or Rails application runs.

The most important reason for this is that an SSH tunnel or SOCKS connection can be used to mask malicious traffic and attacks to other servers, within or outside of the WebFaction network, which could lead to the server being blacklisted or even having its IP address null rooted by the datacenter, causing a disruption to all the clients hosted there.

The majority of our users won’t be affected by the new policy but if you have any questions or concerns regarding this change, please open a support ticket via our control panel to let us know.

2018-03-30 10:02 UTC: This has been deployed everywhere.

-
-

[Fixed] Several US servers inaccessible

Posted in Downtime by

We’ve just got an alert about the following US based servers being inaccessible.

We’re investigating at this time and will update this post when more information is available.

The affected shared servers are: web500, web501, web518, web521, web524, web590, web591, web592, web594, web595, web596, web597, web598, web599, web600, web601, web602, web603, web608, web609, web610, web611, web612, web613, web614, web615, web616, web617, web618, web619, web620, web621, web622, web623, web624, web625, web626, web627, web628, web629, web630, web631, web632, web634.

The affected cloud instances are: wf-148-72-160-10, wf-148-72-160-103, wf-148-72-160-104, wf-148-72-160-105, wf-148-72-160-106, wf-148-72-160-107, wf-148-72-160-108, wf-148-72-160-109, wf-148-72-160-110, wf-148-72-160-111, wf-148-72-160-114, wf-148-72-160-115, wf-148-72-160-117, wf-148-72-160-118, wf-148-72-160-119, wf-148-72-160-12, wf-148-72-160-120, wf-148-72-160-13, wf-148-72-160-14, wf-148-72-160-16, wf-148-72-160-17, wf-148-72-160-5, wf-148-72-160-6, wf-148-72-160-7, wf-148-72-160-8, wf-148-72-160-9, wf-207-38-86-102, wf-207-38-86-125, wf-207-38-86-135, wf-207-38-86-138, wf-207-38-86-140, wf-207-38-86-145, wf-207-38-86-147, wf-207-38-86-149, wf-207-38-86-150, wf-207-38-86-159, wf-207-38-86-160, wf-207-38-86-164, wf-207-38-86-165, wf-207-38-86-166, wf-207-38-86-167, wf-207-38-86-168, wf-207-38-86-170, wf-207-38-86-171, wf-207-38-86-175, wf-207-38-86-187, wf-207-38-86-192, wf-207-38-86-194, wf-207-38-86-67, wf-207-38-86-68, wf-207-38-86-77, wf-207-38-92-106, wf-207-38-92-115, wf-207-38-92-122, wf-207-38-92-123, wf-207-38-92-124, wf-207-38-92-125, wf-207-38-92-135, wf-207-38-92-14, wf-207-38-92-144, wf-207-38-92-149, wf-207-38-92-176, wf-207-38-92-18, wf-207-38-92-182, wf-207-38-92-183, wf-207-38-92-184, wf-207-38-92-215, wf-207-38-92-244, wf-207-38-92-5, wf-207-38-92-55, wf-207-38-92-6, wf-207-38-92-61, wf-207-38-92-7, wf-207-38-92-93, wf-207-38-92-94, wf-207-38-92-95, wf-207-38-93-134, wf-207-38-93-174, wf-207-38-93-187, wf-207-38-93-216, wf-207-38-93-252, wf-207-38-93-253, wf-207-38-93-254, wf-207-38-93-35, wf-207-38-93-36, wf-207-38-93-93, wf-207-38-94-108, wf-207-38-94-111, wf-207-38-94-140, wf-207-38-94-159, wf-207-38-94-181, wf-207-38-94-206, wf-207-38-94-21, wf-207-38-94-22, wf-207-38-94-224, wf-207-38-94-230, wf-207-38-94-235, wf-207-38-94-241, wf-207-38-94-251, wf-207-38-94-69, wf-207-38-94-70, wf-207-38-94-78, wf-207-38-94-91

2018-03-03 16:19 UTC We’ve identified the cause as a power outage. Servers are beginning to come back online now. We’ll update this post if anything changes.

2018-03-03 17:14 UTC The power outage was caused by a cooling failure. This is being worked on now. We’ll update this post when more information becomes available.

2018-03-03 18:50 UTC The issue is resolved and all servers have been restarted. We’ll continue to monitor. If you see any issues, please open a support ticket.

-
-

Unexpected downtime for Web463.

Posted in Uncategorized by

We had a brief period of downtime while we restarted the hardware. Web463 should be back online.

-
-

[Fixed] Webmail problems

Posted in Problems by

There is currently an issue with the Webmail interface at https://webmail.webfaction.com which is resulting in sporadic 500 Internal Server Errors for some email users. We are looking into the problem and hope to have normal service restored soon. We will update this entry as soon as we have more information.

2018-03-02 14:50 UTC: The root cause of the errors has been fixed. Thank you for your patience, and if there are any issues please feel free to contact support by opening a ticket.

-
-

[Done] Emergency maintenance on Web572 on Sunday, March 4, 2018

Posted in Uncategorized by

Web572 will be taken down to replace a failing memory module Sunday, March 4, 2018 between 00:00 and 01:00. The expected downtime should be 15 minutes or less.

2018-03-04 00:58 UTC: The maintenance is complete and the server is back online.

-
-