• 19-03-2016, 23:43:26
    #1
    Üyeliği durduruldu
    Merhabalar, bugün kullandığım vpsde sorun oluştu veritabanına ulaşamıyorum.

     service httpd restart
     service mysqld restart
    daha öncede benzer sorunla karşılaştığım zaman ssh bu işlemleri yaptığımda sorun ortadan kalkıyordu.

    şimdi bu hatayı veriyor.
    Stopping mysqld:                                           [  OK  ]
    MySQL Daemon failed to start.
    Starting mysqld:                                           [FAILED]
    mysqld.log
    150907 14:38:43 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    150907 14:38:43 [Note] /usr/libexec/mysqld (mysqld 5.5.45) starting as process 12235 ...
    150907 14:38:43 [Note] Plugin 'FEDERATED' is disabled.
    150907 14:38:43 InnoDB: The InnoDB memory heap is disabled
    150907 14:38:43 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    150907 14:38:43 InnoDB: Compressed tables use zlib 1.2.3
    150907 14:38:43 InnoDB: Using Linux native AIO
    150907 14:38:43 InnoDB: Initializing buffer pool, size = 128.0M
    150907 14:38:43 InnoDB: Completed initialization of buffer pool
    InnoDB: The first specified data file ./ibdata1 did not exist:
    InnoDB: a new database to be created!
    150907 14:38:43  InnoDB: Setting file ./ibdata1 size to 10 MB
    InnoDB: Database physically writes the file full: wait...
    150907 14:38:43  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
    InnoDB: Setting log file ./ib_logfile0 size to 5 MB
    InnoDB: Database physically writes the file full: wait...
    150907 14:38:43  InnoDB: Log file ./ib_logfile1 did not exist: new to be created
    InnoDB: Setting log file ./ib_logfile1 size to 5 MB
    InnoDB: Database physically writes the file full: wait...
    InnoDB: Doublewrite buffer not found: creating new
    InnoDB: Doublewrite buffer created
    InnoDB: 127 rollback segment(s) active.
    InnoDB: Creating foreign key constraint system tables
    InnoDB: Foreign key constraint system tables created
    150907 14:38:43  InnoDB: Waiting for the background threads to start
    150907 14:38:44 InnoDB: 5.5.45 started; log sequence number 0
    150907 14:38:44 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
    150907 14:38:44 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
    150907 14:38:44 [Note] Server socket created on IP: '0.0.0.0'.
    150907 14:38:44 [Note] Event Scheduler: Loaded 0 events
    150907 14:38:44 [Note] /usr/libexec/mysqld: ready for connections.
    Version: '5.5.45'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL) by Remi
    150907 16:49:07 [Warning] IP address '45.34.79.110' could not be resolved: Temporary failure in name resolution
    150907 16:49:08 [Warning] IP address '45.34.79.110' could not be resolved: Temporary failure in name resolution
    150907 16:49:09 [Warning] IP address '45.34.79.110' could not be resolved: Temporary failure in name resolution
    150907 16:49:09 [Warning] IP address '45.34.79.110' could not be resolved: Temporary failure in name resolution
    150907 16:49:10 [Warning] IP address '45.34.79.110' could not be resolved: Temporary failure in name resolution
    150907 16:49:10 [Warning] IP address '45.34.79.110' could not be resolved: Temporary failure in name resolution
    150907 16:49:11 [Warning] IP address '45.34.79.110' could not be resolved: Temporary failure in name resolution
    150907 16:49:11 [Warning] IP address '45.34.79.110' could not be resolved: Temporary failure in name resolution
    150907 16:49:12 [Warning] IP address '45.34.79.110' could not be resolved: Temporary failure in name resolution
    İnternette çeşitli sonuçlara baktım sonuç alamadım, yardımcı olanlara şimdiden teşekkürler.
  • 20-03-2016, 13:16:38
    #2
    http://serverfault.com/questions/341...ot-be-resolved


    hocam buradaki çözüme bir göz atın isterseniz
  • 20-03-2016, 13:31:02
    #3
    harddiskte ne kadar boş yer var bir bakabilirmisin?

    InnoDB: The first specified data file ./ibdata1 did not exist:
    InnoDB: a new database to be created!
    150907 14:38:43 InnoDB: Setting file ./ibdata1 size to 10 MB
    InnoDB: Database physically writes the file full: wait...
    150907 14:38:43 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
    InnoDB: Setting log file ./ib_logfile0 size to 5 MB
    InnoDB: Database physically writes the file full: wait...
    150907 14:38:43 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
    InnoDB: Setting log file ./ib_logfile1 size to 5 MB
    InnoDB: Database physically writes the file full: wait...

    bu dosyalar yok olmuş ve yerine yenisini yapıyor..sql dataları ile alakalı bir sorun var gibi..
  • 20-03-2016, 14:24:57
    #4
    Üyeliği durduruldu
    İlk önce alanda sorun vardı 100% doluydu. Alanı genişlettim şuanki alan.
    Filesystem      Size  Used Avail Use% Mounted on
    /dev/vda1        59G   45G   12G  80% /
    tmpfs           2.0G     0  2.0G   0% /dev/shm
  • 20-03-2016, 15:36:11
    #5
    abdullahercan adlı üyeden alıntı: mesajı görüntüle
    İlk önce alanda sorun vardı 100% doluydu. Alanı genişlettim şuanki alan.
    Filesystem      Size  Used Avail Use% Mounted on
    /dev/vda1        59G   45G   12G  80% /
    tmpfs           2.0G     0  2.0G   0% /dev/shm
    df -i çıktısını paylaşabilirmisin hocam yukarıda arkadaşın dediği gibi inode dolmuş olabilir. Eğer inode dolmadı ise benim atığım linke bir göz at istersen
  • 20-03-2016, 15:58:32
    #6
    Üyeliği durduruldu
    bantumi adlı üyeden alıntı: mesajı görüntüle
    df -i çıktısını paylaşabilirmisin hocam yukarıda arkadaşın dediği gibi inode dolmuş olabilir. Eğer inode dolmadı ise benim atığım linke bir göz at istersen
    Çıktı bu şekilde hocam.
    Filesystem      Inodes  IUsed   IFree IUse% Mounted on
    /dev/vda1      3932160 884923 3047237   23% /
    tmpfs           506850      1  506849    1% /dev/shm