VPS.NET Cloud Community: SteveSRS - Viewing Profile - VPS.NET Cloud Community

Jump to content

SteveSRS's Profile User Rating: -----

SteveSRS's Photo
Reputation: 10 Good
Group:
Customers
Active Posts:
35 (0.04 per day)
Most Active In:
Customer Lounge (13 posts)
Joined:
15-September 09
Profile Views:
1,441
Last Active:
User is offline Dec 22 2011 03:07 AM
Currently:
Offline

My Information

Member Title:
I Got Nodes
Age:
Age Unknown
Birthday:
Birthday Unknown
Gender:
Not Telling Not Telling

Contact Information

E-mail:
Click here to e-mail me
  1. Recent Status Updates
  2. About Me
  3. Topics
  4. Posts

Posts I've Made

  1. In Topic: Apache Killer fixing

    02 December 2011 - 12:31 AM

    View PostSteveSRS, on 01 December 2011 - 11:53 PM, said:

    Hi,

    Recently found out my server was vurnable:
    http://httpd.apache....E-2011-3192.txt

    I now fixed it with some extra rules in my htaccess file;
    RequestHeader unset Range
    RequestHeader unset Request-Range

    And it works however I don't feel this is best solution and its not server wide, I'm actually not sure if adding these lines to apache2.conf would help.
    An other fixed I tried (using mod_rewrite) didn't work when I put them in apache2.conf.

    I run debian squeeze, and it says patch was already available but I ran:
    apt-get update + upgrade but that did not solve any problems for me

    Debian version 6.03
    apache version: Apache/2.2.16 (Debian)

    Anybody knows steps for a better solution?

    Thanks

    P.s. if you haven't checked your server I would advise you to do so.. tool is here:
    http://seclists.org/...re/2011/Aug/175


    Edit:
    I noticed just after changing to solution mentioned above I got 500 error on my site due those lines, didn't matter if they were in htaccess or apache2.conf
    So for me only this one works:
    RewriteCond %{HTTP:Range} bytes=0-.* [NC]
    RewriteRule .? http://%{SERVER_NAME}/ [R=302,L]

    in htaccess

  2. In Topic: 2 server Mysql replication + failover

    13 October 2011 - 12:55 AM

    just for others

    In end end We setup the following
    master - master with auto-increment-offset option
    installed maatkit which checks critical tables (by checksum) every 12 hours (3 times with intervals of couple minutes) if they are in-sync on the both servers. If not it syncs the 2 servers and it sends me a notification (you could also just choose a notification).

    The new system isn't yet completely in production but seems to be working smooth so far. Soon we will put new website plus new system completely in production (at the moment mysql writing is still only done on UK not at both yet).

    Best regards,

  3. In Topic: Checking after a freelancer worked on your servers

    10 October 2011 - 11:34 PM

    thanks for the answers. I don't have any control panels installed so no troubles there.. I just want to be secure that a freelancer doesn't leave a backdoor open as you can never be too careful in this world! One of the ssh keys I deleted was from the file authorized_keys for example and I'm pretty sure that line was from an earlier freelancer and there was a line from the current freelancer also.

    I have chrootkit installed already will have a look at the other one and check open ports also. Thanks

  4. In Topic: Tungsten Replicator

    07 October 2011 - 04:26 AM

    Thungsten seems pretty complicated, I was looking at the same thing.

    Thungsten
    MMM
    MTA

    All more or less the same.
    However for me in the end I went with master - master setup just plain with auto-increment-offset config and MaatKit installed to checksum check critical tables and on 3 failed checks (about 5 minutes in total time apart) it will sync all.

    Good luck

  5. In Topic: Lon-B

    30 September 2011 - 06:57 AM

    and again.. down due SAN problems.. time to throw those SANs in the garbage..

Friends

SteveSRS hasn't added any friends yet.

Comments

SteveSRS has no profile comments yet. Why not say hello?