errorlog.txt
[MDEV-11682] Error during installing database and starting server Created: 2016-12-28 Updated: 2017-05-18 Resolved: 2017-05-18 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Configuration, Platform Windows |
| Affects Version/s: | 10.1.20 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Thomas Kiesl | Assignee: | Vladislav Vaintroub |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Windows Server 2013R2 |
||
| Attachments: |
errorlog.txt
|
| Description |
|
During the installation of the database the process stucks on the step "installing services". After a while I receive the error "Service 'test' failed to start. Verify that you have sufficient privileges to start system services." in the logfile. (Installer was started as administrator account). If I check the windows alerts I found the following warning "mysqld.exe: Event Scheduler: Failed to open table mysql.event" The error log is attached to this issue. |
| Comments |
| Comment by Vladislav Vaintroub [ 2016-12-28 ] |
|
From the IRC, the windows error log had these entries. The rerun of installer was successful, so the error does not seem to be persistent. |
| Comment by Vladislav Vaintroub [ 2016-12-28 ] |
|
tKiesl , is there maybe some antivirus software on the machine? that was scanning at about the same time installation was performed? |
| Comment by Thomas Kiesl [ 2016-12-29 ] |
|
There is an anti virus software available, but it scans the machine only once in the week. |
| Comment by Vladislav Vaintroub [ 2016-12-29 ] |
|
I was rather interested on real-time protection feature, many (or maybe all) AV software that has this feature would examine newly created files shortly after the creation, and perhaps a buggy one could open file in exclusive mode (disallow other programs to open for readwrite). |
| Comment by Thomas Kiesl [ 2016-12-29 ] |
|
There is no real-time protection active. |
| Comment by Vladislav Vaintroub [ 2016-12-29 ] |
|
Alright. If you can catch a state where it is reproducible, a procmon trace of mysqld.exe (during the installation) would be extremely helpful. |
| Comment by Thomas Kiesl [ 2016-12-29 ] |
|
I retried it today again and as already mentioned yesterday in IRC, it finished without any issues... |
| Comment by Vladislav Vaintroub [ 2017-05-18 ] |
|
Closing, as not enough information available to reproduce it |