Search results

No idea. While updating to Bullseye perhaps? freshclam updated the database and finished with WARNING: Clamd was NOT notified: Can't connect to clamd through /var/run/clamav/clamd.ctl: No such file or directory I was then able to start the daemon. After a reboot it was still ok.

systemctl status clamav-daemon (snip) Condition: start condition failed at Fri 2021-07-16 12:52:56 CEST; 4min 39s ago └─ ConditionPathExistsGlob=/var/lib/clamav/main.{c[vl]d,inc} was not met mygateway:~# ll /var/lib/clamav total 55M -rw-r--r-- 1 clamav clamav 55M 2021-07-15 17:15...

The admin guide could be a little bit more verbose than just "Use SMTP HELO tests." (for all the options) ;-) The general information here applies to "SMTP HELO checks"? https://tldp.org/HOWTO/Spam-Filtering-for-MX/smtpchecks.html And I found this for Postfix. Same as "SMTP HELO checks"...

I noticed this in the logs (journalctl -p 4) after having updated PMG: Jul 15 17:10:31 mygateway freshclam[307]: Can't save PID to file /var/run/clamav/freshclam.pid: No such file or directory Jul 15 17:10:31 mygateway systemd[1]: clamav-freshclam.service: Failed with result 'exit-code'...

After some more reading I learnt that it would be a bad idea to put an Exchange server into the DMZ (as it needs a connection to the DC (amongst others)). So, will have to find out how to proxy Active Sync. Anyone using this?

Hello, we are currently running a local Exchange installation. Mail is fetched via Popcon (so there is an annoying delay when receiving mails). Active Sync is possible through Port Forwarding on our firewall to the Exchange host (access is restricted to our VPN and some IP ranges of carriers...

Thanks. https://bugzilla.proxmox.com/show_bug.cgi?id=3388

I have switched the user "user-vm03" for a sync job to some other user and deleted the user afterwards. Though, it still shows up in some files: # grep user-vm /etc/proxmox-backup/* acl.cfg:acl:1:/datastore/sync_datastore:user-vm03@pbs:DatastoreBackup shadow.json: "user-vm03"...

- Save the new name for new backups of that VM (so this would be store per backup and not per VM id) - same as above - agreed =) - Because this would have to be done manually although it could be automated

Oh =) Don't know why, but it seemed like this wouldn't be possible. Also, I didn't find it mentioned in the help.

"Datastore > Content" shows only the VM numbers, e.g. "vm/107". Would be handy to see the same VM name (e.g. "myserver") as configured in PVE. Lars

Hello, we have two internal PBS and one external one. The external is using remote sync to pull backups from the first local installation. Now, I wanted to add the (new) second one, but noticed that I cannot specify a port. This is needed so I can configure our firewall to forward different...

ok, thx!

Did you try reinstalling grub from the rescue system (with your device mounted)? Something like grub-install --root-directory=/mnt/sdb2 /dev/sdb2 Doing a backup before couldn't hurt.

Hello, I have seen some articles that recommend to configure the swappiness to 10 or even 0: https://blog.lbdg.me/proxmox-best-performance-disable-swappiness/ https://4noobs.de/viewtopic.php?t=116 Is there a general recommendation what value to use? I am using a mix of Linux containers and...

Thanks! Reported as https://bugzilla.proxmox.com/show_bug.cgi?id=3336

I had seen that the old backups were connected to the old user and have deleted them. There are no entries in the content tab anymore. I looked around a little bit more and noticed that the name is stored in "sync_datastore/vm/107/owner". Changed it there and the sync is starting again =)...

Hello, I have tested a sync from our local server to our external server (both running PBS 1.0-8) using "user1@pbs" (the sync destination). This worked as expected. As I now started to use this more regularly, I have "beautified" user names to "user-vm03@pbs", but the sync started to fail...

Thanks a lot! Command to be used (example) would be: lvcreate -n thin1 -V 1M --thinpool data pve

Regarding the output of lvs above: Do I have to resize "data" to make space for another LV or can I create a LV inside "data" (as it seems to be the case for "backup")?