Results 1 to 9 of 9
  1. #1
    Join Date
    Feb 2005
    Posts
    60

    Help! My server has been down since last Thursday!

    Last Thursday I got up and discovered my server went down around 4am. I submitted a ticket to Resellerworkz and they had to hand it over to NOC. I'm still waiting but in the meantime I thought I'd ask for advice on here.

    I can still SSH in but I can't start up Apache because the filesystem became read only so it fails when trying to open the log file for writing.

    When I ssh in I get this message:

    /tmp/RsJGCrJu: Read-only file system
    [email protected] [~]#


    When I try to start apache I get:

    [email protected] [/usr/local/apache/bin]# httpd start
    fopen: Read-only file system
    httpd: could not open error log file /usr/local/apache/logs/error_log.
    /usr/sbin/httpd start: httpd could not be started
    [email protected] [/usr/local/apache/bin]#


    The last response I got from resellerworkz was:

    Hello

    "The NOC updated us saying that your server got stuck while doing a file system check. We are tryiing our level best with the NOC engineers to make the server online ASAP, we appreciate your patience and cooperation at this time

    We will keep you posted, please hold on"

    I'm the only one who uses this server and the only things I installed myself were iftop, vnstat, ipf, and bfd. Everything was running really great then all of a sudden I can't do anything.


    Should I ask for a credit for the downtime?

    I'm a newb so any help would be much appreciated, thanks!

  2. #2
    Join Date
    May 2004
    Location
    Blue Springs, Missouri
    Posts
    366
    nope.


    kind of sounds to me like you got owned ...

  3. #3
    Join Date
    Feb 2005
    Posts
    60
    Originally posted by omaha.stylee
    nope.


    kind of sounds to me like you got owned ...
    yep.

    I'm moving files to friends' servers now. They need to format and reinstall the OS

  4. #4
    All the best in recovering from this. Make sure that you secure the server down prior to putting back on live or else this issue might come to haunt you again.

  5. #5
    Join Date
    Feb 2005
    Posts
    60
    Originally posted by eddy2099
    All the best in recovering from this. Make sure that you secure the server down prior to putting back on live or else this issue might come to haunt you again.
    thanks.

    you think it was hacked?

  6. #6
    There can only be two possible explanation for this, one is that the server is hacked and the other is that there is some hardware or OS fault.

    In any case, even if it is not hacked, it is still important to secure the server down.

    My personal worst was a server which went online for 2 hours and get hacked.

  7. #7
    Join Date
    Feb 2005
    Posts
    60
    Originally posted by eddy2099
    There can only be two possible explanation for this, one is that the server is hacked and the other is that there is some hardware or OS fault.

    In any case, even if it is not hacked, it is still important to secure the server down.

    My personal worst was a server which went online for 2 hours and get hacked.
    2 hours, ouch. I was lucky to make it almost 3 months. I'll have to pay to get it locked down better this time.

  8. #8
    Join Date
    May 2004
    Location
    Blue Springs, Missouri
    Posts
    366
    or just read?


  9. #9
    Join Date
    Feb 2005
    Posts
    60
    Originally posted by omaha.stylee
    or just read?

    Yeah reading a lot on here is how I was able to install IPF, BFD, remap the SSH port and IP, and vnstat and iftop to monitor bandwidth.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •