I have an iRedMail installation in a Centos 6.6 VM, I'm trying to create email accounts through the database: the procedure change if you have 0.9.6 version or minor as you can read here.
Because it works with the minor's version process I know that's my case but I still don't know which version of iRedMail I have.
Someone said here that you can check it with
more /etc/iredmail-release
In fact, in the docs, for every version update you have that instruction.
Related
This question may sound absurd as I am totally new to XMPP & Openfire. I have a setup of Openfire 4.2.3 in Ubuntu 18.0.4 LTS that being used in my android chat app. During testing I received a Timeout error. While investigating the issue I found the solution rely on the XMPP updated version, check this link for more info.
Well I tried my best to find out my XMPP version and how to update it. Unfortunately I didn't find anything on it. So, I have two obvious questions here:
How to check XMPP version my Openfire is running on?
How to update XMPP version on my existing Openfire setup?
Since you are able to use the web-interface, just log in. On the start page look for the server properties. Theres the version.
For upgrading follow these steps:
To stop openfire on ubuntu: /etc/init.d/openfire stop;
Backup copy of the openfire installation directory: /usr/share/openfire;
Backup Openfire Base in Postgres: If you use the pgAdmin application, right-click on openfire base and click “Backup”. To run backup, it can be with own postgres as user. I recommend tar format, and encoding “SQL_ASCII”.
To install the new version: you can actually use the “dpkg -i” command, you will be asked if you want to keep your current version (choose this one), but you will still upgrade (option N or O - keep your currently -installed version).
On the java, has a statement informing that from version 4.3 will be necessary Java 8 installed.
Source: https://discourse.igniterealtime.org/t/update-openfire-4-1-6-to-4-2-1-in-ubuntu-server/80336
And if you really meant the "XMPP-Version". There is not really such a thing. XMPP is implemented to a different extend on different server-providers. Some have more extensions, some less.
To see which ones you have, refer to the wikipedia site:
https://en.wikipedia.org/wiki/Comparison_of_XMPP_server_software
I am running a web server based on CentOS 5.8 and I need to upgrade my version of bind to make it PCI compliant. I'm currently running bind 9.3.6 and I need to have bind 9.9.8 or higher. I've tried yum update bind but apparently I already have the latest version according to yum. I did some Googling and I found an RPM file bind-9.10.2-1.el5.i686.rpm which looks like it would work but i don't know if it should try installing it or not. I think I would need bind-devel and bind-libs which I can get from the same site. Am I better off compiling from source? I know CentOS 5 is old but I'm trying to avoid reinstalling the whole server.
Installing binary rpm's from later versions of CentOS is unlikely to work: there are many changes since CentOS5.
Rebuilding a src.rpm locally is one way to see what issues there are.
Meanwhile, upgrading to CentOS6 (at least: CentOS7 uses systemd which takes some study) is often not a whole lot more effort than retrofitting something like bind, and will have other efficiencies. YMMV, everyone's does.
I am trying to upgrade my Xcart 4.6.2 to 4.7.5. I followed the documentioan exactly as mentioned here http://help.x-cart.com/index.php?title=X-Cart:Upgrading#Upgrading_from_version_4.7.0_or_later
However the software is updated and the db remains the same. I said because when I check http://wwww.example/VERSION it says 4.7.5 and when I check http://www.example.com/include/version.php it says X-Cart DB Version: 4.6.2 GOLD.
I did the following steps :
made a development copy of live site in server.
made a fresh installation of the xcart 4.6.2 and pointed the db to the development copy
Downloaded the 4.6.2-4.7.2 upgrade package, extracted it to the root and ran the upgrade from backend. No errors.
I checked http://wwww.example.com/VERSION it says 4.7.2 and http://www.example.com/include/version.php it says X-Cart DB Version: 4.6.2 GOLD
Do you guys faced such issue? Your advises are very much appreciated. Thanks in advance.
Most likely something goes wrong while applying the sql patch (upgrade/4.6.2-4.7.2/patch.sql) because
UPDATE xcart_config SET value = "4.7.2" WHERE name = "version";
is at the very end of it.
So, please, check the following logs for anything out of the ordinary:
var/upgrade/4.6.2-4.7.2/patch.log
var/log/x-errors_sql-.php
When trying to get local data to Heroku, I am encountering a version mismatch between two different versions of pg_dump.
Specifically, I am getting this message:
pg_dump: server version: 9.2.2; pg_dump version: 9.1.4
pg_dump: aborting because of server version mismatch
I have found others with this problem, but do not know enough to implement the proposed solutions. (I am new to Ruby on Rails, PostgreSQL, Heroku, and the Mac! Very much at the stage of playing around the picking things up as I go.)
I was thinking I might simplify my life if I uninstalled all PostgreSQL on my local machine and started again with a clean install of PostgreSQL 9.2.2 from http://postgresapp.com/, but I don't know how to go about doing the uninstall.
I'm running Mac OS X Mountain Lion 10.8.2.
OS X 10.8 comes with pg_dump version 9.1.4 in the /usr/bin directory, along with psql and other programs that are client-side PostgreSQL tools. It does not mean that PostgreSQL as a server is installed (unless you have OS X Server Edition).
So you don't have to uninstall PostgreSQL because it's not installed and it's better not to remove these postgres client tools in /usr/bin because they belong to the system as shipped by Apple. They just need to be side-stepped.
The package provided by postgres.app comprises both the PostgreSQL server and the client-side tools of the same version as this server. These tools get installed in /Applications/Postgres.app/Contents/MacOS/bin
To use these instead of the 9.1 ones from Apple when you work in a Terminal, postgres.app documentation says to do:
PATH="/Applications/Postgres.app/Contents/MacOS/bin:$PATH"
and put it in your .profile file.
Once you have done that and you run pg_dump, you should no longer get the error that's it's the wrong version, because it would be the one that ships with postgres.app (currently 9.2.2).
I have this setup and it works OK for me.
If you only need to upgrade your pg_dump to the latest version and you have homebrew and mac, if the app has the latest version and your local pg doesn't:
brew upgrade postgresql
If you're using postgresapp 9.3.x, the path is different. The following worked for me (courtesy of http://sigmyers.com/blog/2013/3/12/postgres-pgdump-version-mismatch-error-postgresapp-postgresappcom)
export PG_BIN_PATH="/Applications/Postgres.app/Contents/Versions/9.3/bin/"
PATH=$PG_BIN_PATH:$PATH
Check here for the latest path: http://postgresapp.com/documentation/cli-tools.html
I'm running Mountain Lion Server. My PostgeSQL server is at version 9.2.1 and the default tools are at 9.1.5.
I had to use:
PATH="/Applications/Server.app/Contents/ServerRoot/usr/bin:$PATH"
to make it work.
Yep, sometimes if you run Postgres.app this may happen after upgrade. Make sure you restart your Postgres.app - it will update your PATH.
In my case I have postgresql installed via homebrew and the executables are here: /usr/local/opt/postgresql#9.6/bin
Or you copy the dump and restore executions to the /Applications/Postgres.app/Contents/SharedSupport folder
or in PdAgmin you point the PG bin Path (in properties -> binary Path) to the path of the executables of your postgre
Does anyone know how to install a Vista UPGRADE edition to a virtual machine? Id like to use it for testing with older versions of .NET, but it wont let me install the upgrade version. I'd rather not have to install XP and then Upgrade it. Its a licensed legal copy with CD-Key and all. It just wont install to an empty VM because its an Upgrade version.
Thanks
WARNING: The following does violate your EULA
Install Vista without using a serial number and choose the basic edition and also unselect auto activate.
After install, reinstall and now you can use your serial number and perform an upgrade.
See Paul Thurrot's site for more in depth information.