Clean install not working in Ubuntu 12.04

[heberth]

Hello,

I have installed many times zpanel on Ubuntu 12.04 and now sentora on 14.04 without issue. However I tried installing Sentora on two different VPS from ovh running ubuntu 12.04. The script completes and gives me all the passwords.

But when I try to login usin the server IP the site doesn't load. I checked the services and bind9, apache and mysql are not running. I can manually start bind9 and apache but when I run "service mysql start" I get an error "Job failed to start"

This is the error log I found on /var/log/mysql/error.log

150319 12:51:53 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150319 12:51:53 [Note] Plugin 'FEDERATED' is disabled.
150319 12:51:53 InnoDB: The InnoDB memory heap is disabled
150319 12:51:53 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150319 12:51:53 InnoDB: Compressed tables use zlib 1.2.3.4
150319 12:51:53 InnoDB: Initializing buffer pool, size = 128.0M
150319 12:51:54 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
150319 12:51:54 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
150319 12:51:54 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...
150319 12:51:54 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
150319 12:51:54 InnoDB: Waiting for the background threads to start
150319 12:51:55 InnoDB: 5.5.41 started; log sequence number 0
150319 12:51:55 InnoDB: Starting shutdown...
150319 12:51:56 InnoDB: Shutdown completed; log sequence number 1595675
150319 12:51:56 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150319 12:51:56 [Note] Plugin 'FEDERATED' is disabled.
150319 12:51:56 InnoDB: The InnoDB memory heap is disabled
150319 12:51:56 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150319 12:51:56 InnoDB: Compressed tables use zlib 1.2.3.4
150319 12:51:56 InnoDB: Initializing buffer pool, size = 128.0M
150319 12:51:56 InnoDB: Completed initialization of buffer pool
150319 12:51:56 InnoDB: highest supported file format is Barracuda.
150319 12:51:56 InnoDB: Waiting for the background threads to start
150319 12:51:57 InnoDB: 5.5.41 started; log sequence number 1595675
ERROR: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ALTER TABLE user ADD column Show_view_priv enum('N','Y') CHARACTER SET utf8 NOT ' at line 1
150319 12:51:57 [ERROR] Aborting

150319 12:51:57 InnoDB: Starting shutdown...
150319 12:51:57 InnoDB: Shutdown completed; log sequence number 1595675
150319 12:51:57 [Note] /usr/sbin/mysqld: Shutdown complete

150319 12:51:57 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150319 12:51:57 [Note] Plugin 'FEDERATED' is disabled.
150319 12:51:57 InnoDB: The InnoDB memory heap is disabled
150319 12:51:57 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150319 12:51:57 InnoDB: Compressed tables use zlib 1.2.3.4
150319 12:51:57 InnoDB: Initializing buffer pool, size = 128.0M
150319 12:51:57 InnoDB: Completed initialization of buffer pool
150319 12:51:57 InnoDB: highest supported file format is Barracuda.
150319 12:51:58 InnoDB: Waiting for the background threads to start
150319 12:51:59 InnoDB: 5.5.41 started; log sequence number 1595675
150319 12:51:59 InnoDB: Starting shutdown...
150319 12:51:59 InnoDB: Shutdown completed; log sequence number 1595675
150319 12:51:59 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150319 12:51:59 [Note] Plugin 'FEDERATED' is disabled.
150319 12:51:59 InnoDB: The InnoDB memory heap is disabled
150319 12:51:59 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150319 12:51:59 InnoDB: Compressed tables use zlib 1.2.3.4
150319 12:51:59 InnoDB: Initializing buffer pool, size = 128.0M
150319 12:51:59 InnoDB: Completed initialization of buffer pool
150319 12:51:59 InnoDB: highest supported file format is Barracuda.
150319 12:51:59 InnoDB: Waiting for the background threads to start
150319 12:52:00 InnoDB: 5.5.41 started; log sequence number 1595675
ERROR: 1050 Table 'plugin' already exists
150319 12:52:00 [ERROR] Aborting

150319 12:52:00 InnoDB: Starting shutdown...
150319 12:52:01 InnoDB: Shutdown completed; log sequence number 1595675
150319 12:52:01 [Note] /usr/sbin/mysqld: Shutdown complete

Anyone know what the issue is or how to fix it?
Thanks a lot for your help!

[Me.B]

You have an issue with Mysql here. It's like mysql failing to create temp file.

Try to fix mysql as it's key for all the system to work.

M B

[heberth]

Thanks for the answer.

The issue is that after installation I reboot the server and it gets stuck on the booting part. That's why many services don't start.

There is something strange over there. So in the mean time I will install zpanel.

Thank you,
Heberth

[Me.B]

It's likely related to the image your using for VPS.

M B

[heberth]

Well it's OVH's default and only option for Ubuntu 12.04.
Their option for Ubuntu 14.04 works fine with Sentora.

[Me.B]

Well it's OVH's default and only option for Ubuntu 12.04.
Their option for Ubuntu 14.04 works fine with Sentora.

OVH also use custom kernels... I don't have an idea, do you have a rescue mode in VPS to check config?

M B

[heberth]

Yes the vps can be rebooted into rescue mode but I have no idea how to use it. I only know how to login via ssh to it. Then I wouldn't know what to do.

Perhaps if you tell me commands to check once in rescue mode.

thanks,
Heberth

[Me.B]

Check /var/log/messages or /var/log/syslog