We are using two Varnish cache behind aws elb. And traffic coming through aws cloudfront. All of a sudden both varnish service crashed, It happens only once. Anybody has any similar experience or any advise on this? There is no hints in server log or elb log!
OS: Debian GNU/Linux 7
Varnish: varnish-3.0.2 revision 55e70a4
Thanks in advance
The last released version of Varnish 3.0 (before it was defined as end of life) was 3.0.7. There are significant bugfixes between 3.0.2 and 3.0.7.
You can try to ask the Debian maintenance team for help, but I wouldn't hold my breath.
Related
Rookie getting my feet wet. Reasonably new to Linux, Apache, Elasticsearch and Kibana.
Running SUSE Linux Enterprise Server (SLES) 11, and Elasticsearch 1.5.2, Apache (apache2).
Tried working with Kibana 4.0.2, found some bugs and weird issues, want to use Kibana 3.1.2 instead. I'm on a deadline.
What do I need to configure so that I can browse to the Kibana 3 instance? I have configured my kibana-3.1.2/config.js to point to my ES server, but am unsure of other changes, especially within Apache.
Any help would be great and I can offer any more details needed.
Thanks!
I run logstash, es and kibana4 and love it on debian 8. Im not sure of what you got feedimg to what but digital ocean is a great resource. Here is a nice walkthrough to help you figure out ejar you should do next depending on where you stand in your setup.https://www.digitalocean.com/community/tutorials/how-to-use-logstash-and-kibana-to-centralize-and-visualize-logs-on-ubuntu-14-04
It also explains the ins and outs a littlite bit so you wont feel so new. Enjoy.
I'm managing a PLESK server and got this error from a client after they did a PCI scan on their site. What is ProFTP and is this really an issue? How would I go about fixing this issue?
Proftpd version 1.3.5 is used in latest version of Plesk. Please, consider upgrade possibility.
I don't mean to sound harsh but you are managing a Plesk server and you don't know what ProFTPd is? Its an FTP server. FTP is File Transfer Protocol and is the protocol used to upload web pages to websites. The version you are using is out of date and has more than one known vulnerability which could mean your server gets compromised. I'd recommend you upgrade.
Image:
Debian GNU/Linux 7.6 (wheezy) amd64 with backports kernel and SSH packages built on 2014-10-17
Machine type:
n1-highcpu-2 (2 vCPU, 1.8 GB memory)
Zone:
urope-west1-b
I have 10-20 ruby workers which listen for external RabbitMQ server. Nothing special minimizing css/js/html code, upload pictures via http, transfer data from MongoDB to Mysql.
Everything works fine, but after some time (several hours ~5-6) instance hangs. I can't ssh to it from external client or browser console. Only instance reboot helps.
What should I check? or change? or whatever to fix this behavior?
One of the reasons of "hanging" might be IO throttling. You'd need to understand disk access patterns and see if your disk type/size is a good match.
Please refer to this section of documentation that explains Compute Engine disk performance:
https://cloud.google.com/compute/docs/disks#pdperformance
I have pretty strange problem with Collectd. I'm not new to Collectd, was using it for a long time on CentOS based boxes, but now we have Ubuntu TLS 12.04 boxes, and I have really strange issue.
So, using version 5.2 on Ubuntu 12.04 TLS. Two boxes residing on Rackspace (maybe important, but I'm not sure). Network plugin configured using two local IPs, without any firewall in between and without any security (just to try to set simple client server scenario).
On both servers collectd writes in configured folders as it should write, but on server machine it doesn't write data received from client.
Troubleshooted with tcpdump, and I can clearly see UDP traffic and collectd data, including hostname and plugin names from my client machine, received on server, but they are not flushed to appropriate folder (configured by collectd) ever. Also running everything as root user, to avoid troubleshooting permissions.
Anyone has any idea or similar experience with this? Or maybe some idea what could I do for troubleshooting this beside trying to crawl internet (I think I clicked on every sensible link Google gave me in last two days) and checking network layer (which looks fine)?
And just small note: exactly the same happened with official 4.10.2 version from Ubuntu's repo. After trying to troubleshoot it for hours moved to upgrade to version five.
I'd suggest trying out the quite generic troubleshooting procedure based on the csv and logfile plugins, as described in this answer. As everything seems to be fine locally, follow this procedure on the server, activating only the network plugin (in addition to logfile, csv and possibly rrdtool).
So after no way of fixing this, I upgraded my Ubuntu to 12.04.2 LTS (3.2.0-24-virtual) and this just started working fine, without any intervention.
I have a fresh install of Moodle 2.1, PHP v5.3, Windows Server 2008 R2, IIS, MySQL, 3GB Ram, 4 CPUs.
I use Moodle as a VLE for a School, but have recently been having problems with it not responding (the browser just sits & loads, until eventually it receives a network connection error to the site).
Now, if I restart "Manage Server" in IIS - the problem is rectified, but occurs again a few days later. Some people suggested increasing the "recycling" time of the pools which kind of seemed to delay this problem, but it is starting to happen frequently again.
I have tried the Moodle forums but hit a dead end, please can anyone help? Thank You
I had a lot of problems trying to get Moodle going on IIS and eventually abandoned it. It sounds a lot like you have a memory leak (in IIS, not Moodle). A temporary solution would be a scheduled task that restarts IIS before and after the school day to reset it, but this is not ideal.
The pro advice is not to use IIS at all. Apache is the industry standard, it's available as an install package for Windows and it's not enormously hard to install and configure (see moodle.org's instructions). If you have come up blank on the forums and are still having trouble, then I would suggest that the small learning curve to get Apache going is probably the least work in the long run. Have a go on a test machine (could be an old desktop) and see how you get along. There are far, far more people who can help you configure Moodle on Apache than can help on IIS, which is enough reason in itself to have a go.
Sorry I can't be more helpful!