Results 1 to 10 of 10
  1. #1

    VPS stopps running randomly

    Hi,

    I am new to all of this. I have a ordered a vps and it is up and running ... for most times anyway.

    The problem is that it switches from running to mounted without me having anything to do with it. It seems to be quite randomly, for example this morning at 1.42 am. This happens once a day and stops my vps and therefore my website - which is quite annoying.
    I checked for log files or anything, but there was nothing mentioning resources or anything.

    Does anyone have a clue what this might be? If I cannot fix the problem there is still the opportunity to just start the vps once it goes to status mounted. How would I automate this?

    Oh, I am using Virtuozzo and Plesk.
    Would be great if someone could help.

    Br.

  2. #2
    I don't know why it would be doing this, but do you get any extra information in the logs? Do you have any cron jobs running that could be causing this?

  3. #3
    I do not have any cronjobs and since the behavior is somewhat random I do not think it has anything to do with that.

    I have surfed some more for the reason and I think it could have something to do with the size of my mysql database and the low ressources I have on my vps. I have changed some settings. Now, my.cnf looks like this:

    key_buffer = 64M
    max_allowed_packet = 16M
    thread_stack = 192K
    thread_cache_size = 8
    max_connections = 40
    table_cache = 256

    Before it was:

    key_buffer = 16M
    max_allowed_packet = 16M
    thread_stack = 128K
    thread_cache_size = 8
    max_connections = 40

    Are these settings okay? Is there anything else I could change?


    I do not know if that is the reason. I have to see. I see that there are mysql logs for every time it stopped my vps. What would I look for to find an error there? It is not an error log.

  4. #4
    Is there anything relevant in the /var/log/messages file? Does it show anything happening at 1:42 this morning?

  5. #5
    Nope, it just says --Mark-- in the messages log.

  6. #6
    Holy ****, I found something in the syslog.

    /USR/SBIN/CRON[30585]: (root) CMD (/opt/psa/admin/sbin/backupmng >/dev/null 2>&1)

    Seems as if you are right with the cronjob. But what the hell is that? I have to check the backupmanager.

  7. #7
    Join Date
    Apr 2008
    Location
    USA & Germany
    Posts
    193
    Depending on distribution, it might be some error-notification in /var/log/syslog .

  8. #8
    Seems as we wrote it at the message at the same time. So, it looks like this:

    May 29 01:40:01 makiola-nahrung /USR/SBIN/CRON[30068]: (www-data) CMD ([ -x /usr/lib/cgi-bin/awstats.pl -a -f /etc/awstats/awstats.conf -a -r /var/log/apache/access.log ] && /usr/lib/cgi-bin/awstats.pl -config=awstats -update >/dev/null)
    May 29 01:42:01 makiola-nahrung /USR/SBIN/CRON[30585]: (root) CMD (/opt/psa/admin/sbin/backupmng >/dev/null 2>&1)

    After that, the vps stops. It does not say that in the syslog, but according to the time of stop those are the last messages in syslog.

    It might be that for some reason I am running out of memory in the backup process or I have too many connections to mysql. Could that be?

  9. #9
    And here is what it shows after I restart manually:

    May 29 07:57:43 makiola-nahrung mysqld[7494]: 080529 7:57:43 InnoDB: Database was not shut down normally!
    May 29 07:57:43 makiola-nahrung mysqld[7494]: InnoDB: Starting crash recovery.
    May 29 07:57:43 makiola-nahrung mysqld[7494]: InnoDB: Reading tablespace information from the .ibd files...
    May 29 07:57:43 makiola-nahrung mysqld[7494]: InnoDB: Restoring possible half-written data pages from the doublewrite
    May 29 07:57:43 makiola-nahrung mysqld[7494]: InnoDB: buffer...
    May 29 07:57:43 makiola-nahrung mysqld[7494]: 080529 7:57:43 InnoDB: Starting log scan based on checkpoint at
    May 29 07:57:43 makiola-nahrung mysqld[7494]: InnoDB: log sequence number 0 1543826.
    May 29 07:57:43 makiola-nahrung mysqld[7494]: InnoDB: Doing recovery: scanned up to log sequence number 0 1543826
    May 29 07:57:43 makiola-nahrung mysqld[7494]: InnoDB: Last MySQL binlog file position 0 1659366, file name /var/log/mysql/mysql-bin.000013
    May 29 07:57:43 makiola-nahrung mysqld[7494]: 080529 7:57:43 InnoDB: Started; log sequence number 0 1543826
    May 29 07:57:43 makiola-nahrung mysqld[7494]: 080529 7:57:43 [Note] Recovering after a crash using /var/log/mysql/mysql-bin
    May 29 07:57:44 makiola-nahrung mysqld[7494]: 080529 7:57:44 [Note] Starting crash recovery...
    May 29 07:57:44 makiola-nahrung mysqld[7494]: 080529 7:57:44 [Note] Crash recovery finished.
    May 29 07:57:44 makiola-nahrung mysqld[7494]: 080529 7:57:44 [Note] /usr/sbin/mysqld: ready for connections.
    May 29 07:57:44 makiola-nahrung mysqld[7494]: Version: '5.0.32-Debian_7etch5-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian etch distribution

  10. #10
    Join Date
    Oct 2007
    Posts
    1,902
    Oeli,

    Normally vps goes into mounted state when it tries to change the state of a vps. For example, If you try to restart the server when the vps is backing up(not plesk backup), then there is a chance of getting the vps in mounted state. Please contact your vps provider and tell them to have a check.
    ServerPoint.com - a true hosting company offering online presence solutions since 1998.
    >>Web Hosting, colocation, dedicated servers and virtual private dedicated servers.
    >>>>Wholly owned multi homed network, servers and facilities.

Posting Permissions

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