Recent content by JTY

  1. J

    Use of AIDE, Tripwire on Proxmox VE nodes

    While I haven't used AIDE or Tripwire on Proxmox hosts, I do run Wazuh which performs similar function among other things. I've been using it for years on Proxmox and other servers without any issues.
  2. J

    [SOLVED] Node in other building keeps showing up as offline to other 2 nodes, possible corosync issues?

    What kind of network connection is there between the buildings? Are there any firewalls or other layer 3 devices in between the nodes?
  3. J

    New host with SATA

    I've had great luck with Seagate ES drives.
  4. J

    Gluster storage

    Proxmox uses libgfapi
  5. J

    Request: Please remove required email field from installer

    Look in /root/.forward, it calls the command /usr/bin/pvemailforward
  6. J

    Request: Please remove required email field from installer

    All emails sent to 'root' are forwarded to that address. So, apt notices, etc. The email address is stored in /etc/pve/user.cfg Curious, what KVM are you using? I've installed Proxmox via iLO, DRAC, IPMI, and Avocent KVMs many times, without issues.
  7. J

    apcupsd port 3551 is block? how to access to the gui ?

    apcupsd isn't a web server, so it won't work from a browser. If you want a web interface for it, you'll need to setup a web server running the apcupsd CGI scripts, http://www.apcupsd.org/manual/manual.html#apcupsd-network-monitoring-cgi-programs
  8. J

    'dd' raw drives to lvm is slow. Is there a better way?

    Add the bs parameter to dd, and set it to 64k. Example... dd if="IE11 - Win7-disk1.raw" --bs=64k|pv| dd --bs=64k of=/dev/mapper/pve-vm--103--disk--1
  9. J

    ProxMox 4.x is killing my SSDs

    FWIW, we've yet to have an Intel SSD fail in any of our nodes, or other servers for that matter. So, it is likely a problem with the SSDs themselves.
  10. J

    gluster fsyncing/closing Input/output error

    Probably best to upgrade to latest Gluster 3.7, or 3.8 from the Gluster repo. I recall some fixes recently related to issues with ZFS based bricks. That said, RedHat currently only recommends XFS for bricks.
  11. J

    gluster fsyncing/closing Input/output error

    What version of Gluster are you using? And, what file system are your bricks using?
  12. J

    Broke Server Networking Need to Manual Repair

    This is what /etc/network/interfaces looks like on one my hosts. auto lo iface lo inet loopback auto vmbr0 iface vmbr0 inet static address 192.168.1.10 netmask 255.255.255.0 gateway 192.168.1.1 bridge_ports eth0 bridge_stp off bridge_fd 0
  13. J

    Genuine Intel(R) CPU 0000 @ 2.2GHz

    Yep, http://www.intel.com/content/www/us/en/support/processors/000005567.html
  14. J

    Genuine Intel(R) CPU 0000 @ 2.2GHz

    FWIW, Proxmox with kernel 4.4.10 detects the E5-2698 V4 CPUs that are in one of my boxes. And correctly indicates they have 20 cores. processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 79 model name : Intel(R) Xeon(R) CPU E5-2698 v4 @ 2.20GHz stepping : 1...
  15. J

    what do i need to have a windows vm in proxmox

    I only install the VirtIO SCSI (block driver), and VirtIO Network. That method works for me with Server 2008R2 and 2012R2.