Search results

I posted a response on the other thread.

This might be the reason then, but it's hard to know without seeing the settings of ufw. sudo ufw status verbose If it's a matter of the ports are open but only to localhost, for example, then changing the ufw settings will probably fix it.

I found a better fio version which worked, this first one is Windows 10 normal mode. I am not sure what test would be most relevant but fio-rand-RW seemed like it might be:

Yeah, good point. I restarted in Safe Mode, ran the same test and the results are: It's been maybe 6 years since I last used fio but I did a fresh install of it and could not get it to output anything - not sure why. I even tried a job file, and didn't see any errors. When inspecting the...

Can you clarify what you mean by "If I boot without OS, the server remains active for a long time."

I have a TeamGroup 1TB nvme that is advertised to do 1800/1500 read/write MB/s. It is a PCIE3.0 4x drive, using a M.2 to PCIE adapter with backwards compatibility to 2.0. The motherboard only has PCIE2.0 slots (a 16x and 4x). The reduction in speed is seen noted in dmesg where 0000:00:15.0 is...

I know this thread is a bit old, but I was looking for a resize solution and found something that works for me and thought I would post it here. From https://unix.stackexchange.com/questions/16578/resizable-serial-console-window/19265#19265 The function res() which is noted can check the size...

Thanks @Neobin - for whatever reason the search of "wiki edit" only shows posts from 2012 and earlier.

I was just about to start a new VM for the latest freebsd. The wiki seems outdated. I acquired a wikimedia account, but it doesn't link with the Proxmox wiki. I would offer a proposed update if I were allowed to be a wiki User.

That was it. There was a ipv6 address and gateway in the networks settings. The file date was from back in May - it's strange I haven't seen the error before now. Very helpful hint, thank you! It's showing an active subscription now with prompt response. I really appreciate the support. Thanks...

I'm sorry I am not aware of any other changes. There is a firewall in front of it, yes. No changes have been made. It is not showing any other troubles accessing the internet. A curl POST call also immediately returns an invalid status response. Interestingly, I see firewall activity if I run...

Yes, same result and there is a delay before it displays. And if I curl it I get <status>Invalid</status> right away. root@pve:~# curl https://shop.proxmox.com/modules/servers/licensing/verify.php <status>Invalid</status>

Sorry about the confusion. I had found this thread and poorly referenced it https://forum.proxmox.com/threads/no-valid-subscription.115738/ I see the error message right after I log in. Then, when I go to the Subscription page for the node I see the Status is showing as invalid: subscription...

Is this error expected for non-PMG users? I just got it for the first time, and I saw that there was a PMG related issue, but I am not a PMG user. It appears there is a timeout occurring so the information is old. Can you explain what the check process is so I can check into further...

Files looked alright, but memtest86 test 7 turned up a bad address on one of the cards. I'll be swapping that one out for a spare. Thanks for your help.

@fabian Yes, happy to. root@pve:~# pveversion -v proxmox-ve: 7.2-1 (running kernel: 5.15.35-1-pve) pve-manager: 7.2-4 (running version: 7.2-4/ca9d43cc) pve-kernel-5.15: 7.2-3 pve-kernel-helper: 7.2-3 pve-kernel-5.13: 7.1-9 pve-kernel-5.15.35-1-pve: 5.15.35-3 pve-kernel-5.15.30-2-pve: 5.15.30-3...

No, but AMD - an old FX-8350.

This is the visible difference. service pvestatd status showed the service failed. I restarted it, and it is working okay again.

Had this show up in logwatch: WARNING: Segmentation Faults in these executables pvestatd : 1 Time(s) 1 Time(s): Code: 76 01 00 00 48 8b 52 10 49 89 f7 89 cd 48 8d 04 c2 4c 8b 28 48 89 44 24 20 4d 85 ed 0f 84 94 00 00 00 4c 89 eb 0f 1f 44 00 00 <48> 8b 43 08 39 28 75 78 48 63 48 04 4c 39...

It's the remote content of the update that is failing. The failing portion is not currently in the working files. There is a fix in the works so when the error goes away it will mean the update is successful with the fix.