Search results

  1. N

    Trying to modify the headers - regex error?

    I am getting these results ... Reading package lists... Done W: The repository 'https://enterprise.proxmox.com/debian/pmg stretch Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8)...
  2. N

    Trying to modify the headers - regex error?

    I found another situation where the regex is causing input errors. Under the "what" action group, create a new group called "Keyword" and then choose Match Field. I want to put a two word keyword in the Match Field Value box. It won't let me. Thanks!
  3. N

    Trying to modify the headers - regex error?

    root@pmg01:~# pmgversion -v proxmox-mailgateway: 5.0-4 (API: 5.0-43/51c9b72f, running kernel: 4.13.13-1-pve) pmg-api: 5.0-43 pmg-gui: 1.0-20 proxmox-spamassassin: 3.4.1-53 proxmox-widget-toolkit: 1.0-9 pve-kernel-4.13.13-1-pve: 4.13.13-31 libpve-http-server-perl: 2.0-8 lvm2: 2.02.168-2...
  4. N

    Trying to modify the headers - regex error?

    Could this be a bug also? The negative report of spam >= 10?
  5. N

    Block spam level

    Attached. Should I assume that this is supposed to be anything 10 or higher? And also see the spam quarantine for my account, these ones in the 20s shouldn't even be quarantined right? Thanks for your attention! EDIT: It might be working, I may just be impatient. I'll keep an eye on it...
  6. N

    Block spam level

    There is a rule to block spam at level 10; however anything with a value higher than 10 is getting quarantined. Is this a bug? Shouldnt it expect to block anything higher than 10, and not just equal to 10? Thanks.
  7. N

    Trying to modify the headers - regex error?

    Im just trying to add the SPAM level to the header and I am getting these errors. What does this mean? What patten is expected? This is on PMG 5 beta. Also note that I can't even go back to the original setting "SPAM: __SUBJECT__" without it giving me these errors also. Thanks
  8. N

    Hourly Spam Report

    We are investigating the PMG and so far all is well, except you have to tell me there MUST be a way to get a report more than once / day. We have used systems like MXForce and Fusemail that make it possible for users to get a report at least every 3 hours. This is the only deal breaker we have...
  9. N

    iSCSI read only?

    Well, after discussing with our storage vendor, Nimble, we realized there was a upgrade to fix one of the commands for iscsi write! My bad, but thank you to everyone who helped!
  10. N

    iSCSI read only?

    Thanks for your help. I'm still baffled. The results from a 3.4 node look the exact same as on 4.4! I did attempt to setup the iSCSI using only one of the IPs on the Nimble and had the same result. This is driving my crazy!
  11. N

    iSCSI read only?

    OK well ... in further news, I setup a iSCSI on a different storage box, a QNAP, and it worked just fine. We use a Nimble storage box as our production iSCSI SAN and that works with 3.4 but not with 4.4. The only difference is the Nimble does multipath by default, so I'm now wondering if I'm...
  12. N

    iSCSI read only?

    Thanks for your reply! Here is a screenshot of what is happening during install of a Linux image. I tested this with PVE 3.4 to work just fine. I am going to test next with a fresh 3.4 install and doing a live upgrade into 4.4. Wish me luck!
  13. N

    iSCSI read only?

    So, PVE 3.4 iscsi = zero problems! I installed a new PVE 4.4, and setup iscsi the way I always do, but now when I try to setup a new VM, I get read only file systems, and basically can't write to iscsi. Anyone else experience this? Ideas? Thanks!
  14. N

    Dirty Cluster!

    Sorry for the delay, I ran this on two different hosts and still have this result. root@sunfire:~# service pve-cluster restart Restarting pve cluster filesystem: pve-cluster. root@sunfire:~# service pvedaemon restart Restarting PVE Daemon: pvedaemon. root@sunfire:~# pvecm nodes Node Sts...
  15. N

    Dirty Cluster!

    Here is my output... no good at all! :( root@sunfire:~# pvecm nodes Node Sts Inc Joined Name 1 M 27208 2016-03-07 15:46:24 sunfire 2 X 27212 banshee 3 X 27212 magneto 4 X 27212...
  16. N

    Dirty Cluster!

    Hello PM community! I fear I have created quite a doozy for my cluster. For months, cluster was operating just fine. I have high end switches meshed between dedicated interfaces for the LAN and SAN of my virtual cluster. The other day I went to remove a node from the cluster. I followed...
  17. N

    Insane load on PVE host

    I'm really only worried about the annual fsck check, but I guess I could disable that. :)
  18. N

    SNMP

    And I'm an idiot ... I replaced the PVE 3.x wheezy repositories with the PVE 4.x Jessie. Oops guess I'm reloading. :)
  19. N

    SNMP

    Here's a good one for you ... I was trying to install SNMP on my PVE host. I used "apt-get update", "apt-get install snmpd" and "apt-get --configure -a" to install SNMP (hopefully cleanly on my host). During the process the pvestatd and pve-cluster became offline, and now I get this error when...