Enable OpsCenter User Login

-

                                                                         



                          Enable OpsCenter web user authentication by adding below value in file /etc/opscenter/opscenterd.conf

                                        [authentication]
                    enabled = True 


  Restart opscenter service after that




                   service opscenterd restart   




                


  The default admin username is admin and the password is admin .




                   http://opscenter-host:8888/              


   




















































Comments











Post a Comment



















Popular posts from this blog









Datastax  Error : Cassandra - Saved cluster name Test Cluster != configured name






-














Image







     While changing existing cluster name in datastax, i got name mismatch exception in log file. Process i followed was changed the cluster name in cassandra.yaml configuration file.  $ nano /etc/dse/cassandra/cassandra.yaml       cluster_name: 'Test Cluster1'            Solution :     Change the cluster name  to "New Cluster Name" :   $ cqlsh `hostname -I`   cqlsh> UPDATE system.local SET cluster_name = 'New Cluster Name' where key='local';  cqlsh> exit;   $ nodetool flush system   Stop the cluster :   $ sudo service dse stop;sudo service datastax-agent stop   Edit the file :   $ sudo vi /etc/dse/cassandra/cassandra.yaml       cluster_name: ' New Cluster Name '   Start the cluster :   $ sudo service dse start;sudo service datastax-agent start   Check Installation log :    $ cat /var/log/cassandra/output.log    Reference  : https://support.datastax.com/hc/en-us/articles/205289825-Change-Cluster-Name-     








Continue Reading »»»»










Datastax Error : Cannot start node if snitch's data center (dc1) differs from previous data center (dc2)






-














Image







     This error occurs when the node try to start and see it has snitch information which differ from previous data center. In my case, i was using DseSimpleSnitch which name the datacenter based on workload type. Previously i had enabled solr in dse default  configuration file ( /etc/default/dse ) and datasenter name was Solr. Now i tried to start the dse with graph enabled, which change the name to datacenter SearchGraph which is default workload type name.    CassandraDaemon.java:698 - Cannot start node if snitch's data center   (Solr) differs from previous data center (SearchGraph). Please fix the   snitch configuration, decommission and rebootstrap this node or use   the flag -Dcassandra.ignore_dc=true    Solution :   1) In the last line of  cassandra-env.sh  set in the jvm opts as given below :      JVM_OPTS="$JVM_OPTS -Dcassandra.ignore_dc=true"    2) If it starts successfully, execute:        nodetool repair     nodetool cleanup    








Continue Reading »»»»










Configure Nagios plugin " check_logfiles "  for scanning log file 






-















 I was checking for a nagios plugin which could filter the specified log file which i had mentioned and notify me whenever a warning or error appeared in log. Finally i get in hand check_logfile  created by Gerhard Lausser. Check_logfiles is used to scan the lines of a file for regular expressions.   Install the plugin on client system :    $ wget https://labs.consol.de/assets/downloads/nagios/check_logfiles-3.8.0.2.tar.gz   $ tar xvzf check_logfiles-3.8.0.2.tar.gz   $ cd check_logfiles-3.8.0.2/   $ ./configure   $ make   $ make install   check_logfiles executable file will get installed on location "/usr/local/nagios/libexec"    Configure Check Pattern :   $ nano  /etc/nagios-plugins/config/check_log.cfg   @searches = (    {      tag => 'Error',      logfile => '/var/logs/error.log',      criticalpatterns => 'Error',    }  );   Here i am filtering pattern "Error" from log file which i had mentioned in logfile  parameter section    C








Continue Reading »»»»















Popular posts from this blog









Datastax  Error : Cassandra - Saved cluster name Test Cluster != configured name






-














Image







     While changing existing cluster name in datastax, i got name mismatch exception in log file. Process i followed was changed the cluster name in cassandra.yaml configuration file.  $ nano /etc/dse/cassandra/cassandra.yaml       cluster_name: 'Test Cluster1'            Solution :     Change the cluster name  to "New Cluster Name" :   $ cqlsh `hostname -I`   cqlsh> UPDATE system.local SET cluster_name = 'New Cluster Name' where key='local';  cqlsh> exit;   $ nodetool flush system   Stop the cluster :   $ sudo service dse stop;sudo service datastax-agent stop   Edit the file :   $ sudo vi /etc/dse/cassandra/cassandra.yaml       cluster_name: ' New Cluster Name '   Start the cluster :   $ sudo service dse start;sudo service datastax-agent start   Check Installation log :    $ cat /var/log/cassandra/output.log    Reference  : https://support.datastax.com/hc/en-us/articles/205289825-Change-Cluster-Name-     








Continue Reading »»»»










Datastax Error : Cannot start node if snitch's data center (dc1) differs from previous data center (dc2)






-














Image







     This error occurs when the node try to start and see it has snitch information which differ from previous data center. In my case, i was using DseSimpleSnitch which name the datacenter based on workload type. Previously i had enabled solr in dse default  configuration file ( /etc/default/dse ) and datasenter name was Solr. Now i tried to start the dse with graph enabled, which change the name to datacenter SearchGraph which is default workload type name.    CassandraDaemon.java:698 - Cannot start node if snitch's data center   (Solr) differs from previous data center (SearchGraph). Please fix the   snitch configuration, decommission and rebootstrap this node or use   the flag -Dcassandra.ignore_dc=true    Solution :   1) In the last line of  cassandra-env.sh  set in the jvm opts as given below :      JVM_OPTS="$JVM_OPTS -Dcassandra.ignore_dc=true"    2) If it starts successfully, execute:        nodetool repair     nodetool cleanup    








Continue Reading »»»»










Configure Nagios plugin " check_logfiles "  for scanning log file 






-















 I was checking for a nagios plugin which could filter the specified log file which i had mentioned and notify me whenever a warning or error appeared in log. Finally i get in hand check_logfile  created by Gerhard Lausser. Check_logfiles is used to scan the lines of a file for regular expressions.   Install the plugin on client system :    $ wget https://labs.consol.de/assets/downloads/nagios/check_logfiles-3.8.0.2.tar.gz   $ tar xvzf check_logfiles-3.8.0.2.tar.gz   $ cd check_logfiles-3.8.0.2/   $ ./configure   $ make   $ make install   check_logfiles executable file will get installed on location "/usr/local/nagios/libexec"    Configure Check Pattern :   $ nano  /etc/nagios-plugins/config/check_log.cfg   @searches = (    {      tag => 'Error',      logfile => '/var/logs/error.log',      criticalpatterns => 'Error',    }  );   Here i am filtering pattern "Error" from log file which i had mentioned in logfile  parameter section    C








Continue Reading »»»»