Author: Shay Maor

After installing Docker through Microsoft Visual Studio, you may have noticed VMware claims Hyper-V Hypervisor is installed.

If like me, you’ve already removed Hyper-V feature from Windows and are wondering why this error comes up. You might want to read on to find a way to use your VMware

The first step, you may have examined the Windows Feature to come across this perplexing setting. Hyper-V looks disabled. Why this error.

These are troubleshooting steps

• Go to Command Prompt as Admin and type in systeminfo 
• If this claims that a Hyper Visor has been detected try the below
• In PowerShell as Admin type
• Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
• DISM /Online /Disable-Feature:Microsoft-Hyper-V
• In Command Prompt
• bcdedit /set hypervisorlaunchtype off
• Now Restart your computer and discover that VMWare now works

Source:

How to Uninstall or Disable Hyper-V in Windows (nakivo.com)

2 years ago I successfully set up Pikrellcam for the Raspberry Pi for motion capture detection. An open source package that sets up nginx and a custom PHP Web application that communicates with a series of server side scripts written in C to analyze the content coming through the Camera.

Raspberry Pi Camera Module V2 with Open Source PiKrellCam detecting reflections of water off ceiling.

I was exploring StackOverflow and noticed this was a common issue. After a few explorations of my own. I found the answer.

Configuration

sysadmin@appserver:/var/canvas$ sudo vi config/outgoing_mail.yml

You’ll need to replace the production part with something along the lines of the following. If you’re using Gmail, you will need to create an application password. More information on that is provided in the bottom of this post.

 production:
    enable_starttls_auto: true
    address: smtp.gmail.com
    port: 587
    user_name: USERNAME@gmail.com
    password: PASSWORD
    authentication: plain        # plain, login, or cram_md5
    domain: smtp.gmail.com
    outgoing_address: USERNAME@gmail.com
    default_name: Instructure Canvas

Automated Jobs Daemon

You first must set up the Automated Jobs Daemon with the following:

sysadmin@appserver:/var/canvas$ sudo ln -s /var/canvas/script/canvas_init /etc/init.d/canvas_init
sysadmin@appserver:/var/canvas$ sudo update-rc.d canvas_init defaults
sysadmin@appserver:/var/canvas$ sudo /etc/init.d/canvas_init start

Update Configuration

If for whatever reason you need to update the configuration.

sysadmin@appserver:/var/canvas$ sudo /etc/init.d/canvas_init restart

Setting up Gmail for Outgoing Mail

Regarding setting up outgoing mail through gmail:

This might be a new update, but in order for the mail to work correctly, you have to set up an application specific password with Gmail. There are a ton of tutorials online on how to do that… here it is from Google:

https://support.google.com/accounts/answer/185833?hl=en

Troubleshooting

If you’re having any issues, delayed jobs daemon sets up a log file that you can search through

sysadmin@appserver:/var/canvas$ sudo vi log/delayed_job.log

Hope this helps anyone that needs it