Posts made by NashBrydges

@DustinB3403 No idea. But it worked.

Ok, I started looking into the error.log file to get more info about what was happening. I found that there was an error about not being able to load something but the log file was pretty large so I created a new log file to replace this one and went to restart mysql so I would have the one attempt's worth of records to review. To my surprise, after having provided a new error.log file, mysql started up no problem. Not sure wtf that was all about or why it failed with the current error.log contents.

I'm removing mysql and starting from scratch to see if I can replicate the issue.

@scottalanmiller said in MySQL db refusing to start after Ubuntu 16.04.1 reboot:

Can you try this...

sudo apt-get install apparmor-profiles apparmor-profiles-extra apparmor-docs apparmor-utils

See if that does anything?

This did install additional packages but mysql service still isn't starting however this time the output of journalctl -xe shows:

-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has failed.
--
-- The result is failed.
Feb 11 12:42:35 REDACTED systemd[1]: mysql.service: Unit entered failed state.
Feb 11 12:42:35 REDACTED systemd[1]: mysql.service: Failed with result 'exit-code'.
Feb 11 12:42:35 REDACTED systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Feb 11 12:42:35 REDACTED systemd[1]: Stopped MySQL Community Server.
-- Subject: Unit mysql.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has finished shutting down.
Feb 11 12:42:35 REDACTED systemd[1]: Starting MySQL Community Server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has begun starting up.
Feb 11 12:42:37 REDACTED systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE

This seems even more cryptic than the first output.

@DustinB3403 said in MySQL db refusing to start after Ubuntu 16.04.1 reboot:

@NashBrydges said in MySQL db refusing to start after Ubuntu 16.04.1 reboot:

@DustinB3403 said in MySQL db refusing to start after Ubuntu 16.04.1 reboot:

/usr/sbin/mysqld

Just checked. There is no file named "/usr/sbin/mysqld"

The fact that you don't see the path means that either your running under the wrong account (don't have permission) or that something was removed.

The root account still existed in the mysql.user table, along with the debian maintenance account that is setup during install. I added a new underpriviledged user to the mysql.user table but not to the server. Thatis still running under the only account that exists.

@DustinB3403 I created a new user with select, update, insert delete privs on a new database within mysql but there nothing under any other users anywhere. I've been using this user for the past 2 days and it worked well.

I should mention that mysql is running on the standard port and nothing has been changed on the mysqld.cnf file.

@scottalanmiller said in MySQL db refusing to start after Ubuntu 16.04.1 reboot:

I thought that Ubuntu came with MariaDB, not MySQL. Where did you get MySQL?

Installed from "sudo apt-get install mysql-server"

@DustinB3403 said in MySQL db refusing to start after Ubuntu 16.04.1 reboot:

/usr/sbin/mysqld

Just checked. There is no file named "/usr/sbin/mysqld"

@DustinB3403 Correct. To start I used "sudo service mysql status" and this is where I discovered it wasn't running.

@DustinB3403 It basically shows apparmor is denying mysql startup.

@DustinB3403 said in MySQL db refusing to start after Ubuntu 16.04.1 reboot:

What does journalctl -xe have to say?

I've posted that output in my original post. It's at the bottom of the post.

I have mysql recently installed on an Ubuntu 16.04.1 server and have been testing the application for the last couple of days without issue. I updated Ubuntu (mysql didn't require any updates - it is a recent install so it's already current) and after the update and a reboot, mysql refuses to start. I'm new to mysql so I'm hoping someone here can help me figure out why it isn't starting up.

service mysql status output:

● mysql.service - MySQL Community Server`
   Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
   Active: activating (start-post) (Result: exit-code) since Sat 2017-02-11 11:54:54 EST; 27s ago
  Process: 3129 ExecStart=/usr/sbin/mysqld (code=exited, status=1/FAILURE)
  Process: 3126 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
 Main PID: 3129 (code=exited, status=1/FAILURE);         : 3135 (mysql-systemd-s)
    Tasks: 2
   Memory: 332.0K
      CPU: 519ms
   CGroup: /system.slice/mysql.service
           └─control
             ├─3135 /bin/bash /usr/share/mysql/mysql-systemd-start post
             └─3723 sleep 1

Feb 11 11:54:54 REDACTED systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Feb 11 11:54:54 REDACTED systemd[1]: Stopped MySQL Community Server.
Feb 11 11:54:54 REDACTED systemd[1]: Starting MySQL Community Server...
Feb 11 11:54:58 REDACTED systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE

Looking at journalctl -xe reveals:

-- The result is failed.
Feb 11 12:05:04 REDACTED systemd[1]: mysql.service: Unit entered failed state.
Feb 11 12:05:04 REDACTED systemd[1]: mysql.service: Failed with result 'exit-code'.
Feb 11 12:05:04 REDACTED systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Feb 11 12:05:04 REDACTED kernel: audit: type=1400 audit(1486832704.624:84): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/6321/status" pid=6321 comm="mysqld" requested_mask="r" d
Feb 11 12:05:04 REDACTED kernel: audit: type=1400 audit(1486832704.624:85): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" pid=6321 comm="mysqld" requested_ma
Feb 11 12:05:04 REDACTED kernel: audit: type=1400 audit(1486832704.624:86): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/6321/status" pid=6321 comm="mysqld" requested_mask="r" d
Feb 11 12:05:04 REDACTED audit[6321]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/6321/status" pid=6321 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=117 ouid=117
Feb 11 12:05:04 REDACTED audit[6321]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" pid=6321 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=117 o
Feb 11 12:05:04 REDACTED audit[6321]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/6321/status" pid=6321 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=117 ouid=117
Feb 11 12:05:04 REDACTED systemd[1]: Stopped MySQL Community Server.
-- Subject: Unit mysql.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has finished shutting down.
Feb 11 12:05:04 REDACTED systemd[1]: Starting MySQL Community Server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has begun starting up.
Feb 11 12:05:06 REDACTED systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE

Can't figure out why it's is being denied startup by apparmor. Any ideas on where to go next to get this thing started?

@Tim_G said in I'll Show You Mine If You Show Me Yours, Home Labs:

@NashBrydges said in I'll Show You Mine If You Show Me Yours, Home Labs:

@Tim_G said in I'll Show You Mine If You Show Me Yours, Home Labs:

@NashBrydges said in I'll Show You Mine If You Show Me Yours, Home Labs:

@Tim_G According to my UPSs, I'm running my lab on about 1.2kw and yeah, I definitely notice the increase in power bill. It's costing me about $125 per month based on loca rates, delivery charges and taxes in.

Is that $125 extra or $125 total? If total, how much extra does it add for you with your setup?

It's $125 extra per month. Just for the networking and server gear.

Wow... your setup is something I'd love to have at home. But there's no way I could justify that cost per month, if you know what I mean.

I know what you mean. The only reason I have this is because most is tax deductible through my business otherwise i would find a way to do without it all.

@Tim_G said in I'll Show You Mine If You Show Me Yours, Home Labs:

@NashBrydges said in I'll Show You Mine If You Show Me Yours, Home Labs:

@Tim_G According to my UPSs, I'm running my lab on about 1.2kw and yeah, I definitely notice the increase in power bill. It's costing me about $125 per month based on loca rates, delivery charges and taxes in.

Is that $125 extra or $125 total? If total, how much extra does it add for you with your setup?

It's $125 extra per month. Just for the networking and server gear.

@Tim_G According to my UPSs, I'm running my lab on about 1.2kw and yeah, I definitely notice the increase in power bill. It's costing me about $125 per month based on loca rates, delivery charges and taxes in.

@MilkySibb The home lab has changed quite a bit since I posted this. I've replaced the 2 x R710s + MD1000 with 2 x R510 each with 12 x 6TB drives. Primary use is as a single VM fileserver. Two other Hyper-V hosts are now a R420 and R620 all running SSDs.

@wirestyle22 said in Large Linux Samba Server On Hyper-V 2012 R2 - Caveats? Best Practices?:

So does the host file system (NTFS) not manage the partition the VM file system is on (XFS)? Is that why @scottalanmiller is saying to separate the two? i'm a little confused how the two interact or if they interact directly/indirectly.

From what Scott is suggesting, I would create 2 VHDX. One where I'll install Linux. The other to actually hold the data. This second VHDX will be mounted to the Linux VM from within the VM and formatted from within the VM. The host will create the VHDX container and the VM will format the container and mount the container for presentation to the users. Because the 2 VHDXs have different functions (one is to run the vistual machine OS and the other just to hold data), keeping them separate appears to present some advantages for their individual intended purpose.

The host will simply set aside the "data blocks" and the VM OS will format them.

@Dashrender said in Large Linux Samba Server On Hyper-V 2012 R2 - Caveats? Best Practices?:

@scottalanmiller said in Large Linux Samba Server On Hyper-V 2012 R2 - Caveats? Best Practices?:

@Dashrender said in Large Linux Samba Server On Hyper-V 2012 R2 - Caveats? Best Practices?:

@NashBrydges said in Large Linux Samba Server On Hyper-V 2012 R2 - Caveats? Best Practices?:

@scottalanmiller Thanks for this. So is it fair to say you'd also recommend formatting the data partition accordingly (ie: NTFS vs. Ext4)?

Am I correct in my understanding, from the hypervisor perspective, the VM storage partition will be NTFS, but the VM will be formatted something Linux friendly?

Hyper-V uses ReFS or NTFS, if that is what you are asking.

yes, it is. So depending on how @NashBrydges looks at it, he'll see one filesystem or another.

Correct. Accessing the Hyper-V host I'll see the native file system. And the VM performs the file server function is what the users will be presented with

@Dashrender said in Large Linux Samba Server On Hyper-V 2012 R2 - Caveats? Best Practices?:

So I have a couple of questions - You're getting rid of Windows Licensing, but not Windows in general? Why use Hyper-V instead of XenServer? Is it because you're using Veeam?

Why a server instead of a NAS?

They're a Windows shop. They use Windows on their desktops and that's not going away. They already have Veeam so didn't make sense to move them away from something they already knew well and worked well. They already have 2 Synology NAS. One is used for local backup which is then copied over to a remote NAS at the owner's home. They also already have the R510 which is a perfect solution for their large storage needs and also supports a few other VMs.

@scottalanmiller Thanks for this. So is it fair to say you'd also recommend formatting the data partition accordingly (ie: NTFS vs. Ext4)?

I have a client who is eliminating their Windows license cost and setting up a Linux VM on a Dell R510. The host will be running Hyper-V 2012 R2 (not Windows with Hyper-V role) and looking to setup a large file server for their team of 4. The Linux VM will simply be a Samba file server and serve no other function. Expected size for the VM is around 30TB+. I'm used to setting up web servers and small file servers where I don't manually adjust partition sizes or setup anything special at OS install but wondering if there are any caveats I should know about when going this large.

Are there any best practices you would recommend? Should I setup 2 different virtual disks (1 for OS and 1 to mount for data) or just a single disk? Do I need to manually adjust partition sizes during install? Any special considerations to keep in mind knowing that I may need to expand the data storage down the road? I may be over-complicating this in my head but I'm of the "measure twice and cut once" mindset, especially when I can ask a group of experts.

In case some of you want to know, there is no Active Directory (Workgroup environment), all Windows PCs, Veeam B&R for backup. Anything else you want to know, just ask.

[Edit] For spelling error in thread title.