theotherp / nzbhydra2

Usenet meta search
Other
1.23k stars 75 forks source link

My installation only works on my desktop and not my laptop #859

Open kanishknishar opened 1 year ago

kanishknishar commented 1 year ago

I am trying to restore my NZBHydra 2 config files from my Desktop and so I backed it up and tried to restore it. However instead of reloading the app is stuck on trying to reload the wrapper. I closed the application from Task Manager and started it again. I can see the icon in my task bar but the application doesn't start up. Double clicking or restarting does nothing as well. I originally used to run NZBHydra 2 straight from the folder as I synced it via OneDrive but that caused the same issue as what I just described.

I can attach the log files but apparently they can contain sensitive info? I can't really anonymize my log as the app won't open but I suspect I can see the issue:

C:\Users\Lance\Desktop\nzbhydra2-5.1.8-windows)
2023-04-25 19:35:19.043  INFO --- [              main] org.nzbhydra.NzbHydra                    : The following 1 profile is active: "default"
2023-04-25 19:35:19.156  INFO --- [              main] trationDelegate$BeanPostProcessorChecker : Bean 'hydraTaskConfiguration' of type [org.nzbhydra.tasks.HydraTaskConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-25 19:35:19.225  INFO --- [              main] trationDelegate$BeanPostProcessorChecker : Bean 'baseConfig' of type [org.nzbhydra.config.BaseConfig] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-25 19:35:19.227  INFO --- [              main] trationDelegate$BeanPostProcessorChecker : Bean 'categoriesConfigValidator' of type [org.nzbhydra.config.validation.CategoriesConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-25 19:35:19.230  INFO --- [              main] trationDelegate$BeanPostProcessorChecker : Bean 'downloaderConfigValidator' of type [org.nzbhydra.config.validation.DownloaderConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-25 19:35:19.230  INFO --- [              main] trationDelegate$BeanPostProcessorChecker : Bean 'downloadingConfigValidator' of type [org.nzbhydra.config.validation.DownloadingConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-25 19:35:19.231  INFO --- [              main] trationDelegate$BeanPostProcessorChecker : Bean 'searchingConfigValidator' of type [org.nzbhydra.config.validation.SearchingConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-25 19:35:19.232  INFO --- [              main] trationDelegate$BeanPostProcessorChecker : Bean 'loggingConfigValidator' of type [org.nzbhydra.config.validation.LoggingConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-25 19:35:19.233  INFO --- [              main] trationDelegate$BeanPostProcessorChecker : Bean 'mainConfigValidator' of type [org.nzbhydra.config.validation.MainConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-25 19:35:19.234  INFO --- [              main] trationDelegate$BeanPostProcessorChecker : Bean 'userAuthConfigValidator' of type [org.nzbhydra.config.validation.UserAuthConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-25 19:35:19.234  INFO --- [              main] trationDelegate$BeanPostProcessorChecker : Bean 'authConfigValidator' of type [org.nzbhydra.config.validation.AuthConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-25 19:35:19.235  INFO --- [              main] trationDelegate$BeanPostProcessorChecker : Bean 'indexerConfigValidator' of type [org.nzbhydra.config.validation.IndexerConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-25 19:35:19.236  INFO --- [              main] trationDelegate$BeanPostProcessorChecker : Bean 'notificationConfigValidator' of type [org.nzbhydra.config.validation.NotificationConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-25 19:35:19.236  INFO --- [              main] trationDelegate$BeanPostProcessorChecker : Bean 'baseConfigValidator' of type [org.nzbhydra.config.validation.BaseConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-25 19:35:19.237  INFO --- [              main] org.nzbhydra.config.BaseConfigHandler    : Using data folder C:\Users\Lance\Desktop\nzbhydra2-5.1.8-windows\data
2023-04-25 19:35:19.259  INFO --- [              main] trationDelegate$BeanPostProcessorChecker : Bean 'baseConfigHandler' of type [org.nzbhydra.config.BaseConfigHandler] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-25 19:35:19.261  INFO --- [              main] trationDelegate$BeanPostProcessorChecker : Bean 'configProvider' of type [org.nzbhydra.config.ConfigProvider] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-25 19:35:19.262  INFO --- [              main] trationDelegate$BeanPostProcessorChecker : Bean 'hydraGlobalMethodSecurityConfiguration' of type [org.nzbhydra.auth.HydraGlobalMethodSecurityConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-25 19:35:19.263  INFO --- [              main] trationDelegate$BeanPostProcessorChecker : Bean 'methodSecurityMetadataSource' of type [org.springframework.security.access.method.DelegatingMethodSecurityMetadataSource] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-25 19:35:19.265  INFO --- [              main] trationDelegate$BeanPostProcessorChecker : Bean 'taskExecutor' of type [org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-25 19:35:19.429  INFO --- [              main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 5076 (http)
2023-04-25 19:35:19.440  INFO --- [              main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 307 ms
2023-04-25 19:35:19.568  INFO --- [              main] o.n.a.HydraAnonymousAuthenticationFilter : Granting basic user rights to anonymous users
2023-04-25 19:35:19.569  INFO --- [              main] o.n.a.HydraAnonymousAuthenticationFilter : Granting stats rights to anonymous users
**2023-04-25 19:35:19.569  INFO --- [              main] o.n.a.HydraAnonymousAuthenticationFilter : Granting admin rights to anonymous users
2023-04-25 19:35:19.585  INFO --- [              main] o.s.boot.web.servlet.RegistrationBean    : Filter characterEncodingFilter was not registered (possibly already registered?)
2023-04-25 19:35:19.670  WARN --- [              main] w.s.c.ServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'getDatabaseRecreationBean': Unable to open database file C:\Users\Lance\Desktop\nzbhydra2-5.1.8-windows\data\database\nzbhydra.mv.db
2023-04-25 19:35:19.673 ERROR --- [              main] o.s.boot.SpringApplication               : Application run failed**

The application works fine on my Desktop though.

theotherp commented 1 year ago

On your desktop machine make a backup of your data using nzbhydra (see the system section) and import it using nzbhydra on your laptop. Most likely you made a copy of the data whole the program was running when the database file locked.

On Wed, 26 Apr 2023, 04:47 kanishknishar, @.***> wrote:

I am trying to restore my NZBHydra 2 config files from my Desktop and so I backed it up and tried to restore it. However instead of reloading the app is stuck on trying to reload the wrapper. I closed the application from Task Manager and started it again. I can see the icon in my task bar but the application doesn't start up. Double clicking or restarting does nothing as well. I originally used to run NZBHydra 2 straight from the folder as I synced it via OneDrive but that caused the same issue as what I just described.

I can attach the log files but apparently they can contain sensitive info? I can't really anonymize my log as the app won't open but I suspect I can see the issue:

C:\Users\Lance\Desktop\nzbhydra2-5.1.8-windows) 2023-04-25 19:35:19.043 INFO --- [ main] org.nzbhydra.NzbHydra : The following 1 profile is active: "default" 2023-04-25 19:35:19.156 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'hydraTaskConfiguration' of type [org.nzbhydra.tasks.HydraTaskConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.225 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'baseConfig' of type [org.nzbhydra.config.BaseConfig] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.227 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'categoriesConfigValidator' of type [org.nzbhydra.config.validation.CategoriesConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.230 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'downloaderConfigValidator' of type [org.nzbhydra.config.validation.DownloaderConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.230 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'downloadingConfigValidator' of type [org.nzbhydra.config.validation.DownloadingConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.231 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'searchingConfigValidator' of type [org.nzbhydra.config.validation.SearchingConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.232 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'loggingConfigValidator' of type [org.nzbhydra.config.validation.LoggingConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.233 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'mainConfigValidator' of type [org.nzbhydra.config.validation.MainConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.234 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'userAuthConfigValidator' of type [org.nzbhydra.config.validation.UserAuthConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.234 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'authConfigValidator' of type [org.nzbhydra.config.validation.AuthConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.235 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'indexerConfigValidator' of type [org.nzbhydra.config.validation.IndexerConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.236 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'notificationConfigValidator' of type [org.nzbhydra.config.validation.NotificationConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.236 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'baseConfigValidator' of type [org.nzbhydra.config.validation.BaseConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.237 INFO --- [ main] org.nzbhydra.config.BaseConfigHandler : Using data folder C:\Users\Lance\Desktop\nzbhydra2-5.1.8-windows\data 2023-04-25 19:35:19.259 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'baseConfigHandler' of type [org.nzbhydra.config.BaseConfigHandler] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.261 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'configProvider' of type [org.nzbhydra.config.ConfigProvider] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.262 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'hydraGlobalMethodSecurityConfiguration' of type [org.nzbhydra.auth.HydraGlobalMethodSecurityConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.263 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'methodSecurityMetadataSource' of type [org.springframework.security.access.method.DelegatingMethodSecurityMetadataSource] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.265 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'taskExecutor' of type [org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.429 INFO --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 5076 (http) 2023-04-25 19:35:19.440 INFO --- [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 307 ms 2023-04-25 19:35:19.568 INFO --- [ main] o.n.a.HydraAnonymousAuthenticationFilter : Granting basic user rights to anonymous users 2023-04-25 19:35:19.569 INFO --- [ main] o.n.a.HydraAnonymousAuthenticationFilter : Granting stats rights to anonymous users 2023-04-25 19:35:19.569 INFO --- [ main] o.n.a.HydraAnonymousAuthenticationFilter : Granting admin rights to anonymous users 2023-04-25 19:35:19.585 INFO --- [ main] o.s.boot.web.servlet.RegistrationBean : Filter characterEncodingFilter was not registered (possibly already registered?) 2023-04-25 19:35:19.670 WARN --- [ main] w.s.c.ServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'getDatabaseRecreationBean': Unable to open database file C:\Users\Lance\Desktop\nzbhydra2-5.1.8-windows\data\database\nzbhydra.mv.db 2023-04-25 19:35:19.673 ERROR --- [ main] o.s.boot.SpringApplication : Application run failed

The application works fine on my Desktop though.

— Reply to this email directly, view it on GitHub https://github.com/theotherp/nzbhydra2/issues/859, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADNUA6OEPNNCABARO5KBEDLXDCEEXANCNFSM6AAAAAAXLZWQR4 . You are receiving this because you are subscribed to this thread.Message ID: @.***>

kanishknishar commented 1 year ago

I did a system backup and restore and the logs that I attached are from then. Before that, I had simply copy pasted the folder but that didn’t work so system backup and restore.

From: @.> Sent: 25 April 2023 21:33 To: @.> Cc: @.>; @.> Subject: Re: [theotherp/nzbhydra2] My installation only works on my desktop and not my laptop (Issue #859)

On your desktop machine make a backup of your data using nzbhydra (see the system section) and import it using nzbhydra on your laptop. Most likely you made a copy of the data whole the program was running when the database file locked.

On Wed, 26 Apr 2023, 04:47 kanishknishar, @.***> wrote:

I am trying to restore my NZBHydra 2 config files from my Desktop and so I backed it up and tried to restore it. However instead of reloading the app is stuck on trying to reload the wrapper. I closed the application from Task Manager and started it again. I can see the icon in my task bar but the application doesn't start up. Double clicking or restarting does nothing as well. I originally used to run NZBHydra 2 straight from the folder as I synced it via OneDrive but that caused the same issue as what I just described.

I can attach the log files but apparently they can contain sensitive info? I can't really anonymize my log as the app won't open but I suspect I can see the issue:

C:\Users\Lance\Desktop\nzbhydra2-5.1.8-windows) 2023-04-25 19:35:19.043 INFO --- [ main] org.nzbhydra.NzbHydra : The following 1 profile is active: "default" 2023-04-25 19:35:19.156 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'hydraTaskConfiguration' of type [org.nzbhydra.tasks.HydraTaskConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.225 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'baseConfig' of type [org.nzbhydra.config.BaseConfig] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.227 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'categoriesConfigValidator' of type [org.nzbhydra.config.validation.CategoriesConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.230 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'downloaderConfigValidator' of type [org.nzbhydra.config.validation.DownloaderConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.230 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'downloadingConfigValidator' of type [org.nzbhydra.config.validation.DownloadingConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.231 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'searchingConfigValidator' of type [org.nzbhydra.config.validation.SearchingConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.232 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'loggingConfigValidator' of type [org.nzbhydra.config.validation.LoggingConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.233 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'mainConfigValidator' of type [org.nzbhydra.config.validation.MainConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.234 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'userAuthConfigValidator' of type [org.nzbhydra.config.validation.UserAuthConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.234 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'authConfigValidator' of type [org.nzbhydra.config.validation.AuthConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.235 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'indexerConfigValidator' of type [org.nzbhydra.config.validation.IndexerConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.236 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'notificationConfigValidator' of type [org.nzbhydra.config.validation.NotificationConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.236 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'baseConfigValidator' of type [org.nzbhydra.config.validation.BaseConfigValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.237 INFO --- [ main] org.nzbhydra.config.BaseConfigHandler : Using data folder C:\Users\Lance\Desktop\nzbhydra2-5.1.8-windows\data 2023-04-25 19:35:19.259 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'baseConfigHandler' of type [org.nzbhydra.config.BaseConfigHandler] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.261 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'configProvider' of type [org.nzbhydra.config.ConfigProvider] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.262 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'hydraGlobalMethodSecurityConfiguration' of type [org.nzbhydra.auth.HydraGlobalMethodSecurityConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.263 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'methodSecurityMetadataSource' of type [org.springframework.security.access.method.DelegatingMethodSecurityMetadataSource] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.265 INFO --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'taskExecutor' of type [org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2023-04-25 19:35:19.429 INFO --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 5076 (http) 2023-04-25 19:35:19.440 INFO --- [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 307 ms 2023-04-25 19:35:19.568 INFO --- [ main] o.n.a.HydraAnonymousAuthenticationFilter : Granting basic user rights to anonymous users 2023-04-25 19:35:19.569 INFO --- [ main] o.n.a.HydraAnonymousAuthenticationFilter : Granting stats rights to anonymous users 2023-04-25 19:35:19.569 INFO --- [ main] o.n.a.HydraAnonymousAuthenticationFilter : Granting admin rights to anonymous users 2023-04-25 19:35:19.585 INFO --- [ main] o.s.boot.web.servlet.RegistrationBean : Filter characterEncodingFilter was not registered (possibly already registered?) 2023-04-25 19:35:19.670 WARN --- [ main] w.s.c.ServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'getDatabaseRecreationBean': Unable to open database file C:\Users\Lance\Desktop\nzbhydra2-5.1.8-windows\data\database\nzbhydra.mv.db 2023-04-25 19:35:19.673 ERROR --- [ main] o.s.boot.SpringApplication : Application run failed

The application works fine on my Desktop though.

— Reply to this email directly, view it on GitHub https://github.com/theotherp/nzbhydra2/issues/859, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADNUA6OEPNNCABARO5KBEDLXDCEEXANCNFSM6AAAAAAXLZWQR4 . You are receiving this because you are subscribed to this thread.Message ID: @.***>

— Reply to this email directly, view it on GitHubhttps://github.com/theotherp/nzbhydra2/issues/859#issuecomment-1522767060, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZSSVPORQJVYNGW6QYULV5LXDCQS3ANCNFSM6AAAAAAXLZWQR4. You are receiving this because you authored the thread.Message ID: @.***>

theotherp commented 1 year ago

Make sure the file C:\Users\Lance\Desktop\nzbhydra2-5.1.8-windows\data\database\nzbhydra.mv.db exsists and can be accessed by the process.

If you don't care about history or stats you can just delete it while hydra is down.