java.net.BindException: Address already in use
This means that you are trying to bind to a port which is already in use by another process
Try using lsof -i:<port> to determine which process is already bound to the ports that fredhopper is trying to use
FredHopper typically uses ports starting from 8180 and rising by 1000 each time, e.g. 8180, 9180, ...
In Linux the slashes have to be the other way around. In the root of your Fredhopper installation, type:
./bin/deployment-agent-client remove INSTANCE_NAME
Be sure to stop the instance before that, using the same path separator.
Interesting that you ask this question here, while it really isn't a Tridion related question (it would belong at https://superuser.com/, https://askubuntu.com, or equivalent), but I guess that is my opinion.
The answer is depending on your Linux distribution, but in general you can add the startup script to /etc/rc.local.
You can also create a full init ...
This type of architecture is perfectly possible, with files stored on some kind of shared resource across the web servers. Usually I see a NAS or SAN type device used for this purpose. Steer clear of syncing technologies - in my experience they are prone to issues.
However, these architectures are less common in Tridion deployments today. I would urge to ...
As David mentioned, one or more of the ports are already in use by some other process. So you can try to find out what that is and change its port.
Or you could just use a different "preset" for your instances in topology.txt. The presets define all of the ports for the different Fredhopper services. So for instance, the Query Server for preset 1 uses port ...
Linux systems come in more or less two main flavours: those whose startup is governed by SystemV init.d scripts, and those which use the more modern SystemD
The details of getting your services to start on startup are not really a Tridion question, but a generic Unix/Linux one. So the answer is "Yes - it is possible to automate starting a script at system ...
SDL Fredhopper has its built in web server. It does not run in an application server like Tomcat.
The instances are deployed in the [fredhopper-home]/data/instances folder, so home/ubuntu/fredhopper/data/instances in your case.
You might be confused with the SmartTarget deployment web service, this service is running in a web application server like Tomcat ...
HTTP Code 409 is a conflict. When in response to a PUT, it would typically mean that something else is already in that location.
So in this context, it seems that you already have instances with preset 1 and 2 and so cannot create new ones with those presets. You should either delete the existing instances or chose different presets for 'dev' and 'devlive'.
Thanks to Jeroen Suurd the problem was fixed.
I've made a mistake in 'dxa.service' for PIDFile, should be as follows:
After some trial and error, it seems to be working when I install java 1.7 on my linux machine, instead of java 1.8.
The Fredhopper documentation specifies that the version I wanted to install requires java 1.7 or later, but apparently, running it with java 1.8 gives issues.
you can look at following to increase PostSizeLimit key, if value is less than your required.
It entirely depends which web server you are using. For example: if you are using Tomcat, then you may want to follow the below link:
Here refer the maxPostSize property which you should be considering.
Share the specific Web Server you are using, and the community will be in better shape to help you ...
Smart target deployment webservice is only used to push the Smart target enabled components from Tridion to Fredhopper and it is not relevant to retrieve the promotions from Frdhopper. Please refer following doc for more details.
From your shared log, i noticed an issue with server IP address and hence it throws 404 error. Please provide the correct ...