Artifactory 3 to 6 version upgrade issue - artifactory

Migrating artifactory is throwing error like db_properties table does not exist.

Please check if you are following the below process to upgrade.
If you are on a version 3.x which is lower than 3.9.x, you first need to upgrade to 3.9.x. Please refer to this confluence page for the details.
If you are already on a version higher than 3.9.x and now trying to upgrade to version 6.x. First you need to upgrade to 6.10. This is because there are breaking changes in this version with respect to database structure etc.
Please refer to this confluence page for the complete details.
If you are following the process correctly but still encountering the issue, you may share the complete error message and version information.

Related

Is there an artifactory 7 release containing a fix for RTFACT-26825 (memory leak and timeouts using nuget-repositories)

In our company we recently upgraded to artifactory-pro:7.38.10 from version 6. To cleanup old artifacts we are using lavatory which runs an aql-search to identify the artifacts to be removed by filtering them by the date. This worked without issues our previous installation based on artifactory 6. Now after the upgrade artifactory frequently crashes with an OutOfMemoryError and the instance seems to require either significantly more memory than before or there is a memory leak. After further investigation it turned out that when problem is caused by running the aql-search and the memory usage jumps from 4 GB to over 10 GB. That's +6 GB for something that hasn't changed.
After searching for known issue I found https://www.jfrog.com/jira/browse/RTFACT-26825 which is resolved and might solve our problem but there is no version specified containing a fix. Since there is a workaround and the issue was fixed, I expect that there must be a release.
Is there already a release containing a fix?
The JIRA that you are referring to is fixed in the Artifactory version 7.38.0. So mostly, that should not be causing an issue as you are in higher version than 7.38.0.
In order to confirm, you may try the below. Add the system property to $JFROG_HOME/artifactory/var/etc/artifactory/artifactory.system.properties file and restart Artifactory for changes to take effect:
artifactory.nuget.v2.search.page.size=1000
Alternatively, you may put all the Nuget Devexpress repositories as offline. Now, check if you are encountering the memory issue. If you are not encountering this issue, maybe there is a regression issue. But according to my assumption, your server needs more resources as there are a lot of microservices introduced in Artifactory 7, when compared to Artifactory 6.
Please check if you are satisfying the resources requirement as mentioned in this page. In that case, you would need to tune your Artifactory as per this article.

The website encountered an unexpected error. Please try again later.-- Upgrading Drupal from 8.9 to 9.3.5

I am upgrading my drupal project from 8.9 to 9.3.5 but after the upgrade while hitting website one error occur i.e
The website encountered an unexpected error. Please try again later.
I followed the steps mentioned in the drupal site for upgrading drupal from 8 to 9 or (later) click here for steps but didn't work for me.
Will anyone please help me or provide proper steps to upgrade drupal from 8.9 to 9.3.5?
You should try to get more information about the error.
Add to your settings.php file:
$config['system.logging']['error_level'] = 'verbose';
and check the output on your screen again.
You may also try drush to take a look at selecting the option errors from the terminal.
drush watchdog:list
I've run into this same issue multiple times. If you haven't already done so, try going to /update.php multiple times. (It seems to clear out the update process junk/leftovers and let it work.)
Other than that, it's always some kind of file issue. (I still update manually due to my server setup.) Sometimes it was a folder/sub folder that didn't upload fully or other times it was that some module simply refused to work with the new upgrade until that was updated.

unable to bootstrap command in Marklogic 9.0-5 from roxy 1.7.3

I am trying to run bootstrap command from roxy 1.7.3 to configure Marklogic 9 database set up it showing below error
ERROR: 500 "SECURITY-BADREQUEST (err:FOER0000): Your session has been terminated
by another login. Refresh Query Console to create a new session."
ERROR: {"error":{"format-string":"SECURITY-BADREQUEST (err:FOER0000): Your sessi
on has been terminated by another login. Refresh Query Console to create a new
session."}}
Here we are using app-type=hybrid & server-version=9
Any one please suggest what need to be fix it here?
Roxy version 1.7.3 doesn't recognize server-version 9, and falls back to server-version 8 behavior, which isn't fully compatible with ML 9. You'll need to upgrade. That should be fairly straight-forward:
./ml upgrade --branch=master
HTH!
Note: there is a slight chance you might hit issues when upgrading, similar to https://github.com/marklogic-community/roxy/issues/802. Create a github ticket if you do..

Cloudera-manager 4.7

Has anyone else had trouble with the new release of Cloudera manager? '4.7' With brand clean ubuntu vm nodes it seems to be placing a file in /etc/apt/sources.list.d called cloudera-manager.list with "http://archive.cloudera.com/cm4/ubuntu/precise/amd64/cm/ precise-cm4.7.0-SNAPSHOT contrib pointed" to as the source, however this url does not exist and when ever it tries to install my nodes if fails.
Does anyone know where this url is kept on the manager so I could change it before it sends it to my nodes?
Greg,
The repository URL is constructed based on the version of the CM server that you are running. So if the server is reporting itself as "4.7.0-SNAPSHOT", then that's what the node installer will use. Now, we've not published any release that describes itself as 4.7.0-SNAPSHOT, so I'm left scratching my head as to how you got into this situation. If you still have that installation, I would recommend that you:
1) Check the reported version of the server from the Support menu at the top right.
2) Check the full package version(s) as reported by "dpkg -l | grep cloudera"
so that we can establish where the build came from.
Thanks.
PS: The installer url you reference in your update is the latest installer and not a 4.6 installer. It's the one people should use for sure.

Updating Symfony 2.0.9 the right way

I'm developing a Tool using Symfony 2. Since my Version of Symfony is a bit old, I would like to update. My current installation is the one "with vandors" and I'm using it under Win7 with XAMPP.
I feel somehow stupid, but even after searching the internet for over an hour, I didn't figure out how to update correctly to Version .15
You would be a great help, if you could give me some dumb-secure instructions on this, because all I've done so far to install or patch software was running an exe-file.
Hopefully my english was good enough to point out what my problem is, but nethertheless I excuse myself for all mistakes.
Greetings GrimReaper1908
The update steps are always given in the release announcement (see Symfony 2.0.15 released):
If you already have a project based on the Symfony Standard Edition
2.0.x, you can easily upgrade to 2.0.15 by getting the new deps and deps.lock files. Then, run the vendors script (it also clears your cache):
./bin/vendors install
If you modified deps file to include additional vendors you'll have to manually merge it with the latest Symfony one.
Vendors script requires git client to work. You'll have to install it.
Since you're on windows: Symfony2 installing vendors in Windows

Resources