daily_admin_issues
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| daily_admin_issues [2011/12/22 14:32] – [Daily Admin Issue] k2patel | daily_admin_issues [2021/09/21 16:13] (current) – [Force chronyc time sync] k2patel | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| * [[ sar reporting ]] | * [[ sar reporting ]] | ||
| * [[ Kernel Tuning ]] | * [[ Kernel Tuning ]] | ||
| + | * [[ inotify monitor ]] | ||
| + | * [[ Security ]] | ||
| + | |||
| + | ==== Centos 6 to 7 Upgrade ==== | ||
| + | |||
| + | I've followed [[https:// | ||
| + | But after reboot i've started seeing following error " | ||
| + | |||
| + | After looking further it appeared to the issue with " | ||
| + | After Successful reboot simply downgrade the grep package and error will disappear. | ||
| + | |||
| + | Also it is good idea to place selinux in permissive mode before you start upgrade. | ||
| + | |||
| ==== Drupal Throw watchdog error ==== | ==== Drupal Throw watchdog error ==== | ||
| Line 20: | Line 33: | ||
| ) | ) | ||
| </ | </ | ||
| - | |||
| ==== Locale Issue on Linux ==== | ==== Locale Issue on Linux ==== | ||
| Line 79: | Line 91: | ||
| touch / | touch / | ||
| | | ||
| + | </ | ||
| + | |||
| + | === Reset context on Specific Folder === | ||
| + | <code bash> | ||
| + | restorecon -Rv / | ||
| </ | </ | ||
| Line 88: | Line 105: | ||
| </ | </ | ||
| + | === Web Application can not connect to db === | ||
| + | This behavior can not get logged in audit.log some time.\\ | ||
| + | which make it harder to troubleshoot. you can manually enabled network connection for db on http context.\\ | ||
| + | |||
| + | < | ||
| + | |||
| + | <code bash> | ||
| + | setsebool -P httpd_can_network_connect_db on | ||
| + | </ | ||
| ==== Telnet IMAP Test ==== | ==== Telnet IMAP Test ==== | ||
| Line 129: | Line 155: | ||
| You are all set. | You are all set. | ||
| + | === Allow Other computer === | ||
| + | In order to allow other computer on network to access your proxy use following command. | ||
| + | <note warning> | ||
| + | |||
| + | <code bash> | ||
| + | ssh -N -f -D 0.0.0.0: | ||
| + | </ | ||
| + | |||
| + | Now setup other computer' | ||
| + | That should do it | ||
| + | |||
| + | ==== Download java using wget ==== | ||
| + | <code bash> | ||
| + | wget --no-check-certificate --no-cookies --header " | ||
| + | </ | ||
| + | |||
| + | ==== Force chronyc/ | ||
| + | <code bash> | ||
| + | chronyc -a 'burst 4/4' | ||
| + | chronyc -a makestep | ||
| + | </ | ||
| + | |||
| + | ==== Multiple BAR 13: no space for [io size 0x1000] ==== | ||
| + | |||
| + | :!: Multiple BAR 13: no space for [io size 0x1000] messages seen on RHEL guest on VMWare ESX vCenter 6.0 host at boot. | ||
| + | |||
| + | best bet is to contact vmware, but temporary fix should be as follow | ||
| + | <code bash> | ||
| + | try booting with pci=nocrs kernel command line option. | ||
| + | This parameter is used to discard ACPI resource information for various devices. | ||
| + | </ | ||
daily_admin_issues.1324564378.txt.gz · Last modified: 2020/08/10 02:29 (external edit)
