We require help.
We are applying Service Pack 2 to AEM 6.1 and SP2 deployment failed with Error 500. Unfortunately we've started the AEM and startup failed due to missing bundles or in correct bundle dependencies. We restored AEM from backup a which we took before night but while starting we received below error.
Any help to recover the instance is appreciated.
* [FelixStartLevel] org.apache.jackrabbit.oak.plugins.nodetype.TypeEditorProvider Node type change for cq:PollConfig requires repository scan: org.apache.jackrabbit.oak.plu
gins.nodetype.NodeTypeDefDiff[
nodeTypeName=cq:PollConfig,
mixinFlagDiff=NONE,
supertypesDiff=NONE,
propertyDifferences=[
org.apache.jackrabbit.oak.plugins.nodetype.NodeTypeDefDiff$PropDefDiff[itemName=target, type=TRIVIAL, operation=MODIFIED],
org.apache.jackrabbit.oak.plugins.nodetype.NodeTypeDefDiff$PropDefDiff[itemName=source, type=MAJOR, operation=ADDED]
],
In general, whenever a node type definition is changed, OAK triggers a scan to ensure the consistency of the repository. AEM 6.1 SP2 upgrade has a few node type definition changes and depending on the size of your repository the full scan (which is basically an in-depth node traversal) could take a substantial amount of time (several hours).
The message you are seeing in the log is an INFO message and not an error. If you keep monitoring your logs, you will eventually see something like:
[FelixStartLevel] org.apache.jackrabbit.oak.plugins.nodetype.TypeEditorProvider Node type changes: [cq:PollConfig, cq:PollConfig]; repository scan took <time duaration>ms
The startup is slow and hasn't failed unless you see errors from repository scans or other causes. Post an error if you see one and it can be looked at.
You can also try running the consistency checks via oak-run tool to verify the repository state after the upgrade. Detailed instructions can be found below:
https://github.com/apache/jackrabbit-oak/tree/trunk/oak-run
Note that this tool can work on offline repositories so you don't need a running instance to check for issues.
It is also recommended to install critical hotfixes and service packs using the crx-quickstart/install folder. Leave the packages in this folder after installation as they won't reinstall after subsequent startups but deleting some packages may uninstall them.
Hope this helps.
Related
We have been running Artifactory (currently version 6.9.0) in EC2 for months now with no problems. This was originally a licensed instance of Enterprise Artifactory that we let lapse (intentionally).
Last week we started getting a storage warning (we use cluster-s3 storage) that we were at 95% utilization (which disables uploads) so we started cleaning up old artifacts (i.e., binaries, Docker images) to get the storage down. We got it down for a while, but it crept back up -- high enough this time that we couldn't ssh in, so we rebooted the machine via the EC2 Console.
It came right back with no obvious problems. Then we deleted a generic repository that someone had set up as a back up of another system (300GB) which bought us back plenty of space.
Today, a number of our builds started failing because the step to push the artifact to Artifactory failed. Upon further investigation, a number of our "generic" repositories are now appearing (and behaving) as "Docker" repositories. Further, a number of our v1 Docker repositories are now reporting as v2 Docker repos and blocking standard pushes from v1 clients.
The docs are pretty clear that we can't change the repo type, and I'm not seeing a way to migrate back to v1 from v2 Docker repos. I'm currently exporting one of the repos to see if we can import it as the right type.
Any idea what happened here? Did something get corrupted in the database? What can I even start to check?
I am getting error while restoring package from my Azure Artifacts Feed.
How I do is , I have one nuget.config file(which contains url for my Azure artifacts feed and credentials) which I am calling from nuget.exe from my build machine.
Problem is , From the same network's build machine this process is working fine. From another network's machine also packages are getting restored except one, for only one package I am getting an error here.
Error-
Errors in packages.config projects
Unable to find version '1.1.32.1' of package 'MyPackage'.
https://MyOrg:8080/tfs/MyProj/_packaging/MyFeed/nuget/v3/index.json: Error downloading 'MyPackage.1.1.32.1' from 'https://MyOrg.
56c70b71-9921-40e7-968e-1234567cfe4d/nuget/v3/flat2/MyPackage/1.1.32.1/MyPackage.1.1.32.1.nupkg'.
The HTTP request to 'GET https://MyOrg:8080/tfs/MyProj/_packaging/56c70b71-9921-40e7-968e-1234567cfe4d/nuget/v3/flat2/MyPackage/1.1.32.1/MyPackage.1.1.32.1.nupkg' has timed out after 100000ms.
What I tried -
Checked with Disabling parallel processing.
Able to browse feed's url from all the build machines(also from another network's build machine)
Checked nuget.exe version 3.5.0/4.1.0/5.5.1
Deleted all nuget cache and checked again.
Can anyone help with this ?
You can also try:
Use dotnet restore if your projects target .net core. See note here
Use the .NET Core task, which has full support for all package scenarios currently supported by dotnet, including restore, pack, and nuget push.
Check the feed and make sure it do exist valid 1.1.32.1 version of the package there.
Use Feeds I select here option to check if it makes any difference(I guess maybe this issue has something to do with your nuget.config file):
Since the tns-plugin-firebase update to version 15. When doing sidekick cloud builds I receive the message:
Unable to find a specification for Firebase/Core -> 5.5
I followed the intructions fron the community which basically tells to do pods repo update, I even rm -rf the .cocoapods folder and reinstall it.
When building locally it works, but when doing cloud builds with sidekick I received the abve mentioned message.
Is possibl that the pods repo update has to be done in the sidekick server too?, because if not I don´t have a clue why this is happening!!!
Thanks for ideas or hints.
Javier
The issue is indeed related to the Sidekick cloud build service. The pods management is done entirely on the cloud machines, even when you build from a macOS system.
Having said that, the pod is now updated to the latest available version and after a couple of hours (time needed to propagate the changes to the entire infrastructure), you should no longer experience the "Unable to find a specification for Firebase/Core -> 5.5" error while building for iOS in the cloud.
I am moving a site over to a different server to test.
getting this error
Call to undefined function field_attach_load() in my-path-to-root/my-site/includes/entity.inc on line 320
strange... if i try accessing a subdirectry http://www.mysite/randomstuff
i get this error
Fatal error: Call to undefined function user_access() in /home/borsodas3/digipowers.devserver2012.com/modules/overlay/overlay.module on line 130
Fatal error: Call to undefined function node_access_needs_rebuild() in /home/borsodas3/digipowers.devserver2012.com/sites/all/modules/taxonomy_access/taxonomy>_access.module on line 598
here are the two php.info files
going to this server [http://www.freeenergymedia.com/phpinfo-to.htm][1]
from this one [http://www.freeenergymedia.com/phpinfo-from.htm][2]
the drupal status report from the site I am migrating FROM looks like this...
Info
Drupal 7.8
OK
Access to update.php Protected
Error
CTools CSS Cache Unable to create
The CTools CSS cache directory, ctools/css could not be created due to a misconfigured files directory. Please ensure that the files directory is correctly configured and that the webserver has permission to create directories.
OK
Configuration file Protected
OK
Credit card encryption Credit card data is encrypted during checkout for maximum security.
OK
Cron maintenance tasks Last run 26 min ago
You can run cron manually.
To run cron from outside the site, go to mysite.com
OK
Database system MySQL, MariaDB, or equivalent
OK
Database system version 5.1.57-log
OK
Database updates Up to date
OK
Date API System date settings
The timezone has been set to America/New_York. The first day of the week has been set to Monday. The medium date format has been set to to F j, Y - g:ia.
Error
Drupal core update status Not secure! (version 7.12 available)
There is a security update available for your version of Drupal. To ensure the security of your server, you should update immediately! See the available updates page for more information and to install your missing updates.
OK
File system Writable (public download method)
OK
Fitvids library Installed
Fitvids Javascript Library. Download it from here, copy it to the module directory, and rename it to jquery.fitvids.js.
OK
GD library PNG support bundled (2.0.34 compatible)
OK
GD library rotate and desaturate effects bundled (2.0.34 compatible)
OK
Images Product image support has been automatically configured by Ubercart.
Error
Module and theme update status Not secure!
There are security updates available for one or more of your modules or themes. To ensure the security of your server, you should update immediately! See the available updates page for more information and to install your missing updates.
OK
Node Access Permissions 1832 permissions in use
If the site is experiencing problems with permissions to content, you may have to rebuild the permissions cache. Rebuilding will remove all privileges to content and replace them with permissions based on the current modules and settings. Rebuilding may take some time if there is a lot of content or complex permission settings. After rebuilding has completed, content will automatically use the new permissions. Rebuild permissions
OK
PHP 5.3.2 (more information)
OK
PHP extensions Enabled
OK
PHP memory limit 300M
OK
PHP register globals Disabled
Warning
Unicode library Standard PHP
Operations on Unicode strings are emulated on a best-effort basis. Install the PHP mbstring extension for improved Unicode support.
OK
Update notifications Enabled
Info
Upload progress Not enabled
Your server is capable of displaying file upload progress through APC, but it is not enabled. Add apc.rfc1867 = 1 to your php.ini configuration. Alternatively, it is recommended to use PECL uploadprogress, which supports more than one simultaneous upload.
OK
Web server Apache/2.2.3 (CentOS)
OK
cURL Enabled
The first thing I'd do is update to the latest version of Drupal Core. The error message you are seeing is coming from core, but could be from a contrib module. Update all your modules if any are as outdated as your Drupal core is. There are security issues in Drupal 7.8 and other issues which might affect your situation could well have been resolved. The current version of Drupal is 7.12 and a lot has been fixed since Drupal 7.8, which was released about 6 months ago, so you definitely want to upgrade core. Is it also possible that you are running different versions of core on the different machines? If so, the database might not be compatible, especially if you are taking a newer database (more recent modules and core) and loading it into a system with older modules/core.
After also updating other contrib modules and running update.php at appropriate times, if your problem still persists, you might want to use the "divide and conquer" method to identify which module is actually responsible. Remove groups of contrib modules and see where the problem disappears, then narrow it down to which one is causing the problem. It could also be a compatibility issue or configuration problem. Or you might have modules where the code has been updated, but update.php hasn't been run so the database isn't what it should be. You can also use tools such as the Devel module to try to track down issues, but it depends on how "broken" your site is. If you are getting "fatal errors", then you might first want to see what you can do to get past that.
I also notice you need to properly set the permissions/ownership of your files directory so that CSS caching can take place (among other tasks the webserver may be trying to do and which could also be involved in errors you are experiencing), even if not at the root of the "fatal errors".
Hope that helps some… troubleshooting can be a pain sometimes.
When I installed for the first time, I hadn`t checked "Create new database" and had the same bag but in line 321.
In drupal, keep getting an upgrade message all over site from htmlpurifier that a 4.0 is available. Ran upgrades (uploaded files and ran update.php) but still have message. No finds on this when I googled around.
Supposedly a flush.php in a maintenace folder will flush it's cache (which is invconveniently separate from the rest of Drupal's cache), but trying to execute in browser gets me an error.
Either upgrade is bad or needs cache flushed, or just shut off this message. Advice?
Did you install both the updated module and the library? The module is here while the library you should download here.