Sponsored Content
The Lounge What is on Your Mind? OUTAGE: Data Center Problem Resolved. Post 303040470 by RavinderSingh13 on Wednesday 30th of October 2019 02:47:17 AM
Old 10-30-2019
Quote:
Originally Posted by Neo
There was a problem with our data center today, creating a site outage (server unreachable).
That problem has been resolved.
Basically, it seems to have been a socially engineered denial-of-service attack against UNIX.com; which I stopped as soon as I found out what the problem was.
Total down time was 30 minutes.
Thank you for your patience.
Thanks a TON Neo for informing us on same. I am able to access site without any issues and hope all others would also be. Cheers for UNIX.com Smilie

Thanks,
R. Singh
 

6 More Discussions You Might Find Interesting

1. Solaris

Booting up problem after power outage

hi guys, i'm new so don't bite too hard. having a problem booting up a V210 running sol9 on after a power outage... an init5 was done but not a init0 before the power cut... so now when booting up it gives the ff: SC Alert: Host System has Reset Probing system devices Probing memory... (2 Replies)
Discussion started by: lungsta
2 Replies

2. HP-UX

Need to set up a HP cluster system in a data center

What are the server requirements, Software requirements, Network requirements etc, Please help me.. as 'm new 'm unable to get things done @ my end alone. Please refrain from typing subjects completely in upper case letters to get more attention, ty. (5 Replies)
Discussion started by: Sounddappan
5 Replies

3. AIX

Role of sys admin during power outage in Data center

i am new to aix environment and all my servers are @ remote location just curious to know , what issues/tasks we will be facing when there is a power outage in a data centre, i heard outage's will be a challenging task for administrators.. any example of that sort will be a great help (2 Replies)
Discussion started by: rigin
2 Replies

4. Shell Programming and Scripting

Failure rate of a node / Data center

Hi, Please, i have a history of the state of each node in my data center. an history about the failure of my cluster (UN: node up, DN: node down). Here is some lines of the history: 08:51:36 UN 127.0.0.1 08:51:36 UN 127.0.0.2 08:51:36 UN 127.0.0.3 08:53:50 DN 127.0.0.1 ... (6 Replies)
Discussion started by: chercheur111
6 Replies

5. What is on Your Mind?

Cut Over to New Data Center and Upgraded OS Done. :)

Three days ago we received an expected notice from our long time data center that they were going dark on Sept 12th. About one and a half hours ago, after three days of marathon work, I just cut over the unix.com to a new data center with a completely new OS and Ubuntu distribution. (22 Replies)
Discussion started by: Neo
22 Replies

6. What is on Your Mind?

Resolved: Issue in Server Data Center

Dear All, There was a problem in the data center data, which caused the server to be unreachable for about an hour. Server logs show the server did not crash or go down. Hence, I assume there was a networking issue at the data center. Still waiting for final word on what happened. ... (4 Replies)
Discussion started by: Neo
4 Replies
LURKER-PRUNE(1) 					      General Commands Manual						   LURKER-PRUNE(1)

NAME
lurker-prune -- prunes the web-server cache SYNOPSIS
lurker-prune [-c <config-file>] [-f <frontend>] [-m <days>] [-a <days>] [-p -v] DESCRIPTION
lurker-prune prunes obsolete or stale files from the web-server accessible cache. This command must be run at regular intervals from eg. a cronjob. If it is not run, then the lurker web interface will appear to not be receiving new mail or have contradictory links between pages. A good interval is every 15 minutes and should not exceed one hour. Be aware that it is possible for an attacker to use up a large amount of disk space through lurker. An attacker could request many distinct lurker web pages each of which is cached, thus using disk space. Please setup a quota for the lurker user, read your logs, and follow what- ever site-specific policies you have for denial of service. A good script to run in parallel with normal lurker-prune use is one similar to: if test `du -s /var/www/lurker | cut -f1` -gt 32768; then lurker-prune -p; fi This might help guard against a potential denial-of-service attack. OPTIONS
-c config-file Use this config file for lurker settings. -f frontend The directory of the lurker frontend cache to clean. You can selectively purge cache with this option. By default, lurker-prune will clean all frontends specified in the config file. -m days Keep cached files for at most this many days. Any cached file regardless of last access will be deleted after the specified num- ber of days (defaults to 7). Files which are obsolete due to new mail, config changes, or no accesses will be deleted earlier. Deleted files will be automagically regenerated if needed. -a days Kill cache files not accessed for this many days. Any cached file which has not been read from for the specified number of days (defaults to 1) will be deleted. Files which are obsolete due to new mail or config changes will be deleted earlier. Deleted files will be automagically regenerated if needed. -p Purge mode. Delete all cache files even if they do not appear to be expired. This will only deletes files that are generated by lurker, and is thus preferable to rm */*. -v Verbose operation. Indicate which files are being deleted and the reasoning behind lurker's decisions. This can help in tracking down why some files are deleted and not others. SEE ALSO
lurker-index(1), lurker-params(1), lurker-list(1) lurker documentation on http://lurker.sourceforge.net/ COPYRIGHT
Copyright (C) 2002: Wesley W. Terpstra <terpstra@users.sourceforge.net> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. BUGS
Before reporting a bug, please confirm that the bug you found is still present in the latest official release. If the problem persists, then send mail with instructions describing how to reproduce the bug to <lurker-users@lists.sourceforge.net>. LURKER-PRUNE(1)
All times are GMT -4. The time now is 03:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy