Golfreeze.packetlove.com: Life style of Golfreeze Canon400D Family kammtan.com Jazz Freebsd Unix Linux System Admin guitar Music

เจอ error #1264 Out of range value adjusted for column 'ID' at row 1 ID บน board smf
แก้ไขโดย
alter table smf_ads change HITS HITS BIGINT NOT NULL default '0';

=====CRM manual  Putting cluster in maintenance mode for a maintenance activity on the SAP servers.
Many times there will be a need to do some kind of maintenance of a SAP server like OS patching, kernel upgrade, SID stacking etc.

In cases like these you might need to restart the servers but if the servers/nodes are in the cluster then the pacemaker will start migrating the services which can create a setback for the administrators. To avoid such scenarios we can simply put the cluster or a particular node in maintenance mode to avoid unwanted resource migrations.

There are three ways to achieve this depending on the situation.

Put the cluster in maintenance mode
crm configure property maintenance-mode="true"
Put the node in maintenance mode
crm node maintenance <node>
Put the node in standby mode
crm node standby <node>

==Once the activity is completed move the cluster or node out of maintenance using below commands.

Move the cluster out of maintenance
crm configure property maintenance-mode="false"
Move the node out of maintenance
crm node ready <node>
Move the node out of standby
crm node online <node>

====Most Important Commands for managing a pacemaker cluster

CRM monitoring commands-

-> crm status : Check the status of the cluster and its services.
-> crm_mon    : Live nonitoring of the cluster

CRM Node Commands

-> crm node show                : list the nodes in the cluster.
-> crm node standby <node name> : put a node on standby
-> crm node fence <node name>   : fence a particular node. (Restart)
-> crm node online <node name>  : bring a node online after standby.
-> crm node clearstate <node>   : clear a nodes state. (if in error)
-> crm node maintenance <node>  : put the node in maintenance mode. Will not affect the cluster services or resources
-> crm node ready <node>        : put the node out of maintenance

CRM Cluster Commands

-> crm cluster health           : Check the health of the cluster.
-> crm cluster start            : Start cluster services on the node.
-> crm cluster stop             : Stop cluster services on the node.
-> crm cluster restart          : Restart cluster services on the node.
-> crm cluster status           : Show cluster services on this node.

CRM Resource Commands

-> crm resource status <name>   : Check status of the resource
-> crm resource start <name>    : Start the resource.
-> crm resource stop  <name>    : Stop the resource.
-> crm resource cleanup <name>  : Cleanup the resource.(if in error)
-> crm resource migrate <name> <node> : Migrate the resource from this node to another.

==special thank you
https://www.linkedin.com/pulse/everything-you-need-know-sap-pacemaker-cluster-testing-robin-singh/

การมีระบบ SIEM ทำให้เราวิเคราะห์การโจมตีได้ก่อน บางทีจะมี log ที่เป็นลางบอกเหตุมาก่อน เมื่อเห็นทันและทำการยกระดับการป้องกันได้ทัน ปัญหาที่จะส่งผลกระทบขนาดใหญ่ และสามารถมีแนวทางการป้องกันที่ชัดเจน ก็ทำให้ความรุนแรงและผลกระทบทุเลาลงไปได้ครับ

=== Snort rule และระบบ Blueliv Threat Context สามารถจับพฤติกรรม ของ ransomware Avaddon ได้ก่อนจาก กลุ่ม ip ของ campaign นี้
ET TROJAN Win32/Avaddon Ransomware Style External IP Address Check

1.Renew cert on by generate csr file submit to Trust CA

===2.for exim & dovecot
/etc/exim.cert
/etc/exim.key
systemctl restart exim
systemctl restart dovecot

===3.for roundcube cert
===/usr/local/directadmin/conf/directadmin.conf
apachecert=/etc/httpd/conf/ssl.crt/server.crt
apachekey=/etc/httpd/conf/ssl.key/server.key

==restart httpd service
systemctl restart httpd

===4. for :2222 directadmin login 
===/usr/local/directadmin/conf/directadmin.conf
cacert=/usr/local/directadmin/conf/cacert.pem
cakey=/usr/local/directadmin/conf/cakey.pem

==restart directadmin service
systemctl restart directadmin

===== firo No funds at specified address (code -32603) how to fixed =====
No funds at specified address (code -32603)
เนื่องจาก wallet มีการย้ายตำแหน่งเมื่อทำการ โอน firo ออกจาก wallet ทำให้เหรียญตำแหน่งเคลื่อน ทำการเชคใหม่ เป็น
 
===generate new
listaddressbalances 0.01
and get line3 value to input as "feeSourceAddress”

protx update_service proTxHash ipAndPort operatorKey (operatorPayoutAddress feeSourceAddress)

==== setup snmpd for Centos 8 , Centos7
https://kifarunix.com/install-and-configure-snmp-ubuntu-18-04-and-centos-7/

===Let request point snmpd server to 103.131.22.33
Community name: packetlovehaha

==Client
103.119.22.10:199 tcp
103.119.22.11:199 tcp
103.119.22.12:199 tcp

##Install by
yum install net-snmp net-snmp-utils
systemctl enable snmpd
systemctl restart snmpd

vi /etc/snmp/snmpd.conf
rocommunity packetlovehaha 103.131.22.33
systemctl restart snmpd

===configure listen interface all for snmpd tcp 199
cd /lib/systemd/system
cp /lib/systemd/system/snmpd.service /lib/systemd/system/snmpd.service.bak
==change with vi snmpd.service
ExecStart=/usr/sbin/snmpd $OPTIONS -f tcp:127.0.0.1:199 tcp:103.119.22.10.199

===reload and restart snmpd
systemctl daemon-reload
systemctl restart snmpd

==Check Will show listen 199 on
netstat -tnlp
127.0.0.1:199
103.119.22.10.199

http.title:BIG-IP&reg:-Redirect& country:"TH" city:"Bangkok"