I have been following the instructions on
https://docs.adobe.com/docs/en/aem/6-1/deploy/upgrade.html
I reached "Once the upgrade is finished, the AEM homepage will be shown."
However, all I get is "an HTTP 503 status for all requests except for those under http:///system/console", exactly as described at the NOTE under this step.
The problem is that I always get this error, not only during the upgrade, but also after the upgrade is finished!
The error.log states:
11.11.2015 12:38:29.888 *ERROR* [qtp231586654-77] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request.
11.11.2015 12:38:29.888 *ERROR* [qtp231586654-77] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.
Any help is highly appreciated.
We've encountered this once:
There were issues with diskspace (the disk was simply full), make sure you have an adequate amount of space available.
There could be two possible reasons:
Some of the bundles are not active.
Lucene is corrupt and hence not able to start
Possible fix is:
Bring your bundles back to active, if it is not active.
Stop your instance. go to crx-quickstart\repository\index and delete index folder.
Restart the instance (This will regenerate Lucene indexes fully).
Quick fix:
Stop the AEM instance.
Go to folder crx-quickstart\repository\ remove folder index
Start the AEM.
Everything should working fine. (It's working for me)
Check the permissions under crx-quickstart\repository\ after you deleted the index.
For me it had nothing to do with the segmentstore or the index or any unsatisfied bundles. Instead, it was the datastore.
The permissions for the datastore directory didn’t allow the user running aem to access it. The datastore directory is configured in org.apache.jackrabbit.oak.plugins.blob.datastore.FileDataStore.
This error really should reveal its root cause a little bit more easily. I’m sure it was somewhere in the logs, though…
Related
I am trying to upgrade the site from v 7.6 to v. 7.15.1.
I have done the upgrade on localhost which included updating the db.
Now I transferred my files from localhost o the test site and on there I am getting an error in log:
ERROR Umbraco.Core.UmbracoApplicationBase - An unhandled exception occurred
System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'umbracoUserLogin'.
and I can't login to the backoffice.
It seems to be looking for umbracoUserLogin on test while it doesn't exist yet because on test the db is not updated yet.
How to update the db on test in this case while the files have already been updated on localhost and transferred to test site?
I have done 2 umbraco upgrades recently; one is from 7.5.7 to 7.13.1 and the recent one is from 7.13.1 to 7.15.1.
During my upgrade; I have seen this problem and fix in this issue can help you for your problem(and I didn't see this problem again after doing the upgrade again, but this time checking all the auto changing files and accepting them one at a time-see details below for this) but coming back to your question; "What's the best way to upgrade from umbraco 7.6 to 7.15.1(including db upgrade)"; here are the steps that you should follow;
Create a backup for your project and your umbraco db before you start. If you are using Git, then things will be super easy for this.
Open up Nuget Package Manager for your Umbraco project and do the package upgrade using the Nuget Package Manger window or the consol. Search for UmbracoCms version 7.15.1 for your case.
Once you start doing the upgrade, you will see some popup windows that will ask you to approve some auto file changes(including some config files changes). As you don't want to lose some of your pre-upgrade settings, don't accept them all or discard them all, check all of them one by one, and as a general rule; if you don't have any custom changes for those files, then simply approve the change, otherwise, check your changes and make sure you don't loose anything and discard some of these file changes as a result.
Once you're done with your UmbracoCms upgrade(which will automatically do some dependency package upgrades), build your project, make sure all is looking good then go to your local project's umbraco back-office url, this will trigger the rest of the umbraco upgrade process and simply complete the upgrade steps by following the screens- at this point your umbraco db changes will be done automatically and it is possible that you might have some issues with some old corrupt cached files, if this happens, then simply delete App_Data/TEMP files and App_Data umbraco.config file and try again. If you see some other problems during the installation, check the logs(browser developer tools can be handy to understand the problems in this case), and fix them one at a time. It is possible that you don'T need some of your old web.config settings and they might cause some issues, simply comment out those lines and see if this will fix some of the issues.
Once you are done with you local upgrade, deploy your code to your testing environment, and go to the umbraco url of your test environment and follow the screens to complete the installation for your testing environment. If you see any problems, please check my notes for step 4 above.
Do your umbraco upgrade for other testing environments(QA, UAT, Training etc) and complete your umbraco upgrade tests. Once the tests are done, then you are ready to go live. After the live deployment, you will have to complete the umbraco upgrade one last time, but this time for the live system.
Always get your back-ups for each environment before you do the upgrade, so you will be ready to rollback your changes if things go wrong(which might happen as you're doing a big umbraco upgrade).
Final note; there are some good articles for this, please take a look to understand the process better. Good luck!
I was fixing things on a not well-maintained typo3 installation and it resulted in blank pages of frontend, backend and install tool.
I wanted to fix extensions because the powermail-extension was not working anymore even after updating to latest compatible version (tried emptying cache and database compare).
I deactivated an extension "compatibility6" to see if it was interfering and since then all pages have been blank including Install Manager. I reactivated the extension via PackageStates.php, emptied the cache but it did not change anything. I was not able to see any error messages even though I set the parameter in LocalConfiguration.php which made it hard to try to find out what is wrong. Then I restored a backup using vmware. Still, backend and frontend are blank.
I am using Apache and Typo3 7.6.23.
I do not know what might be causing the problem and would like to know what else to look for?
It means you have a PHP error there. The first thing would be to examine logs. If you see anything like "class not found", then your next action would be composer dumpautoload --no-dev.
Long time ago I had an article about blank pages in TYPO3 FE. Not up to date but still can be helpful: https://www.dmitry-dulepov.com/2009/03/blank-empty-page-in-typo3.html
Dmitry already wrote it: you have an error.
In production environment nothing is shown for not revealing any information about your system.
So the only information about the error can be found in the error log of your webserver.
What can you do to get more information about your error?
Enter the install tool and switch to develop mode. This will also enable deprecation logging into a file. Try to avoid filling your system with deprecation warnings by disabling deprecation logging.
Disable the default exceptionhandler by adding this to your typoscript setup:
config.contentObjectExceptionHandler = 0
Now you should see a call stack instead of blank screens.
Be aware that this might reveal confidential information from your system.
because of this you should use a copy of the live-system.
I created a solution with a few applications, and it worked perfectly. But a day later when I was about to debug the solution again, it suddenly cannot start.
I did have firewall and AV disabled, both when it worked and later when it didn't work.
It works fine when deployed to azure, but not locally.
The error thrown is:
Exception from HRESULT: 0x80071BFF
at System.Fabric.Interop.NativeRuntime.FabricGetNodeContext()
at System.Fabric.FabricRuntime.NativeFabricRuntimeFactory.GetNodeContextHelper()
at System.Fabric.Interop.Utility.WrapNativeSyncInvoke[TResult](Func`1 func, String functionTag, String functionArgs)
A related post register-servicefabricapplicationtype-on-a-secure-cluster-always-times-out
describes a similar thing.
However, I get this while debugging locally and with smallest possible application: I even just created 1 application, 1 actor, did no changes, hit F5 and I get this error.
So, I looked at service-fabric-troubleshoot-local-cluster-setup and while I also get the TypeInitializationException, the solution of:
Your path variable was not correctly set during installation. Please sign out of Windows and sign back in. This will fully refresh your path.
did not work at all.
Nothing else on that page seemed to be related.
Now I begin to feel that I've hit the end of what key words I can google, and still I have no idea what to do.
Any help would be greatly appreciated.
EDIT:
I've tried starting via cluster manager and apps can still not start.
I've removed apps, removed cluster, tried with new solutions, over and over. The only thing I haven't tried is reinstalling SDK and VS. I'm a bit reluctant to reinstall VS, so I'd hope to find some clues before resorting to that.
UPDATE1:
Now I reinstalled Service Fabric v. 5.3.311.9590, SDK and Tools.
Created a solution, added a stateless service. Hit F5. The exact same error is thrown.
I will now try to install on another machine with mostly the same configuration.
UPDATE2:
Installed the SDK on an identical VM, Win10, also with VS2015 Update 3. Created solution, added 1 actor, hit F5 and also on this macchine the exact error is thrown.
I tried Debug without debugging (as mentioned here) to attach later. But the application never starts. It is failed. This is the same on both the machines.
It all worked and from one day to the other it doesn't, and it's a problem that I cannot find anywhere on the net. What can this be? I found that the security updates from windows was made about the same date this happened...
I will uninstall and try again.
UPDATE3:
Uninstalling security update was not possible, but I could hide a couple of other updates. To no luck though.
From here I found this https://github.com/Azure/service-fabric-issues/issues/15 and realised I actually was very low on diskspace, and so I increased it (hyper-v manager) to 20 gigs free. But no, still the same problem.
I am in the middle of rebuilding my VPS and I am getting an error in WHM.
CENTOS 6.5 x86_64 virtuozzo – vps-1......... WHM 11.34.2 (build 8)
Reasons for blocked updates
Please correct these issues and rerun updates.
fatal: Upgrade is blocked because EXIMUP is set to 'never' in your configuration. To proceed, you can touch file '/var/cpanel/exim.unmanaged' and run the upgrade one more time. Please refer to our documentation at http://go.cpanel.net/1136UpgradeExim for more information.
The URL for help doesn't exist.
I do not see this file in when I check for it.
I found the Exim Configuration Manager but do not see anything that matches what the error states.
I have a feeling this is fairly easy fix but I am far from an expert on VPS managing. I'm learning the hard way to put it nicely...
Does anyone know how I can clear this out so I can upgrade WHM?
I see in their documentation:
To upgrade from cPanel & WHM version 11.34 and earlier:
Touch /var/cpanel/exim.unmanaged
Run the upgrade again.
What does "Touch"mean? I tried toggling the exim option in preferences but it made no difference.
After a night of fighting this I find the answer right after I post. Here is how I solved it.
Touch means to create or modify a file without actually writing to it. So in this case since the file did not exist. I created a new file in /var/cpanel/ called 'exim.unmanaged'
After placing that file in the directory I ran the updates again and it is now upgrading WHM and cPanel.
Pros know this I am sure but hopefully this will be helpful for newbi VPS admins like myself.
I recently uninstalled, then re-installed WAMP, But now my domains(zend projects) are malfunctioning. I can only access the front pages for these domains but not any further pages, which I explained in a previous thread Everything suggested on the thread and more have not worked so far.
So I have another idea from searching google which suggests that WAMP has not been completely uninstalled when I did the first uninstall, and the solution is to go to regedit after uninstall, do a search for "wamp" then delete all records related to wampserver. I'd done this but I'm getting 216-records and only three of them has a mention of "wamp" on the record names. I feel it can't be right to delete all 216-records and i'm scared because these records point to other programs and systems in windows. But this blog seems to suggest that I delete them all as below:
...into the registry. Highlight 'Computer' and press the [Ctrl][F]
key combination to launch a search box. Type in 'wamp' as a search
term. Delete all instances of a record pertaining to WampServer. On
a healthy installation, there may be 70 such entries or more. Just
grit your teeth and get it done, making sure all the while that the
search result is indeed a WampServer related entry...
I have deleted the 3-records I found with mentions of "wampserver", but yet no solution to my problem. So my question is: Could the instruction possibly be to delete the entire 216-records in order to completely clear my system of all traces of the old WAMP installation?
Removing WampServer should consist of:
stopping and uninstalling the services (wampapache and wampmysql) either with the uninstall services batch file included or on the command line
deleting the wamp folder
Bear in mind any changes to:
Your web root folder(s)
Your hosts files
Your firewall
Now, if you've done the above and have problems still, it'll likely there are other problems. Such things as different httpd configs, .htaccess files, different versions of wampserver and components like PHP and it's modules, databases and their security credentials, etc.
Check the above, and if there are more specific errors feel free to post them too.
Thanks guys for your time. I think my actions as in the OP were successful in completely uninstalling wampserver. Just that my fresh instal of WAMP was mis-behaving and not finding pages beyond the home page. It's been sorted by enabling mod_rewrite. Though I'm not quite sure what went wrong as I'd applied the same mod_rewrite severally without a resolution.