sed -i 's/nopeer/nopeer noquery/' /etc/ntp.conf ; /etc/init.d/ntpd restart; /sbin/auto-backup.sh; cat /etc/ntp.conf
Run this command in shell.
Done.
sed -i 's/nopeer/nopeer noquery/' /etc/ntp.conf ; /etc/init.d/ntpd restart; /sbin/auto-backup.sh; cat /etc/ntp.conf
Run this command in shell.
Done.
failregex = .*\[<HOST>\]:[0-9]+ .*(?:Unrouteable address|rejected)
Or, if You want to replace CPanel CPHULK by fail2ban do that:
/etc/fail2ban/jail.conf
[cpanel-iptables] enabled = true filter = cpanel logpath = /usr/local/cpanel/logs/login_log action = iptables-multiport[name=cpanel, port="21,80,443,2082,2083,2095,2096", protocol=tcp] # sendmail-whois[name=cpanel, dest=root, sender=fail2ban@example.com] findtime = 86400 bantime = 600 maxretry = 5
/etc/fail2ban/filter.d/cpanel.conf
# Fail2Ban configuration file # # Author: Widmo [Definition] # Option: failregex # Notes.: regex to match the password failure messages in the logfile. The # host must be matched by a group named "host". The tag "<HOST>" can # be used for standard IP/hostname matching and is only an alias for # (?:::f{4,6}:)?(?P<host>[\w\-.^_]+) # Values: TEXT failregex = ^<HOST>\s\-\s.*\s\[.*\].*\s(FAILED LOGIN)\s.*$ # Option: ignoreregex # Notes.: regex to ignore. If this regex matches, the line is ignored. # Values: TEXT # ignoreregex =
Save, restart fail2ban:
service fail2ban restart
Done 😉
If You see that’s errors:
Jan 21 23:52:12 torx x-session-manager[8859]: Gdk-WARNING: x-session-manager: Fatal IO error 11 (Resource temporarily unavailable) on X server :14.0.#012 Xvnc[9771]: segfault at 7fffd9e71000 ip 000000000044d31e sp 00007fffd9e6ffc0 error 6 in Xtightvnc[400000+17d000]
[20140121-23:51:06] [INFO ] starting xrdp-sessvc - xpid=8571 - wmpid=8570 [20140121-23:51:10] [INFO ] session 8569 - user root - terminated
Just:
aptitude install xfonts-100dpi xfonts-75dpi
Today I got this interesting error when deploying new VMs from a pre-defined template with customizations. Its basically failing on Setup is applying system settings part and to be precise on specialize pass of Microsoft-Windows-Shell-Setup of unattend.xml file.
Here is the screenshot:
At this point the only option is to press OK which will cause the VM to reboot, needless to say it will be constantly rebooting never taking you back to the actual login screen. Trick to get us out of this one is dating back to old XP days and SCCM troubleshooting during task sequence issues – press SHIFT – F10 ( Or F8) ! You should now have nice cmd window, navigate to C:\Windows\Panther\UnattendGC and look for file called setuperr.log, use notepad to open it up.
As you can see the god damn product key is not valid. Common issue when cloning customizations – you can end up cloning Server 2008 customizations and try to apply them onto Server 2008 R2 which will obviously fail. Only the product key seems to matter, everything else will be exactly the same between the two operating system from vCenter customizations perspective.
———
Source: http://adriank.org/vmware-windows-could-not-parse-or-process-the-unattend-answer-file-for-pass-specialize/
grub> device (hd0) /dev/sda grub> device (hd1) /dev/sdb grub> root (hd0,0) grub> setup (hd0) grub> root (hd1,0) grub> setup (hd1) grub> quit
sfdisk -d /dev/sda > partition.txt OR sfdisk -d /dev/sda | sfdisk /dev/sdb
Simple:
conf t router bgp 1234 no bgp enforce-first-as
message gone.
Just run from CLI…
for hdd in `esxcli storage core device list | grep "/vmfs/devices/disks/" | cut -d"/" -f 5`; do esxcli storage core device smart get -d $hdd; done
Kierowca: 600 mm ( Indeks: VAL575788 (VFB60) VAL567947 )
Pasażer: 450 mm / 540 mm jest ok ( Indeks: VAL575783 (VFB45) VAL567944 )
Tył: 350 mm ( Indeks: VAL574197 )
2003-2005
Turn off the engine.
Press and hold the SELECT/RESET button in the instrument panel and turn the ignition switch to run (one position before starting).
Hold the button for at least 10 seconds, until the indicator resets.
Turn the ignition off and then start the engine to verify the indicator has been reset.
2006-2010
Turn the ignition to run (one position before starting engine).
Press the SELECT/RESET knob repeatedly until the engine oil life indicator is displayed.
Press the SELECT/RESET knob for more than 10 seconds. The engine oil life indicator and the maintenance code(s) will blink.
Press the SELECT/RESET knob for more than 5 seconds. The maintenance items code(s) will disappear, and the engine oil life will reset to 100.
Turn the ignition off and then start the engine to verify the indicator has been reset.
OIL LIFE % | MESSAGE | WHAT TO DO |
---|---|---|
15% | Service Due Soon | Plan to take your vehicle to your local Honda Dealer for Service |
5% | Service Due Now | Take your vehicle to your local Honda Dealer for Service Now. |
0% | Service Past Due | Your vehicle Service is overdue. Take your vehicle to your local Honda Dealer for Service now. |
MAIN-CODE | WHAT IT MEANS: |
---|---|
A | Replace just the Engine Oil |
B | Replace the Engine Oil, Oil Filter, Inspect Front and Rear Brakes, Check the Parking Brake Adjustment, Inspect other items specific to the Vehicle |
SUB-CODE | WHAT IT MEANS: |
---|---|
1 | Rotate Tires |
2 | Replace the Air Cleaner Element, Check the Drive Belt, Replace the Dust and Pollen Filter |
3 | Replace the Transmission Fluid and Transfer Fluid (if equipped) |
4 | Replace the Spark Plugs, Replace the Timing Belt (if equipped), Inspect the Water Pump, Inspect Valve Clearance |
5 | Replace the Engine Coolant |
6 | Replace Rear Differential Fluid (if equipped) |
/etc/sysctl.conf:
net.ipv4.ip_forward = 1
sysctl -p /etc/sysctl.conf
iptables -t nat -A PREROUTING -p tcp --dport 1234 -j REDIRECT --to-ports 22