Database connection error at starting (terminal error from debug.log)
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Database connection error at starting (terminal error from debug.log)
Hi,
Since some weeks UMS has begun to crash during start.
This can follow installation of update 9.3 installation of UMS and windows updates but I am not sure (nevertheless I need to do it twice, I had forgot it was running and after javaw was running too).
I checked the debug.log (and repeat test).
UMS stops with:
ERROR : <date-time> [main] Database connection error : IO exception :null
IOexception : null [90028-199]
what can be the cause ? and solution ? where my first questions.
I must note that several times UMS (it is launched automatically with windows) several times has been shutdown by Wndows with normal shutdown for planned updates and once by system emergency stop due to overheat.
After the test of reinstallation with the care of canceling javaw.exe (associated with UMS) nothing had changed.
Then I have decided to reinstall a full fresh 9.3. For this I have :
- renamed "Programdata/UMS" to "ProgramData/UMS.old"
- used a new directory to install UMS
Everything had function normally but I have now to configure all the parameters, the shared sources and the external media, I kept the *.conf files.
So there are three important questions now, linked with the purpose to avoid this issue in the future :
- Is it a way to check the old database and reuse it ? (unlock or repair integrity)
- to prevent such accident, may be the solution is a daily full backup of the database or whole "Programdata/UMS" linked with a command line defined to checkup the integrity and for, either go on, or exceptionally restore. If it is valid, each two days, the old backup is deleted to avoid large space used by the backup ? Just the current updates of the day have the risk to be lost ?
- when there is a version upgrade, when the database upgrade are they performed (may be it is into the FAQ, I have not found a chapter : precautions before upgrade or upgrade process ; since I uses UMS each upgrade has been automatically successfully performed )
Best regards,
TREBLY
______________________________________________________________________________________________________________________________
PS : joined : the full debug.log and db infos :
in Program/data/UMS/database
- medias.mv.db : last update 2020/03/05 last data of well functioning - 41 Mo
- medias-trace.db last update 2020/03/23-15_32 : last launch (failed) - 227Ko
Since some weeks UMS has begun to crash during start.
This can follow installation of update 9.3 installation of UMS and windows updates but I am not sure (nevertheless I need to do it twice, I had forgot it was running and after javaw was running too).
I checked the debug.log (and repeat test).
UMS stops with:
ERROR : <date-time> [main] Database connection error : IO exception :null
IOexception : null [90028-199]
what can be the cause ? and solution ? where my first questions.
I must note that several times UMS (it is launched automatically with windows) several times has been shutdown by Wndows with normal shutdown for planned updates and once by system emergency stop due to overheat.
After the test of reinstallation with the care of canceling javaw.exe (associated with UMS) nothing had changed.
Then I have decided to reinstall a full fresh 9.3. For this I have :
- renamed "Programdata/UMS" to "ProgramData/UMS.old"
- used a new directory to install UMS
Everything had function normally but I have now to configure all the parameters, the shared sources and the external media, I kept the *.conf files.
So there are three important questions now, linked with the purpose to avoid this issue in the future :
- Is it a way to check the old database and reuse it ? (unlock or repair integrity)
- to prevent such accident, may be the solution is a daily full backup of the database or whole "Programdata/UMS" linked with a command line defined to checkup the integrity and for, either go on, or exceptionally restore. If it is valid, each two days, the old backup is deleted to avoid large space used by the backup ? Just the current updates of the day have the risk to be lost ?
- when there is a version upgrade, when the database upgrade are they performed (may be it is into the FAQ, I have not found a chapter : precautions before upgrade or upgrade process ; since I uses UMS each upgrade has been automatically successfully performed )
Best regards,
TREBLY
______________________________________________________________________________________________________________________________
PS : joined : the full debug.log and db infos :
in Program/data/UMS/database
- medias.mv.db : last update 2020/03/05 last data of well functioning - 41 Mo
- medias-trace.db last update 2020/03/23-15_32 : last launch (failed) - 227Ko
Code: Select all
DEBUG.LOG
[code]DEBUG 2020-03-23 15:32:46.213 [main] Default logfile folder set to: C:\ProgramData\UMS
DEBUG 2020-03-23 15:32:46.332 [main] LogBack started with configuration file: C:\Program Files (x86)\Universal Media Server-9.3\logback.xml
DEBUG 2020-03-23 15:32:46.344 [main] Starting services
DEBUG 2020-03-23 15:32:46.346 [main] Starting ProcessManager
DEBUG 2020-03-23 15:32:46.348 [Process Terminator] ProcessTerminator is starting
DEBUG 2020-03-23 15:32:46.349 [main] Starting SleepManager
DEBUG 2020-03-23 15:32:46.353 [main] Mon Mar 23 15:32:46 CET 2020
DEBUG 2020-03-23 15:32:46.353 [main] Reading cred.path: "C:\ProgramData\UMS\UMS.cred" (default: "")
DEBUG 2020-03-23 15:32:46.519 [main] Writing PID: 33336
DEBUG 2020-03-23 15:32:46.657 [main]
INFO 2020-03-23 15:32:46.658 [main] Starting Universal Media Server 9.3.0
INFO 2020-03-23 15:32:46.658 [main] Based on PS3 Media Server by shagrath, copyright 2008-2014
INFO 2020-03-23 15:32:46.658 [main] https://www.universalmediaserver.com
INFO 2020-03-23 15:32:46.658 [main]
INFO 2020-03-23 15:32:46.658 [main] Build: 72f327891 (2020-02-23)
INFO 2020-03-23 15:32:46.659 [main] Java: Java HotSpot(TM) 64-Bit Server VM 1.8.0_241 (64-bit) by Oracle Corporation
INFO 2020-03-23 15:32:46.660 [main] OS: Windows 10 64-bit 10.0
INFO 2020-03-23 15:32:46.664 [main] Maximum JVM Memory: 1.1 GiB
INFO 2020-03-23 15:32:46.670 [main] Language: French
INFO 2020-03-23 15:32:46.670 [main] Encoding: UTF-8
INFO 2020-03-23 15:32:46.670 [main]
INFO 2020-03-23 15:32:46.671 [main] Working directory: C:\Program Files (x86)\Universal Media Server-9.3
INFO 2020-03-23 15:32:46.678 [main] Temporary directory: C:\Users\bty-a\AppData\Local\Temp\UMS
INFO 2020-03-23 15:32:46.679 [main] Logging configuration file: C:\Program Files (x86)\Universal Media Server-9.3\logback.xml
INFO 2020-03-23 15:32:46.679 [main] Logfile: C:\ProgramData\UMS\debug.log
INFO 2020-03-23 15:32:46.680 [main]
INFO 2020-03-23 15:32:46.680 [main] Profile directory: C:\ProgramData\UMS
INFO 2020-03-23 15:32:46.681 [main] Profile directory permissions: drwx
INFO 2020-03-23 15:32:46.681 [main] Profile configuration file: C:\ProgramData\UMS\UMS.conf
INFO 2020-03-23 15:32:46.682 [main] Profile configuration file permissions: -rwx
INFO 2020-03-23 15:32:46.683 [main] Profile name: ****
INFO 2020-03-23 15:32:46.683 [main]
DEBUG 2020-03-23 15:32:46.683 [main] Reading web_conf: "C:\ProgramData\UMS\WEB.conf" (previous: null, default: "C:\ProgramData\UMS\WEB.conf")
INFO 2020-03-23 15:32:46.683 [main] Web configuration file: C:\ProgramData\UMS\WEB.conf
INFO 2020-03-23 15:32:46.685 [main] Web configuration file permissions: -rwx
INFO 2020-03-23 15:32:46.685 [main]
DEBUG 2020-03-23 15:32:46.693 [main] Using database URL: jdbc:h2:C:\ProgramData\UMS\database\medias
INFO 2020-03-23 15:32:46.693 [main] Using database located at: "C:\ProgramData\UMS\database"
DEBUG 2020-03-23 15:32:46.694 [main] Database logging is disabled
ERROR 2020-03-23 15:32:46.856 [main] Database connection error: IO Exception: null
IO Exception: null [90028-199]