Sponsored Content
Operating Systems Linux Debian How to update Nginx in Debian to current ver? Post 302547096 by bugeye on Saturday 13th of August 2011 10:50:03 PM
Old 08-13-2011
How to update Nginx in Debian to current ver?

I did a fresh install of nginx on a debian server.

When I check the version of nginx, it reports 0.7.67

However, the current stable version of Nginx is 1.0.5 from what I have read.

How can I update my Nginx whilst leaving my server operational?

I am a relative newb, so please do not make answers too complex.

---------- Post updated at 12:50 PM ---------- Previous update was at 12:01 PM ----------

Never mind. I think I have managed to do it. I used the dotdeb.org repository and simply installed nginx again over the top of the old one. It seemed to manage ok.
 

9 More Discussions You Might Find Interesting

1. Debian

Debian Lenny update problems

Hi everybody! I have a very big problem, I can not make any updates on my debian lenny. I get everytime this errors with apt-get update: Err http://security.debian.org lenny/updates Release.gpg Connection failed Err http://www.backports.org lenny-backports Release.gpg Connection... (2 Replies)
Discussion started by: magge
2 Replies

2. Web Development

activecampaign rewrite rules for nginx webserver

Could you help me to write nginx rewite rules for activecampaign at present they only have a apache rewrite rules which to be put in .htaccess cat .htaccess <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / # KB RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME}... (0 Replies)
Discussion started by: unimaxlin
0 Replies

3. Debian

VPN service fails after update applied in Debian Squeeze

Hello everybody, I used to log in to my office via PPTP VPN, but on last October 5th I updated my installed Debian Squeeze and it caused my VPN service (client-side) to fail. After this upgrade I'm unable to log in to the VPN server. Here follows the log: #tail -f /var/log/messages Plugin... (0 Replies)
Discussion started by: r4ym4r
0 Replies

4. Infrastructure Monitoring

How to install Cacti (a system monitoring and graphing solution) with Nginx?

Here's a short tutorial on installing Cacti with Nginx on Linux. (0 Replies)
Discussion started by: notblog
0 Replies

5. UNIX for Dummies Questions & Answers

How to configure NGINX?

Hi , I installed NGINX and when i i go see the browser it says welcome If you see this page, the nginx web server is successfully installed and working. Further configuration is required. is there any kind of document to configure that(i am completly new for this) (1 Reply)
Discussion started by: vikatakavi
1 Replies

6. UNIX for Dummies Questions & Answers

NGINX Setup

Here is my issue: I have two web servers hosting web services (Server A and Server B) I'd like to configure NGINX to achieve load balancing. Do I install NGINX on a third new server, or is it something that gets installed on Server A and Server B? Please share some information. ... (0 Replies)
Discussion started by: ramky79
0 Replies

7. Shell Programming and Scripting

Script to check response time from nginx logs

Hi, My goal is to monitor the response time from the access logs of nginx server. I am using gawk to print the needed fields - 'response time' and 'name of the service' from nginx logs. Command: gawk '($6 ~ /cloudservice/) {print $10, $6}' access.log Output: 0.645 /nc/cloudservice... (6 Replies)
Discussion started by: nshah11
6 Replies

8. Red Hat

Security module in nginx

hi By the command yum install nginx Want a security modules Security modules such as virtual hosts I apply Do you know a quick solution? thanks (0 Replies)
Discussion started by: mnnn
0 Replies

9. Fedora

How to wrap nginx/uwsgi around Flask?

I've SSH installed a Python 3.5 application on CentOS along with uwsgi and nginx, but after doing a sudo vi /etc/nginx/nginx.conf to edit the nginx config file as per usual, the response is currently: nginx: bind() to 0.0.0.0:80 failed (98: Address already in use) these are the contents of... (0 Replies)
Discussion started by: dev5180
0 Replies
OCF_HEARTBEAT_NGINX(7)						OCF resource agents					    OCF_HEARTBEAT_NGINX(7)

NAME
ocf_heartbeat_nginx - Manages an Nginx web/proxy server instance SYNOPSIS
nginx [start | stop | status | monitor | meta-data | validate-all] DESCRIPTION
This is the resource agent for the Nginx web/proxy server. This resource agent does not monitor POP or IMAP servers, as we don't know how to determine meaningful status for them. The start operation ends with a loop in which monitor is repeatedly called to make sure that the server started and that it is operational. Hence, if the monitor operation does not succeed within the start operation timeout, the nginx resource will end with an error status. The default monitor operation will verify that nginx is running. The level 10 monitor operation by default will try and fetch the /nginx_status page - which is commented out in sample nginx configurations. Make sure that the /nginx_status page works and that the access is restricted to localhost (address 127.0.0.1) plus whatever places _outside the cluster_ you want to monitor the server from. See the status10url and status10regex attributes for more details. The level 20 monitor operation will perform a more complex set of tests from a configuration file. The level 30 monitor operation will run an external command to perform an arbitrary monitoring operation. SUPPORTED PARAMETERS
configfile The full pathname of the Nginx configuration file. This file is parsed to provide defaults for various other resource agent parameters. (unique, optional, string, no default) httpd The full pathname of the httpd binary (optional). (optional, string, default /usr/sbin/httpd) port A port number that we can probe for status information using the statusurl. This will default to the port number found in the configuration file, or 80, if none can be found in the configuration file. .sp (optional, integer, no default) status10url The URL to monitor (the nginx server status page by default) when given a level 10 monitor operation. If left unspecified, it will be inferred from the nginx configuration file, or defaulted to /nginx_status. .sp If you set this, make sure that it succeeds *only* from the localhost (127.0.0.1) and no other cluster nodes. Otherwise, the cluster software may complain about it being active on multiple nodes. (optional, string, no default) status10regex Regular expression to match in the output of status10url. Case insensitive. (optional, string, default Reading: [0-9]+ Writing: [0-9]+ Waiting: [0-9]+) testclient Client to use to query to Nginx for level 10 and level 20 tests. If not specified, the RA will try to find one on the system. Currently, wget and curl are supported, with curl being preferred. For example, you can set this parameter to "wget" if you prefer that to curl. (optional, string, no default) testurl URL to test. If it does not start with "http", then it's considered to be relative to the document root address. (optional, string, no default) test20regex Regular expression to match in the output of testurl. Case insensitive. (optional, string, no default) testconffile A file which contains a more complex test configuration. Could be useful if you have to check more than one web application or in case sensitive info should be passed as arguments (passwords). Furthermore, using a config file is the only way to specify certain parameters. .sp Please see README.webapps for examples and file description. (optional, string, no default) test20name Name of the test within the test configuration file. (optional, string, no default) external_monitor30_cmd Command string to run which implements level 30 monitoring. (optional, string, no default) options Extra options to apply when starting nginx. (optional, string, no default) SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 40s. stop Stops the resource. Suggested minimum timeout: 60s. reload Suggested minimum timeout: 40s. status Performs a status check. Suggested minimum timeout: 30s. monitor Performs a detailed status check. Suggested minimum timeout: 30s. Suggested interval: 10s. monitor Performs a detailed status check. Suggested minimum timeout: 30s. Suggested interval: 30s. monitor Performs a detailed status check. Suggested minimum timeout: 45s. monitor Performs a detailed status check. Suggested minimum timeout: 60s. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5. validate-all Performs a validation of the resource configuration. Suggested minimum timeout: 5. EXAMPLE
The following is an example configuration for a nginx resource using the crm(8) shell: primitive p_nginx ocf:heartbeat:nginx op monitor timeout="30s" depth="0" interval="10s" op monitor timeout="30s" depth="10" interval="30s" op monitor timeout="45s" depth="20" op monitor timeout="60s" depth="30" SEE ALSO
http://www.linux-ha.org/wiki/nginx_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 03/09/2014 OCF_HEARTBEAT_NGINX(7)
All times are GMT -4. The time now is 10:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy