I have cluster with cloudera installed on it with all services running. I have to make one configuration change for hive(used in hive-site.xml). I have changed into machine where hive is installed.
/etc/hive/conf/hive-site.xml
I did changes in machine where hive is installed and changes gets reflected and gettign desired results.But after restarting cluster changes are getting overridden.
Please let me know what should i do here.
You should not hand edit the client hive-site.xml if your cluster is being managed by Cloudera Manager. Instead, there is a configuration you can make in Cloudera Manager that will handle the edits for you.
In Cloudera Manager go to Hive > Configuration > Service-Wide > Advanced.
Add or overrride configurations in Hive Service Advanced Configuration Snippet (Safety Valve) for hive-site.xml (your name may be different depending on your CM version).
Click Save Changes button.
Click Actions button and click Deploy Client Configuration. This will update hive-site.xml across all of your cluster hosts.
Related
I am installing pentaho 8.1 CE on ubuntu 16.04
have made change of bd from HSQLDB to Mysql, tables have been created, jackrabbit, hibernate and hibernate.
When starting the server, not login, I imagine that the users are missing or not created. ??
the error that throws me in
catalina.out
ERROR [CompositeUserRoleListService] User / Role List could not be obtained.
java.lang.IllegalStateException: Target of Bean was never resolved: org.springframework.security.core.userdetails.UserDetailsService
atorg.pentaho.platform.engine.core.system.objfac.spring.BeanBuilder$1.invoke(BeanBuilder.java:159)
at com.sun.proxy.$Proxy84.loadUserByUsername(Unknown Source)
..
..
Database Jackrabbit no created tables..
any idea?
When changing the back-end database, there's a few things you need to make sure you check.
repository.xml
quartz.properties
hibernate-settings.xml
[your-database].hibernate.cfg.xml
context.xml (in WEB-INF)
You'll need to confirm the settings for the connection to the new database has been properly configured in all of these different config files. Some additional details on how to config these files for MySQL specifically can be found in the documentation here: https://help.pentaho.com/Documentation/8.1/Setup/Installation/Archive/MySQL_Repository
Past that, make sure that you delete the "repository" directory inside of /pentaho-solutions/system/jackrabbit as this is an index of the repository. If you change your database back-end, then this index needs to be rebuilt. The index is rebuilt automatically if the server sees that "repository" directory doesn't exist at startup.
I've found the same issue on Windows Server 2016 and MySQL8.0, with Pentaho 8.0.2.
Starting Pentaho server from the start-pentaho.bat command, everything was fine.
The problem arise when I was using Tomcat.
The solution was to be sure that Tomcat service was running with the LOCAL SYSTEM account.
If the Tomcat service runs with lower privileges, maybe it can't access to the pentaho-solutions directory and it cannot load the required java beans.
if everything as per the document is configured correctly, then You might be missing the connection change in applicationContext-spring-security-hibernate.properties, please check that.
Due to some problems we changed server name and after doing this we restarted server. We found that rabbitmq service stopped and we started rabbitmq service but we lost total data related to rabbitmq and it is looking like we setup new one and cluster name also changed to new server name. Now i want to switch back to my old cluster or i want to retrieve old data. We are using windows server 2012. How to do this?
RabbitMQ by default, stores the data inside an directory based on hostname.
The default dir in widows is:
C:\Users\{youruser}\AppData\Roaming\RabbitMQ\db
In my case for example is:
C:\Users\gabriele\AppData\Roaming\RabbitMQ\db\rabbit#windowsdev-mnesia
and
C:\Users\gabriele\AppData\Roaming\RabbitMQ\db\rabbit#windowsdev-plugins-expand
Now you should have 2 directories inside C:\Users\{youruser}\AppData\Roaming\RabbitMQ\db with old-hostname and new-hostname.
You can:
stop rabbitmq
backup your old-hostname directory
delete the new-hostname directory
rename the old-hostname directory with the new-hostname
I think that you still have your data in your server.
LEt me know.
I have a web server running on a virtual machine and I need some actions (e.g. "service apache2 reload") to be performed there automatically after I'll deploy my code from Idea
Automatically -- no way AFAIK.
https://youtrack.jetbrains.com/issue/WI-3344 -- watch this ticket (star/vote/comment) to get notified on any progress.
You may also watch related tickets:
https://youtrack.jetbrains.com/issue/WI-23938
https://youtrack.jetbrains.com/issue/WI-3239
The only manual solutions I may suggest right now are:
either keep SSH console opened (IDE has it built-in) and execute such command manually once deployed
or create "Remote SSH External Tools" entry that will do such job (connect and issue specified command) manually after deployment (once created you can assign custom shortcut to it so it can be run more easier).
In both cases -- check this manual.
I am trying to deploy the MobileFirst Admin Operational console using Server Configuration Tool. Started the configuration tool as root user. Create a configuration and saved the xml. Pressed the "Deploy" button. Its failed with JVM terminated Exit code -1 error.
MobileFirst Server Version 7.1.0.0-MFPF-Server-IF201510051721
WebSphere 8.5.5.7
Installation Manager JRE:jre_7.0.7001.20140909_1712
After this error, I am able to see the Admin console application and admin services application in WebSphere. But in Configuration Tool not able to create / add runtime under this configuration. It says no configuration found.
After this error, I am able to see the Admin console application and admin services application in WebSphere. But in Configuration Tool not able to create / add runtime under this configuration. It says no configuration found.
This is not a solution to the JVM crash you experiment, but a workaround to enable to be able to add the runtime (I understand from the above description that the crash happens after the Server Configuration Tool saved the configuration and deployed it).
Go to (homeDir)/.mobilefirst_platform_server/server-configuration-tool. You should find a directory named after your configuration. In that directory, you should find a file named (ConfigName).xml. Copy this file as (ConfigName).lastdeployed (ie same name as the xml file but change the suffix). The Server Configuration Tool would have created this file after deployment completion (and uses it for later operations such as uninstall) and it uses it as an indicator that the configuration is deployed.
I have tried following this tutorial but the new password doesn't take effect after security is enabled again, still have to use old password to login as wasadmin:
http://weblogic-wonders.com/weblogic/2014/03/27/reset-websphere-admin-console-password/
I even tried the guide from IBM:
http://www-01.ibm.com/support/docview.wss?uid=swg21392427
But I'm lost at this step:
_Navigate via command prompt to /ConfigEngine
Because in my WebSphere it doesn't have this ConfigEngine folder in order the run the rest of the commands.
Can anyone help me?
EDIT: This is WebSphere 7 for Maximo 7.5
Have you tried the following?
To disable security, please perform the following steps via wsadmin:
/bin/> wsadmin -conntype NONE
wsadmin> securityoff
wsadmin> exit
Restart the servers.
Enable the security from administrative console.
Once the needed corrections are made, you can re-enable security in the admin console and then restart WebSphere.
NOTE: To restart the servers, you will first need to manually kill the java process since security is still enabled in the currently running process.
Or editing the xml file
Following this link you have 2 optiont:
This is for the standalone version
Make a backup of the security.xml file:
/config/cells/cellname/security.xml
Edit the security.xml file by searching for the first instance of " enabled= ". You should see enabled="true" as in:
Change to enabled="false".
Save the security.xml file.
Restart server1 and the WebSphere_Portal servers. If you get authentication exceptions while trying to stop the servers, you may have to manually kill the server processes and then restart them.
In the wpconfig.properties file, make the following changes:
PortalAdminId=wpsadmin
PortalAdminGroupId=wpsadmins
Refer to the Information Center link for specific instructions.
Save the wpconfig.propeties file.
Try to disable security again using the disable-security task:
./WPSconfig.sh disable-securit y
At this point, security should be disabled. You can verify by accessing the WebSphere Application Server admin console. You should be prompted for only a user name, not a password.
Follow these instructions for a clustered version:
Make a backup of the security.xml file on the Deployment Manager machine:
/config/cells/cellname/security.xml
Edit the security.xml file by searching for the first instance of "enabled= ". You should see enabled="true" as in:
Change to enabled="false".
Save the security.xml file.
Copy the security.xml file to the nodes:
/config/cells/cellname/security.xml
/config/cells/cellname/security.xml
Restart DMGR, NodeAgents, and WebSphere_Portal servers. If you get authentication exceptions while trying to stop the servers, you may have to manually kill the server processes and then restart them.
In wpconfig.properties, make the following changes:
PortalAdminId=wpsadmin
PortalAdminGroupId=wpsadmins
Refer to the Information Center link for specific instructions.
Save the wpconfig.propeties file.
Try to disable security again using the disable-security task. Note that the DMGR and the nodeagent should be running:
./WPSconfig.sh disable-security
At this point, security should be disabled. You can verify by accessing the DMGR AdminConsole. You should be prompted for only a user name, not a password.
Or more option is explained here
Note: I haven't tried this myself yet
Goto DMGR bin directory and follow the below process.
[root#localhost bin]# ./wsadmin.sh -connType NONE -lang jython
wsadmin>AdminTask.changeFileRegistryAccountPassword('-userId saddam -password saddamm')
wsadmin>AdminConfig.save()
Please restart dmgr.
If you have forgotten the password, then you have to directly kill the dmgr process id and start dmgr.
Login to WebSphere Console -> Users and Groups -> Manage Users -> click on <user_name> -> change the password value -> save the configuration.