Van Der Toorn & Geertse

Auteur: Mike van der Toorn-Geertse

  • memory_limit > post_max_size > upload_max_filesize

    PHP Default: 128M > 8M > 2M

    By default, post_max_size should be 4 times greater than upload_max_filesize.
    In turn memory_limit should be 16 times greater than post_max_size

  • “Symantec Endpoint Protection has detected that there are pending system changes that require a reboot. Please reboot the system and rerun the installation.”

    When trying to install Symantec Endpoint Security the following error may show up:
    “Symantec Endpoint Protection has detected that there are pending system changes that require a reboot. Please reboot the system and rerun the installation.”

    The first step would be to reboot, but sometimes this is not possible because of important system services, or after a reboot the error still shows.
    Please try the following:

    1. Open the Windows Registry using regedit.exe.
    2. Search for the entry “PendingFileRenameOperations” in:
      • HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession Manager
    3. Restart the SEP installation; the install should finish without error.

  • Another service operation is currently in progress

    When trying to install Symantec Endpoint Protection the following error may popup:
    “Aanother service operation is currently in progress”

    Try a reboot first, if not possible or problem still exists, try the following:

    1. Open Windows Registry Editor. Click Start > Run, type regedit, and click OK.
    2. Back up the registry.
      Note: For Windows Registry backup and restore instructions, see How to back up and restore the registry in Windows.
    3. In the left pane, navigate to the following key:
      HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstaller.
    4. In the left pane, right-click on the Inprogress key, and click Delete.
    5. Click Yes to permanently delete the entire Inprogress key and all of its subkeys.

    Source: https://support.symantec.com/en_US/article.TECH218138.html

  • Default passwords

    Below we will publish default passwords we encounter.

    General (vendor):
    3Com: admin/admin
    Belkin: admin/admin
    BenQ: admin/admin
    Grandstream: admin/admin
    D-Link: admin/admin
    Digicom: user/password or admin/michelangelo
    Linksys: admin/admin
    Netgear: admin/password
    Sitecom: sitecom/admin
    Thomson: user/user
    US Robotics: admin/admin
    Zebra: admin/1234

    Specific (device):
    Brother MFC-L9570CDW: initpass
    Brother LP844: admin/1234
    Panasonic KX-UT133NE: admin/adminpass

  • Moving directory to another partition (part 1)

    Due to the fact that the primaire virtual disk (containing the Debian OS and currently the /var) of one of our customers servers is on a SSD pool and almost reaching its capacity (>75%) we need to add a second virtual disk and move the /var folder (HDD space costs less and is fast enough to serve websites and email).

    First we started with creating the new virtual disk and adding it to the VM.
    Secondly we partitioned it:
    1. Use “fdisk -l” to get the disk name (in our case vdb)
    2. cfdisk /dev/<diskname>
    3. Select new
    4. Press enter at the “Specify size in MB” to use the whole disk.
    5. “mkfs.ext4 /dev/<diskname>”
    6. “mkdir /var2”
    7. Get the UUID of the disk with the command “blkid”.
    8. “echo “UUID=<UUID> /var2 ext4 errors=remount-ro 0 1″ >> /etc/fstab”

    Next we can copy the data from /var to /var2 (we use rsync to preserve permissions).
    We are currently running the following command to make a first copy:
    “rsync -av /var/ /var2”

    The next step would be stopping all services (apache, mysql, dovecot etc.) but we will continue on this after the data has been copied (which will take a full night).

  • Change network interface on FreeNAS Jail

    Today we created a jail on our FreeNAS Server to compile a driver.
    By default the jail got a IP Address from our management network and there was no GUI option to change the network interface.

    We did the following:
    1. Stop the jail.
    2. SSH to FreeNAS server.
    3. cd to /mnt/<dataset>/jails/.<jailname>
    4. echo <interfacename> > iface
    5. echo “<ipofgateway>” > defaultrouter-ipv4
    6. warden start <jailname>

  • Proxmox storage offline due to DNS issues

    So today we encountered the error “pvestatd[1446]: storage ‘<storagename>’is not online”.

    After some trial and error the problem happened because the FreeNAS server where Proxmox was trying to mount the storage from had no working DNS server.