OSA Service does not start with 4.7 and fresh build of Win10

A place to report bugs and discuss testing
Post Reply
Message
Author
Datahead
Posts: 710
Joined: Fri Jan 27, 2012 6:50 am
Location: San Marcos, Ca.

OSA Service does not start with 4.7 and fresh build of Win10

#1 Post by Datahead » Wed Dec 09, 2015 5:26 pm

So went through a fresh install of Win 10, MySQL, and OSA 4.7. Everything seened to install correctly and the DB is there etc. But I am getting a 1053 error (Service timed out) when I try to start the service as it is not starting automaticly.

Any ideas???

Vaughn
Site Admin
Posts: 1432
Joined: Thu May 13, 2010 2:17 pm

Re: OSA Service does not start with 4.7 and fresh build of W

#2 Post by Vaughn » Wed Dec 09, 2015 5:54 pm

Try opening the screen.exe app and the web page. If there are DB connection issues, they will show trying to run screens.

Next you can check the Windows event log for any errors.

Make sure the MySQL is not only installed, but that the MySQL service is running.

Make sure your Windows firewall is off, and maybe anti-virus software until you have OSA working.

I did have the service not start for me a couple times in the past, and they were never code issues, but can't remember for sure anything that would be affecting a new install at the moment.

If I think of anything I will post it, and keep me up-to-date if you see anything out of place, errors or the such that might help me troubleshoot.

Vaughn
Site Admin
Posts: 1432
Joined: Thu May 13, 2010 2:17 pm

Re: OSA Service does not start with 4.7 and fresh build of W

#3 Post by Vaughn » Thu Dec 10, 2015 12:26 am

I was just falling asleep and remembered, I think the last time I was having issues with the service starting was that my `osa` user did not have super-privileges, so when the service tried to start, it runs a command to turn on global events in MySQL and that required super-privileges, causing the service to hang.

So using Workbench, check the osa account, make sure super privileges is checked and restart the service.

I will take a look at the code and make sure that it just skips that step and does not hang if there are problems.


Vaughn

mlinnen
Posts: 9
Joined: Sun Nov 29, 2015 3:25 pm

Re: OSA Service does not start with 4.7 and fresh build of W

#4 Post by mlinnen » Thu Dec 10, 2015 8:24 am

I wanted to mention that in 4.6 I had to change the service to delayed start as it would not start on boot until I did this. This doesn't really sound like the problem the user was actually having but I did wan't to mention it in case it was a "service not starting on boot" problem.

Datahead
Posts: 710
Joined: Fri Jan 27, 2012 6:50 am
Location: San Marcos, Ca.

Re: OSA Service does not start with 4.7 and fresh build of W

#5 Post by Datahead » Thu Dec 10, 2015 9:01 am

GOT IT WORKING!!!
I am not sure why, but OSA does not seem to like MySQL 5.7... I uninstalled 5.7 completely and reinstalled 5.6 and the OSAE system came up perfect...
Woo Hoo!!!

Vaughn
Site Admin
Posts: 1432
Joined: Thu May 13, 2010 2:17 pm

Re: OSA Service does not start with 4.7 and fresh build of W

#6 Post by Vaughn » Thu Dec 10, 2015 10:24 am

Every machine I have, including all my test boxes are all running on 5.7.9 or 5.7.10.

What did you name the MySQL service when you installed? That is the only difference between the versions as far as OSA knows. 5.7 will try to name your service MySQL57, where in the videos and on my machines, I rename it to MySQL. Our code should handle the MySQL57 name, but I did not test it well.

Vaughn

Datahead
Posts: 710
Joined: Fri Jan 27, 2012 6:50 am
Location: San Marcos, Ca.

Re: OSA Service does not start with 4.7 and fresh build of W

#7 Post by Datahead » Thu Dec 10, 2015 7:10 pm

I just left it at whatever the default name was on the two different versions of MySQL...

Datahead
Posts: 710
Joined: Fri Jan 27, 2012 6:50 am
Location: San Marcos, Ca.

Re: OSA Service does not start with 4.7 and fresh build of W

#8 Post by Datahead » Mon Dec 14, 2015 9:42 am

I am however showing a error when I startup Manager:
Manager seems to still function however.
Attachments
2015-12-11.png
2015-12-11.png (13.03 KiB) Viewed 2395 times

Post Reply