I have problem viewing my hadoop userlogs files via web interface. The same log files are visible via terminal. What do you think the reason is? Thank you
Related
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 made an application with Next.js and used node.js in the api part. I had no problems using it on my own computer, but when I run it on my server in digitalocean, the photos I uploaded from the administration panel are not shown. When I check the database and directory, there is no problem. The photo is being recorded there. section is correct when I enter the site and check it. When I wear path / file.jpg it gives 404 error.
There is no problem in the previous recordings and it shows the photos. The photos do not show after running on the server.
I made folder permissions 777, but nothing else came to my mind. I didn't add code because I didn't think there was a problem with the code.
I solved the problem as follows: It started to work after defining express static files into the API.
I am setting up SolrCloud configuration for already existed solr configuration with drupal-7. I have configured zookeeper in 3 different machines and SolrCloud in 2 other machines. All the conf files are present in the configs directory in zookeeper.
Everything is fine till here but communication between drupal and Solr in not happening due to the following error.
Error: "You are using an incompatible schema.xml configuration file. Please follow the instructions in the handbook for setting up Solr."
Currently, Application is running on drupal-7 and solr-7.x-1.13 module is installed.
Till now, I didn't touch any solr configuration files in drupal server.
What else configuration I have to modify here to resolve the schema.xml incompatibility error?
I tried by configuring solrCloud using 5.4.1 and 6.4.1 version but I am getting same error.
In my case, what fixed this issue was killing the solr process and then starting solr again.
First, find the relevant solr process by trying to start solr...
cd /base/path/for/your/solr
bin/solr start
You will see something like...
Port 8983 is already being used by another process (pid: 12345)
Kill whatever process ID is mentioned in the "already being used" message...
kill 12345
Now you should be able to start solr...
bin/solr start
After this restart of solr, I refreshed the page in Drupal and the "incompatible schema.xml" message was gone.
You will have to look at the solr error logs to see what part of your schema.xml is not right.
You'd really have to do this is each one of your solr cloud nodes, since there isn't any guarantee that zookeeper uploaded the correct schema.xml on all shards, and that's why you could be getting that error.
You could use zkcli to upload your configs (https://lucene.apache.org/solr/guide/6_6/command-line-utilities.html), and then reload your collection on all nodes to apply the changes, but even then there's no guarantee it'll work.
To save time and stress, you could just use a SaaS service, such as https://opensolr.com
You can get it setup for free and you get a UI to edit your config files, upload your config files to your server, and a lot of other nice UI features to manage your solr index.
I am trying to set up thingworx composer on a Linux machine.
In the Application logs the Server is ON and db is initialized.
But when in the browser I try to open composer, then it is stuck at the landing page (the black page with Thingworx logo in green) and doesn't go to the Composer Home page.
#Tarun if you are still facing the problem, then try restarting the tomcat and db servers. Make sure that there exists 'Thingworx' folder under Tomcat install dir/webapps folder, as upon successful installation Thingworx will automatically creates a folder over there.
Considering the Thingworx directory exists, try to access the apache tomcat's catalina logs and look for any errors at the End of File.
Have you tried clearing the browser cache? If this is a migration/upgrade, you may have a prior UI cached in your browser and it is conflicting with the version you are currently trying to install.
Additionally, checking the Security Log and Application Log for any warnings or errors may provide more insight into why the server is not loading Composer.
Make sure that JAVA_HOME environment variable is set and Thingworx related folders have write permission of the user. Also, this can be caused of license problem. Make sure your license.bin file exists in ThingworxPlatform folder and platform-settings.json file is valid.
For further assistance, you can create a ticket from PTC Support.
I am facing a problem while starting the websphere message engine for one of the application deployed on websphere. This application is getting deployed automatically as a part of the installation of Websphere Lombardi 7.2 express edition. It's using websphere 7 internally to deploy it. When I try to start the message engine from the administrative console of websphere I am getting following error:
The messaging engine ProcessCenter01.twperfsvr-twperfsvr_bus cannot be started as there is no runtime initialized for it yet, retry the operation once it has initialized. For the runtime to successfully initialize the hosting server must be started, have its 'SIB service' already enabled, and dynamic configuration reload enabled. If this is a newly configured messaging engine and it is the first messaging engine to be hosted on this server, then it is most likely the 'SIB service' was not previously enabled and thus the server will need to be restarted. The messaging engine runtime might not be initializing because of an error while trying to start, examine the SystemOut.log of the hosting server to check for error messages indicating the problem.
After restarting the server, the same error shows. Can anyone help me to to find what gets loaded as a part of "initialization of runtime"? Are there any config files etc. that I need to check to solve this issue? I am suspecting some missing configuration causing error to load the runtime for this particular application.
I too faced this issue today had to delete all the files under the message store
check the directory-file path mentioned in
Application servers > server1 > Messaging engines > XXX.server1-primaryBus > File store
Just Enable the SIB Services For the particular Server.
Example:Server-->Application Server-->click on Server Name-->right hand side we can see SIB services-->Check box the Enable services.
This will solve your problem
Recently I have faced the same issue when I rebuilt the jvms in UAT envt. After searching on web I found that because of the old messages saved in the message store(flat files in my envt) the messaging engines was not getting initiated. After deleting the old messaging store and restarting the servers it got initialized.
I have struggled with this problem too.
In our situation the problem was that the file message store location was used that was already created for a different (or old) message-engine.
If you add a busmember to the service-bus and use a file store implementation, then you need to supply the path for the store and log folder. Make sure these locations don't exist yet, other wise you will run in the problem above. The message-engine for this member will use these folders.
If you have a script for creating the message-bus infrastructure, make sure that when you delete the bus or remove message-engines, that you remove the file store/log folders for these, before you re-run your script.
Another possibility is that you are using a external database as a data store, and the user that is used for the connection is not allowed to create a database. You might find a ffdc entry like this:
DB2 SQL Error: SQLCODE=-552, SQLSTATE=42502, SQLERRMC=DB2ADMIN;CREATE
SCHEMA, DRIVER=3.61.65
Then you have to go to your database administration tool and give DB2ADMIN the proper privileges. Then restart the server or cluster.
Finally this issue is been resolved. I did not create the schema in SQL Server with same name as that of the username I gave to connect SQL Server during the installation of WLE 7.2
Please find details about this at below link:
http://www.ibm.com/developerworks/forums/message.jspa?messageID=14795282