text:
Error during upgrade from 9.0.2 to 9.2.2

Summary
I'm having problems upgrading an existing website from version 09.00.02 to 09.02.02.
Would it be possible to point me in the right direction to solve this?
Extended description
I'm getting the error below, apparently while trying to update to 9.1.0, and the update hangs.
Error log (if necessary)
01/24/2019 11:09:51 [INFO] DotNetNuke.Services.Upgrade.Upgrade Start RemoveAdminPages://Admin//SearchAdmin
01/24/2019 11:09:53 [ERROR] DotNetNuke.Services.Upgrade.Upgrade Error: The ''' character, hexadecimal value 0x27, cannot be included in a name. Line 44, position 19.   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.ParseElement()
   at System.Xml.XmlTextReaderImpl.ParseElementContent()
   at System.Xml.XPath.XPathDocument.LoadFromReader(XmlReader reader, XmlSpace space)
   at System.Xml.XPath.XPathDocument..ctor(TextReader textReader)
   at DotNetNuke.Services.Installer.Installers.PackageInstaller..ctor(PackageInfo package)
   at DotNetNuke.Services.Installer.Installer..ctor(PackageInfo package, String physicalSitePath)
   at DotNetNuke.Services.Upgrade.Upgrade.UninstallPackage(String packageName, String packageType, Boolean deleteFiles, String version)
   at DotNetNuke.Services.Upgrade.Upgrade.UpgradeToVersion910()
   at DotNetNuke.Services.Upgrade.Upgrade.UpgradeApplication(String providerPath, Version version, Boolean writeFeedback)

Affected version

[ ] 9.3.0
[x] 9.2.2
[ ] 9.2.1
[ ] 9.2
[ ] 9.1.1
[ ] 9.1
[x] 9.0

I tried to delete the modules like @valadas suggested but changing the isAdmin value did not enable the uninstall button for the modules. After further investigation I did find the reason for the error however.
A lot of modules had a single quote in the Manifest column of the Packages table.
Example from DotNetNuke.MobileManagement:
<moduleControl>
  <controlKey>RedirectionSettings</controlKey>
  <controlSrc>DesktopModules/MobileManagement/RedirectionSettingsView.ascx</controlSrc>
  <supportsPopUps>True</supportsPopUps>
  <s'upportsPartialRendering>True</supportsPartialRendering>
  <controlTitle>Redirection Settings</controlTitle>
  <controlType>Edit</controlType>
  <iconFile />
  <helpUrl>http://www.dnnsoftware.com/help</helpUrl>
  <viewOrder>0</viewOrder>
</moduleControl>

After fixing all these records so they have valid xml in the Manifest column the update progressed further to 64% where it give's a tim-out error while executing the following SQL:
IF EXISTS (SELECT * FROM sysobjects WHERE id = object_id(N'dbo.PurgeEventLog') AND OBJECTPROPERTY(id, N'IsProcedure') = 1)  BEGIN     EXEC dbo.PurgeEventLog END

I looked into the PurgeEventLog procedure and it uses a cte which is just extremely slow.
Is there a way to manually purge the eventlog so this doesn't block the update?

Can anyone confirm if there is a way to manually purge the eventlog so II can update to 9.2.2?

I created a truncate script, which can be obtained from https://github.com/dnnwerk/truncateEventlog

Thanks for the truncate script, it worked perfectly. I just tried to upgrade again after running the script but still can't get the upgrade to complete.
It seems to be stuck at 63% with no exceptions in the log file or EventLog table.

03/28/2019 10:29:19 [INFO] DotNetNuke.Services.Upgrade.Upgrade Start InstallPackage:D:\Websites\PCA\Install\Module\Newtonsoft.Json_10.00.03_Install.zip
03/28/2019 10:35:02 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Uitvoeren van upgrade script09.01.00
03/28/2019 10:35:02 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpgradeVersion:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.01.00.SqlDataProvider
03/28/2019 10:35:02 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartExecuteScript:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.01.00.SqlDataProvider
03/28/2019 10:35:03 [INFO] DotNetNuke.Services.Upgrade.Upgrade EindeExecuteScript:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.01.00.SqlDataProvider
03/28/2019 10:35:03 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpgradeVersion:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.01.00.SqlDataProvider
03/28/2019 10:35:03 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Uitvoeren van upgrade script09.01.01
03/28/2019 10:35:03 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpgradeVersion:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.01.01.SqlDataProvider
03/28/2019 10:35:03 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartExecuteScript:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.01.01.SqlDataProvider
03/28/2019 10:35:04 [INFO] DotNetNuke.Services.Upgrade.Upgrade EindeExecuteScript:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.01.01.SqlDataProvider
03/28/2019 10:35:04 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpgradeVersion:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.01.01.SqlDataProvider
03/28/2019 10:35:04 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Uitvoeren van upgrade script09.02.00
03/28/2019 10:35:04 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpgradeVersion:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.02.00.SqlDataProvider
03/28/2019 10:35:04 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartExecuteScript:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.02.00.SqlDataProvider
03/28/2019 10:35:07 [INFO] DotNetNuke.Services.Upgrade.Upgrade EindeExecuteScript:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.02.00.SqlDataProvider
03/28/2019 10:35:07 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpgradeVersion:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.02.00.SqlDataProvider
03/28/2019 10:35:07 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Uitvoeren van upgrade script09.02.01
03/28/2019 10:35:07 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpgradeVersion:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.02.01.SqlDataProvider
03/28/2019 10:35:07 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartExecuteScript:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.02.01.SqlDataProvider
03/28/2019 10:35:08 [INFO] DotNetNuke.Services.Upgrade.Upgrade EindeExecuteScript:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.02.01.SqlDataProvider
03/28/2019 10:35:08 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpgradeVersion:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.02.01.SqlDataProvider
03/28/2019 10:35:08 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Uitvoeren van upgrade script09.02.02
03/28/2019 10:35:08 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpgradeVersion:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.02.02.SqlDataProvider
03/28/2019 10:35:08 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartExecuteScript:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.02.02.SqlDataProvider
03/28/2019 10:35:09 [INFO] DotNetNuke.Services.Upgrade.Upgrade EindeExecuteScript:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.02.02.SqlDataProvider
03/28/2019 10:35:09 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpgradeVersion:D:\Websites\PCA\Providers\DataProviders\SqlDataProvider\09.02.02.SqlDataProvider
03/28/2019 10:35:09 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Upgraden van Applicatie naar9.1.0
03/28/2019 10:35:09 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartApplicatie Upgrades: 9.1.0
03/28/2019 10:35:09 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveHostPage:Host Settings
03/28/2019 10:35:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveHostPage:Site Management
03/28/2019 10:35:11 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveHostPage:Schedule
03/28/2019 10:35:11 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveHostPage:Superuser Accounts
03/28/2019 10:35:12 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveHostPage:Extensions
03/28/2019 10:35:12 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveHostPage:Device Detection Management
03/28/2019 10:35:13 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveAdminPages://Admin//Extensions
03/28/2019 10:35:15 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveAdminPages://Admin//SiteSettings
03/28/2019 10:35:17 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveAdminPages://Admin//SecurityRoles
03/28/2019 10:35:18 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveAdminPages://Admin//Taxonomy
03/28/2019 10:35:20 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveAdminPages://Admin//SiteRedirectionManagement
03/28/2019 10:35:22 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveAdminPages://Admin//DevicePreviewManagement
03/28/2019 10:35:23 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveAdminPages://Admin//SearchAdmin
03/28/2019 10:35:28 [INFO] DotNetNuke.Services.Installer.XmlMerge StartRemoveNode:
03/28/2019 10:36:04 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Upgraden van Applicatie naar9.1.1
03/28/2019 10:36:04 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartApplicatie Upgrades: 9.1.1
03/28/2019 10:36:04 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Upgraden van Applicatie naar9.2.0
03/28/2019 10:36:04 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartApplicatie Upgrades: 9.2.0
03/28/2019 10:36:04 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveAdminPages://Admin//SearchEngineSiteMap
03/28/2019 10:36:05 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveAdminPages://Admin//Solutions
03/28/2019 10:36:05 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveAdminPages://Admin//BulkEmail
03/28/2019 10:36:05 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveHostPage:Marketplace
03/28/2019 10:36:05 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveHostPage:Module Definitions
03/28/2019 10:36:05 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartRemoveHostPage:Portals
03/28/2019 10:36:06 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartAddHostPage:Superuser Accounts
03/28/2019 10:36:06 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartAddPage:Superuser Accounts
03/28/2019 10:36:06 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartAddModuleToPage:15
03/28/2019 10:36:07 [INFO] DotNetNuke.Services.Upgrade.Upgrade EindeAddModuleToPage:15
03/28/2019 10:36:07 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Upgraden van Applicatie naar9.2.1
03/28/2019 10:36:07 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartApplicatie Upgrades: 9.2.1
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Upgraden van Applicatie naar9.2.2
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartApplicatie Upgrades: 9.2.2
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Bijwerken van Config voor9.1.0
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpdateConfig:09.01.00
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpdateConfig:9.1.0
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Installer.XmlMerge StartRemoveNode:
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade EindeUpdateConfig:9.1.0
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade EindeUpdateConfig:09.01.00
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Bijwerken van Config voor9.1.1
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpdateConfig:09.01.01
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpdateConfig:9.1.1
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Installer.XmlMerge StartUpdateNode: keyAttribute=name
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade EindeUpdateConfig:9.1.1
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade EindeUpdateConfig:09.01.01
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Bijwerken van Config voor9.2.0
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpdateConfig:09.02.00
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpdateConfig:9.2.0
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Installer.XmlMerge StartRemoveNode:
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade EindeUpdateConfig:9.2.0
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade EindeUpdateConfig:09.02.00
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Bijwerken van Config voor9.2.1
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpdateConfig:09.02.01
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpdateConfig:9.2.1
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade EindeUpdateConfig:9.2.1
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade EindeUpdateConfig:09.02.01
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Bijwerken van Config voor9.2.2
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpdateConfig:09.02.02
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartUpdateConfig:9.2.2
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade EindeUpdateConfig:9.2.2
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade EindeUpdateConfig:09.02.02
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Verwijderen van oudere bestanden voor9.1.0
03/28/2019 10:36:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartDeleteFiles:09.01.00
03/28/2019 10:36:11 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Verwijderen van oudere bestanden voor9.1.1
03/28/2019 10:36:11 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartDeleteFiles:09.01.01
03/28/2019 10:36:11 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Verwijderen van oudere bestanden voor9.2.0
03/28/2019 10:36:11 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartDeleteFiles:09.02.00
03/28/2019 10:36:11 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Verwijderen van oudere bestanden voor9.2.1
03/28/2019 10:36:11 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartDeleteFiles:09.02.01
03/28/2019 10:36:11 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Verwijderen van oudere bestanden voor9.2.2
03/28/2019 10:36:11 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartDeleteFiles:09.02.02
03/28/2019 10:36:11 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Upgraden van Applicatie
03/28/2019 10:36:12 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Module - DDRMenu_09.02.02_Install.zip
03/28/2019 10:36:12 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\DDRMenu_09.02.02_Install.zip
03/28/2019 10:36:13 [INFO] DotNetNuke.Services.Installer.XmlMerge StartUpdateNode: keyAttribute=name
03/28/2019 10:36:15 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Library - Dnn.EditBar.UI_01.06.01_Install.zip
03/28/2019 10:36:15 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.EditBar.UI_01.06.01_Install.zip
03/28/2019 10:36:15 [INFO] DotNetNuke.Services.Installer.XmlMerge StartRemoveNode:
03/28/2019 10:36:16 [INFO] DotNetNuke.Services.Installer.XmlMerge StartUpdateNode: keyAttribute=name
03/28/2019 10:36:16 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Library - Dnn.PersonaBar.UI_01.06.01_Install.zip
03/28/2019 10:36:16 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.UI_01.06.01_Install.zip
03/28/2019 10:36:17 [INFO] DotNetNuke.Services.Installer.XmlMerge StartRemoveNode:
03/28/2019 10:36:17 [INFO] DotNetNuke.Services.Installer.XmlMerge StartAddNode:
03/28/2019 10:36:17 [INFO] DotNetNuke.Services.Installer.XmlMerge StartRemoveNode:
03/28/2019 10:36:17 [INFO] DotNetNuke.Services.Installer.XmlMerge StartAddNode:
03/28/2019 10:36:17 [INFO] DotNetNuke.Services.Installer.XmlMerge StartRemoveNode:
03/28/2019 10:36:17 [INFO] DotNetNuke.Services.Installer.XmlMerge StartAddNode:
03/28/2019 10:36:17 [INFO] DotNetNuke.Services.Installer.XmlMerge StartRemoveNode:
03/28/2019 10:36:17 [INFO] DotNetNuke.Services.Installer.XmlMerge StartAddNode:
03/28/2019 10:36:17 [INFO] DotNetNuke.Services.Installer.XmlMerge StartRemoveNode:
03/28/2019 10:36:17 [INFO] DotNetNuke.Services.Installer.XmlMerge StartUpdateNode: keyAttribute=name
03/28/2019 10:36:19 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Library - DNNCE_01_Web.Deprecated_09.02.02_Install.zip
03/28/2019 10:36:19 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\DNNCE_01_Web.Deprecated_09.02.02_Install.zip
03/28/2019 10:36:20 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Connector - DNNCE_AzureConnector_09.02.02_Install.zip
03/28/2019 10:36:20 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\DNNCE_AzureConnector_09.02.02_Install.zip
03/28/2019 10:36:21 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Module - DNNCE_Console_09.02.02_Install.zip
03/28/2019 10:36:21 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\DNNCE_Console_09.02.02_Install.zip
03/28/2019 10:36:24 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Module - DNNCE_CoreMessaging_09.02.02_Install.zip
03/28/2019 10:36:24 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\DNNCE_CoreMessaging_09.02.02_Install.zip
03/28/2019 10:36:26 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Module - DNNCE_DigitalAssetsManagement_09.02.02_Install.zip
03/28/2019 10:36:26 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\DNNCE_DigitalAssetsManagement_09.02.02_Install.zip
03/28/2019 10:36:29 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Module - DNNCE_HtmlEditorManager_09.02.02_Install.zip
03/28/2019 10:36:29 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\DNNCE_HtmlEditorManager_09.02.02_Install.zip
03/28/2019 10:36:31 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Module - DNNCE_HTML_09.02.02_Install.zip
03/28/2019 10:36:31 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\DNNCE_HTML_09.02.02_Install.zip
03/28/2019 10:36:34 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Module - DNNCE_Journal_09.02.02_Install.zip
03/28/2019 10:36:34 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\DNNCE_Journal_09.02.02_Install.zip
03/28/2019 10:36:39 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Module - DNNCE_MemberDirectory_09.02.02_Install.zip
03/28/2019 10:36:39 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\DNNCE_MemberDirectory_09.02.02_Install.zip
03/28/2019 10:36:42 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Module - DNNCE_ModuleCreator_09.02.02_Install.zip
03/28/2019 10:36:42 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\DNNCE_ModuleCreator_09.02.02_Install.zip
03/28/2019 10:36:45 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Module - DNNCE_RazorHost_09.02.02_Install.zip
03/28/2019 10:36:45 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\DNNCE_RazorHost_09.02.02_Install.zip
03/28/2019 10:36:48 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Library - DNNCE_SiteExportImport_09.02.02_Install.zip
03/28/2019 10:36:48 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\DNNCE_SiteExportImport_09.02.02_Install.zip
03/28/2019 10:36:54 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Module - DNNCE_SocialGroups_09.02.02_Install.zip
03/28/2019 10:36:54 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\DNNCE_SocialGroups_09.02.02_Install.zip
03/28/2019 10:36:56 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Library - DNNCE_Website.Deprecated_09.02.02_Install.zip
03/28/2019 10:36:56 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\DNNCE_Website.Deprecated_09.02.02_Install.zip
03/28/2019 10:36:57 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren JavaScript_Library - jQuery.zip
03/28/2019 10:36:57 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\JavaScriptLibrary\jQuery.zip
03/28/2019 10:36:59 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Library - Telerik_09.02.01_Install.zip
03/28/2019 10:36:59 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Telerik_09.02.01_Install.zip
03/28/2019 10:37:01 [INFO] DotNetNuke.Services.Installer.XmlMerge StartUpdateNode: keyAttribute=name
03/28/2019 10:37:01 [INFO] DotNetNuke.Services.Installer.XmlMerge StartUpdateNode: keyAttribute=name
03/28/2019 10:37:01 [INFO] DotNetNuke.Services.Installer.XmlMerge StartUpdateNode: keyAttribute=name
03/28/2019 10:37:01 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren JavaScript_Library - Selectize.zip
03/28/2019 10:37:01 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\JavaScriptLibrary\Selectize.zip
03/28/2019 10:37:02 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Provider - AspNetClientCapabilityProvider_09.02.02_Install.zip
03/28/2019 10:37:02 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Provider\AspNetClientCapabilityProvider_09.02.02_Install.zip
03/28/2019 10:37:03 [INFO] DotNetNuke.Services.Installer.XmlMerge StartUpdateNode: keyAttribute=name
03/28/2019 10:37:03 [INFO] DotNetNuke.Services.Installer.XmlMerge StartUpdateNode: keyAttribute=name
03/28/2019 10:37:04 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Provider - DNNCE_FolderProviders_09.02.02_Install.zip
03/28/2019 10:37:04 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Provider\DNNCE_FolderProviders_09.02.02_Install.zip
03/28/2019 10:37:04 [INFO] DotNetNuke.Services.Installer.XmlMerge StartUpdateNode: keyAttribute=name
03/28/2019 10:37:05 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren Provider - DNNConnect.CKEditorProvider_01.00.04_Install.zip
03/28/2019 10:37:05 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Provider\DNNConnect.CKEditorProvider_01.00.04_Install.zip
03/28/2019 10:37:08 [INFO] DotNetNuke.Services.Installer.XmlMerge StartUpdateNode: keyAttribute=name
03/28/2019 10:37:10 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.AdminLogs_01.06.01_Install.zip
03/28/2019 10:37:10 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.AdminLogs_01.06.01_Install.zip
03/28/2019 10:37:13 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.ConfigConsole_01.06.01_Install.zip
03/28/2019 10:37:13 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.ConfigConsole_01.06.01_Install.zip
03/28/2019 10:37:17 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.Connectors_01.06.01_Install.zip
03/28/2019 10:37:17 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.Connectors_01.06.01_Install.zip
03/28/2019 10:37:19 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.CssEditor_01.06.01_Install.zip
03/28/2019 10:37:19 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.CssEditor_01.06.01_Install.zip
03/28/2019 10:37:21 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.Extensions_01.06.01_Install.zip
03/28/2019 10:37:21 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.Extensions_01.06.01_Install.zip
03/28/2019 10:37:22 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.Licensing_01.06.01_Install.zip
03/28/2019 10:37:22 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.Licensing_01.06.01_Install.zip
03/28/2019 10:37:23 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.Prompt_01.06.01_Install.zip
03/28/2019 10:37:23 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.Prompt_01.06.01_Install.zip
03/28/2019 10:37:24 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.Recyclebin_01.06.01_Install.zip
03/28/2019 10:37:24 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.Recyclebin_01.06.01_Install.zip
03/28/2019 10:37:28 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.Roles_01.06.01_Install.zip
03/28/2019 10:37:28 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.Roles_01.06.01_Install.zip
03/28/2019 10:37:30 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.Security_01.06.01_Install.zip
03/28/2019 10:37:30 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.Security_01.06.01_Install.zip
03/28/2019 10:37:31 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.Seo_01.06.01_Install.zip
03/28/2019 10:37:31 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.Seo_01.06.01_Install.zip
03/28/2019 10:37:33 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.Servers_01.06.01_Install.zip
03/28/2019 10:37:33 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.Servers_01.06.01_Install.zip
03/28/2019 10:37:35 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.SiteSettings_01.06.01_Install.zip
03/28/2019 10:37:35 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.SiteSettings_01.06.01_Install.zip
03/28/2019 10:37:36 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.Sites_01.06.01_Install.zip
03/28/2019 10:37:36 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.Sites_01.06.01_Install.zip
03/28/2019 10:37:37 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.SqlConsole_01.06.01_Install.zip
03/28/2019 10:37:37 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.SqlConsole_01.06.01_Install.zip
03/28/2019 10:37:38 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.TaskScheduler_01.06.01_Install.zip
03/28/2019 10:37:38 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.TaskScheduler_01.06.01_Install.zip
03/28/2019 10:37:39 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.Themes_01.06.01_Install.zip
03/28/2019 10:37:39 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.Themes_01.06.01_Install.zip
03/28/2019 10:37:41 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.Users_01.06.01_Install.zip
03/28/2019 10:37:41 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.Users_01.06.01_Install.zip
03/28/2019 10:37:43 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.Vocabularies_01.06.01_Install.zip
03/28/2019 10:37:43 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.Vocabularies_01.06.01_Install.zip
03/28/2019 10:37:44 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren JavaScript_Library - jQueryMigrate.zip
03/28/2019 10:37:44 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\JavaScriptLibrary\jQueryMigrate.zip
03/28/2019 10:37:45 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren JavaScript_Library - jQueryUI.zip
03/28/2019 10:37:45 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\JavaScriptLibrary\jQueryUI.zip
03/28/2019 10:37:46 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.Pages_01.06.01_Install.zip
03/28/2019 10:37:46 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.Pages_01.06.01_Install.zip
03/28/2019 10:37:48 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installeren PersonaBar - Dnn.PersonaBar.SiteImportExport_01.06.01_Install.zip
03/28/2019 10:37:48 [INFO] DotNetNuke.Services.Upgrade.Upgrade StartInstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.SiteImportExport_01.06.01_Install.zip

Is there anywhere else I can look for a cause of the upgrade freezing?

I did find the following errors in the normal log, the previous one was the installer log:
2019-03-28 16:58:34,630 [LCCTT2][Thread:1][ERROR] DotNetNuke.ComponentModel.ProviderInstaller - System.Configuration.ConfigurationErrorsException: Could not load provider DotNetNuke.NavigationControl.DNNMenuNavigationProvider, DotNetNuke.DNNMenuNavigationProvider
2019-03-28 16:58:34,651 [LCCTT2][Thread:1][ERROR] DotNetNuke.ComponentModel.ProviderInstaller - System.Configuration.ConfigurationErrorsException: Could not load provider DotNetNuke.NavigationControl.DNNTreeNavigationProvider, DotNetNuke.DNNTreeNavigationProvider
2019-03-28 16:58:34,653 [LCCTT2][Thread:1][ERROR] DotNetNuke.ComponentModel.ProviderInstaller - System.Configuration.ConfigurationErrorsException: Could not load provider DotNetNuke.NavigationControl.ASP2MenuNavigationProvider, DotNetNuke.ASP2MenuNavigationProvider
2019-03-28 16:58:34,656 [LCCTT2][Thread:1][ERROR] DotNetNuke.ComponentModel.ProviderInstaller - System.Configuration.ConfigurationErrorsException: Could not load provider DotNetNuke.NavigationControl.SolpartMenuNavigationProvider, DotNetNuke.SolpartMenuNavigationProvider
2019-03-28 16:58:34,657 [LCCTT2][Thread:1][ERROR] DotNetNuke.ComponentModel.ProviderInstaller - System.Configuration.ConfigurationErrorsException: Could not load provider DotNetNuke.NavigationControl.DNNDropDownNavigationProvider, DotNetNuke.DNNDropDownNavigationProvider

Anyone has any hints on how I could solve this?
Thanks

Another thing that comes to mind, but it is another shot in the dark. Can you empty the contents of the following folders before applying the update files.
/Install/Module
/Install/Provider
/Install/AuthSystem

Please try the upgrade again, we added some additional logging in v9.3.1 and v9.3.2 which will help identify which package is preventing the upgrade from finishing successfully. It won’t fix the issue, it’ll only log more details when it fails where it was before.

I first cleared the 3 Install subfolders and updated all modules and themes to the latest versions before starting the update to v9.3.1. I did it two times to be sure I didn't miss anything. I've attached both installer logs as they stop on a different step but can't see anything obvious.
InstallerLog20190418 - attempt 1.resources.txt
InstallerLog20190418 - attempt 2.resources.txt
In the normal log I also noticed the following error right at the start of the upgrade, other than that there was nothing in the normal log:
2019-04-18 15:28:24,947 [LCCTT2][Thread:11][ERROR] DotNetNuke.Services.Exceptions.Exceptions - System.IndexOutOfRangeException: TermsTabId
   at System.Data.ProviderBase.FieldNameLookup.GetOrdinal(String fieldName)
   at System.Data.SqlClient.SqlDataReader.GetOrdinal(String name)
   at System.Data.SqlClient.SqlDataReader.get_Item(String name)
   at DotNetNuke.Entities.Portals.PortalInfo.Fill(IDataReader dr)
   at DotNetNuke.Common.Utilities.CBO.FillObjectFromReader(Object objObject, IDataReader dr)

Did you give a try to 9.3.2 also, there where some fixes regarding installation on some environments.
9.3.2 is a RC (Release Candidate), so not for production, backup first, it can change before the official release, etc.
But it is a bug fix release and should be out of RC soon unless we spot important issues.

Hi
I tried again with the latest release but didn't get any further.
Attached is the installer log but I don't see any errors.
InstallerLog20190510.txt
In the normal log I get the same error right at the start of the upgrade:
2019-05-10 16:54:33,830 [LCCTT2][Thread:88][ERROR] DotNetNuke.Services.Exceptions.Exceptions - System.IndexOutOfRangeException: TermsTabId
   at System.Data.ProviderBase.FieldNameLookup.GetOrdinal(String fieldName)
   at System.Data.SqlClient.SqlDataReader.GetOrdinal(String name)
   at System.Data.SqlClient.SqlDataReader.get_Item(String name)
   at DotNetNuke.Entities.Portals.PortalInfo.Fill(IDataReader dr)
   at DotNetNuke.Common.Utilities.CBO.FillObjectFromReader(Object objObject, IDataReader dr)

Is there any extra logging I can turn on?

Ha, the TermsTabId thing was a but in the RC, can you try again the official 9.3.2 release now that it is out of RC stage @Ceten

Ha, the TermsTabId thing was a but in the RC, can you try again the official 9.3.2 release now that it is out of RC stage @Ceten

Sorry, I was on holiday leave so couldn't get back to this earlier. I can try again on Friday but I'm pretty sure I used the official release as that was released on May 1? The only file I can still find in my download folder is DNN_Platform_9.3.2.24_Upgrade.zip.

@valadas I tried again but got the exact same error in the log at the start of the upgrade:
2019-09-06 14:29:33,066 [LCCTT2][Thread:36][ERROR] DotNetNuke.Services.Exceptions.Exceptions - System.IndexOutOfRangeException: TermsTabId
   at System.Data.ProviderBase.FieldNameLookup.GetOrdinal(String fieldName)
   at System.Data.SqlClient.SqlDataReader.GetOrdinal(String name)
   at System.Data.SqlClient.SqlDataReader.get_Item(String name)
   at DotNetNuke.Entities.Portals.PortalInfo.Fill(IDataReader dr)
   at DotNetNuke.Common.Utilities.CBO.FillObjectFromReader(Object objObject, IDataReader dr)

The last lines in the installerlog were again about intalling the Personabar 2.0.1:
09/06/2019 12:50:12 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Installing PersonaBar - Dnn.PersonaBar.SiteImportExport_02.00.01_Install.zip
09/06/2019 12:50:12 [INFO] DotNetNuke.Services.Upgrade.Upgrade Start InstallPackage:D:\Websites\PCA\Install\Module\Dnn.PersonaBar.SiteImportExport_02.00.01_Install.zip

Well, I am a bit out of ideas, that TermsTabId bug was resolved before 9.3.2, soooo what else....
You appear to have a couple of different issues here, when following suggestions above, did you restore the backup before each trial? Both the database and files?

Yes, I always started by taking a backup of the live website and database and ran the update on a copy on my laptop.

@Ceten we are now at 9.4.1, is this still an issue ?

@valadas I'm afraid it still doesn't work with 9.4.1.
Attached the complete log files.
2019.10.03.log.resources.txt
InstallerLog20191003.resources.txt

Hmm, running out of ideas. What about looking for a stray single quote in the database tables relating to modules and pages ?

And what tables would that be? I've already corrected errors in the Manifest column of the Packages table which resulted in incorrect xml.

Well, there are many tables all related to each other, as a quick list of things I would check:
Modules
DesktopModules
Packages
TabModules
Also, are you are if some database tools might have been used before for performance tuning or maybe TurboScripts or some such?

in the logs, I see a couple of issues:

Stored Procedure dbo.AuthCookies_Find is missing
the eventLog table seems to be having too many rows to clean it (you may use my script from  https://github.com/dnnwerk/truncateEventlog/releases)
There is a problem accessing a RadEditor file - you should switch to CKEditor prior to the upgrade.
the other issues in the first script might be follow ups.
the installer log doesn't contain any uprade errors

to check, whether TurboScripts are installed, run the following statement in the SQL Console:
SELECT * FROM HostSettings WHERE SettingName Like N'Turbo%'

@Ceten in the spirit of cleaning up the backlog and since this is more specific to your install than an actual issue with Dnn, I am closing this issue. This does not mean you cannot keep discussing here, everybody on this thread would still be notified of future comments.

I seem to be having a similar issue, https://dnncommunity.org/forums/aft/495
Working fine with 9.1.1 but with update to 9.3.2 I receive this TermsTabID error &
DotNetNuke.Entities.Portals.PortalInfo.get_HomeDirectoryMapPath()
DotNetNuke.HttpModules.UrlRewrite.BasicUrlRewriter.RewriteUrl,

@Gilderroot
Did you unblock downloaded upgrade package (first tab of file properties near the bottom), prior to unzipping the files contained and overwriting existing files in the IIS website folder?

@sleupold
No i didn't, being as when the ZIP file is in my server that option doesn't exist.
I unblocked it on my local Host and copied the upgrade files over top still receiving the same issues.

I am getting the same issue in log after upgrade from 9.2.1 to 9.3.8. How to resolve this issue in the same version 9.3.8?
at DotNetNuke.Professional.LicenseActivation.Licensing.License.MagicKey(XmlDocument xmlDoc)
2020-10-05 09:51:15.269-04:00 [BTIW61][D:3][T:77][ERROR] DotNetNuke.Services.Exceptions.Exceptions - System.IndexOutOfRangeException: TermsTabId
at System.Data.ProviderBase.FieldNameLookup.GetOrdinal(String fieldName)
at System.Data.SqlClient.SqlDataReader.GetOrdinal(String name)
at System.Data.SqlClient.SqlDataReader.get_Item(String name)
at DotNetNuke.Entities.Portals.PortalInfo.Fill(IDataReader dr)
at DotNetNuke.Common.Utilities.CBO.FillObjectFromReader(Object objObject, IDataReader dr)
2020-10-05 09:51:16.248-04:00 [BTIW61][D:3][T:77][ERROR] DotNetNuke.Services.Exceptions.Exceptions - System.IndexOutOfRangeException: TermsTabId
at System.Data.ProviderBase.FieldNameLookup.GetOrdinal(String fieldName)
at System.Data.SqlClient.SqlDataReader.GetOrdinal(String name)
at System.Data.SqlClient.SqlDataReader.get_Item(String name)
at DotNetNuke.Entities.Portals.PortalInfo.Fill(IDataReader dr)
at DotNetNuke.Common.Utilities.CBO.FillObjectFromReader(Object objObject, IDataReader dr)
2020-10-05 09:51:16.381-04:00 [BTIW61][D:3][T:77][ERROR] DotNetNuke.Services.Exceptions.Exceptions - System.NullReferenceException: Object reference not set to an instance of an object.
at DotNetNuke.Entities.Portals.PortalInfo.get_HomeDirectoryMapPath()
at DotNetNuke.Entities.Urls.CacheController.FindFriendlyUrlParmsConfigFilePath(Int32 portalId, Boolean& portalSpecificFound)
at DotNetNuke.Entities.Urls.CacheController.GetParameterRedirects(FriendlyUrlSettings settings, Int32 portalId, List`1& messages)
2020-10-05 09:51:16.480-04:00 [BTIW61][D:3][T:77][ERROR] DotNetNuke.Services.Exceptions.Exceptions - System.IndexOutOfRangeException: IsSystem
at System.Data.ProviderBase.FieldNameLookup.GetOrdinal(String fieldName)
at System.Data.SqlClient.SqlDataReader.GetOrdinal(String name)
at System.Data.SqlClient.SqlDataReader.get_Item(String name)
at DotNetNuke.Entities.Tabs.TabInfo.Fill(IDataReader dr)
at DotNetNuke.Common.Utilities.CBO.FillObjectFromReader(Object objObject, IDataReader dr)
2020-10-05 09:51:16.599-04:00 [BTIW61][D:3][T:77][FATAL] DotNetNuke.Web.Common.Internal.DotNetNukeHttpApplication - System.NullReferenceException: Object reference not set to an instance of an object.
at DotNetNuke.Entities.Portals.PortalInfo.get_HomeDirectoryMapPath()
at DotNetNuke.Entities.Portals.PortalSettingsController.LoadPortal(PortalInfo portal, PortalSettings portalSettings)
at DotNetNuke.Entities.Portals.PortalSettings.BuildPortalSettings(Int32 tabId, PortalInfo portal)
at DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabId, PortalAliasInfo portalAliasInfo)
at DotNetNuke.Entities.Urls.AdvancedUrlRewriter.Handle404OrException(FriendlyUrlSettings settings, HttpContext context, Exception ex, UrlAction result, Boolean transfer, Boolean showDebug)
at DotNetNuke.Entities.Urls.AdvancedUrlRewriter.ProcessRequest(HttpContext context, Uri requestUri, Boolean useFriendlyUrls, UrlAction result, FriendlyUrlSettings settings, Boolean allowSettingsChange, Guid parentTraceId)
at DotNetNuke.Entities.Urls.AdvancedUrlRewriter.RewriteUrl(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
2020-10-05 09:52:04.545-04:00 [BTIW61][D:3][T:77][ERROR] DotNetNuke.Services.Exceptions.Exceptions - System.IndexOutOfRangeException: IsSystem
at System.Data.ProviderBase.FieldNameLookup.GetOrdinal(String fieldName)
at System.Data.SqlClient.SqlDataReader.GetOrdinal(String name)
at System.Data.SqlClient.SqlDataReader.get_Item(String name)
at DotNetNuke.Entities.Tabs.TabInfo.Fill(IDataReader dr)
at DotNetNuke.Common.Utilities.CBO.FillObjectFromReader(Object objObject, IDataReader dr)
2020-10-05 09:52:04.554-04:00 [BTIW61][D:3][T:77][ERROR] DotNetNuke.Services.Exceptions.Exceptions - System.IndexOutOfRangeException: IsSystem
at System.Data.ProviderBase.FieldNameLookup.GetOrdinal(String fieldName)
at System.Data.SqlClient.SqlDataReader.GetOrdinal(String name)
at System.Data.SqlClient.SqlDataReader.get_Item(String name)
at DotNetNuke.Entities.Tabs.TabInfo.Fill(IDataReader dr)
at DotNetNuke.Common.Utilities.CBO.FillObjectFromReader(Object objObject, IDataReader dr)
2020-10-05 09:52:04.561-04:00 [BTIW61][D:3][T:77][ERROR] DotNetNuke.Services.Exceptions.Exceptions - System.IndexOutOfRangeException: IsSystem
at System.Data.ProviderBase.FieldNameLookup.GetOrdinal(String fieldName)
at System.Data.SqlClient.SqlDataReader.GetOrdinal(String name)
at System.Data.SqlClient.SqlDataReader.get_Item(String name)
at DotNetNuke.Entities.Tabs.TabInfo.Fill(IDataReader dr)

@BiswaRath
are you running DNN Platform or Evoq?

Evoq 9.3.8

I did not see any issue during upgradation. It can be seen from below steps. But still I can see the issues.
Upgrading DNN
Current Assembly Version: 09.03.08
Current Database Version: 09.03.01
Upgrade Status Report
00:00:00.050 - Upgrading to Version: 09.03.02
00:00:00.090 -   Executing Script:09.03.02.SqlDataProvider Success
00:00:00.822 -   Application Upgrades : 09.03.02 Success
00:00:00.827 -   Cleaning Up Files: 09.03.02 Success
00:00:00.831 -   Updating Config Files: 09.03.02 Success
00:00:00.841 - Performing General Upgrades
00:00:02.074 -   Installing Package File DDRMenu_09.03.02_Install:  Success
00:00:03.644 -   Installing Package File Dnn.PersonaBar.UI_02.00.01_Install:  Success
00:00:05.316 -   Installing Package File DNNCE_AzureConnector_09.03.02_Install:  Success
00:00:05.653 -   Installing Package File DNNCE_Console_09.03.02_Install:  Success
00:00:06.054 -   Installing Package File DNNCE_CoreMessaging_09.03.02_Install:  Success
00:00:06.903 -   Installing Package File DNNCE_HtmlEditorManager_09.03.02_Install:  Success
00:00:07.291 -   Installing Package File DNNCE_Journal_09.03.02_Install:  Success
00:00:07.813 -   Installing Package File DNNCE_MemberDirectory_09.03.02_Install:  Success
00:00:08.378 -   Installing Package File DNNCE_ModuleCreator_09.03.02_Install:  Success
00:00:09.391 -   Installing Package File DNNCE_RazorHost_09.03.02_Install:  Success
00:00:10.249 -   Installing Package File DNNCE_SiteExportImport_09.03.02_Install:  Success
00:00:10.973 -   Installing Package File DNNCE_SocialGroups_09.03.02_Install:  Success
00:00:11.640 -   Installing Package File DNNCE_Website.Deprecated_09.03.02_Install:  Success
00:00:11.859 -   Installing Package File DNNEvoqLibrary_09.03.08_Install:  Success
00:00:13.182 -   Installing Package File DNNPro_09.03.08_Install:  Success
00:00:13.992 -   Installing Package File DNNPro_AmazonS3Connector_09.03.08_Install:  Success
00:00:14.297 -   Installing Package File DNNPro_EvoqContentLibrary_09.03.08_Install:  Success
00:00:15.608 -   Installing Package File DNNPro_SearchCrawler_09.03.08_Install:  Success
00:00:16.371 -   Installing Package File DNNPro_UNCConnector_09.03.08_Install:  Success
00:00:16.641 -   Installing Package File Social_01_Mechanics_09.03.08_Install:  Success
00:00:17.213 -   Installing Package File D3:  Success
00:00:17.489 -   Installing Package File AspNetClientCapabilityProvider_09.03.02_Install:  Success
00:00:17.814 -   Installing Package File DNNCE_FolderProviders_09.03.02_Install:  Success
00:00:18.259 -   Installing Package File Dnn.PersonaBar.AdminLogs_02.00.01_Install:  Success
00:00:19.162 -   Installing Package File Dnn.PersonaBar.ConfigConsole_02.00.01_Install:  Success
00:00:19.426 -   Installing Package File Dnn.PersonaBar.Connectors_02.00.01_Install:  Success
00:00:19.815 -   Installing Package File Dnn.PersonaBar.CssEditor_02.00.01_Install:  Success
00:00:20.121 -   Installing Package File Dnn.PersonaBar.Extensions_02.00.01_Install:  Success
00:00:20.519 -   Installing Package File Dnn.PersonaBar.Licensing_02.00.01_Install:  Success
00:00:20.803 -   Installing Package File Dnn.PersonaBar.Prompt_02.00.01_Install:  Success
00:00:21.171 -   Installing Package File Dnn.PersonaBar.Recyclebin_02.00.01_Install:  Success
00:00:21.546 -   Installing Package File Dnn.PersonaBar.Roles_02.00.01_Install:  Success
00:00:21.937 -   Installing Package File Dnn.PersonaBar.Security_02.00.01_Install:  Success
00:00:22.327 -   Installing Package File Dnn.PersonaBar.Seo_02.00.01_Install:  Success
00:00:22.646 -   Installing Package File Dnn.PersonaBar.Servers_02.00.01_Install:  Success
00:00:23.082 -   Installing Package File Dnn.PersonaBar.Sites_02.00.01_Install:  Success
00:00:23.454 -   Installing Package File Dnn.PersonaBar.SiteSettings_02.00.01_Install:  Success
00:00:23.827 -   Installing Package File Dnn.PersonaBar.SqlConsole_02.00.01_Install:  Success
00:00:24.193 -   Installing Package File Dnn.PersonaBar.TaskScheduler_02.00.01_Install:  Success
00:00:24.542 -   Installing Package File Dnn.PersonaBar.Themes_02.00.01_Install:  Success
00:00:24.917 -   Installing Package File Dnn.PersonaBar.Users_02.00.01_Install:  Success
00:00:25.400 -   Installing Package File Dnn.PersonaBar.Vocabularies_02.00.01_Install:  Success
00:00:25.725 -   Installing Package File DNNPro_ContentLayout_09.03.08_Install:  Success
00:00:26.245 -   Installing Package File DNNPro_EvoqPortableServiceLibrary_09.03.08_Install:  Success
00:00:26.448 -   Installing Package File DNNPro_GoogleAnalyticsConnector_09.03.08_Install:  Success
00:00:26.939 -   Installing Package File DNNPro_HTMLPro_09.03.08_Install:  Success
00:00:27.979 -   Installing Package File DNNPro_KayakoMessengerConnector_09.03.08_Install:  Success
00:00:28.349 -   Installing Package File Evoq.PersonaBar.AccountSettings_01.07.05_Install:  Success
00:00:28.656 -   Installing Package File Evoq.PersonaBar.Assets_01.07.05_Install:  Success
00:00:29.370 -   Installing Package File Evoq.PersonaBar.Servers_01.07.05_Install:  Success
00:00:29.701 -   Installing Package File Evoq.PersonaBar.UI_01.07.05_Install:  Success
00:00:30.785 -   Installing Package File Evoq.PersonaBar.Users_01.07.05_Install:  Success
00:00:31.173 -   Installing Package File Evoq.PersonaBar.Workflow_01.07.05_Install:  Success
00:00:31.506 -   Installing Package File DNNPro_FolderProviders_09.03.08_Install:  Success
00:00:32.004 -   Installing Package File Dnn.PersonaBar.Pages_02.00.01_Install:  Success
00:00:32.577 -   Installing Package File Dnn.PersonaBar.SiteImportExport_02.00.01_Install:  Success
00:00:32.938 -   Installing Package File Evoq.PersonaBar.Licensing_01.07.05_Install:  Success
00:00:33.243 -   Installing Package File Evoq.PersonaBar.Pages_01.07.05_Install:  Success
00:00:33.914 -   Installing Package File Evoq.PersonaBar.Recyclebin_01.07.05_Install:  Success
00:00:34.313 -   Installing Package File Evoq.PersonaBar.Sites_01.07.05_Install:  Success
00:00:34.695 -   Installing Package File Evoq.PersonaBar.SiteSettings_01.07.05_Install:  Success
00:00:35.053 -   Installing Package File Evoq.PersonaBar.Templates_01.07.05_Install:  Success
Upgrade Complete
Click Here To Access Your Site

authors: BiswaRath Ceten Gilderroot ohine sleupold valadas


text:
Explain how to use Dask to parallelize grid search across GPUs

Based on #237
Work in progress, but please give me feedback.
Also explains how to use Palladium to run grid search in parallel.  This feature currently requires https://github.com/ottogroup/palladium/pull/87

addresses #95

Updated to use joblib's parallel_backend instead of dask-searchcv.

Thanks, great work.

source: gharchive/pull-request

authors: benjamin-work dnouri

repo: dnouri/skorch

license_type: permissive

license_source: github-api


text:
Memory Leakage in case of many switches between ChromeOS and Ubuntu

First of all thanks for this great project, I highly appreciate your work!
For some jobs I need to switch back and forth between ChromeOS and Ubuntu. While this works very smoothly in the beginning, after a certain amount of times I can feel how the performance lowers. At some point it is so slow that I restart my chromebook and then everything is fine again. The performance loss is both when running Ubuntu and ChromeOS. While in the beginning just software is executed slower, in the end I can hardly move the mouse and JavaScript applications refuse to respond.
I guess for this issue you might need some log files, tell me which ones and I will attach them here.

I would first try to see with top what is using your resources when it is running slow.

Ok, I just had one such a case from which it could recover. That is by
the way not always the case, sometimes it seems to get stuck. After I
waited for 2min I normally assume it won't come back.
THis time, next to the normally running software it showed kswapd0. It
went up to 70%. Well, the only difficulty of course is that when it runs
low on ressources it is also difficult to run all those programs.
Anyhow, after I observed the 70%, some seconds later it could recover
and I could show this:
top - 09:58:51 up 20:07,  0 users,  load average: 3.79, 2.82, 2.11
Tasks: 245 total,   2 running, 242 sleeping,   0 stopped,   1 zombie
Cpu(s): 10.5%us,  9.1%sy,  0.0%ni, 73.8%id,  6.4%wa,  0.0%hi,  0.2%si,  0.0%
Mem:   1966832k total,  1931180k used,    35652k free,      564k buffers
Swap:  2881100k total,  2359796k used,   521304k free,   339352k cached
PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
6865 marvin    20   0 1072m  50m 5280 S   13  2.6  70:35.94 chrome
27 root      20   0     0    0    0 S    7  0.0   4:26.31 kswapd0
23168 marvin    20   0  390m  13m 3324 S    3  0.7   7:50.06 Xorg
1071 marvin    20   0  409m 4944 2852 S    2  0.3   0:04.48 xfce4-terminal
18922 marvin    20   0  455m  13m 1492 R    2  0.7  39:30.25 skype
23890 marvin    20   0 1716m 338m  10m S    2 17.6  22:42.04 firefox
23442 marvin    20   0 1300m  14m 3192 S    2  0.8   8:29.54 compiz
54 root      20   0     0    0    0 S    1  0.0   1:29.94 mmcqd/0
8258 marvin    20   0  675m  31m 7320 S    1  1.7   0:13.65 chrome
52 root     -51   0     0    0    0 D    1  0.0   0:08.45 irq/51-ELAN0000
7250 root      20   0     0    0    0 S    1  0.0   0:06.21 kworker/u4:20
15298 marvin    20   0 11252 1068  512 S    1  0.1   0:01.59 top
15868 marvin    20   0 17472 1068  596 R    1  0.1   0:00.19 top
25417 root      20   0     0    0    0 S    1  0.0   0:27.31 kworker/u4:2
712 marvin    20   0 1081m  63m 9080 S    0  3.3  10:14.77 chrome
1216 root      20   0  166m  244  216 S    0  0.0   0:16.09 esif_ufd
5889 marvin    20   0  916m  34m 6876 S    0  1.8   0:25.95 chrome
For comparison, now, while I am writing the email, top shows the following:
top - 10:11:28 up 20:20,  0 users,  load average: 0.53, 2.06, 2.89
Tasks: 240 total,   1 running, 238 sleeping,   0 stopped,   1 zombie
Cpu(s): 11.8%us,  3.7%sy,  1.0%ni, 83.2%id,  0.3%wa,  0.0%hi,  0.0%si,  0.0%
Mem:   1966832k total,  1892172k used,    74660k free,     5328k buffers
Swap:  2881100k total,  1611604k used,  1269496k free,   354844k cached
PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
6865 marvin    20   0 1072m  40m 5304 S   16  2.1  72:00.69 chrome
8258 marvin    20   0  682m  32m  10m S    6  1.7   0:46.24 chrome
1120 marvin    20   0  376m  24m 6612 S    3  1.3   6:19.55 chrome
23890 marvin    20   0 1721m 410m  25m S    2 21.4  23:22.68 firefox
18922 marvin    20   0  455m  31m 9284 S    2  1.7  39:49.15 skype
712 marvin    20   0  952m  63m  13m S    2  3.3  10:43.11 chrome
17797 marvin    20   0 17472 1568 1104 R    1  0.1   0:00.11 top
15298 marvin    20   0 11252 1008  524 S    1  0.1   0:10.15 top
10082 root      20   0     0    0    0 S    0  0.0   0:00.88 kworker/0:3
23168 marvin    20   0  372m  30m  14m S    0  1.6   8:12.43 Xorg
23471 marvin    20   0 20184  236  172 S    0  0.0   0:11.45 syndaemon
23608 marvin    20   0  849m 117m  21m S    0  6.1   1:34.38 thunderbird
23612 marvin    20   0  398m 4604 2716 S    0  0.2   0:02.19 unity-applicati
27004 marvin    20   0 1402m  29m 3596 S    0  1.6   2:19.29 soffice.bin
1 root      20   0 11856  768  204 S    0  0.0   0:00.41 init
2 root      20   0     0    0    0 S    0  0.0   0:00.99 kthreadd
3 root      20   0     0    0    0 S    0  0.0   0:01.28 ksoftirqd/0
I hope you can read the numbers and the table is not totally distorted;
if it is so, tell me and I can format it.

It is readable. To me it seems you are running out of physical and swap memory. Especially compiz is using a lot. Maybe this is related https://bugs.launchpad.net/compiz/+bug/1315261 However not really a solution offered in that bug report. Maybe disabling the transition effects in windows will reduce it, or like I would prefer, switch to xfce or lxde especially on a 2Gb ram chromebook.

Thank you very much. I guess because everything is neatly set up I will just take care to close programs and tabs accordingly and restart it properly more often. In case it turns out more annoying I might change the desktop environment. Still my feeling continues that sometimes the working memory is not cleaned appropriately after closing some software. The problem occurs after I ran the laptop for a longer time and not always clearly related to my usage in the moment of slowing down.

@1kastner Yes, compiz shouldn't use so much memory. It doesn't seem to clean up properly. You could backup your chroot, then add the xfce target to the original and try that. If you don't like it put your backup back.

source: gharchive/issue

repo: dnschneid/crouton


text:
I-D-K what I am doing..... :(

Please paste the output of the following command here: sudo edit-chroot -all

Please describe your issue:
I have downloaded and installed Crouton. I entered the following command:
sudo startunity
Which went black for a second and then went back to chromebook with the following in the terminal;
chronos@localhost ~/Downloads $ sudo startunity
Entering /mnt/stateful_partition/crouton/chroots/precise...
Failed to start message bus: Failed to open "/etc/selinux/targeted/contexts/dbus_contexts": No such file or directory
WARNING: starting chroot system dbus daemon failed with code 1
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
X.Org X Server 1.15.1
Release Date: 2014-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.42-75-generic x86_64 Ubuntu
Current Operating System: Linux localhost 3.18.0-13527-gc2f2230 #1 SMP PREEMPT Wed Feb 1 15:08:20 PST 2017 x86_64
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 3584000 verity payload=PARTUUID=19a28b48-3f80-894b-ba19-46d6aaa818bc/PARTNROFF=1 hashtree=PARTUUID=19a28b48-3f80-894b-ba19-46d6aaa818bc/PARTNROFF=1 hashstart=3584000 alg=sha1 root_hexdigest=44225f79a27b9aeb9436c73033bf600cb26245a5 salt=a15acb0bf4c70e61e6138718acfc1c653c70c7797e7ae0fcb275908e10354a2c" noinitrd vt.global_cursor_default=0 kern_guid=19a28b48-3f80-894b-ba19-46d6aaa818bc add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic intel_idle.max_cstate=7
Build Date: 12 February 2015  03:37:52PM
xorg-server 2:1.15.1-0ubuntu2~precise5 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.30.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Fri Feb 17 19:49:37 2017
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
setversion 1.4 failed: Permission denied
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
[intel_init_bufmgr:1069] Error initializing buffer manager.
setversion 1.4 failed: Permission denied
crouton: version 1-20170216202114~master:2f7cfb5e
release: precise
architecture: amd64
xmethod: xorg
targets: unity
host: version 9000.82.0 (Official Build) stable-channel sentry
kernel: Linux localhost 3.18.0-13527-gc2f2230 #1 SMP PREEMPT Wed Feb 1 15:08:20 PST 2017 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Running exit commands...
/usr/bin/xinit: connection to X server lost
waiting for X server to shut down Hangup
(EE) Server terminated successfully (0). Closing log file.
Unmounting /mnt/stateful_partition/crouton/chroots/precise...
WHAT AM I DOING WRONG!?!?!??!?!?!?!? Please help!
If known, describe the steps to reproduce the issue:

My recommendation is, if possible, keep experimenting with different setups and don't worry too much if the first time fails. One major benefit to this environment is that chroots are easy to create and modify.
Given your current issue, try one or more of the following:
1). Install more targets. I use xorg, xiwi, keyboard, and unity
sudo sh -e ~/Downloads/crouton -t xorg,xiwi,keyboard,unity -r precise -e
That command assumes you also want encryption.
2). After running the install script, try starting the chroot with a different target. Add the crouton Chrome extension and try running with the xiwi target: sudo enter-chroot -n chrootname -X xiwi
See here: https://github.com/dnschneid/crouton/wiki/crouton-in-a-Chromium-OS-window-(xiwi)
3). Try a different release. Trusty is well-supported. I'm running Xenial (with a bit of effort).
4). Finally, if you can't get unity to run on your system, try installing with xfce.
Happy hunting! Don't give up!

So first type;
sudo sh -e ~/Downloads/crouton -t xorg,xiwi,keyboard,unity -r precise -e
then install using command;
sudo enter-chroot -n chrootname -X xiwi
Im a super beginninger.... sssoooooo.... laying out the steps would be super greatful.

Also, when I type in:
sudo sh -e ~/Downloads/crouton -t xorg,xiwi,keyboard,unity -r precise -e
Then the files were downloaded and updated. After, I typed;
sudo enter-chroot -n chrootname -X xiwi
Which this had came up in the terminal;
grep: /mnt/stateful_partition/crouton/chroots/chrootname/.crouton-targets: No such file or directory
/mnt/stateful_partition/crouton/chroots/chrootname does not contain XMETHOD 'xiwi'
Sooooo what am I doing wrong?

I am also having this issue. Is there a way to directly download the
missing files straight to the path folder?
TIA
Caleb
On Mon, Feb 27, 2017 at 12:51 PM, zmcase notifications@github.com wrote:

Also, when I type in:
sudo sh -e ~/Downloads/crouton -t xorg,xiwi,keyboard,unity -r precise -e
Then the files were downloaded and updated. After, I typed;
sudo enter-chroot -n chrootname -X xiwi
Which this had came up in the terminal;
grep: /mnt/stateful_partition/crouton/chroots/chrootname/.crouton-targets:
No such file or directory
/mnt/stateful_partition/crouton/chroots/chrootname does not contain
XMETHOD 'xiwi'
Sooooo what am I doing wrong?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/3089#issuecomment-282812907,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWm280rYAILMyJw-VLjRKoBvU8YhXQvrks5rgxsigaJpZM4ME-7f
.

Might be good to try xenial instead.

authors: IMadeYouReadThis777 drinkcat rwwishart zmcase


text:
Installing linux, when I come to the end of the installation it fails and doesn't complete.

Please paste the output of the following command here: sudo edit-chroot -all
```name: melon
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/melon...
crouton: version 1-20190902190258~master:9a594a66
release: xenial
architecture: amd64
targets: xfce
host: version 12239.92.0 (Official Build) stable-channel snappy
kernel: Linux localhost 4.4.180-16566-g51163f4278d1 #1 SMP PREEMPT Tue Aug 27 17:07:15 PDT 2019 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/melon...
name: xenial
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/xenial...
crouton: version 1-20190902190258~master:9a594a66
release: xenial
architecture: amd64
targets: xfce
host: version 12239.92.0 (Official Build) stable-channel snappy
kernel: Linux localhost 4.4.180-16566-g51163f4278d1 #1 SMP PREEMPT Tue Aug 27 17:07:15 PDT 2019 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...

#### Please describe your issue: I have tried to install linux multiple times, and every time it fails right at the end. I am trying to do the simplest installation. I am a noob at this so all help would be appreciated. I just followed the readme. I tried adding xenial into the commands to see if it would fix it and I tried updating

#### If known, describe the steps to reproduce the issue:
Step one: Install crouton
Step two: Go to command terminal
Step three: do the required steps to start the installation. (this time I used xfce, but I have tried unity. It also didn't work.
Step four: At the end of the installation a bunch of stuff like this shows up
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/l/linux/linux-libc-dev_4.4.0-161.189_i386.deb  Cannot initiate the connection to archive.ubuntu.com:80 (2001:67c:1560:8001::11). - connect (101: Network is unreachable) [IP: 2001:67c:1560:8001::11 80]

E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/g/glibc/libc6-dev_2.23-0ubuntu11_i386.deb  Cannot initiate the connection to archive.ubuntu.com:80 (2001:67c:1560:8001::11). - connect (101: Network is unreachable) [IP: 2001:67c:1560:8001::11 80]

and I don't know what to do.
at the end it says:

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Failed to complete chroot setup.

Any and all help would be appreciated.

@crazywatermelon10,
Part of the error message is: 101: Network is unreachable
Sometimes that's just a temporary network glitch that only lasts for a short time.
Try updating your chroot using the below command and see if it finishes:

sudo crouton -n melon -u

-DennisLfromGA


text:
🛑 Site Histovec is down

In 9bf64fa, Site Histovec (https://histovec.interieur.gouv.fr/histovec) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Site Histovec is back up in b89133f after 52 minutes.

repo: dnum-mi/stats-sites-api

license: MIT


text:
Collapse build.yaml and build-pr.yaml together

They're equivalent, except triggering conditions. The config can just specify both push and pull_request.

Since secrets aren't passed into runs for PRs, all the acceptance tests are skipped on PRs: https://github.com/docker-credential-magic/docker-credential-magic/pull/42/checks#step:6:7
We could either keep this how it is, or explicitly skip acceptance tests if the run is being triggered by PR.


text:
1.13-git variant doesn't allow you to access the shell?

Current version of the -git tags of docker allowed you to run:
docker run -ti --rm docker:git sh

and access the command line, e.g. to clone out a private repo and/or start performing any pre-build actions upon it, before executing docker build.
The 1.13 rc versions seem to only allow you to run the container with build <repourl>, and that the repo must be public and ready to build as-is.
The entrypoint script seems to suggest that I should be able to run any regular command as long as there isn't a matching docker command?

Nevermind - it's a dupe of docker/docker#28329

repo: docker-library/docker

license_source: bigquery


text:
Issue running make, getting gotestsum: not found

When running the command make it fails to run the unit tests and returns the error gotestsum: not found. The quick fix is to simply run go get gotest.tools/gotestsum, and this could be the right answer but this isn't mentioned in the BUILDING.md and it is automated in the docker.Makefile.
So my question is, should the BUILDING.md be updated to mention this step ? Or should the Makefile be updated to run git clone -q https://github.com/gotestyourself/gotestsum like the docker.Makefile does?
Thanks!

Steps to reproduce the issue:

Run make
Get to: Running unit tests...

Describe the results you received:
gotestsum: not found
Describe the results you expected:
The unit tests to execute
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Version: 18.09.7

Output of docker-app version:
Latest checkout from master

Hi @BattleBas Thank you for opening this ticket. Indeed we are going to update BUILDING.md

authors: BattleBas jcsirot

repo: docker/app


text:
Update logrus vendor

Uses formatter from external package. No functional change to use hooks.
closes #2125

Noticed one minor difference in logstash format, "@version":"1" to "@version":1. Not sure that is even worth noting.

Current coverage is 51.20% (diff: 100%)

Merging #2128 into master will decrease coverage by 10.02%

@@             master      #2128   diff @@
==========================================
  Files           129        129
  Lines         11416      11416
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           6990       5846   -1144
- Misses         3535       4821   +1286
+ Partials        891        749    -142

Powered by Codecov. Last update 76f514b...1d6c1a6

LGTM

authors: aaronlehmann codecov-io dmcgowan

repo: docker/distribution


text:
Confusing Sentence Under "Step 2. Install UCP" That May Lead to Errors

File: ee/dtr/admin/install/index.md
Under "Step 2. Install UCP" is the following: "Since DTR requires Docker Universal Control Plane (UCP) to run, you need to install UCP on all the nodes where you plan to install DTR."
This makes it appear that the user should install DTR on the same nodes that are running UCP. This is not recommended as it could cause resource and port conflicts. We generally recommend customers install DTR on worker nodes (not UCP nodes). This sentence seems to indicate otherwise.

PR submitted for approval.

#10120 merged and closed.

authors: KoryKessel-Docker javajason


text:
Can I deploy this project locally? For easy reference

Deploy it in my private environment so it's easy to reference

I think I found a way


text:
Feedback for: compose/django.md

URL: https://docs.docker.com/compose/django.md
Is it safe for production to use standard passwords here?

@ramboldio, I don't know what you mean by standard passwords, but you should never use passwords supplied by default.
For an interesting discussion about handling secrets, I recommend checking up on https://github.com/docker/docker/issues/13490

@konstruktoid thanks for the link :wink:

authors: konstruktoid ramboldio


text:
Document how to use Docker on Windows (Server, primarily) from non-admin prompt

eg. add to docker-users.
https://github.com/docker/for-win/issues/868#issuecomment-312639000
... this should not be documented in the context of CE, I think - where this is supposed to be automatic.
cc @johnstep @mstanleyjones

@mstanleyjones , @friism , what do you think about a note on one or both of these pages?
https://docs.docker.com/docker-for-windows/install/
https://docs.docker.com/docker-for-windows/

@gbarr01 given @friism 's comment re: "should not be documented in the context of CE .." the better place for a note would likely be somewhere on this page, install for EE: https://docs.docker.com/engine/installation/windows/docker-ee/ (rather than the above two pages)
What do you think @friism ?

yes, docker-ee ftw

While the above was described in the context of Windows CE, I have this same issue.  Win10 corporate install where an admin remoted in/installed Docker Desktop for me, then left. As the installer he was added as a member of docker-users, but not me. Perhaps this would be added as a prompt in the install or a closing note after install is complete?

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!

authors: L-Hudson ehwinter friism gbarr01 londoncalling


text:
Orphan links in docker compose file reference

Problem description
Documentation links to an orphan page
Problem location
https://docs.docker.com/compose/compose-file/#volume-configuration-reference

I saw a problem on the following URL:
https://docs.docker.com/engine/admin/volumes/volumes.md

The correct link is
https://docs.docker.com/storage/volumes/

In general I saw a lot of links are broken.

Thanks for sharing this issue. It appears that the broken link no longer appears in https://docs.docker.com/compose/compose-file/#volume-configuration-reference. If you find that the issue still persists, please let us know.

authors: craig-osterhout tallero


text:
file for visual check of various formatting

Hey @docker/docs-maintainers, this file will be a canary/smoketest that we can use as a quick visual check when we start culling excess JS and CSS.
I've added a bunch of code format blocks at the end; if you know of one that I don't currently have, lmk or add it yourself by pushing to the patch.
Signed-off-by: LRubin lrubin@docker.com

Also of note: I'm not sure where we want this to live? Is root okay?  I've omitted it from all the menuing, so that should be enough I'd hope, but maybe we should make a utility folder (for the allpagelinks and other test files).

Deploy preview ready!
Built with commit b24357cb87b53f36c1b05cfd27a9cd042987719c
https://deploy-preview-585--docker-docs.netlify.com

Alright let's get this in, it's been quiet for awhile and I can't think of anything more to add. We can always iterate. Thanks for this, @sanscontext :)

authors: johndmulhausen sanscontext


text:
Update deploy-with-compose.md

Proposed changes
Fixed a word in the "Deploy a Compose-based app to a Kubernetes cluster" document.
Unreleased project version (optional)

Related issues (optional)

Deploy preview for modest-edison-79d82e ready!
Built with commit 3054360c1122d1bec529532a11e4e3b52f5986db
https://deploy-preview-7268--modest-edison-79d82e.netlify.com

authors: GordonTheTurtle mmcru


text:
Updated Secure Kubernetes Defaults to include local storage class

Proposed changes
Updated Secure Kubernetes Defaults to include local storage class and provided a bit more clarification to the release notes.
Unreleased project version (optional)

Related issues (optional)

@wsong Do you mind taking a look? Thanks :)

Deploy preview for docsdocker ready!
Built with commit 8b3c78b03b706fedfa13e9a3b02d34c426e4b769
https://deploy-preview-8942--docsdocker.netlify.com

Specifically, this change went out in UCP 3.1.3 and 3.0.9

Thanks. I have just pushed a commit to update both the UCP 3.1.3 and 3.0.9 release notes.
@paigehargrave @bermudezmt PTAL :)

LGTM - @ollypom Let me know if I can help with backporting this. Thank you for your help here!

@ollypom Thank you!

authors: GordonTheTurtle ollypom paigehargrave wsong


text:
Cannot start container <..>: write <..>memory.memsw.limit_in_bytes: invalid argument

[root@local ernestas]# docker run -m="2G" -t -i slave /sbin/my_init -- bash -l
2015/01/22 19:15:26 Error response from daemon: Cannot start container 8096197f79ccc8277f0a8482fc148bd3207e615c038a2bf6422556bcf2db3782: write /sys/fs/cgroup/memory/system.slice/docker-8096197f79ccc8277f0a8482fc148bd3207e615c038a2bf6422556bcf2db3782.scope/memory.memsw.limit_in_bytes: invalid argument
[root@local ernestas]#

[root@local ernestas]# docker start bd9041d95adc
Error response from daemon: Cannot start container bd9041d95adc: write /sys/fs/cgroup/memory/system.slice/docker-bd9041d95adcdf46ff49b9220b99deb6aa4dd414d204a62e87b65fd29be6bd56.scope/memory.memsw.limit_in_bytes: invalid argument
FATA[0000] Error: failed to start one or more containers
[root@local ernestas]#

Exactly the same container worked fine on another installation of Fedora 21 in VirtualBox. This is running latest Docker from official RPM repos:
Client version: 1.4.1
Client API version: 1.16
Go version (client): go1.3.3
Git commit (client): 5bc2ff8/1.4.1
OS/Arch (client): linux/amd64
Server version: 1.4.1
Server API version: 1.16
Go version (server): go1.3.3
Git commit (server): 5bc2ff8/1.4.1

journalctl ends with:
Jan 22 19:17:30 local docker[6160]: time="2015-01-22T19:17:30+02:00" level="error" msg="Warning: error unmounting device bd9041d95adcdf46ff49b9220b99deb6aa4dd414d204a62e87b65fd29be6bd56: UnmountDevice: device not-mounted id bd9041d95adcdf46ff49b9220b99deb6aa4dd414d204a62e87b65fd29be6bd56\n"
Jan 22 19:17:30 local docker[6160]: time="2015-01-22T19:17:30+02:00" level="info" msg="+job log(die, bd9041d95adcdf46ff49b9220b99deb6aa4dd414d204a62e87b65fd29be6bd56, slave:latest)"
Jan 22 19:17:30 local docker[6160]: time="2015-01-22T19:17:30+02:00" level="info" msg="-job log(die, bd9041d95adcdf46ff49b9220b99deb6aa4dd414d204a62e87b65fd29be6bd56, slave:latest) = OK (0)"
Jan 22 19:17:30 local docker[6160]: Cannot start container bd9041d95adc: write /sys/fs/cgroup/memory/system.slice/docker-bd9041d95adcdf46ff49b9220b99deb6aa4dd414d204a62e87b65fd29be6bd56.scope/memory.memsw.limit_in_bytes: invalid argument
Jan 22 19:17:30 local docker[6160]: time="2015-01-22T19:17:30+02:00" level="info" msg="-job start(bd9041d95adc) = ERR (1)"
Jan 22 19:17:30 local docker[6160]: time="2015-01-22T19:17:30+02:00" level="error" msg="Handler for POST /containers/{name:.*}/start returned error: Cannot start container bd9041d95adc: write /sys/fs/cgroup/memory/system.slice/docker-bd9041d95adcdf46ff49b9220b99deb6aa4dd414d204a62e87b65fd29be6bd56.scope/memory.memsw.limit_in_bytes: invalid argument"
Jan 22 19:17:30 local docker[6160]: time="2015-01-22T19:17:30+02:00" level="error" msg="HTTP Error: statusCode=500 Cannot start container bd9041d95adc: write /sys/fs/cgroup/memory/system.slice/docker-bd9041d95adcdf46ff49b9220b99deb6aa4dd414d204a62e87b65fd29be6bd56.scope/memory.memsw.limit_in_bytes: invalid argument"

Which could be somehow related to https://github.com/docker/docker/issues/4036, but doesn't seem to be an exact replica of this issue. Full logs here: https://gist.github.com/ernetas/7b1ad29db74cd4f093df
What could be the issue here? The containers fail to start only when started with memory limitations (-m="x").

Can you provide uname -a and cat /proc/cmdline output from the working and failing cases?  I would say to check you have the proper memory limits/swap accounting turned on in the case of the failing system, but I assume you do as I don't see the warnings in the logs that they aren't available (see http://docs.docker.com/installation/ubuntulinux/#memory-and-swap-accounting)

Of course!
This is from the working machine:
[root@localhost ~]# uname -a
Linux localhost.localdomain 3.17.8-300.fc21.x86_64 #1 SMP Thu Jan 8 23:32:49 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[root@localhost ~]# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.17.8-300.fc21.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8
[root@localhost ~]#

The same commands on the failing host:
[root@local]~# uname -a
Linux local 3.17.8-300.fc21.x86_64 #1 SMP Thu Jan 8 23:32:49 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[root@local]~# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.17.8-300.fc21.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8
[root@local]~#

Both seem identical to me.
Yes, the memory/swap accounting seem to be on, as no errors are shown regarding them on both machines.

This may be not even related to Docker, sadly. I launched a simple container with no memory limitations and tried to change it on the fly with simple echo (what seems to be an alternative to what Docker does, right?):
[root@local ~]# docker run -d -t -i phusion/baseimage /sbin/my_init -- bash -l
5b6e94aea7c1a47e8d418e5c66bc966527ea0b5b987e5d27d039d14be85f7bc2
[root@local ~]# docker ps
CONTAINER ID        IMAGE                      COMMAND                CREATED             STATUS              PORTS               NAMES
5b6e94aea7c1        phusion/baseimage:0.9.16   "/sbin/my_init -- ba   2 seconds ago       Up 1 seconds                            dreamy_bardeen
[root@local ~]# echo 2000000000 > /sys/fs/cgroup/memory/system.slice/docker-5b6e94aea7c1a47e8d418e5c66bc966527ea0b5b987e5d27d039d14be85f7bc2.scope/memory.memsw.limit_in_bytes
bash: echo: write error: Invalid argument
[root@local ~]# echo 2000000000 > /sys/fs/cgroup/memory/system.slice/docker-5b6e94aea7c1a47e8d418e5c66bc966527ea0b5b987e5d27d039d14be85f7bc2.scope/memory.limit_in_bytes
[root@local ~]# echo 2000000000 > /sys/fs/cgroup/memory/system.slice/docker-5b6e94aea7c1a47e8d418e5c66bc966527ea0b5b987e5d27d039d14be85f7bc2.scope/memory.memsw.limit_in_bytes
[root@local ~]#

This actually works:
root@5b6e94aea7c1:/# stress --vm 1 --vm-bytes 3G
stress: info: [146] dispatching hogs: 0 cpu, 0 io, 1 vm, 0 hdd
stress: FAIL: [146] (416) <-- worker 147 got signal 9
stress: WARN: [146] (418) now reaping child worker processes
stress: FAIL: [146] (452) failed run completed in 0s
root@5b6e94aea7c1:/#

Default values are:
[root@local ~]# cat /sys/fs/cgroup/memory/system.slice/docker-094e9dd329f1d1fe57a80f6e87a5db9bf7c8b1ec4de91669bfa3b570e34d7963.scope/memory.memsw.limit_in_bytes
18446744073709551615
[root@local ~]# cat /sys/fs/cgroup/memory/system.slice/docker-094e9dd329f1d1fe57a80f6e87a5db9bf7c8b1ec4de91669bfa3b570e34d7963.scope/memory.limit_in_bytes
18446744073709551615
[root@local ~]#

Obviously, one cannot change memory.memsw.limit_in_bytes first. memory.limit_in_bytes has to be smaller or equal to that first. However, the same is on the working (VirtualBox) machine, so it's not clear to me why Docker does this correctly on one host, but not on the other:
[root@localhost ~]# cat /sys/fs/cgroup/memory/system.slice/docker-dcd8ef236c92815fdc327e82539792a485b416f5e23f71558fd51cdd6b4e407d.scope/memory.memsw.limit_in_bytes
18446744073709551615
[root@localhost ~]# cat /sys/fs/cgroup/memory/system.slice/docker-dcd8ef236c92815fdc327e82539792a485b416f5e23f71558fd51cdd6b4e407d.scope/memory.limit_in_bytes 18446744073709551615
[root@localhost ~]#

The above is without memory limitations, whereas the below is with:
[root@localhost ~]# cat /sys/fs/cgroup/memory/system.slice/docker-b3be58b835edfe7d7c6260c7bb9fad4f27c5f13b235ca82e4fd7d792d3ba8293.scope/memory.memsw.limit_in_bytes
4000002048
[root@localhost ~]# cat /sys/fs/cgroup/memory/system.slice/docker-b3be58b835edfe7d7c6260c7bb9fad4f27c5f13b235ca82e4fd7d792d3ba8293.scope/memory.limit_in_bytes
2000003072
[root@localhost ~]#

Also what's interesting on the working host:
Jan 23 00:41:31 localhost.localdomain systemd[1]: Failed to set memory.limit_in_bytes on : Invalid argument
Jan 23 00:41:31 localhost.localdomain systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument

Whatsoever, on that host, both memory.limit_in_bytes and memory.memsw.limit_in_bytes are set correctly.
Once again, logs from a failing host: https://gist.github.com/ernetas/c1ac5cf5ee6e1913c611 Logs from a working host: https://gist.github.com/ernetas/6d0d40aa28e0f49c5103

Reinstalled fresh Fedora, using exactly the same steps as before... Now both hosts are failing.

Same sing here. A new installed & updated Fedora 21 Server fails on setting memory limits in docker.
It seems to be an "new" update since 21.01.2015.
I got the last installation an this day ready. and this one works.

So, this seems to be potentially some interaction with systemd that has changed.. does anything from #7015 seem applicable?

Can't confirm, nor deny. But yes - the working host has systemd upgrade pending, as it turns out. #7015 does not seem to be applicable for my case, though - there are no similar errors in the logs.
Aside - I tested it with vfs before realizing it's a systemd issue - it didn't work as well.

Can confirm - upgrading systemd and libgudev1 is the cause of the issue:
Jan 24 20:46:16 Updated: systemd-libs-216-16.fc21.x86_64
Jan 24 20:46:31 Updated: systemd-216-16.fc21.x86_64
Jan 24 20:46:32 Updated: systemd-python3-216-16.fc21.x86_64
Jan 24 20:46:32 Updated: systemd-python-216-16.fc21.x86_64
Jan 24 20:46:33 Updated: libgudev1-216-16.fc21.x86_64
Jan 24 20:46:33 Updated: systemd-compat-libs-216-16.fc21.x86_64

Should we report this to RedHat bugzilla or is this an issue of Docker (given that you can launch a container with Docker and then later successfully change memory limitations yourself)?

@ernetas are you able to test this with the 1.5.0 RC?  We did some work around memory and mem-swap and I would be interested in seeing if you are encountering the same issue with it.
You can find binary downloads that are easily replaceable on your system in this comment for the upcoming release.
https://github.com/docker/docker/pull/10286#issuecomment-71119626

Sadly, still encountering it:
[root@localhost ernestas]# docker version
Client version: 1.5.0
Client API version: 1.17
Go version (client): go1.4.1
Git commit (client): 7e803ba
OS/Arch (client): linux/amd64
Server version: 1.5.0
Server API version: 1.17
Go version (server): go1.4.1
Git commit (server): 7e803ba
[root@localhost ernestas]# docker run -d -m="2000000000" --cap-add=SYS_NICE -t -i slave nice -n -18 /sbin/my_init -- bash -l
b27956ed3e2753153f210683d23010c94099047e8a0ce0f07326f71d1f44c8dd
FATA[0001] Error response from daemon: Cannot start container b27956ed3e2753153f210683d23010c94099047e8a0ce0f07326f71d1f44c8dd: write /sys/fs/cgroup/memory/system.slice/docker-b27956ed3e2753153f210683d23010c94099047e8a0ce0f07326f71d1f44c8dd.scope/memory.memsw.limit_in_bytes: invalid argument
[root@localhost ernestas]#

I'm looking into this a bit deeper.  I've reviewed any cgroups related changes in the systemd update from -14 to -16; there are a few that look interesting, not to mention there are over 100 patches to the latest systemd update on Fedora.
I have a hunch that something in the systemd changes causes libcontainer's systemd.Apply(..) to fail setting the memory.limit_in_bytes cgroup, which then, since systemd doesn't support the memsw cgroup directly, libcontainer tries to write that file directly and fails because memory.limit_in_bytes wasn't set properly first.  I'm going to validate that given I now have a Fedora21 VM with both pre-.16 and .16 systemd builds available and can dump some more info before failing the container start.
If we can narrow it down and it seems to be a problem in Fedora's systemd, then it would make sense to open a Red Hat bugzilla for the issue.

Ok, thx, there are some new updates of systemd in fed repos today. Sorry, i
don't know the Version number but it keeps failing with docker & memory Limit.
Gesendet mit AquaMail für Android
http://www.aqua-mail.com

Jan 27 23:55:09 Updated: systemd-libs-216-17.fc21.x86_64
Jan 27 23:55:12 Updated: systemd-216-17.fc21.x86_64
Jan 27 23:55:50 Updated: systemd-python3-216-17.fc21.x86_64
Jan 27 23:55:50 Updated: systemd-python-216-17.fc21.x86_64
Jan 27 23:55:50 Updated: systemd-compat-libs-216-17.fc21.x86_64

Tested with these upgrades (-17). Even after reboot and with Docker 1.5, it still throws the same error.

Works for me with systemd-218:
cat /sys/fs/cgroup/memory/system.slice/docker-2046530acac1f15f03399a4dc750fa42f0363a9a16b972abcec127deff7af7d1.scope/memory.memsw.limit_in_bytes
4294967296

So, I'm fairly confident that a single patch that is unique to the Fedora/RH build of systemd is the culprit.  In a working systemd on Fedora (216-12, 216-13, 216-14), this message is output in the logs:
Jan 28 11:01:34 localhost systemd: Failed to set memory.limit_in_bytes on : Invalid argument

While that message comes from the src/core/cgroups.c code that is setting the memory limit, it does appear to work (potentially that code is called again successfully?); I don't have the systemd debug fu (nor time to dig into it), other than to say that clearly the limit_in_bytes setting is being called and does appear to set the value given we can check afterwards and see it is set properly.
That message no longer appears with later systemd builds on Fedora (216-16 and 216-17), and this patch also appeared in those builds which are now failing:
0159-cgroup-memory-limits-on-are-not-supported.patch
diff --git a/src/core/cgroup.c b/src/core/cgroup.c
 12 index 5f3d9907b7..37db3d5289 100644
 13 --- a/src/core/cgroup.c
 14 +++ b/src/core/cgroup.c
 15 @@ -382,7 +382,7 @@ void cgroup_context_apply(CGroupContext *c, CGroupControllerMask mask, const cha
 16                  }
 17          }
 18
 19 -        if (mask & CGROUP_MEMORY) {
 20 +        if ((mask & CGROUP_MEMORY) & !is_root) {
 21                  if (c->memory_limit != (uint64_t) -1) {
 22                          char buf[DECIMAL_STR_MAX(uint64_t) + 1];
 23

The is_root variable is defined as true if path is empty or /, and from the error message above we can see the failing call from prior systemd builds had a path of "" (because the error message ends with "on  :") where path is emitted in the log.  Therefore, it would seem that it assumes this is an attempt to write to root and disallows it.  Maybe that patch is not namespace aware?  It only exists in the Fedora/Red Hat version of systemd, which is why @LK4D4 sees systemd-218 working fine.
A workaround in Docker is possible by catching the error when we try the manual write of memory.memsw.limit_in_bytes and trying to manually write limit_in_bytes and then memsw limit again.  But, I think this should be brought to the attention of the Fedora/RH folks as that patch is suspect and needs further investigation from what I can tell.

Thanks, @estesp. I contacted zbyszek, who commited the patches. For me, it seems that we are missing additional patches. E. g. https://github.com/systemd/systemd/commit/4ad490007b70e6ac18d3cb04fa2ed92eba1451fa, which reverts 0159-cgroup-memory-limits-on-are-not-supported.patch patch and, correct me if I'm wrong, is included in systemd-218.

When it fails, the bad systemd verions is used on the host, in the container, or both?

For me - on the host only. I'm trying to launch an Ubuntu container, so it doesn't support systemd yet. Also, I doubt if systemd could run inside a container?

Hm, so my first theory is wrong.
Yes, it can run in a container.

Its only on the host in my case.
Gesendet mit AquaMail für Android
http://www.aqua-mail.com
Am 31. Jänner 2015 22:14:46 schrieb keszybz notifications@github.com:

When it fails, the bad systemd verions is used on the host, in the
container, or both?

Reply to this email directly or view it on GitHub:
https://github.com/docker/docker/issues/10280#issuecomment-72336965

Fixed in http://cgit.freedesktop.org/systemd/systemd/commit/?id=a3bd89ea99. I'll try to issue an update for systemd package tomorrow, but it'll be a while before it passes through QA. I made a build at http://koji.fedoraproject.org/koji/taskinfo?taskID=8788274 with this one patch added if you want to upgrade now.

I hit this using Fedora 21 atomic. @keszybz Thanks for fixing.. Is there a bz that tracks this issue that I can follow?
This bug (in systemd) isn't really hard to reproduce but if anyone is interested I wrote down some steps to recreate and recover on F21 atomic host:
http://dustymabe.com/2015/01/31/crisis-averted-im-using-atomic-host/

On Sun, Feb 01, 2015 at 08:32:25AM -0800, Dusty Mabe wrote:

I hit this using Fedora 21 atomic. @keszybz Thanks for fixing.. Is there a bz that tracks this issue that I can follow?
Nope, feel free to open one (preferably in the  POST state if you can).

https://bugzilla.redhat.com/show_bug.cgi?id=1188037
@keszybz I could only open in "NEW" or "ASSIGNED". Do you mind updating to "POST" state?

The issue was fixed in systemd-216-20.fc21.

authors: LK4D4 crosbymichael dustymabe ernetas estesp keszybz setiseta

repo: docker/docker


text:
Documentation on boolean flags is wrong

The documentation on boolean flags at http://docs.docker.com/reference/commandline/cli/#boolean states "... specifying them will set the value to the opposite of the default value". Thankfully, this does not seem to be the case, or it would be extremely confusing in the case of default true flags.
For example the --sig-proxy flag for docker run defaults to true. However, the argument --sig-proxy does not turn off signal proxying in my tests, although --sig-proxy=false will.
This is much more important in the case of docker commit --pause, which also defaults to true. I haven't managed to test it, but if it works as the documentation states then calling docker commit --pause would have the effect of not issuing a pause, surely not what the user expects.
Could someone:

Confirm that default true flags are not toggled to false when specified
Update the documentation to reflect this?

Incidentally, It took me a while to figure out what --sig-proxy does - some more docs would be nice (although the main factor here was probably my stupidity).

This is confusing enough that I wonder if it would be possible to deprecate any default true flags and change them to negatives. At the moment, the only values for the flags that make sense are --sig-proxy=false and --pause=false, which isn't very intuitive. Why don't we just create default false alternatives? i.e. --no-sig-proxy and --no-pause?

frustratingly, the --no-preference=false version is also very confusing - there's no really good answer to the dilemma.
I also suspect that documentation was written a very long time ago, so thank you for noting it, I'm re-writing it now.

frustratingly, the --no-preference=false version is also very confusing - there's no really good answer to the dilemma.

Then don't document that they accept a value (even thought they do); From an end-users perspective, the flag itself becomes the Boolean.
I think that's what I proposed in https://github.com/docker/docker/issues/9406, but it's been a while, lol

@thaJeztah yes, well mmm, that would be a code PR, which could not be merged for 1.5 now - whereas this one, being docs, can :)

@SvenDowideit I don't think the situation is unsalvageable :)
My recommendation would be:

fix this issue in the docs and close it
Implement #9406
Deprecate all default true flags in favour of negative versions e.g. --no-sig-proxy

At that point I think things will be pretty clear and intuitive. You will still be able to pass --version=false, but I don't think this is a big problem as long as it isn't shown to users as the primary way to use to the flag. I can see point 3 being controversial though :(
Thanks for looking at this!

that would be a code PR, which could not be merged for 1.5 now

Ah, yes, you mentioned that on the other PR. Looks like now I really need to start learning "Go".
@amouat +1, on those steps.

I just read the new documentation; it's much better. Good job!
I think this can be closed now, not sure if I should do it or leave it to you. If others agree, I'll open a new issue "Deprecate all default true flags in favour of negative versions", but I can see this being controversial!

ok cool sgtm

authors: SvenDowideit amouat jfrazelle thaJeztah


text:
docker build  --net options

the docker run container need --net option when use openvswitch manage network， but docker build  don't use --net option  run container， so I cat't build docker images

i am going to close for lack of info, but if you can give us clear steps to reproduce with version and docker info i will repoen