Search results

Thanks @iay -- I had an iSCSI target on a device that is no longer being used by Proxmox -- it was getting the --login failed message and making pvestatd take too long. Fixing the problem immediately fixed my graphs :)

I suspect a bug as well. I tried upgrading another node to 8.1.3 yesterday and the graphs stopped working as soon as I rebooted the node.

I'm seeing the same thing(s) as Eschin Any suggestions?

Not that I know of. I believe that all of the packages I've installed are on multiple nodes and this is the only node with this problem.

% sudo -u nobody proxmox-mail-forward <<EOF Subject: Test This is a test. EOF sudo: unable to execute /usr/bin/proxmox-mail-forward: Permission denied -rwsr-xr-x 1 root root 981448 May 26 10:01 /usr/bin/proxmox-mail-forward drwxr-xr-x 2 root root 36864 Oct 2 08:12 /usr/bin drwxr-xr-x 12...

Lukas, % proxmox-mail-forward <<EOF Subject: Test This is a test. EOF % Worked fine :) 2023-09-29T08:30:03.109907-04:00 pie postfix/cleanup[726202]: 186BDC03B2: message-id=<20230929123003.186BDC03B2@pie.zzz.com> 2023-09-29T08:30:03.111001-04:00 pie postfix/qmgr[865712]: 186BDC03B2...

% /usr/bin/python3 test.py SyntaxError: Non-UTF-8 code starting with '\x95' in file /usr/bin/proxmox-mail-forward on line 1, but no encoding declared; see https://peps.python.org/pep-0263/ for details

No, I also diffed them against a working node and the only difference was myhostname

Thanks Lukas! No, the sendmail doesn't work. Here is what I see in the log: 2023-09-26T09:31:23.256306-04:00 pie postfix/pickup[3578568]: 3E73DC15CC: uid=0 from=<root> 2023-09-26T09:31:23.264266-04:00 pie postfix/cleanup[3926841]: 3E73DC15CC: message-id=<20230926133123.3E73DC15CC@pie.zzz.com>...

I rebooted to be running the latest kernel % stat /usr/bin/proxmox-mail-forward File: /usr/bin/proxmox-mail-forward Size: 981448 Blocks: 1920 IO Block: 4096 regular file Device: 253,1 Inode: 2362910 Links: 1 Access: (4755/-rwsr-xr-x) Uid: ( 0/ root) Gid: (...

Here is the output from those two commands. Let me know if you need anything else. Thanks! % stat /usr/bin/proxmox-mail-forward File: /usr/bin/proxmox-mail-forward Size: 981448 Blocks: 1920 IO Block: 4096 regular file Device: 0,26 Inode: 27840635 Links: 1 Access...

I have a few proxmox nodes and only one of them is getting this error: (temporary failure. Command output: local: fatal: execvp /usr/bin/proxmox-mail-forward: Permission denied) It only seems to happen with Replication Job emails I can send emails from the command line and it works fine. I have...

Thanks - I'll keep an eye on the memory (I checked this morning and there are no ECC/memory errors in the system logs or the HP-ILO logs).

I just looped on a list of .bad.0 files using this code..... x=$(basename $f | sed -e s/.0.bad//) ; cp -v $f /tmp/$x ; proxmox-backup-debug inspect chunk /tmp/$x --decode /tmp/decoded this should have checked the CRC, correct?

Dominic, Thanks for that. I had clearly misunderstood and thought that inspect file would check the CRC. I just tried the inspect chunk on 20 "bad" chunks and they look "OK" to me.... Am I missing something? If not, any idea how/why they were marked as bad? Thanks again, Jeff...

They have re-appeared...I don't see any disk errors...(output is ls -l and proxmox-backup-debug inspect file) -rw-r--r-- 1 backup backup 980131 Jun 10 13:58 /rpool/ROOT/backups/.chunks/3060/30600d38ebd67a0ae7a24d155795a328de0d391051ee8f4336f80501ca02fac4.0.bad size: 980131 encryption: none...

I haven't had any bad chunks in the last 2 days. I'll post the error(s) when they re-appear.

Hi, If I look for chunks that are named "*.bad" and then run "proxmox-backup-debug inspect file" on the ".bad" files, I will get a zero exit status and size and encryption status on almost all of them and only occasionally will I get a "real" error. Are these chunks really bad? If so, why are...

Dominik, Did you ever find a solution? I'm having the same problem. Thanks

A As far as I can tell that hasn't happened. Should I be able to see this in the logs?