metasfresh v5.123 installed successfully on Ubuntu 16.04 using install script but only http://address:8080 were accessible just after installation and after reboot(s) metasfresh services doesn’t starts.
The hostname in the url has to be resolvable by your client-workstation where the browser is running.
So if your URL is http://myawesomeserver/... your client PC shall be able to ping myawesomeserver.
You might also want to checkout the Docker Installation Method.
You can run it on any system supported by docker and docker-compose and a lot of config issues that may occur are not present (due to the way docker containers work) - How to set up the metasfresh stack using Docker?
well, I install it on notebook to figure out settings and I access it internally for now before I deploy it to VPS,
I’m not fan of docker actually as matters like backup and restore will be more complicated to me.
Is the metasfresh-webui-api service running as well?
And you might want to check the apache2 reverse-proxy if it resolves correctly to the webapi-service.
well, I install it on notebook to figure out settings
We HIGHLY recommend running the server on a dedicated machine or on a VM (like eg. Virtualbox).
Removing the standalone installer with all it’s configs is unfortunately not that easy (one reason we put our main focus on docker these days).
You basically only need to dump your postgresql-database when running a Live Server.
Backing up a non critical docker-installation is even easier:
stop your containers and tarball the whole folder of your container.
Voilá - all backed up.
cd ./metasfresh-docker
docker-compose down
tar cvzf /mybackupstorage/metasfresh.tar.gz ./
yeah I understand, on VPS I will proceed with fresh install on fresh system, not by copying files.
well, I will check out docker documents to get ready before heading to VPS installation.
below are 2 errors logged by apache,
[proxy:error] AH00959: ap_proxy_connect_backend disabling worker for (localhost) for 60s
[proxy_http:error] [client 127.0.0.1:51484] AH01114: HTTP: failed to make connection to backend: localhost, referer: http://localhost/
[proxy:error] AH00940: HTTP: disabled connection for (localhost)
apache config for metasfresh already set for reverse proxy and it should work, Please advise on the above proxy errors, Thanks…
WARN 19974 --- [main] o.apache.activemq.broker.BrokerService : Store limit is 102400 mb (current store usage is 0 mb). The data directory: /opt/metasfresh/activemq-data/localhost/KahaDB only has 80894 mb of usable space - resetting to maximum available disk space: 80894 mb
WARN 9592 --- [ActiveMQ Transport: tcp://HOSTNAME/192.168.43.64:61616@58720] o.a.a.t.failover.FailoverTransport : Transport (tcp://Inspire:61616) failed, attempting to automatically reconnect
I don’t know from where this IP comes 192.168.43.64 nothing in my network have address like that.
by considering platform upgrades, kindly brief on data migration from version to another under docker deployment of metasfresh, I checked out this link about backup PostgreSQL.
Do I need only the database to restore it with later version? Please advise
sorry, not familiar yet with metasfresh and docker, my concern is to migrate data to upgraded image for metasfresh on later stage.
Usually the IP address is pulled from your primary ethernet adapter (eth0) which on a ideal environment (standalone server/dedicated VM) is assigned statically.
Rough background is that the application needs to connect to itself and also provide autogenerated configs for external clients to access. Which usually is the primary network interface.
You can change these values in metasfresh.properties located in /opt/metasfresh/ (application server) or /opt/metasfresh/metasfresh-webui-api/ (webapi server)
Generally, yes. You only need the database since all relevant data is stored in there (including some system configs, etc.). Beware though, once an update on a database is performed, you are not able to return to an older version with the same database. So a backup is highly recommended.
How you can generally perform an update is following:
cd ./metasfresh-docker #the directory containing the docker-compose.yml file
docker-compose down #stop your running metasfresh-docker
tar cvzf /my/backup/location/metasfresh.tar.gz ./ #backup
docker system prune -fa #remove docker images - you won't need them
cp -a ./docker-compose.yml ../ #copy the docker-compose.yml somewhere else so you can keep it on updating
## then follow this guide: http://docs.metasfresh.org/installation_collection/EN/How_do_I_update_metasfresh_using_Docker.html
cp -a ../docker-compose.yml ./ #put your original docker-compose.yml back in place
docker-compose up -d #pull, build and start which will automatically apply update-scripts to the database
To restore your backup simply:
cd ./metasfresh-docker
docker-compose down #stop your new metasfresh-docker version
docker system prune -fa #remove images
rm -rf ./* # just remove everything
cp -a tar cvzf /my/backup/location/metasfresh.tar.gz ./ #put the backup tarball back in place
tar xvzf ./metasfresh.tar.gz #and extract it
docker-compose up -d #pull, build and start which will automatically apply update-scripts to the database
# keep in mind all data between update and restore are lost - so you have exactly the same version as at the time you performed the backup
Of course, there are a lot of optimizations you can do with that and automatic backups and redeploys but this is a general concept of how to perform an update and restore a backup.
