Hello,
in the /etc/mysql/my.cnf I configured all those proberties but not any of them is used.
Like you see for example max_connections=100 is defined as default but the max_connections value stays at 151.
Can anybody say why?
I think you did this:
Had max_connections = 151; in my.cnf (the default)
SET GLOBAL max_connections = 100;
(as shown) restarted mysqld, thereby losing the 100 and reestablishing the 151.
(as shown) saw 151.
SET GLOBAL does not persist past a restart of mysqld. Permanent changes need be put into my.cnf. (Meanwhile, you can temporarily set things with SET GLOBAL.)
Related
I am using some offset as I am running 2 nodes in one Virtual machine but looks like some port like (5672,9611,9711) are directly present so I suppose offset wont be applied to this ports and i will have to change it manually to get it work ... is their any way to optimise this so that when I apply offset it will change all the ports automatically in run time and I don't have to worry about to change it manually ?
You can add the offset to every port by adding the following configuration to the deployment.toml
[server]
offset = ""
You can refer the following documentation for more information on this
https://is.docs.wso2.com/en/latest/references/default-ports-of-wso2-products/
I have noticed in wrapper.conf file, that there is a gap in java.additional. properties:
wrapper.java.additional.5=-Dorg.glassfish.grizzly.nio.transport.TCPNIOTransport.max-receive-buffer-size=1048576
wrapper.java.additional.6=-Dorg.glassfish.grizzly.nio.transport.TCPNIOTransport.max-send-buffer-size=1048576
# Limit the Metaspace Size to protect system memory from unwanted usage
# Increase this value if you get "Java.lang.OutOfMemoryError: Metaspace" error
wrapper.java.additional.8=-XX:MaxMetaspaceSize=256m
Is this OK? I think all additional properties starting from 8 are ignored. Also, when I add new property (18, because last active property in the original file is 17) - it is ignored as well.
Yes, gaps are ok because there is a configuration option in the default wrapper.conf set to accept the gaps:
# Ignore gaps in additional properties sequence
wrapper.ignore_sequence_gaps=TRUE
Ignored options are a symptom of some other problem. Are you running in Windows as a service? There is a known permissions issues about that where auto generated properties override manually set properties: https://help.mulesoft.com/s/article/wrapper-conf-Configuration-is-not-Updated-when-Mule-Runtime-is-running-as-a-Windows-Service
In that case you need to uninstall and reinstall the Mule service.
I have this issue with chef, namely kitchen.local.yml.
It overrides kitchen.yml, that works.
But when I remove the overridden attribute, it behaves like it is not removed. It looks like it is somehow cached.
I can only change the value. This causes issues because i can't get the default attribute coming from the attributes/*.rb.
This is .kitchen.local.yml:
suites:
- name: default
run_list: [ "recipe[bbcpd-bpds-api]" ]
attributes: {
"bbcpd-bpds-api": {
"redis": {
#"host": "${REDIS_PORT_6379_TCP_ADDR:-10.0.2.2FOOO}",
### This above seems to stick even though commented out.
### Changing it FOOO to BAAR works.
### But removing keeps the BAAR appearing
### unless I `kitchen destroy` and recreate again.
}
}
I didn't find the FOOO value on host machine except for the commented out line and logs.
On the guest machine (VM), I found it in /tmp:
kitchen/dna.json:{"bbcpd-bpds-api":{"update_mode":true,"redis":{"dbIndex":"12","host":"${REDIS_PORT_6379_TCP_ADDR:-10.0.2.2FOOO}"},"storage":{"ccr":{"url":"https://ccr-dev-citc.bbcollab.com/v1","client":"BPDS-Client-Id","secret":"ABCDEFGHABCDEFGHABCDEFGHABCDEFGHABCDEFGHunzoneunzoneunzoneunzoneunzoneunzoneunzoneunzone","tokenexpiry":"60","site":"Dev","container":"DevBPDSContainer"}},"libreoffice":{"binary":"/opt/libreoffice5.4/program/soffice"}},"run_list":["recipe[bbcpd-bpds-api]"]}
kitchen/nodes/default-centos-72.json: "host": "${REDIS_PORT_6379_TCP_ADDR:-10.0.2.2FOOO}",
I am not quite sure what is the role of these, but I suspected these are somehow involved in keeping the state.
I have tried to delete /tmp but then, kitchen converge stopped working. It needed kitchen create to fix. But the ...FOOO value appeared there again.
Running kitchen destroy && kitchen create makes the value go away, but since there is no caching for the VM base image, it takes around 15 minutes, so I would like to avoid it.
Questions:
Where are these values being cached so that they stick even after removed from .kitchen.local.yml?
How can I disable/clear that caching?
This is just how it works, sorry. You have to destroy and recreate the instance to see changes in attribute settings.
When I am trying to change window scale options, as a root I am able to change the values by doing net.ipv4.tcp_mem=16777000 in /proc/sys/net/. If I have to change this 100 systems its a lot of work. SO, how can I dynamically change this value instead of manually changing it in every system?
You can try running a script to affect it all the machines .
Similar to the below :
USERNAME=someUser HOSTS="host1 host2 host3" SCRIPT="pwd; ls" for
HOSTNAME in ${HOSTS} ; do
ssh -l ${USERNAME} ${HOSTNAME} "${SCRIPT}" done
I have 300 blocks in my site and when I wanted to change the weight of a block, JavaScript crashed and now I can't make changes to any blocks. How can I make a change to a block now?
Is there a way to change admin/builds/block to show any region in 1 page?
Disable the javascript you will be able to sort your blocks again.
This worked for Drupal 7 and may work for Drupal 6: Try increasing the max_input_vars value in php.ini. Setting that value to 2000 worked in my case (Windows Server 2008/IIS/MySQL/PHP5.3 and over 200 Drupal blocks).
Troubleshooting tips for WIMP:
In php.ini, set: error_log=C:\Windows\temp\php_errors.log
In php_errors.log, look for a message such as: "PHP Warning: Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini. in Unknown on line 0"