You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running installer.pl the user 'otobo' is created in the database and the credentials are stored in the module file Kernel/Config.pm . But when running installer.pl we get an error "Access denied". This seems to indicate that Kernel/Config.pm is not reloaded after it has been writter to disk. After some fiddling @svenoe found out that this effect goes away after S3 support has been removed from bin/psgi-bin/otobo.psgi . The assumption is that loading Kernel::Config in otobo.psgi effects that on old version of Kernel::Config stays around, which does not have the correct credentials.
The text was updated successfully, but these errors were encountered:
For reactivating S3 support in bin/psgi-bin/otobo.psgi it should suffice to registerter Kernel/Config.pm before $S3Active is checked. Calling Kernel::System::ModuleRefresh::update_cache() should guarantee that $ModuleRefreshMiddleware does indeed reload a changed config when the middleware runs for the first time.
When running installer.pl the user 'otobo' is created in the database and the credentials are stored in the module file Kernel/Config.pm . But when running installer.pl we get an error "Access denied". This seems to indicate that Kernel/Config.pm is not reloaded after it has been writter to disk. After some fiddling @svenoe found out that this effect goes away after S3 support has been removed from bin/psgi-bin/otobo.psgi . The assumption is that loading Kernel::Config in otobo.psgi effects that on old version of Kernel::Config stays around, which does not have the correct credentials.
The text was updated successfully, but these errors were encountered: