NickTheGreek

This article demonstrates how to stop receiving e-mail notifications from cron jobs. By default, when a cron job is run, cron sends e-mail notifications to the user account. To disable e-mail notifications, append >/dev/null 2>&1 to the command in the cron job. This redirects all output from the cron job to the /dev/null device. For example, the following cron job does not send e-mail notifications: 15 * * * Sun /home/username/bigtask.sh > /dev/null 2>&1 To resume receiving e-mail notifications from cron jobs, simply remove >/dev/null 2>&1 from the command. https://www.a2hosting.com/kb/developer-corner/linux/disabling-e-mail-notifications-from-cron-jobs

*If you have access to the commandline, and read access to /etc/ssh/sshd_config, run grep Port /etc/ssh/sshd_config * Run nmap -sV <hostname/ip> - which is nmap with service detection, meaning it works out what's actually listening on the port, rather than guessing the service based on the port it's using. This will give you output that looks something like: PORT STATE SERVICE VERSION 666/tcp open ssh OpenSSH 5.3p1 Debian 3ubuntu4 (protocol 2.0) If it still doesn't find the port, run nmap -p- -sV <hostname/IP> - this will scan all 65k ports - it's slower, but it will find it if it's running on a high up port. https://superuser.com/questions/152877/figure-out-non-standard-ssh-port

το είχα αμελήσει και είπα σήμερα να ασχοληθώ καθως τον Ιανουάριο που μεταπτωθηκε το forum σε WHM + CloudLinux είχα αφήσει μονη επιλογη EasyApache4 και τότε δεν υπήρχε άλλη λυση απο custom compile το αμέλησα τότε για να δω ποτε θα το υιοθετήσει και η cPanel μια και ήταν production server και είπα να αποφύγω τις δοκιμές σήμερα λοιπόν που το ξαναείδα τα πράγματα είναι αρκετά απλά: yum install memcached chkconfig memcached on service memcached start service memcached status /opt/cpanel/ea-php56/root/usr/bin/pecl install memcache service httpd restart προσθέτεις και το memcache.so στο php.ini ( local.ini για EA4) και βλεπεις stats εδώ: watch 'php -r '"'"'$m=new Memcache;$m->connect("127.0.0.1", 11211);print_r($m->getstats());'"'" μετά απλά το δηλώνεις και στο ACP που έχει λογικά ανάψει η σχετική επιλογή: επειδή κάνω χρήση memcached από IPB 2.3.x παρακαλώ και με τεράστια βελτίωση σε απόδοση κάπου έπρεπε να γίνει και εδώ, κάνει διαφορά

για τον ορισμό των RDNS / PTR θα πρέπει να ρωτήσεις τον hosting provider, συνήθως γίνεται από το Panel που παρέχεται ή μετά από συνεννόηση μαζί τους.

ωραίο άρθρο αυτο και με πολλαπλές λύσεις, για παράδειγμα: find . -type d -print0 | while read -d '' -r dir; do files=("$dir"/*) printf "%5d files in directory %s\n" "${#files[@]}" "$dir" done αλλά αυτό είναι το πιο ενδιαφέρον: du -a | cut -d/ -f2 | sort | uniq -c | sort -nr https://stackoverflow.com/questions/15216370/how-to-count-number-of-files-in-each-directory

βλεπεις την διαφορα με το εδω πχ box ? https://mxtoolbox.com/SuperTool.aspx?action=ptr%3a85.25.237.104&run=toolpage

για να μην βαζεις τις Ip εδώ ή να το παμε σε private messaging δες αν εισαι οκ αρχικα: https://mxtoolbox.com/ReverseLookup.aspx

επειδη ο παραλήπτης ειναι η Google όμως λογικά αλλού είναι το θέμα γιατί αυτοί δεν έχουν σχέση με Symantec reputation έχεις προσθέσει τα PTR/RDNS στον IP provider ? τυπικά αυτός που σου νοικιάζει τις IP

ριξε μια ματια κι εδω: http://ipremoval.sms.symantec.com/lookup/

IPS Community Suite 4.2.1 Released 07/26/2017 4.2.1 is a maintenance release to fix minor issues.

IPS Community Suite 4.2.0 Released 07/19/2017 Key Changes Version 4.2.0 is the next large release for Invision Community! We are very excited to introduce all the new features and improvements. Invision Community 4.2 is now available as a beta in the client area. The final release will be later in summer 2017. Here is the roundup of what's new in Invision Community 4.2! Highlights There's a lot of new feature in 4.2 but here are a few of the highlights: Promoting Content - A new way to promote content in your Community internally, on Facebook, and on Twitter. Clubs - Clubs are a brand new way of supporting sub-communities within your site. Many people have requested social group functionality in the past and Clubs are our implementation of this concept. Reactions - Offer more fine-grained sentiments towards content than a simple up/down or 'like'. They are now in common usage on social networks, and so users expect to be able to be more nuanced in their response to something they see. Complete Your Profile - Encourage or require members to fill out the details on their profile. Also now allows for quick registration to encourage joining. And a whole lot more.. It goes on... here is the full list! Leaderboard Enhancements Richer Embeds Group Promotion Improvement Fluid Forum View Member History Editor Uploading Improvements Authy Integration Commerce Improvements New REST API Endpoints Gallery Improvements Statistic Reporting Copy Topic to Database Downloads Index Page Blog Sidebar Promoting Content Clubs Reactions Calendar Venues Social Sign In Streamlining Calendar Add Similar Event Gallery Lightbox Navigation Letter Profile Photos SEO Improvements Device Management Delayed Deletes Calendar Event Reminders Content Messages Recommended Replies Complete Your Profile Be sure to visit each entry above for more information and screenshots. We hope you enjoy Invision Community 4.2! Release The final release will be available summer 2017. The supported, public beta is available in the client area now.

http://docs.virtuozzo.com/virtuozzo_7_upgrade_guide/upgrading-from-other-products/upgrading-from-centos-7-to-virtuozzo-7.html 6.3. Upgrading from CentOS 7 to Virtuozzo 7 Warning This procedure cannot be reverted. Physical or virtual servers running CentOS 7.x can be upgraded to Virtuozzo 7. The server must: have a clean CentOS 7.x installation without third-party drivers or packages, have ext4 file system on the root disk, meet Virtuozzo 7 system requirements, have Internet connection for downloading Virtuozzo Linux and Virtuozzo packages. To upgrade CentOS 7.x to Virtuozzo 7, do the following: Convert CentOS 7 to Virtuozzo Linux 7. To do this, download and run the upgrade script: # wget http://repo.virtuozzo.com/vzlinux/vzdeploy/vzdeploy # chmod 755 vzdeploy # ./vzdeploy The script will replace CentOS repositories and packages with Virtuozzo Linux ones, install a Virtuozzo Linux kernel in addition to the current CentOS one, and activate a trial Virtuozzo Linux license. Reboot to the Virtuozzo Linux kernel. Optionally, you can remove the CentOS kernel to make sure that the server always boots to the Virtuozzo kernel. # yum remove kernel Upgrade Virtuozzo Linux 7 to Virtuozzo 7. To do this, run the script do-upgrade-vzlin-vz7 installed with the vzlin-release package on previous steps. # do-upgrade-vzlin-vz7 --key <VZ7_product_key> You can skip license installation by specifying --skip-license instead of --key <VZ7_product_key>. In this case, you will need to install a license later with the vzlicload tool. The script will add Virtuozzo 7 repositories, install Virtuozzo 7 packages, and perform required configuration. No new partitions will be created during installation (e.g., /vz will be a directory on the root disk). Reboot the server to start using Virtuozzo 7.

or use this: http://repo.virtuozzo.com/vzlinux/vzdeploy/vzdeploy #!/bin/sh ## vzdeploy INFO # Short Description :upgrades CentOS or RHEL distro to Virtuozzo Linux # Description :removes yum repo configuration related to CentOS/RHEL, # as well as release related packages. Installs Virtuozzo Linux # release related packages and new kernel ## vzdeploy INFO version="1.0" init_vars() { log=/var/log/vzdeploy.log lock=/var/lock/vzdeploy.lck wget="/usr/bin/wget" wget_options="-q" skipkmodcheck=false skipversioncheck=false NO_ARGS=0 helpdesk="https://bugs.openvz.org" # Update checker URL checksite="http://repo.virtuozzo.com/vzlinux/vzdeploy/" checkfile="version.dat" checkurl="$checksite$checkfile" scriptname="vzdeploy" upgradeurl="$checksite$scriptname" script="vzdeploy" dry_run="0" script="$1" case "$script" in ./*) script="`pwd`/`basename $script`" ;; /*) script="$script" ;; *) script="`pwd`/$script" ;; esac } check_exit_code() { if [ $? -ne $1 ]; then echo $2; rm -f $lock; exit 1; fi; } check_pipestatus() { if [ $PIPESTATUS -ne $1 ]; then echo $2; rm -f $lock; exit 1; fi; } yesno() # $1 = Message prompt # Returns ans=0 for no, ans=1 for yes { if [ $dry_run -eq 1 ]; then echo "Would be asked here if you wanted to" echo "$1 (y/n - y is assumed)" ans=1 else ans=2 fi while [ $ans -eq 2 ]; do echo -n "Do you want to $1 (y/n) ?" ; read reply case "$reply" in Y*|y*) ans=1 ;; N*|n*) ans=0 ;; *) echo "Please answer y or n" ;; esac done } download_file() # $1 = Full URL to download # $2 = Optional basename to save to (if omitted, then = basename $1) # Also allow download to fail without exit if $2 is set { if [ "$2" = "" ]; then dlbase="`basename \"$1\"`" else dlbase="$2" fi if [ $dry_run -eq 1 ]; then echo "Would download this URL to $tmp_tree/$dlbase :" echo $1 ; echo return fi old_dlbase="$dlbase.old" if [ -f "$dlbase" ]; then rm -f "$old_dlbase" mv -f "$dlbase" "$old_dlbase" fi echo "Check for wget, install if absent..." rpm -q wget >/dev/null 2>&1 || yum install -y wget echo "Downloading $dlbase (please wait)" $wget $wget_options -O "$dlbase" "$1" if [ ! -s "$dlbase" ]; then if [ -f "$old_dlbase" ]; then mv -f "$old_dlbase" "$dlbase" fi if [ "$2" = "" ]; then echo "Failed to download $dlbase" rm -f $lock exit 1 fi fi } check_version() # Make sure that we are running the latest version # $* = Params passed to script { echo "Checking for an update to $scriptname" download_file "$checkurl" if [ $dry_run -eq 1 ]; then echo "Would check if this running script (version $version) is out of date." echo "If it's been superseded, the new version would be downloaded and you'd be asked" echo "if you want to upgrade to it and run the new version." echo return fi newversion="`cat \"$checkfile\"`" newversion="`echo $newversion`" rm -f "$checkfile" if [ "$newversion" = "$version" ]; then echo "$scriptname is already the latest version ($version) - continuing" else echo "New version ($newversion) of $scriptname detected" yesno "download and run $scriptname $newversion now" if [ $ans -eq 1 ]; then echo "OK, downloading and executing $script $*" download_file "$upgradeurl" if [ "$scriptname" -ef "$script" ]; then let a=1 else mv -f "$scriptname" "$script" fi chmod u+x "$script" echo "Download of $scriptname $newversion successful" rm -f $lock exec "$script" --skip-version-check $* error "Failed to run $script $*" else echo "New version of script is available: $upgradeurl" echo "Please download new script, review code and run it." echo "If you prefer to use current version, run it with \"--skip-version-check\" key." exit 1 fi fi } check_kernel_update_permission() { if [ -e /etc/yum.conf ] && [ -n "$(grep exclude /etc/yum.conf | grep kernel | grep -v '^#')" ]; then echo Kernel update is prohibited on your system. | tee -a $log echo Remove "exclude kernel" option from /etc/yum.conf | tee -a $log echo and run this script again. | tee -a $log rm -f $lock exit 1; fi; if rpm -q --qf '%{name}\n' `rpm -qa | grep hpahcisr` > /dev/null 2>&1 ; then echo "This server uses a binary driver hpahcisr.ko (HP AHCI Software RAID)." echo "That driver is not compatible with Virtuozzo Linux kernel." echo "We don’t know about any open source alternative for that driver." echo "The only work around known to us today is to disable RAID feature in system BIOS." echo "and configure Linux software raid instead. Such work around requires full re-install of the OS." rm -f $lock exit 1 fi if [ "$skipkmodcheck" = "false" ] ; then if rpm -q --qf '%{name}\n' `rpm -qa | grep ^kmod\-` | grep -v -e iolimits -e aacraid -e megaraid_sas -e1000e -e r8168 -e microsoft -e igb -e libs -e ^kmod$; then echo "You have third-party kernel module rpm installed (see line above)." echo "It's not compatible with Virtuozzo Linux kernel." echo "Please contact Virtuozzo Linux support at $helpdesk" rm -f $lock exit 1 fi fi if uname -r | grep -v $KERNEL_VERSION ; then echo "Your server has non-standard kernel installed (see above)" | tee -a $log echo "To resolve the issue, we can unregister this kernel RPM from RPM database." | tee -a $log echo -n "Do you want to do that [Y/N]: " | tee -a $log read YN case $YN in [yY]|[yY][eE][sS]) echo "Removing non-standard kernels from RPM database" | tee -a $log rpm -e --justdb `rpm -qa | grep kernel | grep -v $KERNEL_VERSION` 2>&1 | tee -a $log ;; *) echo "Please remove non-standard kernels manually and run this script again." | tee -a $log rm -f $lock exit 1 ;; esac fi } check_yum() { if [ ! -n "$(cat /etc/yum.conf | sed -e 's/ //g' | grep -i ^"plugins=1")" ]; then echo "Yum error: Plugins are disabled" | tee -a $log echo "Please enable yum-plugins: add string \"plugins=1\" to the /etc/yum.conf" | tee -a $log rm -f $lock exit 1; fi; } check_release() { rpm -q --whatprovides redhat-release > /dev/null 2>&1 check_exit_code 0 "There is no package providing /etc/redhat-release, please install redhat-release or centos-release first" ARCH=$(uname -i) CPU=$(uname -p) # handle 32bit xen with x86_64 host kernel if ( ! rpm -q glibc.x86_64 > /dev/null 2>&1 ) && [ "$ARCH" = "x86_64" ]; then ARCH=i386 CPU=i686 fi OS_VERSION="$(rpm -q --qf %{version} `rpm -q --whatprovides redhat-release` | cut -c 1)" if [ "$OS_VERSION" -eq "7" ]; then KERNEL_VERSION=3.10.0 VIRTUOZZO_RELEASE=http://repo.virtuozzo.com/vzlinux/migrate/7/${ARCH}/vzlinux-release-7-1.vl7.20.${CPU}.rpm VIRTUOZZO_LOGOS=http://repo.virtuozzo.com/vzlinux/migrate/7/${ARCH}/vzlinux-logos-70.0.5-4.vl7.noarch.rpm else echo "This script is for OS version 7 only" | tee -a $log rm -f $lock exit 1; fi; } backup() { BACKUP=/etc/virtuozzo-convert-saved mkdir -p $BACKUP cp /etc/redhat-release $BACKUP 2>&1 | tee -a $log # Disable RedHat if [ -f /etc/yum.repos.d/RedHat-Base.repo ]; then mv /etc/yum.repos.d/RedHat-Base.repo $BACKUP >> $log 2>&1 #test if that is the rate path fi if rpm -q rhnlib > /dev/null; then yum -y erase rhnlib >> $log 2>&1 fi if rpm -q subscription-manager > /dev/null; then yum -y erase subscription-manager >> $log 2>&1 fi if rpm -q python-vzsubscribe > /dev/null; then yum -y erase python-vzsubscribe >> $log 2>&1 fi if rpm -q redhat-logos > /dev/null; then rpm -e --nodeps redhat-logos >> $log 2>&1 fi if rpm -q redhat-release > /dev/null; then rpm -e --nodeps redhat-release >> $log 2>&1 fi if rpm -q redhat-release-notes > /dev/null; then rpm -e --nodeps redhat-release-notes >> $log 2>&1 fi if rpm -q redhat-release-server > /dev/null; then rpm -e --nodeps redhat-release-server >> $log 2>&1 fi if [ -f /etc/sysconfig/rhn/systemid ]; then mv /etc/sysconfig/rhn/systemid $BACKUP >> $log 2>&1 fi if [ -f /etc/yum/pluginconf.d/rhnplugin.conf ]; then mv /etc/yum/pluginconf.d/rhnplugin.conf $BACKUP >> $log 2>&1 fi # Disable CentOS if [ -f /etc/yum.repos.d/CentOS-Media.repo ]; then mv /etc/yum.repos.d/CentOS-Media.repo $BACKUP >> $log 2>&1 fi if [ -f /etc/yum.repos.d/CentOS-Base.repo ]; then mv /etc/yum.repos.d/CentOS-Base.repo $BACKUP >> $log 2>&1 fi if rpm -q centos-release > /dev/null; then rpm -e --nodeps centos-release >> $log 2>&1 fi if rpm -q centos-release-notes > /dev/null; then rpm -e --nodeps centos-release-notes >> $log 2>&1 fi # Disable Scientific Linux if [ -f /etc/yum.repos.d/sl.repo ]; then mv /etc/yum.repos.d/sl.repo $BACKUP >> $log 2>&1 fi if [ -f /etc/yum.repos.d/cd.repo ]; then mv /etc/yum.repos.d/cd.repo $BACKUP >> $log 2>&1 fi if rpm -q sl-release > /dev/null; then rpm -e --nodeps sl-release >> $log 2>&1; fi if rpm -q sl-release-notes > /dev/null; then rpm -e --nodeps sl-release-notes >> $log 2>&1; fi } prep() { yum clean all 2>&1 | tee -a $log rpm --import http://repo.virtuozzo.com/vzlinux/security/VZLINUX_GPG_KEY >> $log 2>&1 rpm --import http://repo.virtuozzo.com/vzlinux/security/VIRTUOZZO_GPG_KEY >> $log 2>&1 rpm -Uvh $VIRTUOZZO_RELEASE $VIRTUOZZO_LOGOS --force >> $log 2>&1 ; # Handle LES if [ -x /usr/local/sbin/les ]; then LES=true /usr/local/sbin/les -da 2>&1 | tee -a $log check_pipestatus 0 "Unable to turn off LES, please contact Virtuozzo Linux support at $helpdesk" fi } check_source() # We need to install kernel-devel for virtual containers { NEED_SOURCE="NO" if ! rpm -q pciutils > /dev/null 2>&1; then yum -y install pciutils fi if [ -x /sbin/lspci ] ; then if $(/sbin/lspci -n | grep -q 1414) || $(/sbin/lspci -n | grep -q 15ad) || $(/sbin/lspci -n | grep -q 1ab8); then NEED_SOURCE="YES" fi fi } check_root() # Root device link { if [ ! -e /dev/root ]; then if grep -q ^/ /etc/fstab; then ln -s `awk '{ if ($2 == "/") print $1; }' /etc/fstab` /dev/root fi fi } check_efi() { if [ -f /boot/efi/EFI/redhat/grub.conf ] ; then if [ "$(readlink /etc/grub.conf)" != "/boot/efi/EFI/redhat/grub.conf" ] || [ "$(readlink /boot/grub/grub.conf)" != "/boot/efi/EFI/redhat/grub.conf" ]; then ln -sf /boot/efi/EFI/redhat/grub.conf /etc/grub.conf ln -sf /boot/efi/EFI/redhat/grub.conf /boot/grub/grub.conf fi fi if [ -f /boot/efi/EFI/centos/grub.conf ] ; then if [ "$(readlink /etc/grub.conf)" != "/boot/efi/EFI/centos/grub.conf" ] || [ "$(readlink /boot/grub/grub.conf)" != "/boot/efi/EFI/centos/grub.conf" ]; then ln -sf /boot/efi/EFI/centos/grub.conf /etc/grub.conf ln -sf /boot/efi/EFI/centos/grub.conf /boot/grub/grub.conf fi fi } print_help() { cat << EOF >&2 Usage: -h, --help Print this message --skip-kmod-check Skip check for unsupported kmods --skip-version-check Do not check for script updates EOF } # Start here ################################################################ init_vars $0 check_release check_yum if [ -f $lock ] ; then if [ -d /proc/$(cat $lock) ] ; then echo "$scriptname is already running" exit 1 fi fi echo $$ > $lock check_exit_code 0 "Please run $scriptname as root" options=`getopt -o ecmik: -l help,skip-kmod-check,skip-version-check -- "$@"` if [ $? != 0 ] ; then print_help ; rm -f $lock; exit 1 ; fi eval set -- "$options" while true; do case $1 in --help) print_help rm -f $lock exit 0 ;; --skip-kmod-check) skipkmodcheck=true shift ;; --skip-version-check) skipversioncheck=true shift ;; --) shift break ;; -*) echo "$0: error - unrecognized option $1" 1>&2 print_help rm -f $lock exit 1 ;; *) echo "Internal error!" ; rm -f $lock; exit 1 ;; esac done if [ "$skipversioncheck" = "false" ]; then check_version fi yesno "continue with deploy" if [ $ans -eq 1 ]; then conversion=true echo "Deploy started" else conversion=false fi if [ "$conversion" = "true" ] ; then backup prep check_kernel_update_permission check_source check_root yum clean all 2>&1 | tee -a $log # if rpm -qf --queryformat "%{name}" /lib/modules/$(uname -r) > /dev/null 2>&1 ; then # KERNEL=$(rpm -qf --queryformat "%{name}" /lib/modules/$(uname -r)) # else # KERNEL=kernel # fi KERNEL=vzkernel echo "kernel flavour $KERNEL" >> $log PKGS="vzlinux-release" KPKGS="$KERNEL" if rpm -qa | grep -q kmod > /dev/null 2>&1 ; then for kmod in `rpm -q --qf '%{name}\n' $(rpm -qa | grep ^kmod\-) | grep -v x86_64 | grep -v i686 | grep -e e1000e -e aacraid -e r8168 -e microsoft -e igb`; do rpm -e --justdb $kmod --nodeps PKGS="$PKGS $kmod" done fi if [ $NEED_SOURCE = "YES" ] ; then PKGS="$PKGS gcc make"; KPKGS="$KPKGS $KERNEL-devel"; fi if rpm -q subscription-manager 2>&1 > /dev/null; then echo "Uninstalling subscription-manager..." | tee -a $log yum -y erase subscription-manager fi rpm -e --nodeps cpuspeed > /dev/null 2>&1 yum -y --disablerepo=* --enablerepo=virtuozzolinux-base --enablerepo=virtuozzolinux-updates --disableexcludes=main install $PKGS 2>&1 | tee -a $log check_pipestatus 0 "Unable to install required packages, please contact Virtuozzo Linux support at $helpdesk" yum -y --disablerepo=* --enablerepo=virtuozzolinux-base --enablerepo=virtuozzolinux-updates --disableexcludes=main install $KPKGS 2>&1 | tee -a $log check_pipestatus 0 "Unable to install required packages, please contact Virtuozzo Linux support at $helpdesk" yum -y --disablerepo=* --enablerepo=virtuozzolinux-base --enablerepo=virtuozzolinux-updates --exclude=kernel* update 2>&1 | tee -a $log check_pipestatus 0 "Unable to update packages, please contact Virtuozzo Linux support at $helpdesk" if [ -e /sys/firmware/efi ]; then # Bootloader for the previous system is probably dead by now. # Generate new grub config and create the new EFI boot entry. # It would be nice to remove the previous EFI entry as well, but we don't know which one it is... grub2-mkconfig > /boot/efi/EFI/virtuozzo/grub.cfg efidir_part="$(grub2-probe --target=device --device-map= /boot/efi)" efidir_part_num="$(echo "$efidir_part" | sed 's/^[^0-9]*//')" efidir_disk="$(echo "$efidir_part" | sed 's/[0-9]\+$//')" efibootmgr -c -L VirtuozzoLinux -d "$efidir_disk" -p "$efidir_part_num" -l /EFI/virtuozzo/shim.efi fi # Packages present in VzLinux installation from ISO VZL_PKGS="vllicutils libreport-plugin-vzlinux-bugs kpatch bzip2 firewalld teamd" yum -y --disablerepo=* --enablerepo=virtuozzolinux-base --enablerepo=virtuozzolinux-updates --disableexcludes=main install $VZL_PKGS 2>&1 | tee -a $log check_pipestatus 0 "Unable to install vllicutils and other VzLinux-specific packages, please contact Virtuozzo Linux support at $helpdesk" fi if [ "$LES" = "true" ]; then echo "Linux Environment Security was disabled, you can re-enable it if needed" fi echo "Installing a trial license..." vllicupdate -a trial echo "You can find complete log in $log" rm -f $lock exit 0

Hi, I was now able to reproduce and document the steps needed to go from CentOS 7 -> Virtuozzo Linux 7 -> Virtuozzo 7. You need to install CentOS 7 your prefered way with /vz ext4 partition (I made all partions ext4, as the Virtuozzo 7 Bare Metal installer does). First the steps to convert CentOS 7 (minimal) to Virtuozzo Linux 7 with vzdeploy: cd /root yum install wget wget http://repo.virtuozzo.com/vzlinux/vzdeploy/vzdeploy chmod 700 vzdeploy ./vzdeploy This takes some time and finishes without interaction needed. At the end you'll see: ----- Complete! Installing a trial license... Start activation for code trial... License VZLINUX [*****] was loaded successfully. Calling 0 sh: 0: command not found Subscription completed unsuccessfully Activation completed successfully with product key ***** You can find complete log in /var/log/vzdeploy.log ----- Pavel told me that this licence is only needed for some features, that are only available in the commercial version. As far as I can see, the licence is no longer installed after conversion to Virtuozzo 7 is done. The next step is adding the Virtuozzo 7 repositories to yum. Note that the factory repository is enabled for my test, but with lower priority than the release repository. I need to check what have been the original settings of the bare metal installer before setting up a production system. echo "# These repositories are for internal use by developers only # Enable them on your own risk!!! [factory] name=Build Factory packages for Containers mirrorlist=http://download.openvz.org/virtuozzo/mirrorlists/7.0/factory-os.mirrorlist #baseurl=http://download.openvz.org/virtuozzo/factory/x86_64/os/ priority=49 enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Virtuozzo-7 [factory-debuginfo] name=Debug packages for Containers from Build Factory mirrorlist=http://download.openvz.org/virtuozzo/mirrorlists/7.0/factory-debug.mirrorlist #baseurl=http://download.openvz.org/virtuozzo/factory/x86_64/debug/ priority=49 enabled=0 gpgcheck=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Virtuozzo-7" > /etc/yum.repos.d/factory.repo echo "[openvz-os] name=OpenVZ mirrorlist=http://download.openvz.org/virtuozzo/mirrorlists/7.0/releases-os.mirrorlist #baseurl=http://download.openvz.org/virtuozzo/releases/7.0/x86_64/os/ enabled=1 gpgcheck=1 priority=50 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Virtuozzo-7 [openvz-updates] name=OpenVZ Updates mirrorlist=http://download.openvz.org/virtuozzo/mirrorlists/7.0/updates-os.mirrorlist #baseurl=http://download.openvz.org/virtuozzo/updates/7.0/x86_64/os/ enabled=1 gpgcheck=1 priority=50 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Virtuozzo-7 [openvz-os-debuginfo] name=OpenVZ os Debug packages mirrorlist=http://download.openvz.org/virtuozzo/mirrorlists/7.0/releases-debug.mirrorlist #baseurl=http://download.openvz.org/virtuozzo/releases/7.0/x86_64/debug/ enabled=0 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Virtuozzo-7 [openvz-updates-debuginfo] name=OpenVZ updates Debug packages mirrorlist=http://download.openvz.org/virtuozzo/mirrorlists/7.0/updates-debug.mirrorlist #baseurl=http://download.openvz.org/virtuozzo/updates/7.0/x86_64/debug/ enabled=0 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Virtuozzo-7" > /etc/yum.repos.d/openvz.repo We now fetch the lists of the available packages: yum update That will import the required GPG key, you have to allow it, when seeing this message: ------ warning: /var/cache/yum/x86_64/7/factory/packages/openvz-logos-70.0.11-1.vz7.noarch.rpm: Header V4 RSA/SHA1 Signature, key ID 44cdad2a: NOKEY Public key for openvz-logos-70.0.11-1.vz7.noarch.rpm is not installed openvz-logos-70.0.11-1.vz7.noarch.rpm | 298 kB 00:00:00 Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Virtuozzo-7 Importing GPG key 0x44CDAD2A: Userid : "Virtuozzo Team (GPG key signature for packages) <security@xxxxxxxxxxxxx>" Fingerprint: c92b bb23 e3c3 1386 6694d5f5 ca0b 7d19 44cd ad2a Package : 1:vzlinux-release-7-1.vl7.15.x86_64 (@virtuozzolinux-base/7.1.0) From : /etc/pki/rpm-gpg/RPM-GPG-KEY-Virtuozzo-7 ------ As Pavel said (thank you very much for the hint) we can use yum groups to install all required packages: yum grouplist | grep -i virtuozzo returns in my case: Virtuozzo Virtuozzo Containers Virtuozzo Hypervisor Then install the groups yum groupinstall 'Virtuozzo' 'Virtuozzo Containers' 'Virtuozzo Hypervisor' Finally reboot to run Virtuozzo 7. Regards Volker https://marc.ttias.be/openvz-users/2016-08/msg00027.php

EasyApache cPanel & WHM installs EasyApache 4 (Home >> Software >> EasyApache 4) by default. If you wish to use EasyApache 3 (Home >> Software >> EasyApache 3) instead, create the /etc/install_legacy_ea3_instead_of_ea4 touch file before you begin the cPanel & WHM installation process. If your chosen version of EasyApache fails to build, the installer will continue and you must troubleshoot the issue. Note: If your system runs CloudLinux™, the system installs the CloudLinux EasyApache 4 repository and the default CloudLinux profile. Systems that do not run CloudLinux install cPanel & WHM's EasyApache 4 repository and default profile. https://documentation.cpanel.net/display/ALD/Installation+Guide+-+Customize+Your+Installation

How to install EasyApache 3 on cPanel & WHM 58?. You all know that the fresh installations of cPanel & WHM 58 come with EasyApache 4 as the default web stack. However, EasyApache 3 is not completely removed out of cPanel as of now and therefore you’ll still be able to use it if you prefer. In this tutorial, I will explain how to install EasyApache 3 on cPanel & WHM 58. Install EasyApache 3 on cPanel & WHM 58 We have to consider two different scenarios while dealing with this. Before cPanel installation. After cPanel installation. Before cPanel installation Consider you have a fresh server and about to start the cPanel installation. In this case, you just need to create a file named “install_legacy_ea3_instead_of_ea4” under “/etc” before you begin the cPanel & WHM installation process. I.e, touch /etc/install_legacy_ea3_instead_of_ea4 Now you can start the cPanel installation by following the steps given below. yum update cd /home/ wget -N http://httpupdate.cpanel.net/latest sh latest Just wait for the cPanel installer script to complete its installation and once it’s done, you can access the WHM panel with the following URL. http://your-server-ip:2086 OR http://your-host-name:2086 After cPanel installation Suppose you have already installed cPanel and WHM with EasyApache 4 on your server and wish to switch back to EasyApache 3, please follow the steps given below. mkdir -p /usr/local/apache.ea3/{conf,htdocs,bin} Then run the following command. /scripts/migrate_ea3_to_ea4 --revert --run This will migrate EasyApache4 to EasyApache3. If you run into any errors related to Apache after migrating, just compile EasyApache 3 once and this will fix all issues. That’s it. Note: As per the cPanel team, the last version of cPanel & WHM to support EasyApache 3 will be version 62. Once version 62 goes End of Life in January of 2018, EasyApache 3 will receive no further updates and will be fully deprecated. EasyApache 3 will be fully removed from cPanel & WHM version 64. So, if you are running EasyApache 3, you will be blocked from upgrading to v64 of cPanel & WHM. https://thegeeksalive.com/how-to-install-easyapache-3-on-cpanel-whm-58/

installserveros.com Install your server now... This tool will install an operating system on a physical server (or anything 32/64-bit compatible, not vServers/VPS) that has an IPv4 addressable IP. The only requirements are that the server is in a recovery or rescue mode and accessible via SSH. The block devices must NOT be mounted or assembled in RAID. To run an installation, please enter the information below:

find -type d -links 2 -exec mkdir -p "/path/to/backup/{}" \; https://askubuntu.com/questions/365877/copy-only-folders-not-files

α ναι τα ειχα φτιαξει μονος μου αυτα μετα

μονο σε IPB 3.x εχω δεί τέτοια θεματα, και ποτέ μα ποτέ σε phpBB

το εχουμε ξαναδει αυτο σε Vesta panel: CONFIGURATION ERROR defaults.inc.php was not found. Και ειναι θεμα Permission chmod 755 /etc/roundcubemail/db.inc.php ή και: chmod 644 /etc/roundcubemail/defaults.inc.php και μετά: https://forum.vestacp.com/viewtopic.php?t=7497

συμβαίνει και στις καλύτερες οικογένειες, δεν έχει φανεί ακόμη το domain και πρέπει να στηθεί προκαταβολικά αλλά το WHM box επιστρέφει το ακόλουθο: Could not determine the nameserver IP addresses for “{your domain}”. Please make sure that the domain is registered with a valid domain registrar. Να η λύση, αλλαγή στο : /var/cpanel/cpanel.config allowunregistereddomains=0 σε allowunregistereddomains=1 και επαναφορά μετά https://stackoverflow.com/questions/30255853/cpanel-could-not-determine-the-nameserver-ip-addresses-for

for cPanel / WHM based WebMail (Horde) Sometimes Horde won’t work after a cpanel update. You may receive below error, while accessing Horde. HTTP error 503 The service is unavailable. Horde is unavailable while the system is setting the hostname. Solution 1: 1. Make sure hostname is correct. /usr/local/cpanel/scripts/check_valid_server_hostname Solution 2: 1. ssh in to the server. 2. cd /var/cpanel/.application-locks 3. rm UpdateHostname\:USERNAME 4. /usr/local/cpanel/bin/update_horde_config –user=USERNAME https://techsemi.wordpress.com/2016/11/08/horde-is-unavailable-while-the-system-is-setting-the-hostname/ https://forums.cpanel.net/threads/horde-wont-load-after-update-to-11-52.503071/

There are many free online tools which you can use to test the vulnerability of your web application. Try using http://www.zubrag.com/tools/sql-injection-test.php to test SQL Injection vulnerability http://www.parosproxy.org : web traffic recorder, web spider, hash calculator, and a scanner for testing common web application attacks such as SQL injection and cross-site scripting HP WebInspect software [ not free ] tests common web attacks such as parameter injection, cross-site scripting, directory traversal, [ try googling it ] http://portswigger.net/suite/ : Burp Suite is an integrated platform for attacking web applications. It contains all of the Burp tools with numerous interfaces between them designed to facilitate and speed up the process of attacking an application. All tools share the same robust framework for handling HTTP requests, persistence, authentication, upstream proxies, logging, alerting and extensibility. https://stackoverflow.com/questions/2351315/testing-for-security-vulnerabilities-in-web-applications-best-practices

by Arunlal Ashok · May 24, 2015 Is it possible? A back-end option to enable SPF and DKIM for already created cPanel accounts? In cPanel, backend scripts are available to enable SPF and DKIM for all accounts that are already created without enabling email authentications, SPF and DKIM. We have already discussed “How to enable SPF and DKIM automatically for all newly creating accounts?“. That’s simple, right! Enabling this features in the DNS will increase the reputation of all emails sent out from that account (domain). SPF stands for “Sender Policy Framework”, it’s a TXT record to the domain DNS. DKIM stands for “Domain Keys Identified Mail”, DKIM is an authentication protocol that is used by email receivers to determine original ownership of that email. In a DKIM enabled domain, an encrypted digital signature will add to all emails sent out from that domain which will help to identify the originality of that email. cPanel script to enable SPF via commandline: Syntax # /usr/local/cpanel/bin/spf_installer $username Where, $username is the cPanel user name. cPanel script to enable DKIM via commandline: Syntax # /usr/local/cpanel/bin/dkim_keys_install $username Replace $username with the actual cPanel username. The above commands will help you to enable email authentications for single cPanel users. If you have hundreds of accounts and you want to enable SPF and DKIM for all accounts, please follow the simple for loop. Here we can get the cPanel usernames from “/var/cpanel/users”. Then give that to installations scripts. Please see the sample script below: Script for username in `ls -A /var/cpanel/users` ; do /usr/local/cpanel/bin/dkim_keys_install $username && /usr/local/cpanel/bin/spf_installer $username ; done That’s it! wait for a while, it’ll set all. https://crybit.com/enabling-email-authentication/