Language Selection

English French German Italian Portuguese Spanish

New Content/Layout OK?

Varnish Proxy

Silly me, a poll would not work on the new server. I forgot that with the Varnish cache proxy at the front almost all visitors arrive from the same IP address (the proxy), which means that Drupal would allocate just one vote to all (except registered and presently logged in users). With Drupal upgrade we can perhaps find polling software that overcomes this.

rpaf

You must use mod_rpaf to fix this problem that Varnish introduces.
See eg https://www.varnish-cache.org/lists/pipermail/varnish-misc/2008-September/016470.html
mod_rpaf for EL6 64bit here: http://centos.alt.ru/repository/centos/6/x86_64/mod_rpaf-0.6-2.el6.x86_64.rpm

Proxy

Thank, we will look into it. Currently, a lot of stuff other than the poll (e.g. views being counted) are not compatible with Varnish and it makes it look as though not many people visit and can participate in the site.

Pageview count and polls

I'll have a look and see if configuration can solve not just the polling issue but also pageview count. The site of this module is down and it seems like it may require configuration on the cache server too.

For sheer stats you could use

For sheer stats you could use an external (i.e. not cached by varnish) service, such as Google Analytics or run your own Piwik.

Piwik

Google Analytics is spyware, but Piwik would be a possibility (Stallman recently told me that it's good). Can it be installed on a cache proxy? I'd have to gain access to it first. Either way, this would not facilitate per-post page request count. Susan had it set up with a module, but it's no longer working correctly. In turn, rating/sorting posts by popularity is no longer possible, and that's the real downside (the front page can no longer list popular items for today).

The problem is not just that IP addresses are not unique. Some requests are never seen by the CMS and Apache.

For the non-unique addresses

For the non-unique addresses look at mod_rpaf, it was made for this situations.
Is this drupal6 or 7? With 6 varnish integration sucks from what I've seen.

See also
https://drupal.org/project/varnish
https://fourkitchens.atlassian.net/wiki/display/TECH/Configure+Varnish+3+for+Drupal+7

Agreed on Google Analytics. You can just install Piwik on the same host and tell Varnish either not to cache it or you can just set its virtualhost on a port other than 80 so it bypasses Varnish completely.

Varnish

Thanks for the pointers.

Yes, it's Drupal 6 and there are other issues that I am beginning to see, such as lack of updates from the RSS feeds around the page (I am currently investigating this, maybe it's related to a cron job or module config although I very much doubt the latter as I haven't changed configs).

Non-unique addresses could be bypassed as an issue even by writing random IP addresses, but that would enable easy poll rigging. I guess it's not essential for operation of the site, but it's a nice-to-have...

From Drupal.org: "This module provides integration between your Drupal site and the Varnish HTTP Accelerator, an advanced and very fast reverse-proxy system. Basically, Varnish handles serving static files and anonymous page-views for your site much faster and at higher volumes than Apache, in the neighborhood of 3000 requests per second."

I have had such issues with Varnish on top of WordPress and MediaWiki (pages served improperly from cache) and it all makes me wonder if removing Varnish altogether is the best way to proceed.

As for Piwik, I have never tried it before, so I will look into it.

RSS feeds

The Piwik demo looks impressive, I have just given them a word of endorsement.

I am still trying to resolve some other issues we've identified.

I think I found the source of the issue above (RSS feeds). It seems like any external site access is denied by default, which helps explain why RSS feeds cannot be retrieved by the Drupal part of the site:


[root@tuxmachines ~]# wget lxer.com
--2014-02-05 04:34:37--  http://lxer.com/
Resolving lxer.com... 108.166.170.174
Connecting to lxer.com|108.166.170.174|:80... failed: Connection refused.
[root@tuxmachines ~]# wget linuxtoday.com
--2014-02-05 04:34:54--  http://linuxtoday.com/
Resolving linuxtoday.com... 70.42.23.121
Connecting to linuxtoday.com|70.42.23.121|:80... failed: Connection refused.

I would keep Varnish on for

I would keep Varnish on for static files (css, js, jpeg etc) and to clean up HTTP traffic (Varnish will not forward incomplete or malformed HTTP requests to the backend, it should also be the front line against synfloods etc).

Here's a sample of what I use (test it first, I'm just beginning with Varnish myself)

director default dns {
.list = {
.port = "8080";
.connect_timeout = 5s;
.first_byte_timeout = 600s;
.between_bytes_timeout = 600s;
.max_connections = 10000;
"172.16.1.53"/32;
}
}
sub vcl_recv {
if (req.url ~ "\.(png|gif|jpg|swf|css|js)$") {
return(lookup);
}
}
sub vcl_fetch {
if (req.url ~ "\.(png|gif|jpg|swf|css|js)$") {
unset beresp.http.set-cookie;
}
if (req.restarts == 0) {
if (req.http.x-forwarded-for) {
set req.http.X-Forwarded-For =
req.http.X-Forwarded-For + ", " + client.ip;
} else {
set req.http.X-Forwarded-For = client.ip;
}
}
}

Then install mod_rpaf and make sure your Apache is listening on port 8080 and add this to /etc/httpd/conf.d/rpaf.conf:
LoadModule rpaf_module modules/mod_rpaf-2.0.so

RPAFenable On
RPAFproxy_ips 127.0.0.1 IPs_OF_THE_SERVER
RPAFsethostname On
RPAFheader X-Forwarded-For

PS: looks like drupal is messing with my comments, here's a text version http://fpaste.org/74672/raw/

Looks like a firewall issue

Looks like a firewall issue at the first glance.

Firewall

Nux wrote:

Looks like a firewall issue at the first glance.

Yes, it was a simply issue to tackle. It works now.

Thanks

Thanks, I will look at it and into it in the weekend.

More in Tux Machines

Android Leftovers

AMD Ryzen 9 3900XT vs. Intel Core i9 10900K Linux Gaming Performance

Following the 130+ benchmarks of the AMD Ryzen 3000XT series earlier in the week looking at the CPU/system performance on Ubuntu Linux, here is our first look at the Linux gaming performance with putting the Ryzen 9 3900XT up head-to-head against the Intel Core i9 10900K. This Linux gaming bout is looking at the Core i9 10900K vs. Ryzen 9 3900XT for Linux gaming while also looking at the CPU power consumption and performance-per-Watt. Read more

Programming Leftovers

Red Hat/Fedora Leftovers

  • IT careers: How to get a job as a DevOps professional

    Editor’s note: In this ongoing series for IT job hunters, we'll explore in-demand roles, necessary skills, and how to stand out in an interview. Here, Pete Sosnowski, co-founder and VP people at Zety, shares insights on getting a DevOps role.

  • Nest With Fedora CfP open

    In a normal year, we’d be getting ready for my favorite event: Flock to Fedora. But as we’re all aware, this is anything but a normal year. Despite this—or perhaps because of this—we still want to bring the community together to share ideas, make plans, and form the bonds that put the Friends in Fedora. Instead of Flocking to Fedora, we’re going to Nest With Fedora. I’m happy to announce that the Call for Participation is now open. Nest With Fedora features five tracks. I included a few examples for each one, but don’t limit yourself. What do you want to share with the Fedora community?

  • Performance and usability enhancements in Red Hat CodeReady Workspaces 2.2

    Red Hat CodeReady Workspaces 2.2 is now available. For the improvements in this release, we focused on performance and configuration, plus updating CodeReady Workspaces 2.2 to use newer versions of the most popular runtimes and stacks. We also added the ability to allocate only the CPU that you need for IDE plugins, and we introduced a new diagnostic feature that lets you start up a workspace in debug mode. CodeReady Workspaces 2.2 is available on OpenShift 3.11 and OpenShift 4.3 and higher, including tech-preview support for OpenShift 4.5.

  • What does the future hold for edge computing?

    That being said, edge computing is still in its infancy and not quite ready for primetime yet. Gartner’s report admitted as much, noting that just 10 percent of enterprise data was generated and processed at the edge in 2018. For “the edge” to become as ubiquitous as “the cloud” in the tech industry, a myriad of technical challenges will need to be tackled. These include the development of compact devices with outsized processing power, the creation of software that enables companies to remotely monitor and update a limitless number of edge devices from across the world and new security technology and protocols to keep everything safe. Many companies are actively working to solve these problems, including Red Hat, Nutanix and Cloudera, all of which have developed their own edge technology. We recently spoke with senior leaders at each to learn what the future holds for edge computing — and what it will take to realize it.

  • Red Hat: Migrating To The Cloud And The Risk Of Sticking With The Status Quo

    The ability for companies to immediately respond to the need to support a work-from-home environment depended, in large part, upon where those firms were already in terms of their digitization journeys. For some, the shift was relatively easy, thanks to an existing embrace of cloud-based platforms and systems. For others, not so much: Continued reliance on legacy infrastructure, which itself often depends on manual intervention to function properly, created a panic for some companies unable to make the move to remote working without major roadblocks. Speaking with PYMNTS, Tim Hooley, chief technologist, EMEA, FSI at Red Hat, explained why organizations continue to delay their cloud migrations, and offered a guide to overcoming the sense of being overwhelmed and making progress in the journey toward fully automated back offices.