Search results

It appears the ClamAV 1.0.9 updates (and many others) have finally been released in the Debian standard repos.

Try the following: In /etc/pmg/templates/main.cf.in - instead of changing the myhostname setting (revert back to original), add below it a new line with: myorigin = $mydomain so it will look like this: ... myhostname = [% dns.hostname %].[% dns.domain %] myorigin = $mydomain ... Careful, you...

Thank you for that.

I am a bit embarrassed to ask this but I still can't figure out how to query easily on command line the PBS version? Yes, it's easy via GUI but like the other Proxmox tools have their own command for this query, I wonder how to check this on PBS? Thanks for any pointer.

Our ratio is about 60% affected, across Adaptec controller models 8405, 8805 and 81605Z. All controllers are on their latest firmware version. We have updated the affected systems with the patched kernel and so far (over night) all have been stable and not shown the former issue so that looks...

I have found this thread only an hour ago after we realised to be affected by the issue ("aacraid: Outstanding commands on ...") at random times. It's Christmas time and here in NZ this is holiday season so we upgraded various servers with different Adaptec RAID controllers (models 8405, 8805...

Yes! So sorry if I created confusion here. I meant the whole time the "no subscription" repo when writing "test" repo. Definitely a mistake here at my end.

You can and are allowed to run OMG in production with using the test repository. You do not need to pay a subscription to get access to the enterprise repo but in doing so, you take some risks that you need to deal with yourself. The test repository will contain at times test versions for some...

So you have a too old version hence the issue. You stated that your server is "not a test server" so I assume you mean that you have paid the Proxmox team for a subscription (which is worthwhile to do) hence you should have enabled the "enterprise" repo. You will need one of the two repos...

Replying but not trying to pretend to be an expert. The fix was released with pmg-api version 8.0.4 in July already and regardless what repositories you use (production or test) you should have a newer version installed if you have updated your system as it looks like. Find out what version is...

Sorry, I found that I had something wrong in my freshclam.conf. Confused myself in the process of updating the template file :( Now fixed and all is working as it was before. Very sorry for the noise here and taking your time. Michael

Yes, VM has been rebooted a few times and error message still persists after reboots. Journalctl as below looks good - but is reported there only once after VM restart (should show hourly download attempts): Jul 04 05:25:42 mailgate systemd[1]: Started clamav-freshclam.service - ClamAV virus...

Thanks for the fix! All working here.

Looking good now: 2023-07-04T05:36:28.985883+12:00 mailgate pmg-smtp-filter[811]: starting database maintenance 2023-07-04T05:36:29.005034+12:00 mailgate pmg-smtp-filter[811]: end database maintenance (19 ms) Thank you.

Others (me included) reported this issue in a different ticket ("After succesfully upgrade to v8 error on pmg-smtp-filter") related to the PMG 8.0 upgrade but you are right, our logs show that this issue must have started with the 7.3-6 upgrade, not as part of the 8.0 upgrade (which we did 2...

After upgrading from 7.3-6 to 8.0.3, freshclam seems to behave differently. On the command line (via ssh access as user root), running "freshclam -v" shows the below - which is the same when trying this in the GUI (Virus detector/Clamav/Update Now) /var/log/clamav/freshclam.log is locked by...

We notice the same here after an in-place-upgrade from 7.3-6

Thank you to all involved with this thread and the research work. We have seen freezes on three systems in recent days (on PVE 7.2) which were all rock solid before. We have now applied the combination of settings that RolandK suggests (virtio-scsi-single & iothread & aio=threads) and hope for...

Ah, quick follow up with success as it looks like. I changed as discussed and regenerated yesterday's report on the commandline with "pmgqm send -receiver michael@xx.yy.nz -timespan yesterday" and the email now included the tokens for easy follow of these links and a frsh access to the panel...

Thanks for asking. It always was set to LDAP and worked before with previous versions. I have just compared with another mailgate ver 6.x instance that we control and it is set to LDAP there as well. The options there that I can see are either - "Ticket" - "LDAP" - "LDAP or Ticket". LDAP now...