I did install AM-5.1.1 and embed it on apache-tomcat-8.5.15 port:9595… looks good. I can start it.
The issue I face is regarding the Configuration Options –> Create Default Configuration.
After entering different passwords for the default OpenAM administrator, and default Policy Agent users, I get the following error:
emb.creatingfamsuffix.failure, refer to install.log under /Users/myUserName/openam for more information.
The install.log file didn’t help that much. Any idea how to solve this?
I got this error message and it was due to the iptables service not allowing the connection. Try turning off the iptables service (if you are running Linux) quickly and trying to run the configurator again. If this solves the problem, turn them back on and add a rule to allow your openam traffic.
Fixed... I had to do with OpenDj which was not installed. Did install and works fine now.
For anyone else that may come across this issue, I received this error because I had XAMPP running. Once I quit XAMPP everything was fine.
Related
I'm trying to disable the IIS localhost from Windows, without success. The only thing I'm finding is, that you have to disable the IIS option that's found in the Windows-Features. I disabled it and restarted my computer multiple times, but each time the localhost is still the default IIS...
Is there anything else I can do? I'm a complete newbie on this topic, so please tell me if there's information missing in my question.
Also tried the advice in this article, without success. The terminal does say, that the service has stopped, but localhost is still the Windows IIS. https://www.names.co.uk/support/1607-how_do_i_stop_iis_via_command_prompt_.html
Seems clearing the browser cache solved the problem.
I just installed b2c_acc_plus recipe and after it i also installed powertools B2B add on. When i am trying to access the accelerator website, i am getting a message on browser "Server Error". However strangely the Platform site is working. The server logs are also not showing any error.
I changed the host file. In HAC/Extentions all the B2C and B2B extention are showing installed.
Before installing the B2B addons the B2C sites were working, server logs are showing cronjobs for B2C & B2B. Any idea what could be problem?
In case an error is thrown, the tomcat server logs are very helpful.
Not sure how you started the application with a recipe or by executing hybrisserver.sh (on linux) in the .../hybris/bin/platform folder. You can take a look in the tomcat logfile directly in .../hybris/log/tomcat/console<date>.log file.
Without this, it's very hard to providing help.
Try to set logging level to debug and make sure you're passing site name in the URL. E.g. .../yacceleratorstorefront?site=electronics
Where did you get trainingstorefront? If you are using OOTB accelerator, it would be yacceleratorstorefront.
Please try to hit below URL and it should work.
http://localhost:9001/yacceleratorstorefront/?site=electronics&clear=true
http://localhost:9001/yacceleratorstorefront/?site=apparel-uk&clear=true
for https please change the port to 9002.
I'm trying to connect my computer to a local redhawk domain. After running omniorb4-nameserver and omniorb-eventservice services I enter the IDE and go to "launch domain" option. Then the domain manager starts successfully, but I can't connect to it. The following message appears:
Failed to connect to Domain REDHAWK_DEV
org.eclipse.core.runtime.CoreException: Error while executing callable. Caused by org.omg.CORBA.ORBPackage.InvalidName
I've already tried to erase the log files in /var/lib/omniorb and /var/lib/omniEvents, stop and start the omniorb4-nameserver abd omniorb-eventservice event services. Nothing worked. My /etc/omniORB.cfg follows the instructions in https://redhawksdr.github.io/Documentation/mainch2.html#x4-160002.3.
A similar question was proposed in REDHAWK_DEV FAILED on 2.0.0, CentOS 6.7, without any useful answer so far.
Any help is appreciated
Thanks
Check that "nameclt resolve REDHAWK_DEV/REDHAWK_DEV" results in an IOR, and that "catior IOR:XXXXX" shows an okay IP address for that IOR. This will at least determine if the domain manager is actually registering in the naming service.
Also take a look through Appendix H of the REDHAWK Manual for other troubleshooting steps.
It turns out my proxy server was blocking even local connections.
To solve the problem I had to edit /etc/environment, adding the line
no_proxy="127.0.0.1,127.0.1.1", which were the local IP's I was using, and reboot.
I just installed Winginx on fresh Windows 10 and nginx never start.
In log I have found:
CreateFile() "C:\Winginx/temp/nginx.pid" failed (2: The system cannot find the file specified)
Has anyone met with such problem before?
I found my solution by giving up and used WampDeveloper Pro Trial. Their installation goes through a check list of items to see if it will cause any problem. And the main problem that came out is the Host file is read only. Which is caused by many Firewall or Antispyware software. In my case it was Spybot.
I simply disabled the read only on my host file, and ran it again and it worked.
Although I got Winginx to work, it may not only be the host file causing the issue. It could be many more, but my WampDeveloper Pro Trial helped fix things I guess, it even check if there are other services uses Port 80 and 443 and disabled them for example. So now, my Winginx is working, that I can turn on and off and so is my WampDeveloper Pro trial, that I turn on and off. So I simply turn one of them on when I need it.
I've got hgweb up and running on II7 7 (on windows server 2008). The web interface works, and I can view, pull, and clone the repositories there. But I cannot push, doing so gives me a 502 error right after "searching for changes". Using --debug shows the last few lines as:
sending unbundle command
sending 622 bytes
HTTP Error: 502 (Bad Gateway)
I am using TortoiseHG to push, but the result is the same when using the mercurial command line.
I had followed the tutorial here: http://www.sjmdev.com/blog/post/2011/03/30/setting-mercurial-18-server-iis7-windows-server-2008-r2.aspx to setup hgweb.
Looks like an old question but someone is bound to come across it again. I was close to drawing a black circle on a wall and ... anyhow the issue for us was the way central repository was created. We cloned it from BitBucket while being Remote connected to the machine as local administrator.
The issue was in [Repository].hg folder. You need to set correct permissions on it. Try it with adding Everyone -> Full permissions for test purpose. Please make sure you change this to a dedicated network login or appropriate local account afterwards.
I was seeing the exact same behaviour - even push worked fine with exception of getting a Bad Gateway after all the time. After correct permissions were set the issue was gone.
Thinking about it now, probably the best solution is to add each network login that uses the repo to machine users and then set up access permissions to .hg folder to local users.
Hope it helps someone.
Try using the ISAPI module method instead of the CGI that executes phython.exe as documented here. There's also another related, and possibly duplicate question here as well.
Take a look at the 'Push_ssl' setting in your hgweb.config file.
I was getting the same error (had mine set to '*'), and was able to resolve it by removing the line entirely. Granted, this makes Mercurial somewhat less secure, but it lets me get by the configuration issue (for now) while I investigate properly configuring SSL on the server.
You may also have to review the 'Allow_push' setting in order to get past further errors (or take another look at your authorization).
NOTE: At least in my case, having 'push_ssl = false' wasn't enough as that resulted in further errors (authorization failed).
(Again this is simply a temporary solution until the server can be properly secured.)
It could happen by different reasons, to get more details about the error run
hg push --config ui.usehttp2=true --config ui.http2debuglevel=info
For example, problem may occur because of proxy server or just in case when the Mercurial Web Server "forgets" about repositories it needs to serve: in case if you are using TortoiseHg workbench go to Workbench UI, Repository -> Start Web Server, make sure that your repository is in the list of the served repos.
Try use https instead http in .hg/hgrc, I have resolve this problem for code.google.com.
I had this issue, and the problem ended up being the server running out of disk space.